Insights

Justify the Sale on the Customer’s Numbers, Not Yours

Buyers have more information than ever and less patience. They can compare your pricing with three competitors in ten minutes. What they can’t easily get is an answer to the question that drives the decision: what will this do for my business, in dollars, and when?

Salespeople who answer that question win meetings, hold price, and close deals that feature-and-benefit pitches leave stalled. Here are the practices that make it work.

1. Start with what’s in it for them

Nobody cares that it’s your quarter-end. Buyers care about lower costs, higher revenue, and less risk. Value justification means quantifying those outcomes in the buyer’s terms, so they see the economic effect of your product and not only its features.

“We reduce downtime” is a feature claim. The buyer’s real question is “what does that mean to me?” Downtime means stopped machines, late inventory, empty shelves, and competitors taking the order. Follow your benefit down that chain until it lands on a number the buyer already tracks.

2. Make the numbers theirs

If the figures come from your brochure, the buyer discounts them. If they come from the buyer, the buyer defends them. You also avoid the “who are you to tell me about my industry?” objection.

The trick is asking questions people can actually answer. Ask a technician manager, “What’s your annual technician labor cost?” and you’ll likely get a brush-off. Ask, “How many technicians do you have?” and they answer immediately. Multiply by an industry-average hourly rate and you’ve rebuilt the cost figure without making them do the work. You also look prepared.

So break every big number into parts:

  • Split the cost into components, such as headcount × rate × hours.
  • Use published averages for the parts nobody should have to look up.
  • Ask only for what the person in front of you knows firsthand.

This takes homework. You need enough knowledge going in to know which components exist.

3. Prove it instead of claiming it

When a customer disputes a savings estimate, a live before-and-after beats any slide. A software vendor claimed a 20% time savings on keeping industrial-controller software backed up and current, and buyers pushed back. The fix was a demonstration on site. The employee who owned the task backed up 20 machines by hand, which took about 20 minutes. Then the vendor did the same with its product, which took seconds. Extrapolated across 1,400 machines, the argument became arithmetic.

Demonstrate on the customer’s own process, with their own people, whenever you can. It’s far more persuasive than describing results from somebody else’s company. It also surfaces concerns early. In that demo, the employee joked the tool might eliminate his job. That’s worth hearing before the contract stage.

4. Find the costs they haven’t counted

Most buyers undercount what your product touches. In a training workshop, a document-management vendor’s regional managers were asked to break out “cost of paper.” The answers were:

  • the paper itself
  • the real estate to store it, which adds up fast at downtown rents
  • call-center staff leaving their chairs to pull files that are sometimes missing
  • longer hold times, which affect customer retention

Each was a separate line item the buyer hadn’t linked to the purchase. In one reported case, a stalled $100,000 deal grew to $500,000 after the rep went back and presented the broader impact.

Try this yourself. Pick your main benefit, ask five colleagues what it means to them, and you’ll get five different answers. Each is a candidate value category to explore with a customer.

5. Remember that timing is part of ROI

Getting $100,000 back on a $100,000 investment isn’t “100% ROI.” It’s break-even. What matters is when the money returns, because earlier cash is worth more than later cash.

Two ideas help here:

  • Net present value (NPV) discounts future benefits to today’s dollars. It shows what a decision made now is worth over the life of the investment, including benefits that continue after payback.
  • Cost of delay. If a project is worth a certain amount per month, every month of waiting costs that amount. When a CFO says, “Let’s wait six months,” you can answer, “Fine, here’s what the wait costs.”

The cost of delay also reframes your real competitor. Often it’s not another vendor. It’s the decision to do nothing, or a pre-budgeted project already in the plan. If you can show your project’s NPV is double that of the one holding the budget, you give the buyer a reason to move the money.

Check your model’s basics before the CFO does. In one story, a Fortune 100 CFO found that a rep’s model omitted taxes. Once it was corrected, the rep’s credibility went up, not down. Make sure the model also updates when assumptions change. If implementation slips from July to September, the benefits timeline should shift automatically, not require rebuilding.

6. Sell to everyone who benefits

Fixating on one champion is risky. In one engagement, the real decision-maker turned out to be a VP of engineering, and the rep only found that out by walking the floor and asking about downtime, inventory, and expensive parts scattered around. Another vendor had focused on IT contacts until it learned that finance and manufacturing felt the benefits too.

Map every function that gains from your solution and interview each one, with its own numbers.

If a mid-level manager wants to control access so they get the credit, let them. Say, “You tell me the best way to present this.” If they’re unwilling to take that offer, you may be talking to the wrong person. And if you can never get in front of someone with budget authority, treat that as information about the deal.

7. Treat price as one input

Discounting assumes price is what decides. Often it isn’t. A $100,000 product delivering $20 million in operational value beats an otherwise identical $50,000 product delivering $1 million. Once the buyer’s gain dwarfs your price, the discount conversation shrinks.

It works in the other direction too. Companies sometimes underprice because they treat their value as soft or intangible. One security vendor reportedly quantified its value, found it was underselling, and raised prices, after which sales improved. A price far below the value signals that something might be wrong with the product.

8. Qualify out early

A deal that won’t close consumes time that could go to one that will. Warning signs:

  • The prospect asks endless questions about your product but won’t answer any about their business.
  • You can’t get access to anyone with real authority.
  • Nobody can supply basic operating data, like uptime or volumes.
  • The numbers show the customer wouldn’t earn a return big enough to justify buying.

Walking away isn’t failure. It’s good use of your time, and it protects your credibility with customers who are a genuine fit.

A quick checklist

  1. List the customer’s three biggest economic outcomes in their language.
  2. Break each into components they can answer.
  3. Prepare industry averages for the rest.
  4. Plan a demonstration on their process.
  5. Map every function that benefits and interview each.
  6. Calculate the cost of waiting.
  7. Test your model for missing basics, such as taxes and timing.
  8. Decide in advance what would make you walk away.

Value-based selling isn’t a trick. It’s the habit of understanding the customer’s economics well enough to show them something they didn’t know about their own business. That is what earns the right to be called an advisor and not just a vendor.