A brand without a synchronized knowledge base is twenty disconnected documents pretending to agree with each other. The 23-column prompt chain is the architectural answer — one row, twenty-three fields, a single source of truth that every downstream library reads. The chain is not how content is written. It is how content stops contradicting itself.
Why 23 Column Prompts and Not One
The intuitive shortcut is to write one mega-prompt that asks an LLM to generate the entire brand identity in one go. The mega-prompt produces a sleek-looking document and a giant blob of text that nothing downstream can use. You cannot query it. You cannot version individual fields. You cannot tell the Content library to read only the positioning section without parsing prose.
The 23-column chain solves all of that by being a database row instead of a document. Each column is one named field — Mission, Positioning, ICP Profile, Brand Voice, Tagline, Bold Claim. Each field is produced by a dedicated prompt. Each field is independently queryable, diffable, version-controllable, and consumable by exactly the downstream library that needs it.
The 23-column chain is not how content is written. It is how content stops contradicting itself.
The 23-Column Prompt Chain
The chain is shown below as 23 tiles. Each tile is one prompt. The order is load-bearing — early columns capture intake, middle columns synthesize identity, late columns produce the public-facing artifacts. Every column reads every column to its left as structured context.
Notion AI vs External AI
Eight columns are Notion AI prompts. Fifteen are external AI prompts (Claude or GPT). The decision rule is simple: if a column needs to read other Notion pages or databases as context — competitor pages, customer records, vocabulary indexes — it runs on Notion AI. If a column needs long-form generation under tight structural control — mission, positioning, manifesto — it runs on external AI.
This is the part most prompt-library projects get wrong. They commit to one engine and pay for it in either speed or output quality. The chain is hybrid because the work itself is heterogeneous; some fields are lookups, some fields are generation. Different jobs deserve different tools.
Each column is tagged with its tool — Notion or External — so the operator running the chain knows what is happening when. The tag is also the routing instruction for the orchestrator: Notion-tagged columns route to the Notion AI API; External-tagged columns route to the hosted model. The same diagram is the documentation and the execution plan.
Before / After — Manual vs the Chain
Before the library, defining brand identity was a multi-week, multi-stakeholder process that produced a deck nobody read after the first three weeks. After the library, it is a 30-minute questionnaire and a four-minute chain run.
- Manual brand definition (before). Founder writes a draft. Marketing manager redrafts. Three weeks of revisions. A 40-page deck. Six months later, no two team members can quote it consistently. The deck is forgotten; the brand drifts.
- Library run (after). Founder completes a 30-minute intake questionnaire. The 23-column chain runs in 200–230 seconds. The output is a single row of structured data — 23 named fields, all internally consistent, all queryable by downstream libraries.
- Downstream regeneration. The Content, Outreach, Sales Enablement, and Visual Asset libraries read the row and regenerate their own artifacts. The website’s About page updates. The sales script primer updates. The LinkedIn description updates. No manual sync, no copy-paste, no drift.
- Maintenance. When the brand evolves — a new positioning, a new value prop — the founder updates the relevant column and the whole downstream system regenerates. Brand evolution becomes a database update, not a six-month rebrand.
Brand Consistency Across Libraries
The reason this matters is the same reason every other library in the platform exists: consistency across surfaces is an architecture decision, not a discipline initiative. The 23-column row is the contract. Every library that consumes the row commits to reading it the same way every time. If the Content library reads positioning as “X for Y”, the Outreach library cannot reframe it as “Y for X”. The row is the source of truth and the source of truth wins.
That is what makes the platform feel like one studio. The articles, the LinkedIn posts, the cold emails, the deck, the website, the press release — they all sound like the same company because they were all generated from the same row. The salesperson, the marketer, and the founder cannot disagree with each other because none of them are writing the brand voice; the brand voice is a database field.
One row, twenty-three columns, every downstream library reading the same data. That is the whole story. The chain is not the impressive thing; the row is. The chain is just how you get the row produced in four minutes instead of four weeks.