Skip to main content

Resolving Consultant vs Internal Team Disputes on Launch Readiness

A practical guide for senior leaders facing conflicting readiness signals from external advisors and internal teams ahead of a product launch. After reading, you will know how to design a fast, defensible test that exposes which view actually reflects customer sentiment.

Start by diagnosing the disagreement, not the market

When consultants say go and your internal team says wait (or vice versa), the instinct is to commission more research. Resist it. The first job is to work out what the two sides are actually disagreeing about. Nine times out of ten, the dispute is not about customer sentiment at all. It is about different reference points: the consultants are usually working from category benchmarks and analogues, while your internal team is working from anecdotes, relationship signals, and operational scar tissue.

Get both sides to write down, in one page each, three things: what they believe the customer will do at launch, what evidence they are basing it on, and what would have to be true for them to be wrong. If either side cannot complete the third, you do not have a readiness debate. You have a confidence problem dressed up as analysis.

Separate the four questions that get conflated

Most launch readiness arguments mash together four distinct questions:

  1. Is there latent demand for the proposition?
  2. Will customers switch or adopt at the price and friction implied?
  3. Are distribution partners and intermediaries ready to sell it?
  4. Is the regulatory and reputational ground stable enough?

Consultants tend to be strongest on question one and weakest on three and four. Internal teams are usually the opposite. If you do not split the questions, you will get a binary go/no-go fight when the real answer is almost always: yes on two of them, no on the others, sequence accordingly.

Run a 10-day validation sprint

You do not need a three-month research programme. You need a focused sprint with three parallel workstreams.

Customer signal

Commission 15 to 20 structured conversations with target customers, split across segments where the two sides most strongly disagree. Do not use your relationship managers to recruit. They filter. Use an independent recruiter and pay for time. The questions should test the specific behavioural claim under dispute, not general appetite. If consultants claim 30 percent will switch within 12 months, ask what would have to happen for the customer to switch, what they last switched and why, and what they nearly switched but did not.

Intermediary and distribution signal

If you sell through brokers, IFAs, platforms, or corporate channels, their readiness is often the binding constraint. Talk to 8 to 10 of them with the same disciplined script. Internal teams usually have this view but rarely structure it. Make them.

Competitive and adjacent signal

Look at the last three comparable launches in your segment over the past 24 months. What did the launch teams predict, what actually happened in the first two quarters, and what did they miss? This is the cheapest correction to both consultant optimism and internal pessimism.

What good looks like at the end of the sprint

A single page that shows, for each of the four questions above, what the customer and intermediary evidence actually says, where the consultants were right, where the internal team was right, and where both were wrong. If you cannot produce that page, the sprint was not disciplined enough.

Good also looks like a revised launch decision that is rarely a clean yes or no. It is usually: launch to segment A in Q1, hold segment B pending distribution readiness, and rework the pricing assumption that both sides quietly accepted without testing.

What most people get wrong

Three failure modes recur. First, treating the disagreement as a political problem to be mediated rather than an empirical one to be resolved. Second, asking customers about intent instead of past behaviour, which inflates every signal. Third, letting whichever side has more seniority quietly win once the noise dies down. The point of the sprint is to make that impossible.

Your next decision

Before your next steering meeting, ask each side to produce the one-page belief statement described above. If either refuses or cannot, you already know whose view to discount. That alone is worth the exercise.

Related guides

Stakeholder Intelligence

Validating Stakeholder Feedback When the Board and the Field Disagree

A practical guide for resolving contradictory signals between board-level confidence and field-level caution about market readiness in regulated industries. After reading, you will know how to weight competing inputs, design validation that holds up under regulatory scrutiny, and reach a defensible decision.

Market entryBoardsCustomers
3 min readRead guide →
Market Entry, Launches & Investment

Go-to-Market Research in Financial Services: A Practical Guide

This guide sets out how to run go-to-market research for a financial services product, proposition, or market entry, covering the specific evidence senior leaders need before launch. After reading it, you will know how to sequence the research, what to test, and how to avoid the failure modes that sink otherwise sound propositions.

Market entryProduct launchCustomers
4 min readRead guide →
Market Entry, Launches & Investment

How to Assess Stakeholder Readiness Before Market Entry in Financial Services

A practical guide to testing whether regulators, distribution partners, customers, and internal capability are actually ready for your market entry, before you commit capital. After reading, you will know which stakeholder signals to test, in what order, and how to interpret ambiguous responses.

Market entryRegulatorsDistributors
4 min readRead guide →
Market Entry, Launches & Investment

When the Board and Compliance Disagree on Regulator Sentiment

This guide sets out how to resolve conflicting internal signals about regulator support before a product launch in a regulated market. After reading, you will know how to structure a validation exercise that produces a defensible answer, not just a louder opinion.

Product launchRegulatorsBoards
3 min readRead guide →
Market Entry, Launches & Investment

Validating Stakeholder Buy-In Across Jurisdictions Before a Product Launch

This guide sets out how to test whether stakeholder support for a multi-jurisdiction product launch is real or performative. After reading, you will know how to sequence validation across regulators, distributors, and internal sponsors, and how to spot the soft signals that predict a launch stalling.

Product launchMarket entryRegulators
3 min readRead guide →

Where internal consensus may be mistaken for validation

Polar Insight's Decision Rooms bring outside challenge to a live decision, so blind spots and untested assumptions surface before commitment, not after.

Explore Decision Rooms