When the Customer Asks: “What Is the Payback?”
A credible answer requires more than a headline ROI percentage.
Revetorque helps industrial companies turn technical performance, customer operating conditions and validated assumptions into transparent ROI, TCO and payback models built around the actual investment decision.
The output is only as credible as the logic underneath it
A model that says:
ROI = 37%
may look precise.
But unless the customer understands where that number comes from, it does very little to build trust.
A stronger business case explains:
- what changed,
- why it changed,
- which inputs came from the customer,
- which assumptions were introduced,
- how the calculations work,
- and what happens when the key variables change.
The financial metric is the output.
The credibility comes from the model underneath it.
What decision does the customer actually need to make?
Before choosing a metric, define the decision.
The real question might be:
- Should we replace the existing system?
- Should we keep the status quo?
- Which alternative has the lowest lifecycle cost?
- How quickly does the additional CAPEX pay back?
- Is the efficiency improvement large enough to justify the investment?
- Which configuration creates the strongest economic case?
Those are different decisions.
They may require different models.
That is why Revetorque does not begin with:
“We need an ROI calculator.”
We begin with:
“What does the customer need to understand before they can make the investment decision?”
Connect technical performance to financial impact
A credible business case needs a visible chain between engineering reality and financial output.
For example:
Higher efficiency
Lower electricity consumption
Lower annual operating cost
Payback or lifecycle economics
Or:
Longer maintenance interval
Fewer interventions
Lower service and labour cost
Lower total cost of ownership
The financial calculation should not exist separately from the technical logic.
It should be the economic expression of that logic.
The same product can create very different economics for different customers
A business case becomes useful when it reflects the operating environment in which the investment will actually be used.
Depending on the application, relevant inputs might include:
- operating hours,
- electricity price,
- production volume,
- utilisation,
- current equipment performance,
- maintenance cost,
- labour,
- consumables,
- downtime,
- equipment lifetime,
- purchase price,
- replacement cost,
- financing assumptions,
- or other application-specific variables.
Not every variable needs to be customer-specific.
The important question is:
Which inputs materially change the investment decision?
Those deserve the most attention.
Do not hide uncertainty behind a precise-looking result
Not every input will be known with certainty.
That is normal.
The problem begins when assumptions are hidden.
A transparent business-case model can distinguish between:
Customer-provided data
Values supplied directly by the customer.
Product data
Validated technical information about the proposed solution.
Engineering assumptions
Values derived from technical expertise when direct measurement is unavailable.
Benchmarks
Reference values used where appropriate.
Scenario assumptions
Variables intentionally changed to understand different outcomes.
A model becomes easier to trust when the customer can see — and challenge — the assumptions behind it.
That is a feature, not a weakness.
A single number can hide the real decision
Real investment decisions often contain uncertainty.
Energy prices change.
Utilisation changes.
Maintenance costs vary.
Downtime may be difficult to estimate.
That is why one “correct” ROI percentage can create false precision.
A stronger model may compare:
- conservative,
- expected,
- optimistic scenarios,
or:
- status quo,
- replacement,
- alternative technology,
- competing configuration.
The same applies to sensitivity.
If energy price materially affects the result, the model should make that visible.
If downtime barely changes the case, the customer should be able to see that too.
The useful question is:
What has to be true for this investment to make economic sense?
ROI is useful. It is not always the whole answer.
Different decisions call for different financial outputs.
Depending on the investment, the customer may need:
Payback period
How long before the economic benefit offsets the investment?
ROI
What return does the investment generate relative to its cost?
Annual operating savings
How much does the operating cost change each year?
Total Cost of Ownership
How do alternatives compare across the full relevant lifecycle?
Lifecycle cost
What is the cumulative economic impact over the expected period of use?
Break-even
At what operating level or time horizon does one option become more attractive?
Cash-flow or NPV analysis
Where the investment structure and decision complexity justify it.
The goal is not to use the most sophisticated metric.
It is to use the one that best supports the decision.
Do not build the calculation backwards from the result you want
A credible model must be allowed to produce an unattractive answer.
If the economics only work under unrealistic assumptions, the tool should show that.
If the customer's utilisation is too low to justify the investment, it should show that.
If the expected savings are too small to support the additional CAPEX, it should show that too.
A model designed to always produce a positive ROI is not a decision tool.
It is sales theatre.
The purpose of the model is to evaluate the investment — not manufacture the answer.
That distinction matters.
Because a model becomes more credible when the customer knows it is capable of saying:
“Under these conditions, this investment does not make sense.”
Turn the model into a tool Sales can actually use
A strong methodology is only useful if it can be applied consistently in real opportunities.
A dedicated tool can bring together:
- guided customer inputs,
- technical product data,
- validated formulas,
- assumptions,
- scenarios,
- sensitivity logic,
- financial outputs,
- comparison views,
- charts,
- and customer-facing results.
The underlying model remains the foundation.
The software makes that model easier to:
apply, explain, repeat and share.
This is especially useful when the current process depends on:
- a specialist rebuilding the calculation manually,
- different salespeople using different spreadsheets,
- formulas that are difficult to audit,
- or outputs that are difficult to present to the customer.
Example: comparing continued supply with an on-site investment
Consider an industrial customer deciding whether to continue purchasing gas externally or invest in an on-site generation system.
The decision may involve inputs such as:
- gas consumption,
- delivered gas price,
- delivery cost,
- required purity,
- operating profile,
- compressor power,
- electricity price,
- investment CAPEX.
The model can compare:
continued external supply
with:
on-site generation
and make visible:
- annual operating-cost difference,
- cumulative economics,
- approximate payback,
- relevant assumptions,
- and how the result changes when customer conditions change.
For one operating profile, the investment may show a strong economic case.
For another, it may not.
That is exactly what the model should reveal.
The calculation may be only the beginning
Once the customer understands the economics, the business case may need to travel internally.
The direct contact may need to explain the investment to:
- Finance,
- Procurement,
- Operations,
- senior management,
- or an investment committee.
At that point, the challenge changes.
It is no longer only:
“Can we calculate the ROI?”
It becomes:
“Can someone else understand and defend this case without the salesperson explaining every assumption?”
That is a separate use case.
A dedicated ROI / TCO tool makes most sense when the model repeats
This approach is especially relevant when:
- customers repeatedly ask for ROI, TCO or payback,
- the product creates measurable operating value,
- customer-specific inputs materially affect the result,
- the current calculation requires manual expert work,
- several salespeople need to use the same methodology,
- results need to be shown or shared with customers,
- and the underlying assumptions can be validated.
A dedicated tool may be unnecessary when:
- the calculation is genuinely one-off,
- the economics are trivial,
- there is too little reliable data,
- or an existing spreadsheet already solves the problem effectively.
The goal is not to replace a working model with software for the sake of it.
The goal is to make a valuable decision model practical where it needs to be reused.
Are you rebuilding the same business case for every opportunity?
Bring us:
- the product,
- the investment decision,
- the spreadsheet or methodology you already use, if one exists,
- the technical variables,
- the financial outputs customers ask for,
- and the assumptions behind the model.
You do not need a finished software specification.
We first model the decision and validate the logic.
Then we determine what kind of tool should sit on top of it.
Discuss This Use Case
Tell us what customers ask you to justify and how your team currently builds the answer.
Discuss This Use Case