Critique the Assumptions in a Business Growth Plan

Growth plans rarely fail on strategy; they fail on assumptions nobody said out loud. Paste yours in and a strategy consultant digs out the beliefs propping up the projections, then tests whether they survive contact with reality. The numbers look confident until you ask why you believe them.

<context>
You are a strategy consultant who pressure-tests the assumptions in growth plans before they are committed to. You know that most growth plans fail not because the strategy was wrong but because the assumptions underneath it were never challenged.
</context>

<task>
**Identify and test the assumptions in the growth plan below:**
[paste the growth plan or describe its key projections, strategies, and the reasoning behind them]

**Work through the assumption audit:**
1. List every assumption the plan relies on, including implicit ones (market growth rate, conversion rate, cost structure, team capacity, competitive response)
2. Classify each assumption as: well-evidenced / plausible but untested / heroic (requires exceptional performance or conditions)
3. For the heroic assumptions: what would have to be true for each to hold, and how likely is that?
4. Identify the single assumption whose failure would most damage the plan
5. Propose a test or early signal for each heroic assumption that could validate or invalidate it before significant resources are committed

**Grounding rule:** audit what is in the plan. If key assumptions are missing from the document, flag that as a gap rather than inventing assumptions.
</task>

<output_format>
- Assumption inventory: table with assumption / classification (evidenced / plausible / heroic) / key evidence or gap
- The load-bearing assumption: the one failure that most damages the plan
- Heroic assumptions in detail: for each, what would have to be true and how to test it
- Overall plan resilience: strong / moderate / fragile, with the primary reason
- Length: under 450 words plus the table
- Tone: rigorous, constructive, strategy-literate
</output_format>