Stress testing a business plan means testing the assumptions behind the numbers, not the numbers themselves. The ones most often too optimistic are the length of the sales cycle, the costs that scale with the product, and market share relative to sales effort. A robust plan can be fully recalculated from one or two assumption sheets.
How to spot a plan built on hope in five minutes
Missing metrics. A good business case sits on one or two sheets where the assumptions are entered openly: prices, conversion, sales cycle, unit costs, hiring. Change one assumption and the whole plan recalculates.
If that sheet does not exist, the numbers are hidden in formulas or typed in by hand. Then the plan cannot be followed. And that is usually where the problem lies: things are hidden or simply not thought through.
The three most common mistakes
1. The sales cycle is underestimated. Between spending money on sales and marketing and seeing it come back as revenue there are often many months. Leads sit in the pipeline, procurement and engineering have to sign off. Ignore that, and you do not have a revenue problem, you have a cash problem.
2. Costs lack detail. Overhead is a flat assumption and the costs that scale with the product are missing altogether. That means unit costs such as materials, but also power, data usage and, today above all, the use of AI models. Without that detail the business cannot be steered properly later.
3. Market share does not match effort. Market sizes are easy to derive today. The interesting question is what share or penetration you want to reach, and whether the sales and marketing effort in the plan fits. Ten percent market share with one salesperson is not a strategy, it is a wish.
Greenfield or existing customers
A plan for a new greenfield business follows different rules than a business unit built on an existing customer base. In the second case conversion is higher because trust exists. But it is often slower, because existing customers change their routines slowly. Both belong in the assumptions.
Ten assumptions we check first
| Assumption | Review question | Warning sign |
|---|---|---|
| Sales cycle | How long from first contact to first invoice? | shorter than in the existing business |
| Conversion | How many leads become customers, backed by data? | targets instead of actuals |
| Market share | What penetration, with what sales effort? | share grows, team stays the same |
| Price | What price after discounts, not list price? | list price in the plan |
| Retention | How many customers remain after twelve months? | no churn assumed |
| Unit costs | Which costs rise with every unit or user? | power, data, AI usage missing |
| Overhead | Which fixed costs come with growth? | flat percentage |
| Hiring | When are new people productive, not just hired? | full output from day one |
| Payment terms | When does the cash actually arrive? | revenue equals cash |
| Dependencies | Which customers, partners or suppliers carry the plan? | one name carries more than a third |
Plan versus reality after twelve months
Twelve months later, plans are never what they were. A plan is orientation; life brings movement, positive and negative. What matters is not whether it is right, but whether you can see which assumption broke.
Constructed example. The patterns come from practice, figures and setting are invented.
A machinery manufacturer launches a digital service for its existing customers. The plan: 100 paying customers after twelve months, break even in year two. After twelve months there are 35. The reason is not the product: approval by customers' procurement and IT takes nine months on average, not three. At the same time, cloud and AI costs per customer are twice as high as assumed, because customers use the service more intensively than expected.
Because the plan had an assumption sheet, it took one hour to see what had happened. Sales cycle and unit costs were adjusted, pricing for heavy usage was restructured, break even moved by two quarters. Without the sheet the discussion would have taken weeks and ended in finger pointing.
FAQ
What does it mean to stress test a business plan?
Testing the assumptions behind the numbers against data, market and experience: sales cycle, conversion, prices, costs, hiring and dependencies.
Which assumptions are most often too optimistic?
The length of the sales cycle, the costs that scale with the product, and market share relative to sales effort.
How do you recognise a robust business plan?
By an assumption sheet that drives the whole plan. Change one assumption and all dependent numbers change.
Who should review a business plan?
Someone with no stake in the outcome who knows executive responsibility. Before an acquisition or investment, it is part of commercial due diligence.