Stage 1

Objections that are really questions

Many objections in a reply are questions in disguise. How to hear what the buyer is really asking, the reply to send, and what not to say back.

Kevin French
· 3 min read

A lot of objections aren't objections. They're questions the buyer didn't want to ask directly. Answer the question and the objection usually goes away.

"We already have a partner for that." "We tried this before." "How is this different?" Sellers hear these as walls and reach for a rebuttal. But a buyer who took the time to reply is still in the conversation. They're telling you what they need to know before they'll take the next step.

Hear the question underneath

"We already have a partner for that" often means "why would I take a risk on you when I have someone who's fine?" The real question is about risk and switching cost, not about whether a partner exists.

"We tried this before and it didn't work" usually means "what would you do differently?" They aren't closing the door. They're asking you to prove you understand why it failed.

"How is this different from what everyone else does?" is the most literal one. They want a specific answer, not a positioning statement.

"Send me some information" can go either way. Sometimes it's a soft brush-off. Often it's a buyer asking "what's the one thing I should read?" since they don't want to commit to a call yet.

Say a CIO replies with the classic

You sent a note to a CIO at a regional logistics company. Your hypothesis was that their warehouse system upgrade had stalled on data migration. They reply with one line. "We've got an SI on this already."

That's the question in disguise. What they're asking is whether you're going to try to replace their incumbent, and whether you have anything to say that their SI doesn't.

Don't argue. Don't list your credentials. Answer the real question, and keep the door easy to walk through.

Makes sense, and I'm not trying to replace them. The question I'd ask is whether the migration piece is where they're strongest, or whether your team is carrying more of it than planned. If it's going fine, ignore me. If it's the part that keeps slipping, I can share how we've run data cutovers alongside a lead SI without stepping on their plan. Which is it?

It respects the incumbent. It names the likely gap. It gives them an easy way to say "it's fine" or "actually, yes."

What to avoid

Don't rebut. A rebuttal tells the buyer you didn't hear them. "But we're different..." is the fastest way to end a thread.

Don't overload. When a buyer asks a question, answer it in three or four sentences. A two-page reply with attachments buries the one thing they wanted.

Don't pretend the objection isn't there. If they say they tried it before, ask what went wrong. Don't skip to your pitch like they didn't mention it.

And don't fake agreement just to keep talking. If the incumbent really is doing a good job, say so and step back. Buyers remember the firm that was honest about not being needed. That's how you get the call six months later when things change. Turning a no into a later goes deeper on that.

Keep the guess alive

The best replies to an objection still carry a hypothesis. You're not just answering. You're offering a new guess they can correct.

"We tried this before" becomes a chance to guess why it failed. "We have a partner" becomes a chance to guess where the partner is thin. "How is this different" becomes a chance to name the one thing you'd do on day one that others wouldn't.

Each of those keeps the conversation inside the buyer's world instead of yours. And it gives them another easy, low-cost way to tell you what's really going on.

An objection is a buyer still talking. Treat it like a question, answer the real one, and let them correct you again.

See which of your accounts are moving.

Stage 1 reads your site, finds accounts that fit and checks their filings and news. Your first Board in about two minutes. Free for 14 days, no credit card.