How to Respond
The instinct when someone objects is to persuade. That instinct is wrong, and prospects can feel it. An objection is information — usually about what they've been burned by before, what they're accountable for, or who else is in the decision.
The four moves
| Move | Why it works | |
|---|---|---|
| 1 | Accept it as legitimate | Never argue with the objection itself. The moment you defend, you've become a vendor and they've stopped telling you things. |
| 2 | Reframe the variable | Most objections assume a fixed condition — total autonomy, perfect data, full replacement. Change the variable and the objection often dissolves on its own. |
| 3 | Return to diagnosis | End with a question, not a claim. The objection then becomes the next part of the conversation instead of the end of it. |
| 4 | Be willing to agree | Sometimes the objection is correct and the answer is "not yet". Saying so is the single fastest way to be believed about everything else. |
The pattern underneath every card here
Accept → Reframe → Ask. If your response doesn't end in a question, you have made a speech rather than had a conversation.
Objections that are actually buying signals
These come from people who have thought about implementation seriously. Treat them as encouragement, and score the prospect up, not down.
- "Our data isn't ready." — They understand that context is what makes any of this work.
- "Who's liable if it gets something wrong?" — There is probably legal input already, which means it's a real project.
- "The team will feel threatened." — They are thinking about adoption, which is where most initiatives die.
- "We tried automation before." — They will tell you precisely what to avoid, if you ask properly.
- "I don't want a black box." — They want governance, and governance is scope you can be paid to design.
Objections that are exits
Recognise these early and end well. A clean, generous "not now" is remembered, and it is where a surprising number of referrals come from.
- "Send me some information" — with no interest in it being tailored.
- "Let's revisit next quarter" — with nothing changing between now and then.
- "This is interesting" — with no owner, no urgency and no measurable outcome behind it.
The one you must never answer quickly
"How much would something like that cost?" Providing implementation pricing from a vague idea anchors you to a number you'll regret, in front of someone who will hold you to it. Name the price of discovery instead — that is a real, defensible figure, and offering it is what separates a consultant from a supplier.