What to say when a prospect calls you "just like [competitor], but worse"

Thirty-one minutes into the demo, the VP of engineering says it.

"So this is basically [the market leader], but worse."

The rep does the natural thing. Starts listing differences. Cheaper at this data volume. An agent that installs in one command. No per-host pricing.

All true. All losing.

The answer to "you're just like [competitor], but worse" is to decline to answer inside that comparison, say so out loud, and name the comparison you'd rather be measured on instead. Arguing the details confirms the frame. Even when we win the exchange, we've just spent ten minutes agreeing that the other company is the measuring stick and we're the thing being held up against it.

We treat this as an objection to handle. It's a frame to refuse.

Why does arguing a competitor comparison lose the deal?

Whatever gets named first in a judgment drags everything after it toward itself.

Amos Tversky and Daniel Kahneman named that effect in 1974, in a Science paper on judgment under uncertainty. People asked to estimate a quantity they couldn't know landed near whatever number had just been put in front of them, even when that number came from a spin of a wheel in the room. "We call this phenomenon anchoring." The finding is fifty-two years old and it still holds, because it describes how human judgment forms rather than how a market happened to behave that year.

What matters for a sales call is what happens when you argue with an anchor.

Adjustment starts from the anchor. So every counterpoint is measured against the competitor, phrased in the competitor's vocabulary, scored on rows the competitor's marketing team wrote. Cheaper than them. Faster than them. Easier than them. Three sentences in, the prospect has heard that name five times and yours twice.

The rep who wins the feature argument and loses the deal isn't unlucky. They did the thing that felt like defending, and it functioned as agreeing.

What "worse" is standing in for

The most common mistake is hearing "worse" as a statement about the product. It's almost always a statement about risk.

Sometimes it means "this is harder for me to defend." Nobody has to write a memo justifying the obvious choice, and the person in the demo knows exactly how the conversation upstairs will go if they push for the smaller vendor and something breaks in March.

Sometimes it means the budget line already has a name on it, and that name isn't ours. The comparison explains why a purchase order would need rewriting.

And sometimes it means a boss, a board member, or a former colleague said something once, and the prospect is repeating a half-remembered opinion they never held strongly enough to examine. That one sounds identical to the other two from across the table.

None of these get resolved by a feature table. We keep answering a product question that nobody asked. That's also how a deal quietly becomes a loss to indecision rather than to a competitor, which is a different and more common ending than losing a bake-off.

They arrive already anchored

The sentence isn't invented mid-call. It usually arrives fully formed, because the comparison already ran without us.

G2's 2026 buyer behavior report found that 82% of buyers had sourced software recommendations from an AI chatbot in the past two years, and half of those buyers said AI mattered most when they were narrowing and comparing options. The same 2026 research found that evaluation has become the longest stage of the buying journey, surpassing research for the first time.

Read that as a sequencing change, not a channel change. Something summarized our category, put us next to the leader, and produced a one-line verdict. Then a person carried that verdict into the meeting.

Which means the frame is set before anyone opens a deck. If our public language reads as a variant of the leader's language, the summarizing layer will compress us into exactly that, and the rep inherits the compression thirty-one minutes into a call.

The reset, in three moves

Say the comparison out loud before you do anything else. Flat, no defense in it. "You're right that we come up in the same searches, and plenty of teams look at both of us." Naming an anchor takes the pressure out of it. Pretending you didn't hear it leaves it sitting on the table for the rest of the hour.

Then refuse to argue it, explicitly. "I'm not going to try to talk you out of that comparison." This is the move that feels wrong and is the whole point. A rep who declines the fight signals that the fight is beneath the actual decision.

Then change what's being compared. Put a different measuring stick on the table and hand the prospect the next move on it.

The losing version, at a hypothetical $12M ARR observability company.

"So this is basically [the market leader], but worse." "Actually we handle high-cardinality data much better, and we're cheaper at your volume." "Sure, but they have the integrations we already use."

Twelve minutes gone, inside a spreadsheet we didn't write.

Now the reset.

"So this is basically [the market leader], but worse." "Fair. We show up in the same searches, and if you line us up row by row they'll win some of those rows. I'm not going to try to talk you out of that. The teams that pick us usually aren't deciding on that list. They come to us because their on-call engineers had stopped trusting their alerts, and a month in, the alerts got quiet enough to act on again. Is that a problem you have?"

The question at the end is load-bearing. Without it the reframe is a speech. With it, the prospect starts describing their own situation on an axis where the competitor's row count is irrelevant.

Try it on a deal you've already half-lost, where there's nothing left to protect. It takes a few calls before it stops feeling like dodging.

When the rebuttal isn't the problem

Here's the test. Say your comparison axis out loud, right now, in one sentence, without opening a document.

If you can't, no script survives contact with the call. The rep is improvising a frame under time pressure against a competitor with a marketing team, and improvised frames default to the loudest one in the room. Battlecards don't fix that either, because a battlecard organized around the competitor's claims teaches the whole team to think in their categories.

That's a positioning job, not an enablement job. The axis has to exist, be true, be narrow enough to lose deals on, and be something a smaller company can actually hold against a larger one. Most teams have four candidate axes and no decision, which is the same as having none.

The measuring stick

Nobody in that room chose the standard you were judged against. It got chosen somewhere else, months earlier, by a market and a machine and a competitor's content team.

You can't win on a stick you didn't cut.

Bring your own.

What to Do Next

If you've been mid-demo, hearing your product described as a cheaper version of someone else's, and you've answered by defending features on their terms, the problem sits upstream of the rep and the rebuttal. The company hasn't decided what it wants to be compared on, so the market decided for you.

A Bare Strategy positioning audit fixes that upstream. We name the axis you can defend, rebuild the language around it, and rewrite the public-facing copy that the comparison engines are reading before a buyer ever books a call.

If that's where you are, start here. The first conversation is free.