"Their price is 30% lower": five talk tracks that do not start with a discount

Four objections in one sentence

A buyer who says a competitor is cheaper has told you a number and nothing else. Behind it sits one of four situations.

The first is a true like-for-like gap: same seats, same scope, same term, and their quote is lower. The second is a scope mismatch: the quotes do not cover the same thing, and the buyer has not noticed. The third is a negotiating move: the buyer prefers you and is testing whether the price moves. The fourth is a proxy: the buyer is worried about risk, or the project was never funded at your number, and "cheaper" is the easiest thing to say.

A reflexive discount answers only the first case, and answers it before the rep has confirmed it is the first case.

Hold the number until the question is answered. Sandler's advice on price objections, in a post on its blog, is that the best way to handle them is to stop them arising at the close, by dealing with every money question early. That is a sales-training firm's advice, and it holds as a sequencing rule: a rep who knows what the competitor's quote covers before the final call is not ambushed by its total.

What the research does and does not say

The published evidence on competitive deals is vendor research, and none of it tells a rep what to say. It does say something about timing and about the arithmetic of a discount.

Gong Labs, analysing its own call data in a 2017 study updated in March 2026, found that deals with a competitive discussion early in the cycle (prospecting, discovery, first demos) had a 49% greater chance of closing than deals with no competitor, while deals where the competitor came up late had a slightly lower probability of closing than greenfield deals. Late-stage competitive deals were also smaller, which Gong reads as reps discounting to beat a competitor they failed to pre-empt; that is Gong's inference, not a measured discount rate, and the page states no sample size. Gong's 2024 roundup, published in January 2025, adds that competitive mentions per deal rose 57% since 2022 and that an early mention raises the odds of winning an enterprise deal by 32% over not discussing the competition at all. Neither page carries discount data newer than 2017.

The discount arithmetic comes from Winning by Design. Their November 2022 paper on the relationship between discount and win rate models a team with a 20% win rate and a $20,000 list price. To hold revenue after a 20% discount, the win rate has to rise from 1 in 5 to 1 in 4; a 35% discount needs 1 in 3; even a 10% discount needs the rate to move from 20% to 22%. Those numbers are a scenario model, not observed field data, and the paper says so. They put a target on the discount: if you cannot name the extra deals it will win, it costs money.

So the evidence supports two moves: raise the competitor early, before the buyer does, and treat a discount as a bet with a stated payoff.

Five talk tracks

Each track below has the weak answer a rep gives under pressure, a stronger one, and the comeback to expect. The wording is ours, written for this lesson and untested with buyers; only the principle at the end of each card is sourced. Adjust the words to your product, keep the shape.

A good track starts with a question and pairs every concession with a counter-ask. A bad one opens with a number, or with "we are worth it" and no buyer-stated outcome to hang it on.

To rehearse, paste an anonymised excerpt of a real call into a plain Claude chat and ask for the buyer's most likely comeback to each stronger answer. It is a rehearsal partner; nothing a model says is evidence of how a buyer will react.

When price really is the reason

Sometimes the sorting question comes back clean: same seats, same term, same scope, and the buyer sees the two products as interchangeable, so nothing in tracks 2 or 3 lands. Price is then the real criterion.

No talk track changes that. The honest move is to say so to the deal desk, with the like-for-like comparison attached, and let whoever owns pricing decide whether this deal is worth a lower number. This lesson offers no discount policy, because none of the sources carry one. What the rep owes the deal desk is the classification: case one, the proof, and what the buyer said when asked about budget and risk.

A commodity position is a product and positioning problem, and a rep cannot talk a buyer out of it on one call. A like-for-like loss that keeps recurring belongs in the next win/loss review, not the next discount request.

Trade, do not discount

When something has to move, trade it. Winning by Design's blueprint puts the rule plainly: never give something away without getting something in return. The counter-asks worth having ready before the call:

• A longer term: two or three years at a lower annual price.
• Payment up front, or annual instead of monthly billing.
• A smaller first phase: fewer seats or one team, at the full per-unit price, with a dated expansion review.
• A later start date that fits your capacity, in exchange for the current price.
• A reference call, a case study or a logo on your site, once the buyer is live.
• Scope removed from the quote: a module, a service tier or an integration the buyer does not need yet.

Each item changes what the buyer gets, so the per-unit price holds. A buyer who wants the lower price without any of them has told you the objection is a negotiating move, and the structure holds.

Log the objection so the card improves

Every time a rep hears "they are cheaper", write down which of the four it turned out to be, which track was used, what the buyer said back, and how the deal ended. That log supplies the real wording this lesson cannot. After a quarter it shows which comebacks occur, which competitor's quotes hide a scope gap, and whether the like-for-like case is rare or routine.

The log feeds two other jobs. The card, built one objection at a time as in battlecards sales actually uses, gets a proof point and a rebuttal from real calls; the loop from a rep's objection back to a card revision is in battlecard feedback. The win/loss review gets a check on its loss reasons: a CRM field that says "price" on every lost deal is the problem covered in win/loss versus the CRM, and the objection log says which of those losses were about price. Checking the "30% lower" claim against the competitor's actual list price is the job of competitor pricing analysis.

Where Steve fits

Two things here go stale by hand: the objection card, and knowing which competitor is in the deal before the call. The DIY fix is the shared log above, a rep who asks the PMM, and a dated read of the competitor's pricing page.

Steve covers the same gap narrowly. Its battle cards include an Objections template among six, and buyer themes from Steve's win/loss interviews land in the card's Objection Handling block for the PMM to review. A rep who asks a competitive question in Slack gets back your messaging, cited to the card and a real call; Steve drafts suggested updates, and a person approves them. On HubSpot and Salesforce deals it suggests the competitor for a person to approve, and it syncs nightly. Card updates are drafted and flagged for review. If the card and the competitor-per-deal are the parts that lapse, see Steve Win/Loss.