How to win a competitive deal when you're not the market leader

Most competitive deals are scored on a list nobody wrote for this buyer.

It came from the last evaluation the company ran, or from an early call with the incumbent, or from an analyst grid somebody found while searching. By the time we get invited, the list is finished, and the questions on it are the questions the market leader answers best.

Call it the inherited scorecard. Every competitive deal has one.

We show up and try to score higher on it. That isn't the job. The job is adding a line to the list, honestly, where the buyer's real problem lives and our answer is genuinely better.

The inherited scorecard

Under every feature on that list is an outcome somebody is actually chasing. Discovery is where we find it.

A buyer arrives with a matrix covering integrations, reporting, and user management. All real, all table stakes, all quietly tilted toward the more mature product.

Ask enough questions and the thing underneath turns out to be that the last rollout dragged on so long the executive who sponsored it stopped showing up to the status meeting.

So we add the criterion nobody put on the list. Time from signature to the first workflow running in production. We win on that line, and it's a line the incumbent would rather not have measured.

The way in is plain. Something like this.

"Teams your size usually find that time to value bites harder than feature depth. Worth putting implementation timeline on the list, because the spread between vendors is wide."

Buyers accept it because it's true for them. We're not inventing an advantage, we're naming a dimension where their pain is real and our answer holds up.

The best version of this leaves them thinking they should have been measuring it all along. More on building the advantages that make it possible in competitive positioning for SaaS companies.

Questions we can answer

A landmine question is one we suggest the buyer ask the other vendor.

Nothing about it is adversarial. We're handing over the questions we'd ask if it were our money, and we're doing it because those answers are hard to dress up.

Two areas repay it most. The first is total cost, because the sticker price is the least interesting number in any proposal.

Implementation fees, required services, the engineering weeks the integration eats, the admin load after go-live. Market leaders often price the license low and make it back everywhere else.

The second is recent references. Ask for customers who went live in the last year, and ask what onboarding was actually like rather than whether they like the product.

A leader's favorite references usually came aboard when the install base was small and somebody senior answered the phone.

One rule governs the whole move. Never plant a question we can't answer ourselves. Suggest they ask about implementation timelines when ours is embarrassing and we've handed the deal away with both hands.

The reference we choose

Deals flip on reference calls, and almost never because the reference said something bad.

The buyer asked an open question, got a careful answer, and filled the silence with their own doubt. That's the whole failure.

The words on that call are the customer's own. Our control sits one step earlier, in which customer we put on the phone and whether both sides know why they're on it.

Match the reference to the situation. Same size, same shape of problem.

Then brief them. Here's who's calling, here's what they're worried about.

Set the frame for the buyer too, before the introduction goes out. They were where you are, they looked at the same alternatives, and the thing they didn't expect after go-live was this. Now both people know what the call is for.

If the incumbent is putting up a marquee logo, say so early. Their use case and this buyer's are different, and it's worth holding that difference in mind while listening. No attack required.

Demos in the wrong order

Most demos are tours. Here's the dashboard, here's the integrations page.

A tour is fine when nobody else is in the room. In a competitive evaluation it burns the best hour we'll ever get.

Sequence backward from where the incumbent is weakest, then lead with those areas framed as answers to problems the buyer named out loud.

We never say the competitor can't do this. We say the thing you mentioned about approvals comes up constantly, and here's how it works here. The contrast assembles itself in their head, which is the only place it counts.

Use their words while we do it. They told us what they cared about in discovery. Hearing their own phrasing come back inside a walkthrough is the clearest signal that somebody was listening.

Show the things that are hard to show. If configuration is faster, configure it live and put a clock on it. If the workflow needs no developer, build one on the call.

A gap described on a slide closes nothing. A gap the buyer watches happen does. More on making that contrast repeatable across a team in how to build competitive battlecards that actually get used.

Alerts nobody opens

Then there's the buyer who says they already have something that does most of this.

The reflex is to list what the current tool doesn't do. What they hear is that we want them to tear out something that works and pay for the privilege.

Look at your phone. Some app has a badge on it with a number you stopped reading months ago. Everything behind it still matters, and it stopped arriving as information anyway.

The workaround this buyer built two years ago is that badge. The spreadsheet somebody rebuilds every Monday. The two people who reconcile an export by hand every close.

Nobody sees it anymore. It's the weather.

So we don't add another alert to a screen full of them. We ask what outcomes they aren't getting, and then we make them count it.

How many hours a week go into the part the current tool doesn't handle, and where does that leave them if it's still true eighteen months from now? If nobody in the room can name a missing outcome, the deal isn't real, and we've saved a quarter finding out.

The buttons moved

Every switching conversation is really about relearning.

An app updates overnight and moves the buttons. The new version is better by every measure its makers can publish, and for a week we're furious, hunting for the thing we used to hit without looking.

That's what the buyer is defending. Their team knows where everything is, and every hour of not knowing has a cost with a name on it.

Which is why we say the switching cost out loud before they do. Name what the first month looks like, who has to be in the room, what breaks.

A cost we name is a cost we're managing. A cost they raise is a cost we spend the rest of the deal defending.

The same discipline holds when the leader cuts their price, which they will the moment they know we're in the deal. If the evaluation has been running on outcomes, the question becomes whether the outcome difference is worth the price difference.

Discount to win and we've set the number for every renewal after it. When we do have to move, trade for something. An earlier close date, or a case study they've already agreed to.

On playing offense from behind without sounding desperate, see startup vs. competitor positioning.

The losses we don't read

Win rates move when we read the losses honestly, and almost nobody does.

The CRM dropdown says price, because price is what buyers say when they want the call to be over. The real answer usually sits further back. We arrived after the list was written, or we ran the entire evaluation on the incumbent's terms and never noticed we were doing it.

So talk to one lost buyer a month. A real conversation, not a survey. Ask what the criteria looked like the day we showed up, and ask who put them there.

Somebody wrote that list, and it was never us.

Ask to see it. Then add a line.

What to do next

If deals keep getting scored on criteria we never helped set, the fix sits upstream of the sales team.

A Bare Strategy positioning audit finds the dimensions where you genuinely win, then rebuilds the story so those dimensions reach buyers early, while the list is still being written.

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