Testing Decision-Maker Support Before You Build the Compliance Case

Start by naming the assumption precisely

Most teams entering a regulated market carry a vague belief that "the regulator will be supportive" or "the board is aligned." That is not an assumption you can test. Before you spend a day validating anything, write down what you actually believe, in specific terms:

• Which named individuals or bodies must support this?
• What exactly must they support: the market entry, the operating model, the capital treatment, the conduct approach?
• What level of support do you need: active advocacy, quiet acceptance, or simply no objection?

If you cannot answer these three questions in a paragraph, you are not ready to validate anything. You are still guessing.

Separate the decision-makers from the noise

In regulated market entry, the people who appear influential in public are often not the ones whose view will determine your outcome. A supervisor two levels below the visible executive may hold the pen on your authorisation. A non-executive director with sector history may quietly shape the board's risk appetite before your paper is even tabled.

Build a short list, no more than eight to ten names, of the people whose view will actually move the decision. Split them into three groups: those inside your firm, those at the regulator or supervisory body, and those in the broader stakeholder set (rating agencies, key clients, industry bodies where relevant). If your list is longer than ten, you have not thought hard enough.

Test through indirect signal first

Do not open with a direct pitch. It compresses your options and forces stakeholders into a position before they have context. Instead, gather signal in the following order:

1. Published positions. What have these individuals said publicly in the last eighteen months? Speeches, consultation responses, board minutes, and letters to the sector often contain the actual view. Contradictions between public statements and your assumed support are the first warning sign.
2. Adjacent conversations. Talk to people who have recently interacted with your decision-makers on similar matters. What questions did they ask? What made them uncomfortable? What did they wave through?
3. Structured soundings. Only after the first two should you engage directly, and even then, through a framed exploratory conversation rather than a proposal. "We are considering entry and want to understand what would concern you" produces better intelligence than "here is our plan."

Design conversations that surface disagreement

The biggest failure in this phase is confirmation bias dressed up as validation. If every conversation leaves you more confident, you are asking the wrong questions.

Use two techniques. First, ask each stakeholder what would cause them to object, not whether they support you. Second, ask them who else in their organisation might see this differently and why. Both questions produce specific, actionable intelligence. Vague reassurance produces nothing.

What good looks like: a written summary after each conversation that includes at least one thing you did not know before, and at least one point of friction or hesitation. If you cannot produce that, the conversation was not useful, regardless of how warm it felt.

Weight the signal honestly

Regulatory and board stakeholders rarely say no directly. They say "interesting," they raise questions, they suggest you speak to someone else. Learn to read the softer signals:

• Repeated redirection to other parties often means the person does not want to own the decision.
• Questions about precedent usually mean the stakeholder is uncomfortable being first.
• Silence on your core proposition, while engagement on peripheral detail, means the core proposition has not landed.

A useful discipline: after each round, force yourself to write the case against your entry using only what you heard. If that case is thin, you probably did not listen properly.

Decide before the sunk cost builds

Set a clear checkpoint, ideally four to six weeks in, where you decide one of three things: proceed with the compliance work, adjust the proposition and re-test, or stop. The trap is drifting into full compliance build while validation is still ambiguous. Every week you delay this decision, the cost of pulling back rises and the objectivity of the assessment falls.

Your next action: write down the three named individuals whose support you are assuming, and what specifically you believe they will accept. If that sentence is hard to write, you have your starting point.