Automation can release time, but a calculation becomes useful only when its assumptions are visible. An estimated value of hours is not the same as profit. Start with a bounded process and establish how the released capacity could be used.
Measure the current work
Count the people involved and the time each spends on the selected process. Where possible, use a short time study or a sample of real cases. Include checks, corrections and exceptions.
If you select multiple processes, do not count the same time twice. Moving an invoice from an inbox into ERP may appear in two workflow descriptions while remaining a single activity.
Calculate a capacity scenario first
Consider this illustrative example: five employees each spend six hours a week on a process. Assume 46 working weeks and that 45% of this time can be eliminated. The calculation is 5 × 6 × 46 × 45% = 621 hours per year.
At an assumed internal cost of €42 per hour, that capacity has an estimated annual value of €26,082. This is an example, not a client result or guaranteed saving. The 45% is an assumption to validate, not a standard automation performance figure.
Separate hours from financial outcomes
Released time might support additional assignments, faster follow-up or less overtime. The actual value depends on demand, constraints and how work is reorganised. Fixed payroll costs do not automatically fall when a task becomes faster.
Calculate demonstrably avoided costs separately from expected extra revenue. Do not treat the full value of additional sales as profit; use a defensible contribution after incremental costs.
Include the complete project cost
Allow for development, setup, internal project time, training, licences, hosting and maintenance. Include remaining human review and exceptions. A simple annual ROI compares supported benefits and costs over the same period: (benefits − costs) / costs. This ratio is not meaningful with zero costs.
Payback period is a different measure: how long recurring net benefits take to recover the initial investment. A positive annual scenario does not mean an investment is repaid immediately.
Compare cautious and favourable assumptions
Vary the automatable share, workload and additional costs. Identify which assumptions a pilot can measure. The business case then becomes a decision tool rather than a sales promise.
Use our ROI calculator to assemble an initial capacity scenario. During a free workflow scan, we can discuss which inputs need validation and what a feasible first step would be.
Practical guidance by Codewera. Examples are illustrative; the right solution and investment depend on your situation.