Stress-Testing Stakeholder Assumptions Before You Fund a Regulated Launch

Start by writing the assumptions down

Most launches fail because the critical assumptions were never made explicit. They sat inside the business case as confident assertions: the regulator will treat us as low-risk, distributors will give us shelf space, corporate customers want this product, the supervisory team in market X will engage constructively. None of these were tested. They were inherited from the deal sponsor's instinct.

Before any validation work, force the team to list every stakeholder assumption the business case rests on. Group them into four buckets: regulator, customer, distribution partner, internal. If you cannot write the assumption as a falsifiable statement, it is not yet an assumption, it is a hope.

Rank assumptions by fragility, not importance

The instinct is to validate the assumptions that matter most. That is the wrong filter. Validate the assumptions that are both material and fragile, meaning you have the least independent evidence for them.

A useful test: for each assumption, ask who told us this, and what would it take for them to be wrong. If the answer is the sponsor, the consultant who wrote the strategy, or a single conversation with a regulator's external affairs team, treat it as fragile. If the answer is three independent sources including someone with no commercial interest in the launch, it is more solid.

The assumptions that sink launches are rarely the ones the team is nervous about. They are the ones nobody thought to question.

Choose the right validation method for each assumption

Different assumptions need different evidence. Confusing them wastes time and money.

Regulator assumptions

Direct engagement is necessary but insufficient. Supervisors will rarely tell you they are uncomfortable with a proposition in a first meeting, they will ask questions. Read the questions, not the words. Triangulate with recent enforcement actions, speeches, Dear CEO letters, and authorisation patterns for comparable firms in the last 18 months. If you are entering a market, talk to two or three firms that went through authorisation recently and ask what surprised them.

Customer assumptions

Quantitative research at this stage is usually a trap. It tells you what people say they will do, not what they will buy. Better: structured interviews with 15 to 20 target customers conducted by someone who is not selling to them, with explicit questions about current providers, switching costs, and what would have to be true for them to change. Pay attention to what they do not say.

Distribution and partner assumptions

The failure mode here is mistaking warm receptions for commitment. A distributor who says the proposition is interesting is telling you nothing. Push for specifics: shelf placement, commercial terms, onboarding timelines, internal approvals required. If they cannot give you those, you do not have a partner, you have a meeting.

Internal assumptions

The assumptions about your own organisation's capacity, risk appetite, and operational readiness are the ones most often skipped. Test them by asking the heads of compliance, risk, and operations to write down what would have to be true for them to support the launch in 12 months. The gap between their list and the business case is your real risk.

Sequence the validation to protect the budget decision

Run validation in two waves. The first wave tests the assumptions that, if wrong, would kill the launch. Regulator stance, target customer demand, one viable distribution route. Three to six weeks. If any of these fail, the decision is no, or redesign before continuing.

The second wave tests the assumptions that would change the size or shape of the investment: pricing, partner economics, operational build cost. This is where most of the budget goes, and it should only happen once wave one is clean.

The common mistake is running both waves in parallel because the timeline is tight. You then discover the killing assumption was wrong after you have spent on the supporting work.

What good looks like

A validated business case has an assumptions register with named owners, evidence sources, confidence ratings, and dates. Anything rated low confidence has a plan to close the gap or a decision to proceed with the risk explicitly accepted at board level.

Your next decision

Before the next investment committee, ask for the assumptions register. If it does not exist, or if more than a quarter of the assumptions are rated on internal opinion alone, defer the budget decision. The cost of a six-week delay is almost always lower than the cost of a launch built on assumptions nobody tested.