We were thirty minutes into a demo with a founder who ran a mid-size logistics company. The product was working. The demo was clean. Then she asked the question that undid months of internal pricing debate in a single sentence.
"How does this save me trucks?"
We had prepared answers about uptime, API calls, throughput. We had none about trucks.
That was the problem.
Before that call, our pricing reflected how we thought about our own costs. Usage tiers. Capacity bands. The kind of structure that made sense on a spreadsheet when you already understood the product inside out.
We had spent weeks modeling margins, running scenarios, arguing about whether the middle tier should include a certain threshold. Every conversation was internal. Every benchmark was ours.
The result was a price sheet that answered one question well: "What does it cost us to serve this customer?" It answered a different question poorly: "Why should this customer pay?"
Those are not the same question. We had been treating them as if they were.
The logistics founder did not measure her business in API calls. She measured it in trucks on the road, loads per week, and dead miles — the distance a truck drives empty between jobs. Her entire operation optimized for fewer dead miles. Every dollar she spent on software had to connect back to that number.
When she looked at our pricing page, she saw units that meant nothing to her. She wasn't hostile. She was confused. The value might have been real, but our price was denominated in a currency she didn't use.
This is common and easy to miss. When you build something, you describe it in the language of its construction. Requests. Seats. Gigabytes. Those terms feel precise. But precision in your units is not the same as clarity in the buyer's units.
After that call, we asked a different question: what does the buyer already track that our product improves?
We started calling prospects and asking the trucks question in reverse. Not "here's what you get for this price," but "what number matters most to your business right now?" Then we listened.
The answers varied. One company cared about time-to-first-response for inbound leads. Another cared about hours spent on manual reconciliation each week. A third cared about error rates in order processing.
None of them cared about our infrastructure units.
So we rebuilt the conversation. Instead of leading with what our tiers included, we led with the outcome. We asked the prospect to name the metric. We showed how the product moved that metric. Then we worked backward to a price that felt proportional to the gain.
We didn't throw away usage-based pricing entirely. The underlying model still reflected real costs. But the packaging — how the price was presented, justified, and discussed — now spoke in the buyer's language.
The effect was immediate.
Before the reframe, our sales cycle ran long. Prospects would take the demo, say positive things, then disappear into internal budget conversations we couldn't influence. We'd follow up. They'd ask for a breakdown of what each tier included. We'd send a comparison table. Silence.
After the reframe, conversations moved faster. When a prospect could connect our price to their own success metric, they could make the internal case without us in the room. The budget conversation still happened, but now the prospect had a sentence: "This costs X, and it reduces Y by Z." That sentence closed deals we used to lose.
We also noticed fewer pricing objections. Not because the price was lower — in some cases it was higher — but because the frame had shifted from cost to investment. A cost is something you minimize. An investment is something you evaluate against a return. Same number, different posture.
The lesson was not that our original pricing was wrong on the numbers. The margins were fine. The tiers were logical. The math worked.
The problem was alignment. We were asking buyers to do translation work — to take our units, convert them into their units, and then decide if the result justified the spend. Most of them never completed that translation. They just moved on.
Pricing is not a spreadsheet exercise you finish and publish. It is an ongoing conversation about what "worth it" means to the person holding the budget. That meaning shifts by company, by role, by quarter.
The founder who asked about trucks taught us something we now repeat internally: if you can't say the price in the buyer's language, you haven't finished pricing. You've just finished costing.
We still open sales conversations with a version of that question. "What number are you trying to move?" Sometimes the answer surprises us. Sometimes it reveals we're talking to the wrong buyer inside the company. Both outcomes are useful.
Pricing got simpler once we stopped treating it as a unilateral declaration and started treating it as a negotiation over shared definitions. The math still matters. But the math comes last.
Be the first to comment.
0 comments
Loading comments...