Sell the job, not the ROI.

The number that does not land

For years I reached for the big number. I ran a marketplace where I could see exactly what made buyers move, and I still stood in front of them with the whole future case: the volume, the savings, three years of it summed up and impressive. It almost never moved the deal. What moved it was one small thing the buyer could already feel was true that day.

I had it backwards, and so do most of the technical founders I talk to about pricing. They reach for the big number: the downtime avoided, the yield gained, the risk reduced, summed over three years across the whole company. It is an impressive slide. It almost never closes the deal.

Because that number lives in the future, and it belongs to the buyer, not to you. To believe it, they have to accept your model of their business: your assumptions, your baseline, your timeline. Any one of those is arguable, and a cautious buyer will argue all of them, or simply nod and not move.

The buyer pays for the job, not the projection

People do not buy a projection. They buy a job getting done. The value metric that sells is the one thing your product does now, named in the buyer’s language, with a number they already believe because it is theirs: the report that took a day now takes an hour; the call that needed you now runs without you; the thing that broke twice a month stops.

The honest, near-term number beats the impressive, distant one whenever the buyer has to choose between them.

Why founders reach for the big number anyway

It is not foolishness. The big number feels safer. It justifies a higher price, it sounds strategic, and it lets you dodge the harder question: what is the one job worth, plainly, today. Naming that is exposing. It is smaller than you want it to be, and it invites the buyer to say “that is not worth much.” But a small number the buyer trusts is worth more than a large one they doubt, because only one of them reaches a yes.

Anchor the price on the transaction

So price on the transaction your product actually delivers, not the downstream gain you hope it unlocks. Pick the job. Put it in their words. Attach the number they already live with. Then, if the deal genuinely needs the big strategic case, the procurement or budget story, bring it after the job has landed, as the reason to expand, not the reason to start.

Where this is too clean

Some sales really do turn on the full ROI case, the big future saving. A seven-figure platform decision, a board sign-off, a capital-spend line, those need the model, and “it saves an hour” will not carry them. But even there, the ROI case rides on top of a job the buyer can feel. Lead with the projection and you are arguing. Lead with the job, prove it, and the projection becomes believable, because now it sits on something they have already seen work.