The knowledge layer of a Business Operating System – Part 6/6

How many decisions in your business are made by people coming to you for the answer?

Not the big strategic decisions that should come to you. The small, operational ones. How does the onboarding work? What template do we use for this? What does the client do when they hit this stage? Where do we log this information? Who’s the contact for this tool?

If the answer to any of those is “ask me” or “it’s in my head”, that’s a Knowledge layer problem. And it costs more than you think.

I’m Chris Wray. This is the final layer of the Business OS: Knowledge.

What “the business that knows itself” actually means

A business that knows itself has the answer to most operational questions in a place that isn’t someone’s memory.

How things get done is written down and findable. Decisions made with clients are recorded. Tools are documented. Automations are explained. Business reviews have templates. New team members can get up to speed without weeks of verbal handover.

None of that happens automatically. It requires a deliberate decision to treat knowledge as a business asset, something worth capturing and maintaining, rather than something that lives in the heads of whoever happens to know it.

What the Knowledge layer includes

SOPs and process guides: step-by-step documentation of how repeating tasks get done. How to onboard a new client. How to run a project kick-off. How to close an engagement. How to handle a scope change. Written clearly enough that someone following the guide for the first time gets a good result.

Client decision records: the key decisions made during a client engagement. What was agreed, when, and why. So when a question comes up six months later, you don’t have to reconstruct it from email threads.

Tool configuration notes: how your tools are set up and why. Pipedrive stages, Notion structures, Make.com automation logic. If someone needs to troubleshoot something, or if a tool changes, the configuration is documented rather than mysterious.

Automation documentation: what the automations do, what triggers them, what they produce. So when an automation breaks (and occasionally they do), someone can diagnose it without it being a crisis.

Business review templates: the structured formats for monthly and quarterly business reviews. So reviews happen consistently, cover the right ground, and produce a comparable record over time.

Why most documentation projects fail

The documentation drive. Someone decides the business needs documentation, a shared folder gets created, a few documents get written, and within three months nobody’s using it.

Why? Because documentation nobody can find is the same as no documentation. And documentation that’s out of date is worse than no documentation. It gives people the wrong answer with confidence.

A working Knowledge layer has to be structured so things are findable, maintained so it stays current, and adopted so people actually use it as a first resource rather than coming to you.

The tool matters less than the discipline. But Notion is where I build virtually all client knowledge bases, because it’s structured enough to be navigable and flexible enough to handle any kind of content.

Where to start

Don’t try to document everything at once. Pick the three processes that generate the most questions or the most variation in quality. Write those first. Then use a simple rule: if you answer the same question twice, write the answer down the second time.

The knowledge base grows naturally from there, driven by real questions rather than a one-off documentation effort that runs out of steam.

Putting the whole system together

This is the final layer. If you’ve watched all six videos, you now have a complete picture of what a Business OS looks like.

Layer One, Pipeline: from stranger to signed client. Built in Pipedrive.

Layer Two, Delivery: consistent client experience, every time. Built in Notion.

Layer Three, Reporting: visibility without manual effort. Built in Notion, automated through Make.com.

Layer Four, Finance: numbers that run themselves. Built in Make.com and Notion.

Layer Five, Knowledge: the business that knows itself. Built in Notion.

And the Make.com Automation Layer connecting all five. information flows between layers automatically, without anyone having to manually move it.

Three tools. Five layers. One system.

If you want to know where to start with your own Business OS, download the free Business Automation Audit. It asks the right questions across all five layers and gives you a clear picture of where your biggest gaps are. Link’s in the description.

And if you want someone to build this for you, that’s exactly what I do. Book a free call and we’ll look at your business together.