RDI

Knowledge base / RDI economics

ROI confidence and credibility

Why a public ROI argument earns trust by publishing ranges, sources, and assumptions, and why a single confident number tends to do the opposite.

Article

A construction technology business case lives or dies on its credibility with finance. The technical question is whether the workflow saves what the case says. The political question is whether the finance partner believes the team did the analysis honestly. The answer to the political question is what determines whether the project gets approved.

Why ranges build trust

A range tells the reader that the analyst understood the inputs were uncertain and refused to pretend otherwise. A single confident number tells the reader that the analyst either did not look at uncertainty or chose to hide it. Finance partners read the second message faster than authors expect. Once read, it is hard to unread.

What to publish

  • Low, mid, and high estimates for each line of value.
  • The assumptions behind each estimate, in plain English.
  • The source of any benchmark used in the model.
  • The sensitivity of the result to the inputs that move it most.
  • A clear statement that the public model is directional and that project-specific data will refine it.

The directional disclaimer

Public ROI calculators are educational. They use industry-typical assumptions to give a buyer a feel for the shape of the value. They are not quotes. The honest position is to say so, on the page, in the report, and in the sales conversation. A directional model that pretends to be a quote is the fastest way to lose a finance partner permanently.

How a project-specific case differs

A project-specific business case replaces directional assumptions with project data. Actual headcount, actual reporting cadence, actual claim history, actual gate volumes. The shape of the model is the same. The width of the range narrows because the inputs are no longer industry estimates but project facts. That is the model the procurement decision should run on.

Credibility compounds across projects. A team known for honest business cases is heard more carefully on the next case. A team known for over-promising is treated more sceptically, even when the next case is good. The discipline pays back in approved projects, not in clever models.

Knowledge base articles are intended as durable reference. For shorter definitions, see the glossary. For shorter essays, browse field notes.