If you can't explain your business to a stranger, don't submit yet

There's a moment that happens in almost every Innovator Founder Visa interview or contact-point meeting: a founder is asked, in some form, to explain what their business does. Not to summarise the business plan. Not to walk through the financial model. Just to explain it — as if to someone who has never heard of it before.

A surprising number of well-prepared founders, with genuinely strong plans behind them, stumble here. They reach for jargon. They start three sentences deep into an assumption the listener doesn't share. They can't find the plain-language version because they've never had to produce one — they've only ever written and rewritten the polished document version. If this happens in front of an assessor, it doesn't matter how good the underlying plan is. The moment reads as a founder who doesn't have full command of their own business.

Why this test matters more than founders expect

A business plan is a document a founder controls completely — they choose every word, revise it as many times as needed, and can get help polishing it. An interview or contact-point conversation is not that. It's live, it's unscripted, and it directly tests whether the founder actually holds the business's logic in their head, or has only ever seen it on paper.

Assessors know this distinction well, which is exactly why interviews exist as a separate assessment stage rather than a formality. A founder who can only produce a coherent explanation of their business when reading from prepared notes is showing the assessor something important: possibly that someone else wrote the plan, possibly that the founder hasn't internalised their own strategy well enough to improvise around it, or possibly both.

The elevator test, precisely defined

The test itself is simple to state and harder to pass than it sounds: explain what your business does, who it's for, and why it matters, to someone with zero prior context, in under two minutes, without industry jargon, in a way that leaves them able to accurately repeat it back.

That last clause is the real bar. It's not enough for the explanation to sound coherent to the founder while they're giving it. The test passes only when the listener — who started with no context — can accurately summarise what they just heard. If they can't, the explanation had a gap, regardless of how it felt to deliver.

Why jargon is the most common failure mode

Founders deep in a specific industry or technology stop noticing which words are jargon to an outsider. Terms that feel like plain description to the founder — a specific acronym, a category name only insiders use, a piece of internal shorthand — land as noise to a genuine stranger, and the explanation collapses the moment the listener stops understanding a key term but is too polite to interrupt and ask.

The fix isn't removing all technical detail — some businesses are genuinely technical and that's fine. The fix is separating what changes for the customer (which should always be explainable in plain terms) from how the technology achieves it (which can stay technical, and belongs in a follow-up answer, not the opening explanation).

A practical drill for building this

This is a skill, and like most skills it responds to deliberate practice rather than hoping it goes well on the day.

Step 1 — write the plain-language version first, separately from the business plan. Three or four sentences: who has the problem, what the problem costs them, what the business does about it, why this founder specifically is positioned to build it. No jargon, no acronyms, no numbers that need context to interpret.

Step 2 — say it out loud to a genuine stranger. Not a colleague, not someone in the industry, not a friend who already knows about the business — someone with real, uncontaminated zero context. A friend outside the field, a family member, someone at an unrelated networking event.

Step 3 — ask them to repeat it back. Don't ask "does that make sense?" — people say yes to be polite. Ask them to explain the business back to you in their own words. The gaps between what you said and what they repeat back are exactly where the explanation needs work.

Step 4 — note precisely where confusion happened, not just that it happened. Was it a specific term? A logical jump that skipped a step? An assumed piece of context they didn't have? Fix that specific point, not the whole explanation.

Step 5 — repeat with a different stranger. Each pass should produce fewer, smaller gaps. When two or three genuine strangers in a row can accurately repeat the explanation back, it's ready.

How this differs from your written plan summary

It's tempting to think a strong one-paragraph executive summary in the business plan satisfies this requirement already. It doesn't, for one specific reason: a written summary is never tested against live, unscripted follow-up questions. The stranger test has to survive "wait, what do you mean by that?" and "how is that different from [thing they've heard of]?" in real time, without a chance to revise the answer afterward. That's a materially harder and more realistic simulation of what actually happens in an interview room.

This connects directly to broader interview readiness — the same clarity discipline underpins how founders should approach explaining a career pivot to assessors and demonstrating founder-market fit. All three depend on the founder being able to produce, unscripted, the same clear logic that took weeks to build into the written plan.

What this reveals about the business itself

There's a secondary benefit worth naming: founders who genuinely struggle to pass this test sometimes discover the difficulty isn't in the explaining — it's that the underlying business logic has a real gap the polished document was quietly papering over. If three strangers in a row get stuck at the same point, that's worth investigating as a substance question, not just a communication one. This is one of the reasons the drill is worth doing early, not the week before an interview.

Sources and further reading

• GOV.UK: Innovator Founder visa guidance
• GOV.UK: Immigration Rules Appendix Innovator Founder
• Davidson Morris: Innovator Founder Visa

Key takeaways

• Assessors can directly observe interview clarity in a way they can't observe how much effort went into the written plan — this makes the stranger test a real, distinct readiness gate.
• The bar isn't sounding coherent — it's a genuine stranger being able to accurately repeat the explanation back afterward.
• Jargon and insider shorthand are the most common failure points; separate what changes for the customer from how the technology works.
• Practice with genuinely uncontaminated strangers, not colleagues or people who already know the idea.
• Track exactly where confusion happens each time, and fix that specific point rather than rewriting the whole explanation.
• Repeated failure at the same point across different listeners often reveals a real gap in the business logic, not just a communication problem.

• founder-clarity
• common-mistakes
• interview-prep
• elevator-pitch