A company wiki that fills itself — from calls, emails and team output
Your company already paid for its knowledge — it's just trapped in call recordings, email threads, meeting notes and people's heads, leaking out every time someone leaves or forgets. That leak has a price tag: hours lost searching, slow onboarding, and expertise that walks out the door. It shows up as three concrete problems — and they're the reason a wiki nobody has time to write never pays off. We show how to build one that fills itself from what your team already produces, so the knowledge stops disappearing.
The problem with classic wikis
Companies don't fail at wikis because the tool is bad. They fail because keeping it up to date is manual work nobody owns:
- the knowledge exists, but in a call recording no one re-listens to,
- a decision was made in an email thread that never made it to the wiki,
- the one page that mattered is six months out of date and quietly wrong.
So people stop trusting the wiki, stop using it, and the knowledge scatters again.
Three real problems this solves — and who has them
1. People burn one to two hours a day just hunting for information
Who has it: a 60-person logistics brokerage where the operating knowledge — carrier quirks, customs edge-cases, who-to-call — lives in email threads and phone calls.
Knowledge workers spend on average ~1.8 hours a day (around 9 hours a week) searching for and gathering information (McKinsey), and 47% of digital workers struggle to find what they need to do their job, juggling 11 different apps on average (Gartner, 2023). The answer usually exists — in a recording nobody re-listens to, a thread nobody linked — it just costs more to find than to redo.
How we solve it: the wiki fills itself from the calls, emails and tickets the team already produces, into interlinked pages with a link to the exact source — so the answer was captured automatically and people trust it instead of re-asking.
2. When an expert leaves, a chunk of "how we do it" walks out the door
Who has it: a 40-person engineering consultancy where two principals hold the deployment know-how and the "why we do it this way" for the firm's flagship methodology — and one just announced retirement.
Around 42% of institutional knowledge is unique to the individual who holds it (Panopto) — so when they leave, the team literally can't do that part of the job. Replacing the person costs 50–200% of their salary and a successor takes 6–9 months to ramp, because the docs were never written: experts are too busy being experts.
How we solve it: the wiki has been capturing the expert's calls, emails and decisions all along, with sources — so the departure becomes a review-and-approve exercise instead of a frantic archaeology dig.
3. New hires ramp slowly and the same questions get answered again and again
Who has it: a 90-person B2B software company hiring two to three reps a quarter, where top reps lose hours every week mentoring instead of selling.
A new hire can't be productive until they've absorbed processes, pricing edge-cases and customer context that live in people's heads — so they interrupt the most expensive people, repeatedly. Sales ramp alone averages five-plus months, and across support, 60–70% of incoming questions are repeats of something already answered.
How we solve it: the wiki auto-builds the onboarding corpus from real winning calls and resolved tickets, answers questions on demand with citations so people self-serve, and flags its own stale pages so the content never silently rots.
The strongest figures here are survey-based industry benchmarks (McKinsey, Gartner, Panopto). The real number for your team is what we measure in the free diagnostic.
The idea: the wiki fills itself
Search time, lost experts, slow onboarding — all three trace to one thing: keeping knowledge current is manual work nobody owns. So we remove the manual step.
Instead of asking people to write documentation, the system listens to what they already produce — calls, emails, meeting notes, ticket resolutions — and turns it into structured, interlinked wiki pages. People only review and approve.
How it works
- Capture — connect the sources you already use: call transcription, a shared mailbox, meeting notes, your ticketing tool.
- Extract & structure — AI pulls out decisions, facts, how-tos and FAQs, and links them to existing pages instead of creating duplicates.
- Draft, don't publish — it proposes a new page or an update, always with a link to the source (which call, which email).
- Human approves — someone confirms or edits in one click. Nothing goes live unreviewed.
- Stay honest — the system flags pages that contradict newer information or look out of date, instead of letting them rot.
Why AI changes the equation
Classic wikis needed a person to write every page. The reason this is newly possible is the same one we wrote about in where AI makes sense: AI can read messy, unstructured input (a rambling call, a long email chain) and turn it into something structured — and it can answer questions over it with citations, the RAG pattern.
But the value isn't "AI writes your docs". It's that the wiki stops being a chore:
| Classic wiki | Self-filling wiki |
|---|---|
| Someone has to write it | It drafts itself from real work |
| Out of date within weeks | Flags its own stale pages |
| "Where was that decided?" | Every fact links to its source |
| Knowledge leaves with people | Knowledge is captured as it happens |
Where it pays off
The biggest impact is in teams where knowledge is created in conversations, not documents: sales and customer calls, support, consulting, operations. If your important decisions live in inboxes and recordings, this is for you.
The point isn't a prettier wiki. It's that the knowledge your team already creates stops disappearing — and the wiki earns back the trust to actually get used.
The return is concrete: hours of searching handed back to the team, new hires productive in weeks instead of months, and the expert's know-how safe before they ever hand in their notice. One captured knowledge area is enough to see it.
Two neighbours turn the same raw input into something you can query: From inbox chaos to a controlled customer request loop and A private GPT for your law firm: AI that knows your precedents.
Want to see it on your own calls and emails? Get a free diagnostic — we map one team or knowledge area and show you exactly what we'd build, the impact and the cost. No obligation.