Best/base/worst case scenarios with financial projections and response plans. This page explains what the deliverable is, why it matters, what it contains, and how it helps turn a business idea into an operating unit.
SCENARIO-PLANNING.mdThree detailed scenarios (best case, base case, worst case) with financial projections, operational implications, and pre-planned response strategies. Each scenario includes specific trigger conditions, monthly burn rate adjustments, hiring/firing implications, and cash runway impact. Designed to eliminate surprise — you know exactly what to do when conditions change. It is written as an implementation-ready asset: specific enough for action, structured enough for review, and connected enough to support the other deliverables in the build.
The page is not a generic description of SCENARIO-PLANNING.md. Your Deputy uses your niche, target customer, location, business model, primary offer, and secondary offers to shape the content and keep the artifact relevant.
This deliverable is designed to work with the rest of the autonomous business unit: website, funnel, CRM, RevOps, analytics, AI/MCP tools, workflows, and self-hostable infrastructure.
The output is written so an owner, operator, developer, advisor, lender, or implementation partner can understand what to do next without decoding raw generator output.
The exact content adapts to the business model, target customer, offer, and launch scope. A typical generated version includes:
The builder extracts the niche, buyer, offer, constraints, and operational assumptions from your brief.
The deliverable is produced with business-specific language, concrete sections, and implementation-oriented structure.
Quality gates check for placeholder residue, generic copy, missing modules, broken routes, and promise-to-artifact drift.
The artifact becomes part of your launch package, supporting sales, operations, engineering, governance, or customer delivery.
Teams can see the purpose, scope, dependencies, and expected next actions instead of guessing from scattered notes.
The deliverable creates a concrete artifact that can be reviewed, improved, tested, and handed to a specialist when needed.
Every artifact ultimately supports acquisition, conversion, fulfillment, retention, governance, or operational scale.
A single deliverable is useful. The full value comes when this file is generated alongside the website, funnel, CRM, RevOps, payments, analytics, AI/MCP tools, workflow engine, self-hosted infrastructure, and validation gates.