Sofgent Logo
Case Studies

AI knowledge platform that turned 8 years of internal docs into an answer engine

Case Study

AI knowledge platform that turned 8 years of internal docs into an answer engine

Designed and built a retrieval system on top of internal SOPs, runbooks, and Slack archives so support and operations teams could get correct answers without crawling Confluence.

Client
Operations leadership — SaaS company
Industry
AI Knowledge System
Duration
4 weeks
Product surface for an internal AI assistant with answer panel, sources, and feedback controls

Outcome

8 yrs

Of docs indexed

Confluence + Slack + Drive

63%

Faster answers

vs. legacy search

4 wks

Idea to production

92%

Answer-acceptance rate

Architecture

How the system fits together.

The Problem

Where the engagement started.

Support, customer success, and operations were all answering the same questions a hundred times a week. Confluence search was unreliable; Slack history was fragmented across years of channels.

Earlier 'just chatbot it' attempts produced confident-sounding but wrong answers, with no source visibility — so leadership pulled the plug.

Our Approach

How we cut the scope and de-risked the build.

We unified the corpus first: Confluence pages, Slack archives (curated), Drive docs, and a hand-picked set of authoritative SOPs. Each chunk carries its source URL and a freshness score.

Retrieval runs through a re-ranker tuned to operational queries; the model is forced to cite the chunks it used or it returns 'not enough context'. No source means no answer.

Every answer ships with an embedded feedback control that writes into a dataset we use to retrain the re-ranker weekly.

The Outcome

What changed after the system shipped.

Median answer time dropped from minutes (and several Slack hops) to under five seconds with a citation.

Acceptance rate sits at 92% across the three teams that adopted it; the unaccepted queries are now the dataset that drives improvements.

Two human-written runbooks were retired because the system answered better and stayed fresh.

Tech Stack

  • Next.js
  • Python
  • Postgres
  • pgvector
  • OpenAI
  • Slack API
  • Confluence API

Want a similar outcome?

Map your build before you start.

A 20-minute conversation is enough to surface scope creep, architecture risk, and the fastest path to production.