The ROI Report: Turning Optimisation Into a Number a CFO Will Actually Sign Off

The ROI report is the second half of the optimisation story. The first half is LucidFlow's optimiser producing an improved version of the BPMN: a rearranged process with different task costs, durations, and sometimes a different structure. The first half shows "we can do better". The report answers the four questions finance will ask in response: how much do we save per execution, per month, per year, and how long until the change pays back its implementation cost. Without those four numbers the optimiser output is a sketch; with them it is a business case.

The report is unlocked on Pro and Enterprise plans because it represents the highest-value output in the analytics stack. It draws on the same KPI data every other view uses: cost per task, duration, frequency, plus the optimised version of the diagram. When those inputs are correct, every number in the report falls out deterministically; when they are off, the report tells you where to fix the inputs.

• Total cost savings per execution: original cost per execution minus optimised cost per execution, in dollars.
• Total time savings on critical path: original critical-path time minus optimised critical-path time, in minutes. Different from total-duration savings, which measures sum across all tasks including non-critical branches.
• Monthly savings: total cost savings multiplied by monthly frequency, aggregated across all tasks that changed between original and optimised.
• Annual savings: monthly savings × 12, the number that matters for budget sign-off.
• ROI percentage: savings relative to original cost, expressed as a percentage. A 40% ROI means the optimised process costs 40% less to run than the original, which is the framing most executives will quote.
• Payback period: months until the cumulative savings cover a hypothetical implementation cost. If you provide an implementation cost estimate (tool subscription fees, integration work, training), the report divides that cost by monthly savings to produce a month count. Without an implementation-cost input, payback is the trivial "immediately" answer.

The role breakdown is where the report stops being a headline summary and starts being actionable. For every distinct role or team that appears in the BPMN (sales rep, compliance analyst, credit officer, customer support agent), the report returns the original cost attributable to that role, the optimised cost, and the absolute and percentage savings. The rows sort by absolute savings, so the first row is always the role that benefits most from the optimisation in dollar terms.

This matters because optimisation almost never distributes savings evenly across roles. A typical output might be: Compliance: $12,400 saved per month (34% reduction on compliance cost), Support: $3,200 saved (8% reduction), Finance: $200 saved (1% reduction). That distribution tells you who is going to feel the change most and who needs to be in the conversation before the change lands. It also tells you which roles you can remove from the conversation: a 1% reduction on finance does not require a meeting with the CFO's team.

The waterfall visualisation shows the path from original cost per execution to optimised cost per execution as a sequence of increments and decrements. Every task that changed contributes one bar: green for a cost decrease (a task was automated, eliminated, or simplified), red for a cost increase (a new task was added, for example a compliance check that did not exist before). The bars sum to the net change, which matches the "total cost savings per execution" headline number.

The value of the waterfall is that finance people trust a decomposed number more than a single-line claim. "We save $18.40 per execution" sounds like a guess. "We save $18.40 per execution because task A goes from $12 to $0 via automation, task B drops from $8 to $2 through a template, task C stays at $6, and we added a new $1.60 compliance step: net $18.40 saved" is a defensible argument. The waterfall shows exactly that decomposition so you do not have to reconstruct it during the meeting.

Payback period is the single number a CFO is most likely to ask for because it compresses "is this worth doing" into one quantity. The calculation is straightforward: hypothetical implementation cost (tool subscriptions, integration effort, training time) divided by monthly savings. If the optimisation saves $3,000 per month and the implementation costs $12,000, the payback period is 4 months. A 4-month payback is generally a green light; an 18-month payback is generally a discussion; a 36-month payback usually means the business case needs rethinking.

One-minute pitch structure: start with the annual savings number (the big dollar amount that earns attention), follow with the payback period (the reassurance that the saving is not decades away), then show the waterfall (the proof that the saving decomposes into specific, defensible steps), finish with the role breakdown (who feels the change and needs to be part of the implementation). This is the order that matches how finance and operations leadership actually think: headline, risk bound, mechanism, stakeholders. The report is laid out in exactly this order.