Sensitivity analysis: stress-testing your visa financial model

Every founder building a UK Innovator Founder Visa business plan reaches the same moment: the financial model needs a revenue line, and the temptation is to draw a smooth curve sweeping up and to the right. It looks confident. It looks ambitious. And to an experienced endorsement assessor, it looks like a warning sign. Commentary on the endorsement criteria is blunt about this — overly ambitious projections, particularly where unsupported by evidence of demand or funding, frequently undermine otherwise credible proposals. The fix is not to lower your ambition. It is to show you have stress-tested it.

Why a single projection reads as a red flag

An assessor at UKES, Innovator International or Envestors reviews a large volume of business plans. They have seen thousands of forecasts that all curve upward at roughly the same optimistic angle. What they have learned is that the shape of the curve tells them almost nothing — what matters is whether the founder can explain the assumptions underneath it and what happens when those assumptions are wrong.

A single projection offers no way to test this. If your plan says you will reach £800,000 in revenue by year two and nothing else, the only honest response an assessor can give is: how do you know? Guidance on the Innovator Founder business plan consistently stresses that projections should be "capable of explanation" with realistic assumptions, and that plans should acknowledge risk with mitigation strategies rather than assume everything goes to plan (DavidsonMorris business plan guide).

The counter-intuitive truth is that showing your business in a worse light — a slower, harder scenario — makes the whole plan more credible. It proves you have looked at the downside and built a business that survives it.

What sensitivity analysis actually is

Sensitivity analysis is the practice of changing one input in your model and observing what happens to the outputs — revenue, cash balance, runway, headcount you can afford. Scenario analysis bundles several of those changes into named cases: a base case, a downside, and often an upside. In a well-built model the two work together. You identify the variables the business is most sensitive to, then you build scenarios around plausible values for them.

For most early-stage businesses, the outputs are most sensitive to a small number of drivers:

• Customer acquisition rate — how fast you win customers, usually a function of lead volume and conversion rate tied to a specific channel.
• Price — the average revenue per customer, contract or subscription.
• Churn or retention — how many customers you keep, which compounds heavily over a three-year horizon.
• Hiring timeline — when each hire lands, which drives your cost base and burn.

You do not flex all of these at once. Change one at a time so the reader can see the effect of each, then combine sensible values into your downside and upside cases.

A worked example

Here is a simple three-year revenue picture for a B2B SaaS business under three scenarios. The base case reflects the founder's genuine expectation. The downside assumes acquisition runs slower and churn runs higher. The upside assumes a referral channel compounds.

The value is not in the numbers themselves but in what surrounds them. Each scenario names the assumptions that produce it, so an assessor can see exactly what has to be true for each outcome. The downside is not a disaster — it is a slower, more expensive path that the business still survives, ideally within the funding you have modelled. That is the story that builds confidence.

Connecting scenarios to runway and cash

Revenue scenarios are only half the picture. Each one implies a different cash trajectory, and the downside case is where the 24-month runway rule earns its keep. If your downside scenario burns through your funding before you reach a sustainable position, that is a problem you want to discover and address in the model — not one an assessor discovers for you.

Run each scenario through your operating costs and you get three burn profiles and three runway figures. The credible plan shows that even in the downside, the business either reaches breakeven within the runway or has a clearly articulated plan to raise the next round on the strength of the traction achieved. Pairing this with a break-even and contribution analysis lets you state precisely how many customers each scenario needs to become self-sustaining.

Use the free assessment at /assess — five assessments, no card — to pressure-test the viability and financial sections of your plan against the endorsement criteria before you submit. For more in this series, see /insights.

Keeping the numbers honest

There is a discipline that underpins all of this: the numbers in each scenario must be computed from stated assumptions, not invented to look good. This is the heart of building a defensible model, and it is covered in depth in deterministic, not hallucinated: the rule for AI in visa financials. If a scenario's revenue figure cannot be traced back to a lead count, a conversion rate and a price, it is decoration, not analysis — and it will not survive questioning.

The same logic connects sensitivity analysis to the other credibility work in your plan. A downside scenario is a form of risk acknowledgement; the assumptions behind it are your revenue assumptions built to survive scrutiny; and the pattern of an unbroken, unexplained hockey stick is one of the classic financial model red flags an assessor reaches for first.

For general best practice on building scenario and sensitivity models, the Corporate Finance Institute's guide to sensitivity analysis is a solid reference on technique, and GOV.UK's guidance on the Innovator Founder route sets out the underlying criteria your model has to satisfy.

Key takeaways

• A single confident projection signals hope; a downside, base and upside range signals judgement — and judgement is what the viability assessment is testing.
• Flex only the two or three drivers your model is most sensitive to — typically acquisition rate, price and churn — and change them one at a time so cause and effect are visible.
• Anchor your base case to what you genuinely expect and can defend; treat the upside as a bonus and the downside as your stress test.
• Run every scenario through your cash model so you can prove the business survives the downside within its runway, not just the optimistic path.
• Every scenario figure must trace back to stated assumptions — computed numbers survive questioning, decorative ones do not.

• financial-model
• sensitivity-analysis
• viability
• risk
• business-plan