Combine workflow volumes, labour value, revenue assumptions, and build cost in a draft business case.
Name each task and the role doing it. Enter the hours you expect to save per run, after review, and the monthly frequency.
Set the hourly rate and build investment. Add revenue only where you can explain how the workflow contributes to it.
Do not count the same benefit as both saved time and new revenue. The displayed payback uses the entered annual value; add operating costs and rollout assumptions to your final business case.
Not necessarily. The tool values time at the hourly rate you enter. Explain how the released capacity will be used or which spending will change.
The baseline, assumptions, build and running costs, risks, owners, and a measurable pilot. Keep uncertain benefits visible rather than treating every estimate as a commitment.
For each workflow, expected hours released per task × monthly frequency × hourly employment cost × 12 gives annual labour value. Revenue upside is shown separately.
Illustrative example: A quarter-hour released across 500 tasks each month at €50/hour gives €75,000 annual labour value before costs. Use hours remaining after review when estimating the release.
Labour capacity and revenue can overlap. Avoid counting the same time twice, and subtract build, running and maintenance costs before committing.
Bring the result and one workflow to a free 30-minute call. We will review the assumptions and discuss a practical next step.