The buyer can't defend the number

Price objections aren’t always price problems.

Sometimes the buyer genuinely can’t afford it. Sometimes the product isn’t important enough. Sometimes procurement is doing procurement.

But often the buyer is telling you something else:

I’m not certain enough to defend this internally.

That’s a different problem. It means the rep doesn’t only need to discount, justify, or explain the line item. They need to help the buyer get clearer on the value, the risk, the trade-off, and the story they’ll have to carry to someone else.

The deal can look healthy right up until pricing goes out. The champion loved the product. The demo landed. Then you send the proposal and hear nothing for two weeks. When they come back, it’s “we need to revisit the numbers” or “there’s been some pushback internally.”

You cut 15%. Nothing moves. You throw in an extra module. Still stuck.

This isn’t always a budget problem. It’s often a commercial certainty problem. Discounting won’t fix it if the buyer can’t defend the number, not at list price and not at 15% off either.

A technical win and a commercial win are different milestones

In any deal of reasonable complexity, there are two distinct milestones before close: the technical win and the commercial win. Treating them as one event, or failing to separate them, is where false pipeline confidence comes from.

A technical win means the buyer believes the product can solve the problem. The demo made sense. The team liked the features. The champion can see how it would help.

A commercial win is different. It means pricing has been discussed, the value case is progressing, and there’s a path to agreement on terms, usually with the economic buyer or finance in the loop.

These can sit weeks apart. A deal can have a strong technical win and still be months from closing if the commercial conversation hasn’t really started. When pricing gets hard, it’s often because you’ve got the first without the second.

In pipeline review, ask two separate questions:

1. Do they believe we can solve the problem?
2. Is there a path to agreement on terms?

If the answer to either is no, the deal shouldn’t be in a late-stage commit category, regardless of how positive the demo feedback was.

Value needs a baseline before price makes sense

Pricing conversations get vague when value is vague.

If the rep says the product saves time, the buyer has to decide how much time, whose time, what that time is worth, and whether the number is credible. If the rep says the product reduces risk, the buyer has to decide which risk, how often it happens, what it costs, and who cares.

The conversation gets better when there’s a shared baseline:

• What happens today?
• How often does it happen?
• What does it cost when it happens?
• Who feels that cost?
• What would be different if the issue was fixed?

That doesn’t require fake precision. It requires a shared model, built in conversation, not assumed in a spreadsheet.

The rep doesn’t need every number ready before the call. Often it’s better to build the estimate with the buyer:

If we were trying to put a rough number around this, what would you count? Time saved? Leakage reduced? Deals protected? Manager hours? Implementation risk?

That question helps the buyer reveal what value means in their world, and avoids pretending the rep knows more about their business than they do.

Certainty is built with the buyer, not presented at them

The temptation is to build a polished ROI deck, send it after the demo, and hope the numbers do the work. That rarely survives internal scrutiny. Finance teams are right to treat vendor-built models as assertions. Procurement teams discount them. Champions can’t walk into a budget conversation carrying your marketing maths and expect it to land.

The shift that helps is simple: stop presenting a case and start building one together.

You bring what you know from similar customers. They bring what they know about their current process, their costs, their constraints. You work through the baseline, the expected improvement, and the assumptions out loud. When the numbers come from that conversation, the champion isn’t forwarding your brochure. They’re presenting analysis they helped shape.

When a prospect says “I need to run the numbers on my end,” that’s often a polite way of saying they don’t yet have a case they trust:

We’ve got benchmarks from similar businesses. Can we spend an hour mapping them against your current process costs? I’d rather we build the business case together than hand you a model.

That changes the dynamic. The buyer becomes a co-author of the justification, not a recipient of it. When it hits internal scrutiny, they’re defending something they helped construct.

The pushback usually happens in a room you’re not in

Late-stage pricing friction is often less about the sticker price and more about whether the champion can survive the next internal conversation.

Once finance or procurement gets involved, the frame shifts. “Does this product work?” becomes “Can we defend this spend?” Those are different questions, and many champions aren’t ready for the second one. They can explain why they liked the demo. They struggle to explain payback, cost of inaction, implementation risk, and why this option beats doing nothing or buying something cheaper.

That pattern shows up everywhere in complex B2B buying, not just in one pricing model or one industry. The champion needs a short internal story that answers questions a CFO or budget holder will actually ask:

• What does the current state cost us, in time, risk, or missed outcome?
• Why change now rather than next quarter?
• What payback period are we assuming, and where did that number come from?
• What happens if adoption is slower than planned?

If the champion can’t answer those without you in the room, the deal isn’t really at pricing yet. It’s still at proof.

When a buyer asks you to “just send pricing so I can share it internally,” treat that as an enablement moment, not a fulfilment request. They often need help preparing for the conversation they’re about to walk into, not a PDF with a number at the bottom.

Discounting can hide the real problem

Discounting is sometimes the right move. But it shouldn’t be the first move when the commercial case is weak.

If the buyer is uncertain, a lower price may make the deal feel easier for a moment. It doesn’t necessarily make the project more important, less risky, or easier to defend. If they can’t defend the number at full price, they often can’t defend it at 15% off either. You haven’t made the case stronger. You’ve made the margin thinner.

The better manager question is:

What would make the buyer more certain this is worth doing?

The answer might be a customer reference in a similar context. A clearer business case the champion can own. A narrower starting scope. Involving the economic buyer earlier. Showing what implementation actually requires, including what happens if rollout is slower than planned.

Those are sales moves. “Can we do 15 percent off?” isn’t always the move.

What to inspect before pricing goes out

Before a proposal leaves your hands, run this check. Not after the objection. Before the proposal.

If those answers are missing, the price may land as a number without a case.

Pricing isn’t just a commercial detail at the end of the process. It’s a test of whether the value has been made concrete enough to travel through the buyer’s business.

The standard worth holding: pricing should confirm a commercial case already made, not start one. When price becomes the whole conversation, go back to certainty.