The plan that keeps thinking

A business plan is usually written once, under pressure, for a single reader — a lender, a board, a grant panel. It wins or loses that meeting and then goes into a folder. Six months later the market has moved, the pricing assumption is stale, and nobody re-opens the file because re-opening it means re-writing it.

That is a tooling problem, not a discipline problem. Planners abandon documents that cannot tell them what changed.

What a thinking plan does differently

Every plan built here carries its evidence with it: the signals found during the live scan, the sources they came from, and the sections that were written against them. Because that link survives, the document can be asked a question no static file can answer — what is no longer true?

1. 1Re-scan. The engine runs the research again against the same venture, country and horizon.
2. 2Diff. New signals, moved signals and dropped signals are separated deterministically — no guessing, no silent rewrite.
3. 3Propose. For each material change, the engine drafts the specific edit to the specific section, with the evidence attached.
4. 4Apply. You accept, adjust or reject. The plan's history keeps the trail.

A plan should be the most current document in the business, not the oldest.

Why the diff matters more than the draft

Anything can produce a first draft now. Very little can tell you, three months in, that the assumption your funding case rests on has weakened and here is the paragraph to change. The draft is commodity; the diff is the product.

Working in a dynamic environment

Small ventures operate where input costs, tariffs, exchange rates and demand shift quarterly. The right response is not a longer plan — it is a shorter loop. Build the document, run it, re-scan it when something feels off, and let the evidence argue with you.