“It’d be too big a change”What It Means. What to Say.
How to handle fear of change in sales: what the prospect really means, how to recognise it, and replies that work, from Merdial’s built-in sales canon.
SEBy Samir El Barbary, Founder, Merdial·Updated
The short answer
“It’d be too big a change” usually means: the cost and disruption of switching or adopting feels larger than the benefit. A reply that works: “What if we started with one team for a couple of weeks, so you see it work before anyone else changes anything?”
What it really means
The cost and disruption of switching or adopting feels larger than the benefit.
How to recognise it
What they say: "it'd be a big change", "my team won't adopt it", "we'd have to migrate everything", "we tried something like this before".
Most likely
when an incumbent or an existing process exists; late in evaluation; closing meetings.
Unlikely
when there is nothing in place to change from; in the first seconds of a cold call.
Replies that work
Reduce the risk
Make saying yes smaller and safer; a pilot, a phased start, a clear way out; within what the product facts allow.
Name the risk they fear.
Offer the smallest safe step the facts support (pilot, short term, one team).
Ask if that step would feel comfortable.
Say it like this
“What if we started with one team for a couple of weeks, so you see it work before anyone else changes anything?”
“Would it help to start small, so the only risk is a few weeks of your time?”
Avoid
Offering guarantees, trials or terms the product facts do not state.
Minimising the risk instead of shrinking it.
Validate, then continue
Show you heard the worry and that it is normal, so they stay in the conversation instead of defending their position.
Name the worry back in their words.
Normalise it: others in their seat feel the same.
Move forward with one question that keeps them talking.
Say it like this
“That's a completely fair worry, and honestly most teams feel exactly that before switching. What's the part that worries you most?”
“I hear you. Nobody wants another tool the team ignores. What happened last time you rolled something out?”
Avoid
"I understand, but…"; the but erases the validation.
Minimising the concern.
Validating and then pitching instead of asking.
Social proof
Borrow credibility from people like them; lower the perceived risk of believing you.
Name a relevant peer group (role, size, industry), never an invented logo.
Share the before-and-after in one sentence.
Ask whether their situation looks similar.
Say it like this
“Most sales managers we work with said the same thing before they tried it. The difference showed up in the first two weeks. Would that kind of result matter to you?”
“Teams your size usually tell us the hard part was the rollout, not the tool. Want to hear how they handled that?”
Avoid
Naming customers or numbers that are not in the product facts.
A testimonial monologue.
Proof that does not match their segment.
How Merdial helps on a live call
In Merdial, your team reviews a reply for each challenge like this one, in your own voice. When a prospect says it on a call, real-time AI assist recognises it and puts that reply on the rep’s screen about a second later; the rep decides whether to use it. Each challenge carries competing versions, and they are tested on real calls, so the reply that actually moves calls forward is the one shown most.
Get these replies on screen during your own calls: $0, one seat, no card.
What does “It’d be too big a change” mean on a sales call?
The cost and disruption of switching or adopting feels larger than the benefit.
What should I say when a prospect says “It’d be too big a change”?
Try this: “What if we started with one team for a couple of weeks, so you see it work before anyone else changes anything?” It works because it follows the move “Reduce the risk”: make saying yes smaller and safer; a pilot, a phased start, a clear way out; within what the product facts allow.
How do I know it is really “It’d be too big a change”?
Listen for "it'd be a big change", "my team won't adopt it", "we'd have to migrate everything", "we tried something like this before". It is most likely when an incumbent or an existing process exists; late in evaluation; closing meetings.
