How to handle the "you're too expensive" objection in B2B SaaS

Expensive is a comparative word. Every time a prospect uses it, there are two numbers in the room and you only put one of them there.

The other one arrived weeks before you did. You're not being asked to justify $60,000. You're being asked to justify $60,000 against something the buyer already decided was the right thing to measure you by, and nobody consulted you while they decided it.

So the answer, stated flat. You win the price conversation by owning what your price gets compared to, and nearly all of that work happens in the messaging and on the pricing page, long before anyone says a number out loud.

The advice that treats the symptom

The received wisdom on price objections is decent, and we've all been handed the list. Don't discount on reflex. Quantify the return. Ask what else they're evaluating. Get the person who actually owns the budget into the room. Teams that do all four hold price better than teams that fold, and that's real.

Every one of those moves assumes the comparison is fair.

Quantify the return and we still have to divide by something. If a buyer has already filed us next to a $9,000 tool, a rigorous ROI case turns us into a $9,000 tool with an unusually good spreadsheet. Ask what else they're evaluating and we get an answer that's already been edited. Most buyers will name the vendors. Almost nobody volunteers the internal workaround, the headcount they'd rather hire, or the number a peer quoted them over drinks at a conference in April.

We drill the objection handling and skip the thing that set it up. "Too expensive" surfaces in a pricing conversation, so we go hunting for the cause in a pricing conversation. Where a problem surfaces and where it was made are usually two different rooms.

The lost-ticket rate

Lose your ticket in an airport parking garage and you pay the maximum daily rate. Nobody thinks you were there nine days. In the absence of your evidence, the posted default applies, and the posted default was never written with you in mind.

Call that the lost-ticket rate. It's the number we get measured against when we didn't supply a comparison of our own.

There's nothing unfair about it. A careful person working from incomplete information needs a reference point to make any judgment at all, and if we haven't handed them one, they'll reach for the nearest thing available. The buyer who says we're too expensive has usually done more homework than the one who says nothing. They built a comparison set. We weren't in the room while they built it.

How do buyers decide what your price should be?

Mostly without us.

Gartner's March 2026 survey of 646 B2B buyers found that 67% say they prefer a rep-free buying experience. Two thirds of the people who will eventually push back on price are forming their view of it in tabs we can't see. On review sites. On somebody else's comparison page. In a Slack channel where a peer types "we pay about forty for ours" and that becomes the number.

The mechanism is old and unusually well established. Tversky and Kahneman's work on anchoring, published in Science in 1974, showed that an initial reference point pulls final judgments toward it even when the anchor is arbitrary. It still holds because it describes how human judgment works rather than how a market happened to behave in one decade.

The first credible number a buyer meets in a category sets the gravity for every number after it, ours included. Which is why the pricing page is doing more work than most teams give it credit for, and why keeping price off that page hands the job of setting the anchor to somebody else.

The three prices you're already being compared to

When we don't supply a comparison, buyers reach for one of three. They're predictable enough that you can write against them by name.

The first is the category floor. Whatever the cheapest credible product with a public price charges becomes what "normal" means in a category, including for buyers who would never seriously consider it. A $48,000 API monitoring platform gets read against the $12,000 one, because the $12,000 one publishes.

The second is a headcount. Buyers convert software into salary, because salary is the unit they think in and the unit their approval process runs on. "That's most of a junior analyst" has ended more deals than any competitor's feature grid.

The third is doing nothing. The spreadsheet, the two contractors, the process somebody rigged up in 2023 that mostly works. This is the comparison that wins most often and the one almost no pricing conversation names out loud, which is why the status quo is so hard to sell against.

Only one of the three is a competitor. Nearly all of our objection handling was built for that one.

What a discount actually concedes

Taking twenty percent off is agreement. It accepts that the number was the problem and the comparison was sound, and it walks us closer to a reference price we never chose. The buyer's model of the category survives the negotiation completely intact, now carrying our signature.

We take the twenty because the quarter is closing and the deal is real, and that's a defensible thing to do once. The trouble is what it buys. A discount makes us a slightly cheaper version of the thing they were already comparing us to, which is not the same as creating room in a budget that's already full.

And it is already full. SaaS Capital's 2026 spending benchmark survey, published in June and covering more than 1,000 private B2B SaaS companies, found total median spend across all departments running at 96% of annual recurring revenue for bootstrapped companies and 101% for equity-backed ones. There's no unallocated pile waiting to be discovered. Our price is competing with something already funded, and the buyer knows precisely what it is.

Then the renewal arrives, and the discounted number is the new anchor.

Where the comparison belongs

Earlier than feels natural. We tend to load the comparison into the sales deck, which is the last place it can still do any work.

Name the alternative you want to be measured against, in your own words, on the pages a buyer reads before they ever fill in a form. Frame it as the situation that makes the purchase make sense, rather than as a swipe at a competitor.

A $5M ARR company selling incident-response tooling can lead its pricing page with tiers and seat counts, or it can lead with a line like "most teams find us after the second outage nobody could explain." The second version sets the comparison at a four-hour war room with six engineers in it. The first version sets the comparison at everything else that has tiers and seat counts.

An exercise worth an afternoon. Write down the number you want a buyer holding in their head at the moment they see your price. Then read the homepage and the pricing page and ask whether either one puts that number there. Most category pages fail this quietly, because they describe what the product is instead of what its absence costs.

This is pricing work, and it belongs with the people who own pricing and packaging, not with whoever happens to be on the call when the objection lands.

What to say when the objection has already landed

Sometimes it lands anyway. Then the move is to find the comparison before defending anything.

"Compared to what?" is the right question in the wrong phrasing, because it sounds like a challenge. Try something closer to "when you say expensive, what number were you holding when you walked in?" It gets the same information and reads as curiosity. Buyers usually answer, because they've been carrying that number a while and nobody has asked for it.

Once you have it, resist the urge to correct it. Argue about the category instead of the amount. If they're holding the category floor, the useful question is what happens the third time the cheap tool misses the thing it was bought to catch. If they're holding a headcount, ask what that person would spend their first quarter doing, and whether anyone has that quarter to give. If they're holding the status quo, put a number on the status quo out loud, since nobody in the building has ever done it and the number is usually bigger than ours. The same instinct applies when the comparison is a named rival, which we've covered in what to say when a prospect calls you a worse version of someone else.

And if it turns out to be a genuine budget-cycle problem, discount it, close it, and go fix the page that let the comparison get set without us.

The garage reads what you hand it, and nothing else.

Hand them the ticket.

What to Do Next

If you're priced above your category average and every deal turns into a defense of the number, the fight is happening downstream of the actual problem. The comparison got set somewhere in the messaging, or it got set by default because the messaging declined to.

A Bare Strategy positioning audit names the comparison your price should be measured against and rewrites the messaging and the pricing page so buyers show up already holding it.

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