The Scenario
Your company has grown from twelve people to forty in two years. The early team carried the entire operational knowledge of the business in their heads. How the booking process actually works. Why the second-step discount on commercial accounts is what it is. The specific way you handle the supplier that has been with you since the founding. The unwritten rules of when to escalate and to whom.
That worked at twelve. At forty, with a third of the team having joined in the last six months, it does not. New starters ask the same question of three different people and get three different answers. The senior team spends a measurable part of every day fielding questions that should have an authoritative answer somewhere outside their head.
The Problem
The specific frustration is the moment a new starter, three weeks in, asks the founder a question that they have already asked the operations manager and the lead in their own team. Each of the three answered slightly differently. The new starter has to triangulate which version is right, often by guessing or by going with whoever sounded most confident. They are starting to learn that “ask whoever picks up” is the operating model. Six months later they are answering similar questions for the next intake the same way.
The cost is two-fold. Senior time leaks into question-answering. A founder spending fifteen minutes a day on Slack DMs answering “quick questions” loses an hour and a quarter a week — and the time is taken out of the deep work the founder is uniquely positioned to do. The deeper cost is institutional drift. Every time a question is answered orally, the answer can shift slightly. By year three, three subtly different versions of the same process are being followed by three subgroups within the company, and nobody quite knows which is the version that was originally agreed.
The Approach
An internal knowledge base built around how the business actually operates — not a generic wiki that nobody maintains. The structure follows the business: how we handle X, what to do when Y, the rules around Z. Each article has an owner, a last-reviewed date, and a clear scope. Articles are short, written in plain language, and updated when the underlying process changes rather than being treated as fixed documentation.
The knowledge base is built on an internal portal system and integrated with the tools people already use — Slack, email, the CRM — so the question “how do we handle commercial discount approvals” gets answered by surfacing the relevant article inline rather than requiring a context switch. An AI search layer trained on your own content lets people ask the question in natural language and get a direct answer with the source article linked. Where appropriate, the knowledge base also captures decision records — why the second-step discount is what it is — so future colleagues understand not just what the rule is but why.
The Outcome
The “ask three people” pattern stops. New starters get an authoritative answer the first time, from a source that does not depend on which colleague happened to be online. The senior team’s day stops being interrupted by quick questions because the quick questions have been pre-answered by the system. The founder reclaims the hour and a quarter a week and uses it on the work only the founder can do.
Institutional drift slows because there is now a canonical version of every operational decision. When the process changes, the article is updated and the change is visible to everyone. The cost of bringing on the next ten people drops materially — not because onboarding gets faster on paper, but because new starters spend their first month learning the business rather than triangulating between competing oral versions of it. By the time the company is at eighty people, the institutional knowledge that used to be at risk every time someone left is stored in a way that survives the leaving.
Who This Applies To
Founders, operations leaders, and people leads at growing businesses between twenty and two hundred staff — particularly those that have grown quickly enough that the founding team can no longer carry the institutional knowledge orally. Most acute for professional services firms, agencies, B2B SaaS, and any business where operational decisions are detailed enough that “ask Sarah” is no longer scalable.
Take the Next Step
If your senior team is spending a measurable part of every day answering quick questions, the knowledge base is the layer that gives them their day back. We build internal knowledge bases that fit how your business actually operates — not generic wikis that nobody maintains. Let us walk through what yours would look like.