Value selling
How to Build a Customer-Specific Value Case Without Guessing
A value case that survives procurement uses the customer's own numbers and clearly labeled assumptions. A structure that holds up under real challenge.
By Onden · Published · 8 min read
Most business cases in B2B sales are written by the seller, populated with the seller's estimates, and presented to a customer who has no reason to defend them. They read well and they collapse the first time a finance team looks closely.
A value case that survives scrutiny has a different origin. It is assembled from what the customer already measures, structured so that every number can be traced, and explicit about which figures are assumptions waiting to be tested.
Separate what the solution does from the difference it makes
Capability statements are not value. 'Automated approval routing' is a description of a product. 'Approvals that currently take nine days complete in one, which releases revenue recognition a week earlier each cycle' is a value statement, because it names a measurable difference in the customer's world.
The test is simple: if the sentence would be equally true for another customer, it is a capability, not a value case.
A structure that holds up
Work through five linked steps for each area of value. Keeping them separate makes the argument auditable, which is what procurement and finance actually respond to.
- Current state — what happens today, in the customer's own description
- Business problem — the consequence of that current state
- Business impact — the measurable cost of the problem, using their numbers
- Future state — what changes operationally when the problem is addressed
- Value created — the quantified difference, with its assumptions visible
Use their numbers, label yours
Prefer customer-owned figures in every case: cycle times, headcount, error rates, churn, contract values, penalty exposure. A number the customer supplied is one they will defend internally. A number you supplied is one they will negotiate against.
Where you have to estimate, say so in the document itself. Marking a figure as an assumption is not a weakness — it is an invitation to correct it, and correction is how the case becomes theirs. The version that gets approved internally is nearly always one the customer has edited.
Be equally disciplined about ranges. A conservative, credible band with stated inputs travels further inside a customer organization than a single confident headline number that no one can reproduce.
Validate through discovery, not through revision
The gap between a guessed value case and a real one is closed by conversations, not by editing. For each assumption, write the specific question that would confirm or kill it, and the person who can answer it.
That produces a discovery agenda ranked by commercial consequence: the assumptions carrying the most value are the ones to test first. It also gives you an honest read on the pursuit — if the largest number in your case rests on something no one has ever confirmed, the deal is weaker than it looks.
Finally, keep the case connected to the decision. A value case exists to help a specific group of people approve a specific spend. If it is not written in the terms that group uses to justify investment, it will not do that job, however well constructed the arithmetic.
Key takeaways
- Value is the measurable difference to the customer, not a description of your capability.
- Structure each area as current state, problem, impact, future state and value created.
- Label assumptions explicitly and convert the biggest ones through discovery, not editing.
Try this on a deal you are working now
Onden turns customer research, value discovery and readiness gaps into a practical win plan. You can start with incomplete information.
Analyze a live dealContinue reading
Why complex B2B deals stall
Enterprise deals rarely stall from one objection. Something structural is missing — urgency, value, access, process or proof. Here is how to find which.
Deal readiness vs win probability
Win probability forecasts an outcome. Deal readiness diagnoses the pursuit. Understanding the difference changes what a sales team does on a Monday morning.
Forecast commit criteria
Define forecast Commit on evidence, not seller confidence. What a complex B2B deal must prove — urgency, value, access, process — before it counts.