Measure costs, time saved and realised outcomes separately
Automation can make work quicker without leaving a business better off. This guide shows how to record the baseline, the full cost, the hours freed and the outcomes that were actually realised, so you can decide whether to continue. It promises no result and offers no benchmark.
Define the baseline
Without a record of how the work runs now, every later figure is a guess about the past. Record the baseline before anything changes.
- 01
Name one workflow and its boundary
Write down the trigger and the finished state, for example a missed call and a booked or declined enquiry. Anything outside that boundary stays out of the count.
- 02
Count volume, handling time and exceptions
Record how many workflows were completed, how long a sample of real cases took, and how many needed a person to look at them. Time real cases rather than asking people to estimate.
- 03
Record the outcome you care about at the same time
For a revenue workflow, count enquiries, bookings made and appointments attended. For an administrative workflow, count errors and rework. Choose the outcome before you see any results.
- 04
Mark every number as actual or assumption
Note where each figure came from, such as a system report, a sample or a recollection. The worksheet has a column for this, and the assumptions are the ones to revisit first.
Count the full cost, not only the invoice
A quote is one line. The cost of running an automation includes every line below, whoever pays it.
- 01
One-off set-up
Include scope, configuration, testing, and your own team's time spent in meetings and in providing access. A project can look cheap until that time is counted.
- 02
Recurring charges
List licences, platform fees, message or usage charges, hosting and support, and name the provider that bills each one. Usage-based charges can rise with volume, so note what drives them.
- 03
Exception cost
Record the time a person spends on cases the automation cannot finish, such as reading an odd reply, correcting an error or calling back. It is easy to leave out because it sits in someone's day and not on an invoice.
- 04
Review and change
Someone has to check the output on a schedule, and the rules will change. Record those hours and what a change request costs.
- 05
The cost of leaving
Note what you would keep if you switched the automation off or changed supplier, such as your data, message templates and a written description of the configuration. A workflow you cannot leave has a cost that only shows when you try.
Time saved is not cash saved
Hours freed are capacity. They become money only through a change you can point to and record.
- 01
Work out hours freed first
Take the handling time before, subtract the handling time after, and multiply by the volume. As a placeholder, say a task took 10 minutes, now takes 2 and runs 30 times a week. That frees 4 hours a week. These are invented round numbers to show the arithmetic, not a result anyone should expect.
- 02
Ask what happened to those hours
Time becomes cash when paid hours fall, for example less overtime, less agency cover or a hire not made. It can also become income if the hours go to other work that earns something and is recorded. Otherwise it is capacity, which is a real benefit and is recorded in hours.
- 03
Do not multiply hours by a wage and call it a saving
Hours multiplied by a wage gives the value of the time, which will not appear in the accounts. If you want to show it, give it its own line and label it as the value of capacity.
- 04
Keep hours that became cash in their own row
The worksheet separates hours freed, hours that became cash and hours used for other recorded work. Side by side, one cannot stand in for another.
- 05
Count quality separately
Fewer errors and faster replies matter. Record them as counts and do not attach an invented price to them.
Conversion is not activity
Messages sent, calls returned and replies received show that the automation is running. They do not show that it earned anything.
- 01
Follow one enquiry to the end
Count each step from message sent, to reply, to booking, to appointment attended or order paid. The last step is the one to value, because the earlier steps can rise while the last one stays flat.
- 02
Define a saved enquiry in advance
A saved enquiry might be one that would have gone unanswered under the old process and was booked after the change. Write the definition, and who decides, before the period starts so it cannot be widened afterwards.
- 03
Allow for what would have happened anyway
Some customers call back or rebook without any automation. Compare with the baseline period or with a service not yet switched over, and record your judgement as an assumption.
- 04
Value an outcome by contribution, not takings
Realised incremental contribution is the income from the extra work minus the direct cost of delivering it. Use your own figures, and ask your accountant what counts. This guide is not accounting advice.
- 05
Do not treat a click as revenue
A page visit, a button click or a form sent is a step on the way. Count it as activity until a person has booked or bought.
Choose a comparison period you can defend
A before and after figure means something only if the two periods are alike. Settle the periods before the work starts.
- 01
Match length, season and mix
Use the same number of weeks, the same services and the same locations. Avoid holidays, closures and price changes, because seasonal demand can look like improvement.
- 02
Write the periods down first
Fix the baseline weeks and the review weeks in writing before the change. Choosing them afterwards makes it easy to pick a flattering pair.
- 03
Change one thing at a time
If timing, wording and channel change together, you will not know which one mattered. Introduce one change, wait for a comparable period, then review.
- 04
Keep a control where you can
If you have two locations or two services, switch one first and compare it with the other. Note any differences between them that could explain a gap.
- 05
Allow for settling in
The first weeks include fixes and learning. Record them, keep them apart from the review period, and base the decision on the weeks that follow.
Test how far the answer depends on your assumptions
Most of the inputs are estimates. A sensitivity check shows which ones the decision rests on.
- 01
Give each uncertain input a low, middle and high figure
Handling time, volume, the number of saved enquiries and the value of a booking are common candidates. Work the result out three times. Report the range, not only the middle figure.
- 02
Find the input that moves the answer most
Change one input at a time and watch the result. The input with the largest effect deserves the most careful measurement.
- 03
Ask what would have to be true to break even
Find the smallest number of saved enquiries, or hours turned into cash, that covers the full cost. Then ask whether your records suggest that is reachable. As a placeholder, say the costs so far equal four months of realised value. Payback is then four months away if that value holds, and eight if it halves. This is arithmetic, not a forecast.
- 04
Run the unflattering case
Assume exceptions take longer, volume is lower and usage charges are higher. If the answer holds, say so. If only the optimistic case passes, say that too. HM Treasury's Green Book guidance notes that appraisers tend to be over optimistic and advises checking estimates against evidence from similar past projects. It is written for public bodies, so use it as a prompt, not as a rule for your business.
Agree proceed and stop criteria in advance
Decide what result would make you continue, change course or stop before you see any numbers.
- 01
Proceed when realised value covers the full cost
State the test as a sentence others can check, with the review period, the exception load your team can handle and a limit on complaints and opt-outs. Write it down before the review period starts.
- 02
Extend or change when the result is unclear
If the data is thin or the period was not representative, extend it for a set time or change one thing. Do not carry on without a date, because an open trial becomes a standing cost.
- 03
Stop when the criteria say stop
A stop is a valid result of a measured trial. Before you start, ask your supplier how to switch the automation off, what that costs and what you keep.
- 04
Agree who records what
Name the person who records each row, the system it comes from and who reviews it. The party that built the automation should not be the only one scoring it, and that applies to us as much as to anyone.
- 05
Set a review date
Put the first review in the diary when the work starts, and give each worksheet row an owner. A measurement nobody owns stops being updated.
Seven checks before you rely on a number
Answer these in writing. The downloadable worksheet has a row for each measure, with columns for the source, whether the figure is an actual or an assumption, and an owner.
- 1.Is the workflow named, with a start and a finished state?
- 2.Is the baseline recorded from real cases, with each figure marked actual or assumption?
- 3.Does the cost include set-up, recurring charges, exception time, review and the cost of leaving?
- 4.Are hours freed kept apart from hours that became cash?
- 5.Is a saved enquiry defined in advance, and is the outcome counted at the last step?
- 6.Are the comparison periods written down and alike?
- 7.Are the proceed, extend and stop criteria agreed, with a review date and an owner for each row?
Download the measurement worksheet (CSV) A plain spreadsheet file with one row for each measure. Edit it freely; it opens in any spreadsheet program.
Continue with the next step
The calculators estimate an opportunity from your own inputs before anything is built. This guide covers what to record afterwards.
Bring your baseline and your questions
Tell us the workflow and what you have already recorded. We will say plainly if the numbers do not support a project, or if a feature you already pay for covers it.