Competitor Objection

"We're looking at a few other options" is one of the most common sentences in any sales conversation, and for a long time it had no name of its own. Without a name, reps handled it in one of two ways. Some read it as a polite no and let the conversation die. Others pulled up a feature comparison and listed everything the other product was missing. The first group walked away from buyers who had decided nothing yet. The second group ended up attacking the judgment of someone who had already chosen that product, and the room went cold.

The records had the same hole in them. Closed lost is the state a deal lands in when it falls through for good, and a reason field that says "went with a competitor" leaves nothing to act on next quarter. Which product won, on what grounds, and at which stage the deal turned are all missing. Twenty records like that tell you only that you lost twenty times.

Objection handling is the craft of answering the reasons a buyer gives for not moving forward, and this type sits apart from the others because the answer has a different shape. A price objection — stalling because the number feels high — is settled by working on the number or the case behind it. A timing objection — not now — is settled by pinning down a real date. Here the obstacle is neither money nor timing. It is an alternative that already exists.

Before answering, separate two situations: the buyer already runs that product, or they are still choosing. Migration cost attaches to the first case and not to the second, so two sentences that sound identical call for different work.

The conversation usually runs in five steps.

1. Ask which product. When no name comes back, there is often no real comparison happening and the sentence is a way of deferring the decision.
2. Find out whether they use it or are evaluating it. "We've been on it for three years" and "we saw a demo last week" describe walls of very different heights.
3. Ask what they like about it first. This is where the buyer's real criteria surface. Someone who talks about speed and someone who talks about approval workflows need different screens in the next meeting.
4. Put the two side by side, framed as which tool suits which conditions rather than which one wins. A five-person team drafting documents together and a 200-person company that needs per-team permissions may genuinely want different tools, and you can say that without dismissing the other product.
5. Ask whether sorting this out clears the way. A yes means you are working on the real obstacle. A second condition appearing right after means the comparison was the surface.

Step 3 explains why running down the competitor rarely works. A buyer who speaks well of a product has already made a judgment, and telling them that judgment is wrong sounds like telling them they are wrong. The move that does work is narrower: take what they like as given, and show where their own criteria point somewhere else.

With buyers it clusters in three places: right after a demo, during procurement review when someone asks for a side-by-side table, and in the weeks before a renewal when an existing customer mentions a proposal from someone else. The last one is the most urgent, and also the one where the usual math flips. This time your product is the incumbent, so switching cost is working for you instead of against you.

Inside the company, this objection is the raw material for sales collateral. A battlecard puts the agreed response to a competitor on a single page, and a battlecard built from anything other than sentences buyers actually said is a document nobody opens. Collect the comparison lines six reps heard last quarter and three or four of them will repeat. Agreeing on how to answer those three or four is what goes on the card. The same lines are worth reading back into lost-deal reviews, since a competitor that shows up in half of them is a product problem rather than a sales one.

"This one's a competitor objection — send me the current battlecard and I'll write the response."

The rep has already diagnosed what stalled the deal and plans to answer with the agreed language rather than improvise.

"What do you like best about the tool you're on now?"

A question that surfaces the buyer's criteria without attacking the other product.

"If we get that sorted, is this something you could move forward with this quarter?"

A check on whether the comparison is the real obstacle or cover for another one.

At Pagedeck, a 300-person account Sofia was working mentioned in the last meeting that they had been on a different collaboration tool for three years. Sofia asked what they liked about it, and the answer had nothing to do with features — people were simply used to it. So the next meeting brought a migration plan and a two-week window of running both tools in parallel instead of a comparison table. What stood in the way was the cost of moving, not the merits of either product.

The most common mistake is reading a competitor's name as a loss already taken. A buyer who knows enough to name one looks like a buyer who has made up their mind. The truth runs closer to the opposite. People who name their alternatives are usually still deciding, because that is when saying it serves a purpose; people who have truly decided mostly stop replying. Walking away here forfeits deals that were winnable, and the closed-lost record ends up documenting an attempt that never happened.

Counting features is the other one. Build the table and the number of checkmarks starts to look like the verdict, but buyers use a handful of rows in one corner of it and the rest never touches the decision. On top of that, hesitation from someone already running another tool often has nothing to do with capability and everything to do with the disruption of changing. That pull is common enough to have its own name, status quo bias. When you keep winning the table and losing the deal, this is usually why.