The disruption seems too great
The expected benefit does not yet outweigh the time, training, or migration required.
Clue: The prospect focuses mainly on workload, timing, and operational continuity.
Interest and change
“We’d rather not change anything for now.”
Address resistance to change
The status quo protects habits, stability, responsibilities, and sometimes the decision-maker’s internal credibility.
What the prospect may really mean
The statement alone is not enough. Look for the meaning that fits the clues already present in the conversation.
Adoption is uncertain
The decision-maker worries that users will not use the new solution.
Clue: They mention past failures, strong habits, or teams that are already stretched thin.
The decision carries political risk
Sponsoring the change puts the person behind it at risk if the project fails or disrupts internal balance.
Clue: Their language focuses on responsibility, manager buy-in, or how certain teams might react.
The status quo seems acceptable
The problem is not costly or urgent enough to justify a change.
Clue: The acknowledged impacts remain minor, diffuse, or long tolerated.
Dig deeper before responding
Choose a question, listen to the full answer, then paraphrase it. An objection is not handled by reciting a questionnaire.
- 1
« Which part of the change seems riskiest to you? »
- 2
« Which teams would be most affected? »
- 3
« What made previous changes difficult? »
- 4
« What evidence or outcome would reduce the risk enough? »
- 5
« What cost or limitation of the status quo could make action necessary? »
Mistakes that shut down the conversation
Say the change will be easy
Minimizing the effort undermines the salesperson’s credibility and prevents the real work from being identified.
Sell only the end state
The prospect needs to understand the path, the owners, the steps, and the safeguards.
Propose a box-checking pilot
A test without a sponsor, users, or criteria does nothing to reduce decision risk.
Several ways to respond
The right approach depends on what the objection means. These examples are starting points, not scripts to impose.
Name the risk
When the resistance remains general.
“Which part of the change seems riskiest to you: deployment, adoption, or continuity?”
The status quo becomes a set of risks that can be examined separately.
Plan a gradual start
When the risk can be tested on a representative scope.
“Which pilot group could help measure adoption without disrupting the entire organization?”
The change becomes limited, observable, and reversible.
Compare with the status quo
When the problem is acknowledged but tolerated.
“If nothing changes over the next few months, what consequence will you continue to accept?”
The prospect compares two real risks instead of comparing risk with no risk.
Two possible conversations
These dialogues are illustrative. They show the logic of diagnosis, not a one-size-fits-all formula.
An adoption concern
The team has already rejected a previous tool.
Prospect
« We’d rather not change anything. The team is tired of new tools. »
Sales rep
« What made the previous change difficult? »
Prospect
« It was imposed without a pilot or a manager champion. »
Sales rep
« Let’s structure the evaluation around a volunteer group and a manager responsible for it before rolling it out more broadly. »
Key takeaway: The response uses past experience to define concrete safeguards.
A status quo that is still acceptable
The prospect acknowledges a problem but not any significant consequences.
Prospect
« It’s not perfect, but we don’t want to change. »
Sales rep
« What consequence of the current system would be significant enough to reconsider this choice? »
Prospect
« A clear increase in errors or delays. »
Sales rep
« Let’s define that threshold. Until it’s reached, I understand that the status quo remains rational. »
Key takeaway: The sales rep doesn’t exaggerate the urgency and establishes an honest condition for revisiting the decision.
What Objeqo can detect in real time
- Mention of habits, fatigue, or past failures
- Concerns about users or managers
- Explicit preference for the status quo despite acknowledging a limitation
Contextual analysis
Objeqo connects resistance to past experiences, the teams involved, and impacts already noted in the memory.
How Objeqo helps
Objeqo can suggest naming the risk, exploring a viable pilot, or honestly comparing change with the status quo.
When not to step in
If the impacts are minor and there’s no trigger, Objeqo won’t manufacture urgency to force change.
Frequently asked questions
How can you reduce fear of change?
By naming the risks, owners, steps, criteria, and conditions for stopping or expanding the rollout.
When should you propose a pilot?
When the group is representative, the sponsor is engaged, and the criteria can address the identified risk.
Should you calculate the cost of the status quo?
Yes, but only using impacts and assumptions acknowledged by the prospect. No figures should be made up.
Continue with a related objection
Competition
“We already work with someone.”
The current solution may satisfy the prospect, create switching costs, or simply serve as a benchmark during the evaluation.
Timing and priority
“This isn’t the right time.”
Timing may depend on a project, workload, risk, or simply a low priority.
Interest and change
“I’m not interested.”
A rejection may signal poor targeting, a misunderstood proposal, low priority, or a firm decision not to continue.
On your next call