Define the unit of work
Choose a repeated task with a clear start and finish: preparing a daily report, checking a document package, or assembling evidence for review. Count completed units that meet the quality requirement.
Measure the current time across a representative sample. For the assisted process, include preparing inputs, operating the tool, checking sources, making corrections and handling exceptions.
Use a simple monthly model
The following figures are invented for illustration. They are not an industry benchmark or a client result.
| Input | Hypothetical value |
|---|---|
| Available tasks each month | 120 |
| Manual time per task | 30 minutes |
| Assisted time, including review | 18 minutes |
| Adoption | 75% |
| Illustrative loaded labor rate | $60 per hour |
| Monthly tool cost | $300 |
| Monthly administration | $120 |
| One-time setup | $3,000 |
At 75% adoption, 90 tasks use the assisted workflow. Twelve minutes released per task equals 18 hours a month. At $60 per hour, that represents $1,080 of capacity value. After $420 of recurring cost, illustrative net monthly value is $660. Dividing $3,000 by $660 gives approximately 4.5 months.
Capacity is not automatically cash. The business needs to decide what the released time enables and whether that benefit is real.
Check the weaker case
At 50% adoption, 60 tasks use the workflow. The same time difference releases 12 hours. At the illustrative rate, that is $720 of capacity value. After $420 of recurring cost, net monthly value is $300. Illustrative payback becomes 10 months.
Change more than adoption. Test higher review time, lower task volume, more administration and a portion of outputs that must be discarded. If the model only works under its most favorable assumptions, it is not ready to support an investment decision.
Avoid double counting
Do not claim the same hour as both capacity value and payroll saving. A salaried employee completing a task faster does not automatically reduce payroll. It may create capacity for other work, reduce delay or lower the need for future overtime, but those are separate hypotheses to verify.
Do not leave review time outside the assisted process. Do not apply the best observed result to every task. Do not treat an avoided error as recovered revenue unless the connection can be supported.
Set decision rules before starting
Define the minimum quality level, the maximum review effort, the operating-cost ceiling and the adoption level required to continue. Record who decides and when.
A pilot can be useful when it shows that the workflow should not expand. That is better than continuing because a demonstration looked promising.