01
The same question, four times
Pricing edge cases. Why that client left. What we actually promised in the SOW. Someone knew, typed it into a DM eleven months ago, and that answer is now functionally gone.
White Coda builds it for you
We build your company brain.
Your company already knows. It just has nowhere to remember.
The answer to almost every question your team asks has already been written down. It is in a thread from March, in a proposal nobody reopened, in the call where you decided not to do the thing and never recorded why. We spend thirty days pulling all of it into one place your people and your agents can both ask questions of.
$4,997 paid once. Thirty days from kickoff to handover, and you own every piece of it.
- Google DriveProposals, SOWs and decks pulled in
- SlackThreads synced on a schedule
- Call recordingsTranscribed and tagged by client
- CRMDeals and notes linked to the calls
- Deck, nine versionsMerged into the one that counts
- PermissionsMapped to your org chart
Why did we change the refund window?
Found the reasoning in two places. Here it is, with both sources attached.
Pricing thread, MarchOps call notes
Illustration. Yours runs on your sources and answers your questions.
Sound familiar
Somebody already answered every one of these. Good luck finding where.
Why did that client leave?What did we actually promise in the SOW?Why did we change the refund window?Which angle worked in March?What discount is this deal allowed?
Who decided not to do the thing, and why?How do we really run a project?What did sales promise this customer?Has anyone fixed this ticket before?Where is the latest version of the deck?
Why this hurts
Forgetting is expensive, and it never shows up on a line item.
02
Decisions with the reasoning stripped off
You changed the refund window for a good reason. Nobody can find the reason, so the same argument gets relitigated every quarter by people who were not in the room.
03
AI that knows everything except you
A general model writes general things, because nothing your company has ever produced is in the room with it. Your own context is what makes the output good, and most teams never load it.
The idea
A company brain is one place that holds what you know, and will answer for it.
It sits on top of the wiki nobody updates and the folder of PDFs. One layer ingests what you already produce, tracks where each claim came from, respects who is allowed to see what, and hands the same grounded answer to a person in Slack or an agent running a workflow at 3am.
DocumentsSOWs, decks, contracts, specs
ConversationsSlack, email, support threads
CallsSales and client transcripts
SystemsCRM, billing, ticketing
One brain, sourced and permissioned
Your teamAsks in plain language, gets an answer with a citation
Your agentsQuery it before acting, so the output is yours
New hiresOnboard against real history, not folklore
YouAsk what the company decided, and why
How we build it
Five layers. We build all of them, in this order.
Most knowledge projects die because someone starts at the chat box. We start at the bottom, because a search box over unstructured mush just gives you confident nonsense faster. The scope and the price are agreed up front, and something is working by the end of the first week.
Day30of 30
Running without us
05GovernRole scoping, audit log, revocation
04ActAPI, MCP endpoint, agent grounding
03RecallSemantic and keyword search, citations
02StructureChunking, metadata, dedup, provenance
01IngestConnectors, scheduled sync, transcription
Fed by Drive, Notion, Slack, email, your CRM and call recordings
-
Week 01, days 1 to 7
Inventory
We map where your knowledge actually lives, including the parts nobody admits to. You get a written inventory and we agree what is in scope and what is deliberately left out.
-
Week 02, days 8 to 14
Ingest and structure
Connectors go live, the back catalogue gets pulled in, transcribed and structured. By the end of the week you can ask it real questions and get sourced answers back.
01 IngestWe connect the places your knowledge actually lives and pull it in on a schedule. Drive, Notion, Slack, email, your CRM, call recordings, the shared folder with the terrifying name. Nothing gets retyped.
02 StructureRaw text is not knowledge. We chunk it properly, attach metadata, deduplicate the nine versions of the same deck, and keep a pointer back to the source so every answer can show its work.
-
Week 03, days 15 to 21
Permissions and grounding
Access rules mirror your org chart. Your agents and workflows get wired to query the brain before they produce anything. We tune retrieval against questions your team really asks.
03 RecallHybrid retrieval, so an exact contract clause and a fuzzy "what did we tell them about onboarding" both land. Answers come back with citations, and when the brain does not know, it says so instead of inventing.
04 ActThe brain becomes an endpoint. Your agents and workflows query it before they write, so proposals, replies and briefs come out sounding like your company instead of like a language model.
05 GovernPermissions that mirror your org, so the brain never answers a question the asker was not entitled to ask. Every query is logged, every source can be revoked, and nothing leaves your tenancy.
-
Week 04, days 22 to 30
Handover
Sync runs on schedule without us. Your team is trained, the admin surface is documented, and you own every piece of it. We stay on for two weeks of support after handover.
What it covers
One brain, six places it changes your week.
Hover or tap any region. It is the same brain, asked a different question, and none of it is a separate tool you have to buy, log into or keep in sync.
MarketingMarketingEvery campaign you have ever run, what it cost and what it returned. The brain writes the next one already knowing which angle worked in March.SalesSalesCall transcripts, objections, the pricing exceptions you actually approved. New reps answer like someone who has been here three years.DeliveryDeliveryScopes, SOWs, the way you really run a project. Briefs come out in your method instead of a generic best practice.SupportSupportEvery ticket and its resolution, deduplicated. The answer a customer gets is the one your best person would have given.FinanceFinanceQuotes, invoices, margins and the reasoning behind discounts. Nobody has to wonder what a deal is allowed to look like.OperationsOperationsProcesses, policies, onboarding and the decisions nobody wrote down. Institutional memory that survives people leaving.Six areas, one memoryHover or tap a region to see what the brain knows there. The connections matter most, like a support answer that knows what sales promised, or a proposal that knows what delivery can actually staff.
What you walk away with
You own the brain outright, down to the keys.
Deliverables
- A running company brain on your own infrastructure and your own keys
- Live connectors to your sources, syncing on a schedule, no manual re-uploads
- A query surface for people, and an API plus MCP endpoint for your agents
- Permission rules mapped to your org, with a full audit log of every query
- A written knowledge inventory, often the most useful artefact of the month
- Admin documentation and a trained team, so nothing depends on us
- Two weeks of support after handover
This is for you if
- You have more than about fifteen people and knowledge is already scattered
- You are putting agents into real work and they keep producing generic output
- Onboarding someone takes months because the context lives in people
- You can name two systems your knowledge lives in right now
It is not for you if
- You want a chatbot on your website
- You are pre-product and have nothing written down yet
- You need someone else to decide what your company knows
The offer
We Build Your Company Brain
One engagement that covers everything on this page, done in thirty days. There is no retainer afterwards and nobody pays per seat.
$4,997
One time. Fixed scope, billed once before week one starts.
Start the buildIf the brain cannot answer questions your team actually asks by the end of week two, we keep working at no extra cost until it can.
Knowledge inventory and scope mapWeek 1
Source connectors, built and syncingWeek 2
Structuring, dedup and provenanceWeek 2
Retrieval tuned on your real questionsWeek 3
Permissions mapped to your org, full audit logWeek 3
API and MCP endpoint for your agentsWeek 3
Team training and admin documentationWeek 4
Two weeks of support after handoverIncluded
Want the slot before you commit the full amount? Pay a $500 deposit. It holds a build slot, pays for the scoping call and comes off the $4,997. If we decide on that call that we are not the right fit, you get it back.
Reserve with a $500 depositQuestions
The ones people actually ask.
Where does our data live?
On your infrastructure, under your keys. We build inside your tenancy, not ours. If you end the relationship the brain keeps running and we lose access, not you.
What if our documentation is a mess?
That is the normal starting condition, and it is the reason week one is an inventory rather than a build. We work with what exists. If something genuinely is not written down anywhere, we tell you that in writing instead of quietly guessing.
Does this replace Notion, Drive or our wiki?
No. It sits over them. Your team keeps working where they already work, and the brain reads from those places on a schedule. Nobody has to move or retype anything.
How is this different from pointing ChatGPT at a folder?
It comes down to permissions, provenance and refusal. A folder upload will happily answer a question the asker should not be able to ask, will not tell you which document an answer came from, and will invent something when it does not know. Getting those three right is most of the work.
What do you need from us?
Admin access to the sources we agree on, one person who can answer questions about how the company works, and about two hours a week. We do the rest.
What happens after the thirty days?
You own it and it runs on its own. Two weeks of support are included. If you want us to keep extending it, that is a separate conversation with separate pricing, and it is genuinely optional.
Can we start with a deposit instead of the full $4,997?
Yes. The $500 deposit holds your slot and pays for the scoping call. It comes off the $4,997, and we contact you within one business day to confirm scheduling and the remaining balance. If we are not the right fit, it is refunded in full.
Thirty days from now
Give it somewhere to remember.
$4,997 one time, or hold your slot today for $500.
