Before you automate, establish the baseline

An automation demo shows that a task can run. It does not show whether the business is better off.

To answer that question, establish the baseline before the build begins.

Measure the process you actually run

Pick a defined unit of work: an invoice, a customer request, a shipment. Track its volume, the active time someone spends on it, the time it waits between steps, and the work required when something goes wrong.

Separate the ordinary path from the exceptions. A process that works for the average order can still consume the team if the exceptions have no clear owner.

Decide what improvement means

Agree on the measures before choosing the technology. Fewer manual touches, shorter waiting time, and fewer corrections are useful when they connect to an operating decision. A dashboard full of activity counts is not a baseline.

Record the source of each number and the period it covers. Keep the same definitions after launch. If the business changes during the build, document the change instead of forcing an artificial comparison.

Give the team a next step

Time saved becomes valuable when someone decides what to do with it. That can mean handling more work, improving service, or removing a recurring bottleneck.

Manual headcount becomes margin through a considered operating decision. The automation is only part of the work.