plan_final_v3_REAL.docx. The deck says one number, the document another. Half the plan is decisions you stand behind and half is placeholder guesses — and nothing tells you which half is which.
Why this keeps happening.
A plan is not written once; it is revised under pressure — before the pitch, after the feedback, around the application deadline. File copies multiply because there is no single living document, and assumptions blur into decisions because prose gives them the same typeface. The cost lands later, when you build on a guess you had promoted to fact without noticing.
The way of working.
One plan, versioned in place
The plan is one document with full revision history. Every edit is a commit; the deck and the application are outputs generated from it, not rival sources of truth.
Decisions, assumptions, and questions are typed
Confirmed choices are recorded as decisions; guesses stay labeled assumptions; unknowns stay open questions. An Agent drafting the next revision is required to keep them distinct.
You approve, the Agent drafts
Each iteration the Agent proposes — new sections, updated numbers, restructured argument — and the document shows what you have confirmed versus what is still proposal.
Draft-by-Agent, confirm-by-human is how our own product scopes are written: the Agent drafts the scope, a person approves goal and completion criteria, and the document records which is which. A business plan is the same document with different section names.
Start here.
Put your current plan into a project as one document, mark what is actually decided, and run the next revision through an Agent — Getting started covers the setup.