All insightsGuide 02

How to measure manual work before you automate it

Published
Reading time
2 minutes

A simple method for building a baseline you can trust, so you know afterward whether the automation worked.

If you cannot say how long a task takes today, you cannot say what automating it saved. Most teams skip this step because it feels slow, then spend the next year arguing about whether the project was worth it. A baseline takes a few days and settles that argument in advance.

Do not rely on what people remember

Ask five people how long it takes to prepare an estimate and you will get five answers. People remember the typical case and forget the exceptions, the rework and the waiting. Interviews are where you learn what to look at. They are not the measurement.

For each workflow, collect three things:

  1. Watch it happen. Have the person who does the work share their screen and do a real one from start to finish. Note every system they touch and every time they copy something from one place to another.
  2. Count the volume. Pull it from the system of record, such as quotes created in the CRM or invoices issued in accounting. Use at least a full month.
  3. Time a sample. Time several real instances, including a messy one. Use the middle of the range.

Volume multiplied by time gives you monthly hours. That is your baseline.

Write one record per workflow

A baseline is only useful if someone can read it six months later. For each workflow, write down:

Field Example
Process Customer estimates
Owner Sales manager
Trigger A qualified prospect asks for a quote
Steps Capture requirements, check pricing sheet, draft, approve, send
Systems CRM, spreadsheet, accounting
Volume 80 a month
Effort 30 minutes each
Problems Manual price checks, inconsistent proposals, slow replies

The example numbers are illustrative. The fields are the point. If any one of them is blank, the workflow is not ready to automate yet.

Look for the exceptions

The typical case is rarely where the time goes. Ask what happens when the price is missing, when the customer changes the request, when the approver is on vacation. Exceptions tell you two things: how much of the work a system can really take over, and where a person still needs to decide.

Agree on the measurement before you build

Before any build starts, the people paying for it and the people building it should agree on which workflows are being measured, over what period, using what data. Then measure again the same way after launch. Same source, same method, same length of time.

It is not complicated. It is just the step that turns "we think it helped" into a number.