How to Test Regulator Reaction Before Building Your Next Product
This guide shows how to validate regulator sentiment on a new product strategy before you commit development and compliance spend. You will finish with a practical sequence for testing assumptions, reading signals accurately, and knowing when to proceed, pivot, or pause.
Start by naming the assumption precisely
"Regulators will welcome this" is not a testable claim. Break it into three specific propositions: which regulators, on which features, under which regime. A digital lending product might get a warm reception from the Treasury on financial inclusion grounds, a neutral view from the FCA on conduct, and a cold reception from prudential supervisors worried about capital treatment. If your leadership team is treating "regulators" as a single audience, that is the first problem to fix.
Write down, in one page, the specific regulatory outcomes you are assuming: no new authorisation required, existing permissions cover the activity, no additional capital or liquidity treatment, no consumer duty escalation, no cross-border complications. Each of these is a separate bet.
Map the actual decision-makers, not the org chart
The person who signs the letter is rarely the person who forms the view. On any material product question there is usually a supervisor, a policy lead, a technical specialist (often in a horizontal function like data, financial crime, or prudential policy), and increasingly a consumer outcomes lead. Any of them can slow you down. Only some can help you.
Identify who has been vocal on adjacent products in the last 18 months. Read their speeches, Dear CEO letters, portfolio letters, and consultation responses. If a Director has publicly warned about a risk your product touches, assume that view is now embedded in supervisory thinking regardless of what your relationship manager says over coffee.
Sequence your soundings carefully
Most firms get this wrong by going to their supervisor first with a polished pitch. That triggers a formal response, often cautious, that then binds the firm. Better sequence:
- Test the policy question informally through trade bodies, law firms, and former regulators who can sanity-check whether the concept sits within current thinking.
- Use industry roundtables and consultation responses from peers to triangulate the direction of travel.
- Approach the regulator with a genuinely open question, not a proposal. "We are exploring X, we see these three risk vectors, we would value your view on which matter most" produces far better intelligence than "we plan to launch Y, please confirm no objection."
- Only formalise once you have absorbed the signals.
Read the signals accurately
Regulators rarely say no directly on a novel product. What they do is ask questions that reveal their concerns. Learn to read these:
- Repeated questions on governance and accountability mean they are not convinced the firm can control the risk.
- Questions on consumer understanding and vulnerability mean conduct concerns are active.
- Requests for scenario analysis, wind-down plans, or operational resilience detail mean they are pattern-matching to a past failure.
- Silence, or a referral to another team, is not neutrality. It usually means the question is being escalated.
A "we have no objection at this stage" letter is worth less than firms assume. It is a snapshot, not a green light, and it will not protect you if supervisory priorities shift.
Stress-test against the regulator's real pressures
Regulators respond to their own stakeholders: Parliament, the Treasury, consumer groups, the press, other regulators. Ask what political or reputational risk your product creates for them. A product that is technically compliant but would produce awkward headlines during a cost-of-living debate will not be welcomed, whatever the rulebook says.
This is where most internal assessments fail. Compliance teams evaluate against rules. Regulators evaluate against consequences.
What good looks like
By the time you commit development spend, you should have: a written articulation of each regulatory assumption, evidence for or against each one from at least three independent sources, a clear view of who inside the regulator holds the pen, and a documented plan for how you would respond if the view shifted mid-build. If you cannot produce that document, you are not ready to invest.
The decision point
Before the next investment committee, ask one question: if the regulator's view moved against us six months into build, what would we lose and what would we do? If the honest answer is "we would have to stop," the validation work is not optional. Do it now, at the cost of weeks, rather than later at the cost of the programme.
Related guides
Validating Regulatory Assumptions Before Committing Compliance Capital
This guide shows senior leaders how to test their reading of regulator priorities before authorising major compliance spend. You will learn where assumptions typically break, which validation methods actually work, and how to sequence testing so you can commit capital with confidence.
The Cost of Untested Assumptions in Regulatory Approval Strategy
This guide examines the specific risks of pursuing a regulatory approval strategy built on inferred rather than tested decision-maker sentiment. Readers will learn how to identify where assumption risk sits in their approach and what to do about it before submission.
Testing Your Leadership's Read on Regulators Before You Spend
This guide sets out how to validate whether your executive team's assumptions about regulatory expectations match what supervisors actually want, before you commit to major compliance investment. After reading, you will know which assumptions to test, how to test them without triggering supervisory concern, and how to convert the findings into a defensible investment case.
Testing Your Read on Regulator Priorities Before You Spend
A practical guide to validating internal assumptions about regulator priorities before committing to compliance investment. After reading, you will know how to structure a low-risk verification exercise that exposes gaps between what your leadership believes and what supervisors actually care about.
When Board Assumptions About Regulators Diverge From Approval Reality
This guide examines what happens when boards approve strategies based on a stylised view of regulator priorities that differs from what case officers and decision-makers actually require at approval. It will help senior leaders detect the gap early, correct it before submission, and avoid the costly rework that follows misreading the room.
Polar Insight helps senior leaders in financial services understand what their key stakeholders actually think before significant decisions are made.
Book a conversation