When I describe the Knowledge Pack to founders, the first image most of them form is a very well-organized Google Drive. Maybe a detailed operations manual. A collection of SOPs in a tidy folder structure.
That is not what it is. The Knowledge Pack is not a documentation project. It is a structured knowledge system — the founder's operating knowledge encoded in a form that AI can actually use and that business systems can actually run on. The difference matters.
What knowledge lives in a founder's head
A founder who has been running a service business for three or more years has an enormous amount of operational intelligence that has never been externalized. She knows how to identify a good-fit client before the intake questionnaire comes back. She knows which types of projects tend to run long and what the early warning signs look like. She knows what level of communication keeps a particular type of client calm, and what crosses the line into hand-holding. She knows the decision logic behind every step of her delivery process.
None of that lives anywhere except her. The CRM might have contact records. The project tool might have timelines. But the judgment behind the work — the rules and patterns she runs on — that is hers, in her head, applied fresh every time she needs it.
The Knowledge Pack is the process of making that knowledge explicit, structured, and retrievable — in a form that is not just readable by a human, but usable by a system.
What AI-ready actually means
For knowledge to be useful to an AI, it needs to be structured in a specific way. Not a wall of text. Not a collection of loosely organized notes. A structured knowledge system has clear taxonomy, consistent formatting, and a retrieval architecture that allows the right information to surface when it is needed for a specific task.
This is what the Knowledge Pack produces. When the build phase comes — if a Custom Build follows the Knowledge Pack — the system that gets built has a structured knowledge layer to work with. The AI inside the system is not starting from scratch on every execution. It has the founder's operating logic encoded in a form it can retrieve and apply.
“You cannot build a system that runs on your judgment until your judgment has been made explicit enough to encode.”
What the Diagnosis determines
The Diagnosis is embedded inside every Knowledge Pack engagement and runs first. Its role is to determine exactly what needs to be structured — which areas of the founder's knowledge are most critical to encode, which workflows those knowledge areas support, and what form the output needs to take to be useful in the eventual system.
This is why the Knowledge Pack is not a standard deliverable with a fixed scope. The content of the pack is determined by what the founder's business actually requires — not by a template, and not by what is easiest to document.
Who the Knowledge Pack is for
The Knowledge Pack is the recommended path when the Audit Review Call shows that the primary problem is organizational knowledge — when the workflow is not yet structured enough to build on, or when the founder's operating logic has never been externalized in a way that could support a system.
Founders who complete the Knowledge Pack and move to a Custom Build receive a 30% continuation discount on the build. This exists because the Knowledge Pack is not just a standalone product — it is the foundation the build works from. Having it done first makes the build faster to scope and more precise to execute.
Whether the Knowledge Pack is the right starting point for a specific founder is determined by the Audit. The Audit is free, and it is always where the process begins.