06-reference

writewithai master business context folder

2026-05-20·reference·source: Write With AI (Substack) — Dickie Bush·by Dickie Bush
agent-contextcontext-architecturebusiness-contextllm-projectsfounder-opssales-flagged

Why this is in the vault

RDCO is literally an experiment in "arming AI (Ray) with everything it needs to help run RDCO." Bush's piece prescribes a specific 8-document folder structure for exactly that problem — concrete, opinionated, and shippable in an afternoon. Even where his structure doesn't map 1:1 to our vault, the gap analysis is useful: it tells us what a $700k/month-portfolio operator thinks the minimum context surface looks like, and where our existing vault under-indexes.

The mapping is not strong-mapping the way 2026-04-15-dbt-ade-bench-data-agent-benchmark-stancil is (peer-N benchmark for the MAC thesis). It's medium-mapping: a practitioner's checklist we can grade ourselves against.

The 8 documents

Bush argues the highest-leverage AI upgrade is not better prompting or better models — it's loading 50+ pages of business context into one LLM Project so every chat inherits it. His 8 docs:

  1. Money Model Builder — what you sell, pricing, upsell/downsell/continuity paths
  2. Perfect Avatar Map — buyer profile: pains, desires, fears, beliefs, top-10 objections categorized by uncertainty/timing/spouse/money
  3. Belief Ladder — sequential 5-7 rungs from current faulty belief to the belief that makes buying obvious; plus a one-paragraph argument summary
  4. Acquisition Blueprint — every channel + end-to-end funnel (capture, conversion, bridge touchpoints with who/when)
  5. North Star Brief — mission/vision/3-5 values/5-12 operating principles
  6. Org Chart Builder — names, roles, reports-to, tenure, department
  7. Tech Stack Inventory — 40+ business functions mapped to specific tools
  8. "What Good Looks Like" Vault — best-performing examples across every content surface, plus one "perfectly nails our voice" exemplar and one "this is NOT our voice" anti-example

The project architecture

One LLM Project as home base, 8 docs loaded as files (every chat inherits context). Persistent chats: one "CEO Strategy" + one per department. Tactical one-offs spawn inside the project so they still get full context. Bonus: dashboards/financials as snapshots, existing SOPs, recent strategy docs, Slack MCP for real-time WIP. Treat all 8 as living documents — update on every pricing/hire/funnel change.

RDCO gap analysis vs Bush's 8

Self-grade against the checklist: 5 gaps, 3 solid.

Where Bush's frame doesn't apply

Portfolio-operator assumptions: employees, departments, sales motion. For RDCO at L4 (solo + Ray) the per-department-chat pattern is overkill — chats already partition by skill. Also, his "load 8 PDFs in a Project" is flat-bag-of-context. RDCO already runs a typed knowledge graph (graph-query, QMD, wikilinks). The 8-doc content checklist is orthogonal to the substrate; docs land as vault notes with frontmatter + cross-links, not PDFs.

Bias / sponsor flag

Sponsored: yes (AI Operator newsletter, paid Context Architecture Starter Kit, AI Writing Skool community PS). Body is genuinely substantive — frameworks are usable without buying anything. Trust the 8-doc skeleton, ignore the kit upsell. Bush (half of Ship 30 for 30 / WriteWithAI) is high-volume operator-content; generally substantive with a sales tail.

Decision

Action item: spawn a focused build pass on the 5 identified gaps (Money Model, Avatar Map, Belief Ladder, Acquisition Blueprint, Tech Stack Inventory, anti-example exemplar collection). Belief Ladder for Sanity Check is the highest-leverage single doc — it'd materially improve every newsletter draft and ad. Queue to Notion as discrete tasks rather than batching, so each can be picked up in an idle cycle.

Cross-references