The master prompt document: why it stops scaling at three people

I want to tell you about a document. I've seen this exact document at so many companies that I can write its biography from memory, version by version. Yours may differ in the details. I doubt it differs much.

Version 1 is born on a Tuesday. Someone competent gets tired of typing the company background into every AI chat and writes it down properly. A page and a half. The team's AI output improves the same week, and the author is quietly pleased. They should be. This is the team's first real piece of AI infrastructure, and it cost an afternoon.

Version 2 adds the tone rules after a client email goes out sounding like a press release. Version 3 adds the pricing section. The document is now three pages, and here the first crack appears, invisible for now: version 2 still lives in four people's saved prompts, and nobody knows.

Version 4 is the good one. A new hire joins, reads it, and produces on-brand drafts in week one. Someone says the document should be "part of onboarding". This is the document's happiest moment.

Version 5 is where physics kicks in. The document is five pages. Pasting five pages before asking a two-line question feels absurd, so people start making judgment calls about when the context is "really needed". The busy people, meaning the senior people, meaning the ones whose output matters most, skip it first.

Version 6 is the fork. Someone makes "AI context SHORT" for quick tasks. There are now two truths, then a third when the sales lead makes a private version "tuned for proposals". The original author, who has a job besides gardening this document, updates version 6 and has no way to reach the copies.

Version 7 never really ships. The pricing changed in March and the document says otherwise until someone notices in May, by way of a customer.

Why three is the number

Notice that nothing broke because anyone was careless. The document failed on structure, and the structure fails at a predictable size.

At one person, the author and the user are the same, so the copy in use is always current. At two or three, the document survives on proximity: you hear the pricing change across the room and fix your paste. Past three, the update and the usage decouple. Copies outnumber the original, delivery depends on discipline, and discipline loses to deadlines everywhere, at every company, forever.

So the master prompt isn't a mistake to be embarrassed about. It's the correct first move, and it carries a team exactly as far as shared memory and shouting distance can carry anything. Which is to say: three people.

What graduation looks like

The fix keeps everything the document got right and changes the two things it structurally can't do. The facts stay written, short and owned by someone. Delivery stops depending on pasting: the context loads into every AI session on its own. And updating stops being a broadcast problem: one change, and there are no copies to chase, because there are no copies.

That's the shape of Company Brain. Your version 6 becomes fifty reviewed facts, each editable alone, delivered automatically to Claude, ChatGPT, Copilot and Cursor through MCP. The document's author usually becomes the curator, which feels right. They were doing the job already, just against the structure instead of with it.

Their afternoon in version 1 was the best investment the team made that quarter. It deserves infrastructure that can keep the promise.