Map where your answers live.Before you build the system.
A paid knowledge audit that surfaces where decisions actually get made, which docs are lying to your team, and what walks out the door when a key person quits. The map is the deliverable — the build proposal comes off the back of it, priced against a real backlog instead of a guess.
Everyone else sells the build first. That's backwards.
Six-figure Notion migrations. Nine-month wiki rebuilds. Consulting engagements that quote the tool before anyone has agreed on what the problem is. The pattern fails the same way every time — the build ships against an imagined organization, not the real one.
The audit fixes that. It's easier to sell (small commitment), faster to deliver (weeks not quarters), and it does the qualifying for you: by the end, you either see a build worth paying for or you don't. Either way, you have a map you didn't have before.
The knowledge that lives everywhere and nowhere.
- ▲Where decisions get made and never written down.
- ▲The same answer typed out by three different people, five different ways.
- ▲The doc that has been wrong for a year and everyone still sends it.
- ▲The thing only one person knows — and what happens when they quit.
- ▲The folder nobody can find. The Slack thread with the answer, three years deep.
Four businesses. Four different maps.
Same audit framework, tuned to what your business actually needs to map. The output artifact is different per industry — because the knowledge that matters is different.
Agencies
Delivery knowledge lives in Slack threads and one account manager's head.
What history exists per client. What walks out the door when someone quits. Which accounts have zero documentation.
Local service businesses
Quotes, FAQs, and technician workarounds live in text messages.
Every question a customer asks and where the current answer sits. Which answers are inconsistent depending on who picked up the phone.
Insurance & financial practices
Client history is split across email and a CRM nobody trusts.
For every category of client data — which system wins when two of them disagree, and where you're one audit away from a problem.
Ecommerce brands
Product knowledge sits in reviews, support tickets, and a supplier email chain.
The exact words buyers use about the product, pulled from reviews and support. What the site should say vs. what buyers actually type.
Interview. Inventory. Map. Build the right thing.
Interviews
Week 1. 4–8 people across your org — the ones who answer the most questions, and the ones who ask them. Structured conversations that surface where answers really live.
Systems inventory
Week 2. Slack, Google Drive, Notion, CRM, email, wikis, shared drives. What's there, what's used, what contradicts, what's dead.
Synthesis + report
Week 3. Knowledge Map, Gap List, Conflict List, and prioritized Build Backlog delivered as a written report. Working session to walk through it and pressure-test the build recommendation.
Build (optional)
If the report shows a build worth doing, we quote it off the backlog. Typical range: $3,500 to $25,000 depending on scope. AI-agent–ready by default so the knowledge you build becomes queryable leverage, not another wiki.
Retainer (optional)
Monthly maintenance keeps the map current as the business changes. New hires interviewed, new systems added, dead docs pruned. Starts at $500/month.
What buyers ask. Answered plainly.
What is a knowledge audit, exactly?
A structured discovery of where your business's answers actually live — Slack threads, email chains, one person's head, the doc everyone still sends that has been wrong for a year. You get a written map: what exists, what's missing, what contradicts itself, and what walks out the door when a key person quits. The map is the deliverable. The build proposal comes off the back of it.
Why not just start with the build?
Because the build is the wrong first step. Every business we've talked to thinks they know where their knowledge lives, and every audit finds three surprises. Auditing first means the build we scope is real, the price is defensible, and you already know whether it's worth doing. Starting with the build is how six-figure Notion migrations get half-shipped and abandoned.
How long does the audit take?
Two to three weeks. Week one is interviews with 4–8 people across the org — the ones who answer the most questions and the ones who ask the most. Week two is document/system inventory (Slack, Google Drive, Notion, CRM, email, wikis). Week three is synthesis and the written report. You get a working session at the end to walk through it and pressure-test the build recommendation.
What does the report contain?
Four things. (1) A Knowledge Map naming the source-of-truth system for each category of answer (client history, pricing, technical decisions, policies). (2) A Gap List — questions that get asked regularly and have no written answer. (3) A Conflict List — where two systems contradict and which one wins. (4) A prioritized Build Backlog with estimated impact and effort per item. Twenty to forty pages, depending on your business size.
What comes after the audit?
If the report shows a clear build worth doing, we quote it (typically $3,500+ depending on scope). That build usually means: consolidating the map's high-impact answers into one queryable system, wiring the source-of-truth systems together, and setting up the workflow that keeps it current. If the report shows you don't need a build — or need less than you thought — we tell you that, and you keep the map.
Do I need to be technical to work with you?
No. The interviews are conversations, not technical reviews. The build itself is technical — that's what you're hiring for — but the audit meets you where you already work. Slack, Google Drive, whatever your team uses; we bring the framework.
How is this different from a standard knowledge-management consultant?
Two things. First, we build the system, not just recommend one — the audit is the qualifier for that build, not a standalone deliverable. Second, we design for AI-agent use from day one: the knowledge that comes out of this is queryable by the RAG assistants, agent workflows, and MCP servers your team is starting to run. That's what turns a knowledge base into leverage instead of overhead.
What if we already have a Notion / Confluence / wiki?
Most audits find that the wiki is one of the systems, not the system. The map surfaces which answers actually live there vs. which live somewhere else that people default to instead. The build usually keeps your wiki — it just gets wired properly and cleaned of the pages that mislead more than they help.
Ready to see where your answers actually live?
Start with a 30-minute call. If the knowledge audit fits, we'll scope it on the spot. If it doesn't, you'll leave with a clearer read on where your team's real knowledge risk sits — either way, worth the time.