Payload Website Template

Chapter 04

ROI language

Connect RDI workflows to financial outcomes, risk reduction, and operational capacity.

What this lesson is about

ROI conversations on RDI go wrong in predictable ways. They overclaim, mixing direct savings with risk credit until the CFO discounts the whole number. They underclaim, treating dispute avoidance as too speculative to mention. They produce one big figure when the right answer is three lines on a page, each with its own confidence band and its own evidence basis. This lesson teaches the language a credible RDI ROI uses. By the end, you should be able to separate operational savings from risk mitigation, write an assumption with the right humility, and recognise the moment a directional public number should give way to a project-specific one. The lesson is short on arithmetic and long on language, because the arithmetic is easy once the categories are right.

Operational savings as the first line

Operational savings are recurring, measurable, and relatively easy to defend. They are the first line on the page. They include reductions in the manual reporting load on the project management team, reductions in evidence retrieval time when the commercial team needs a clip for a payment certificate, reductions in OAC meeting preparation time, reductions in the number of progress photos taken and sent by hand, reductions in the time spent verifying deliveries by phone and radio. Each can be modelled with hours per week multiplied by a loaded labour rate, and each can be calibrated by sampling a few weeks before the workflow goes live. Operational savings rarely justify a platform purchase on their own, and that is fine. They are the line a sceptical buyer can audit, which gives the rest of the model credibility.

Risk mitigation as a separate, honest line

Risk mitigation belongs on a separate line because it has a different shape. It is the expected reduction in low-frequency, high-cost events: a delay claim that holds rather than slips, a weather claim that is granted, a theft investigation that recovers material, an injury that does not happen, a regulatory event that closes without penalty, a non-conformance that is caught in the slab pour rather than on handover. The honest way to model it is as a probability times an impact, with both numbers shown and both anchored in industry or project history. The temptation is to combine risk credit with operational savings into one big number. Resist it. The CFO will discount a combined number by half on principle. Two lines, each defensible on its own, are worth more than one impressive line that is worth nothing under audit.

Capacity, credibility, and assumption discipline

Capacity is the third, often unspoken, line. RDI changes what a given project team can manage. A project director with a working command view can run a portfolio of more projects without a proportional increase in head count. That is real economic value, and it is rarely on the ROI page because it is harder to attribute. Mention it qualitatively. Credibility is the property of the model as a whole. A credible RDI ROI shows assumptions, ranges, evidence basis, and confidence bands. It distinguishes between numbers the vendor sourced from industry and numbers the customer measured on this project. It uses the word "directional" honestly when the data is thin. The discipline is to write down each assumption as a sentence: "we assume manual progress reporting takes the project engineer three hours a week, calibrated by a one-week sample in October." That sentence is what separates a model the CFO trusts from a number the CFO ignores.

Directional calculators and project-specific reports

A public ROI calculator and a customer ROI report do different jobs and should not be confused. A directional calculator educates the market and gives a buyer a rough order of magnitude. It uses ranges, hides nothing, and labels every input as a default the buyer will need to replace. It is honest at the cost of being unspecific. A project-specific ROI report uses real labour rates, real claim history, real retention windows, and the real sample of the workflows already running on the project. It is the document a CFO signs against. The mistake is to pretend the calculator is the report, or to skip the calculator on the assumption that only the report counts. The calculator builds the conversation. The report wins the budget. Use both, and label each clearly.

Practice

01. Draft the three-line ROI summary for one workflow on your current project: one line operational savings, one line risk mitigation, one line capacity. Show the assumption behind each number in a single sentence.
Look for: A strong response keeps the three lines separate, names the assumption clearly, and uses ranges where the data is thin rather than a single confident figure.
02. Write the sentence you would use with your CFO to explain why a directional ROI is worth running before the project-specific ROI is built.
Look for: A strong response frames the directional run as a structuring conversation, not a commitment, and protects the integrity of the project-specific number that follows.

Checkpoint