Money that actually changes and can be linked credibly to the workflow.
Coral Shark Lab · Capacity Is Not Cash
How to Calculate Automation ROI Without Making Up Numbers
Direct answer
Automation ROI is useful only when value and assumptions are labelled honestly. Do not multiply every released hour by an hourly rate and call it cash. Separate cash realised, capacity released, risk/error exposure and opportunity value, then subtract implementation, provider, maintenance and exception/rescue burden.
Capacity Is Not Cash
Capacity Is Not Cash
If an owner spends five hours a week on quote preparation and a better workflow reduces that to two, three hours of capacity may have been released. Cash changes only if something financially measurable changes because of those hours: external cost falls, overtime reduces, a hire is avoided with credible causality, or additional contribution is actually realised.
Capacity Is Not Cash
Keep four value buckets separate
Net human time made available after rescue/review/maintenance.
Measured change in missed actions, rework, delay or other failure modes.
Potential additional output or attention enabled by released capacity.
Capacity Is Not Cash
Use separate models instead of one impressive number
ANNUAL NET CASH EFFECT = evidenced cash gains − implementation/provider/maintenance cash costs.
CAPACITY EFFECT = hours released − human rescue/review/maintenance hours added.
RISK/QUALITY EFFECT = measured change in defined failure/rework/delay metrics.
OPPORTUNITY EFFECT = separately described/measured downstream use of released capacity.
Do not force all four into one number unless every conversion is defensible and explicit.
Capacity Is Not Cash
Label every important input
Current direct evidence: invoice, system count, measured sample.
A supplied estimate with its source visible.
A derived interpretation that still needs proof.
Not established; do not fill the cell for convenience.
Capacity Is Not Cash
The baseline matters more than the forecast
Before predicting improvement, capture enough current data to know what you are comparing against: volume, handling-time sample, exception types/rate, rework/failure count, provider cost, approval/rescue points and any cash measure you plan to claim later.
If a baseline is too expensive to measure, state the uncertainty instead of solving missing evidence with a more elaborate formula.
Capacity Is Not Cash
Include exception and rescue burden
Automation removes 8 minutes from 100 standard cases: 800 minutes. If 25 exception cases each require 15 minutes of rescue, 375 minutes comes back. Net capacity effect is 425 minutes before maintenance/review.
The project may still be worthwhile. The honest number is simply different from the headline.
Capacity Is Not Cash
ROI comes after readiness
An attractive forecast cannot override an unstable process, unknown/high exceptions, high consequence, weak rollback or a consequential human boundary. A £50,000 forecast does not make an unsafe workflow safe.
Run the First-Workflow Gate first →Capacity Is Not Cash
Three levels of business case
Not every worthwhile workflow needs to reach Level 3.
Evidence and claim boundary
What this page is — and is not.
Capacity Is Not Cash is a Coral Shark decision framework, not a claim of scientific or industry consensus. Synthetic examples are illustrative, not customer proof. Where a material external fact is added later, it should be sourced to a current primary source and dated.
Related reading
Need this applied to one real job?
The Owner’s Brief applies the same discipline to one recurring job: what you told us, your estimates, our interpretation and what is still unknown stay separate. The answer can be stop, wait, start smaller or proceed.
Apply this to one job · £249 + VAT