Quantify customer value by defining the customer’s baseline, the change your offer can reasonably influence and the evidence behind each input. Use customer-specific calculations or honest ranges when data varies. Separate capability, leading indicators and realised outcomes. If the evidence cannot support a monetary return, quantify time, volume, delay, error, capacity or risk exposure instead—and label assumptions clearly.
Start with the decision, not a percentage
An ROI figure is useful only when it helps a customer compare a credible benefit with the full cost of achieving it. A large percentage built from optimistic assumptions creates precision without knowledge.
Ask what decision the value case must support. An operations lead may need to compare staff time and implementation effort. A founder may care about speed to first reliable insight. A risk owner may need to understand exposure and controls rather than revenue.
Connect the value case to the outcome level in From Feature to Benefit to Customer Outcome. Do not assign money to a feature merely because it sounds measurable.
Define a baseline the customer recognises
Record the current approach before estimating improvement:
- activity completed and its frequency;
- people, time and tools involved;
- waiting, rework or failure points;
- direct external costs;
- volume and variation over a useful period;
- important consequences that are not readily monetary.
Use the customer’s records where possible. Interview estimates can reveal what to measure, but memory is not the same as observed data. State the period, unit and population. “Eight hours” is uninterpretable without knowing whether it means per task, per person or per month.
Separate three levels of evidence
Keep the causal chain visible:
- Capability: what the offer demonstrably does.
- Operational change: what behaviour, time or flow changes after adoption.
- Business outcome: what that operational change is worth in context.
A product may automatically classify requests. That capability can be demonstrated. Reduced handling time needs before-and-after measurement. The monetary value then depends on what happens to released capacity; saved minutes are not automatically cash saved.
Use a proof-point plan to match each level to suitable evidence.
Build the calculation in components
Use a simple worksheet whose assumptions can be changed:
Estimated value = relevant volume × credible change per unit × value per changed unit − additional delivery costs
This is a structure, not a universal formula. Include only components the decision maker accepts. Show each input, its source, its confidence and who owns it. Add implementation time, training, migration, recurring fees and customer effort when they are material.
Where uncertainty is meaningful, create conservative, central and upper scenarios. A range communicates uncertainty more honestly than a single number with several fragile inputs.
Illustrative example
Illustrative example: a hypothetical service helps an agency prepare monthly client reports. The agency records 40 reports a month. A short observation period suggests that consolidating source files could remove 15–25 minutes of repetitive preparation per report.
The defensible value case is initially 10–16.7 hours of potential monthly capacity, before implementation and review time. It is not yet a cash saving. The agency may use the capacity for additional analysis, faster delivery or fewer late evenings. Each outcome has a different value and needs its own evidence.
The provider should label the figures as scenario inputs, invite the customer to replace them and avoid presenting the upper case as a typical result.
Quantify value that is not money
Useful measures include:
- elapsed time or time to decision;
- work in progress or throughput;
- avoidable hand-offs and rework;
- response consistency;
- auditability or information coverage;
- customer or employee effort;
- capacity available for a higher-value task.
Some outcomes resist responsible conversion to money. Keep them visible rather than assigning an arbitrary price. A value proposition can be specific about the situation, mechanism and observable change without claiming a financial return.
Turn the analysis into customer-facing language
Lead with what the evidence supports. “Bring every approval into one review trail” is a capability claim. “Reduce time spent reconstructing approval history” may be an expected benefit. “Save £50,000 a year” is an outcome claim requiring relevant inputs and substantiation.
Use qualifications beside the claim, not hidden in a remote footnote. The process in How to Support Marketing Claims with Proof helps record scope, evidence and review dates.
Limitations and trade-offs
Value varies with adoption, baseline performance, volume and what the customer does with any released capacity. Before-and-after comparisons can be affected by seasonality or other changes. A customer-specific model is more relevant but harder to scale; a benchmark is easier to publish but may not represent an individual buyer.
Do not quantify safety, health, compliance or financial outcomes casually. Seek appropriate domain and legal review where consequences are material.
Use this value-evidence checklist
- Name the decision and decision maker.
- Define the baseline unit, period and source.
- Map capability to operational change and outcome.
- Include implementation and ongoing customer costs.
- Distinguish measured, estimated and assumed inputs.
- Show a range when inputs vary.
- State what must happen for value to be realised.
- Review every public claim against its evidence.
Frequently asked questions
Do buyers always need an ROI calculation?
No. Some decisions are better supported by a clear account of fit, risk, capacity, service quality or time to value. Ask what comparison the buyer actually needs to make.
Can we use an industry benchmark?
Yes, if the source, population, date and relevance are clear. Do not present a broad benchmark as the customer’s baseline or your product’s result.
What if customers will not share cost data?
Provide an editable model using operational units and let the customer supply sensitive values privately. You can still validate the structure without collecting every number.
Your useful next step
Choose one important promise and draw its chain from capability to operational change to business outcome. For every arrow, write the evidence required. Publish only the strongest supported level, then use a value proposition test to learn whether that value matters to the intended buyer.
