If You Can't Say What It Costs Today, You Can't Prove It Worked
The baseline measurement is the cheapest and most-skipped step in automation. Skipping it guarantees the second project never gets funded.
Three numbers, measured rather than estimated
Volume, in transactions per month. Touch time, in minutes per transaction, timed with a stopwatch by the people doing the work. Error and rework rate. Add cycle time for anything customer-facing.
Estimates run 40–60% wrong in both directions. People overstate the time of tasks they dislike and understate tasks they perform on autopilot. A five-day tally sheet across five people costs nothing and settles it.
For revenue-touching processes, baseline the leak
The percentage of inbound enquiries with no response inside twenty-four hours, and the percentage never entered into a system at all. This is usually the single largest number in the whole exercise.
Write the baseline down with a date before any vendor or internal team starts scoping. After the build, everyone's memory of how bad it was adjusts conveniently.
Why finance stops funding automation
A post-hoc claim of "we saved about 30%" gets discounted to zero, correctly, and the credibility cost lands on the next request.
Set the target at the same time as the baseline: what number, by when, would make this a success — and what number would make it a failure worth killing.
Pick the process. Give the five people who perform it a tally sheet for volume and minutes, for five working days. No survey, no estimates.
Has run organisations above €100 million in revenue with teams exceeding 10,000 people.
Meet the team →Questions we get asked
Why do so many automation projects fail to get a second round of funding?
Because the first one was never baselined. Unmeasured savings get discounted to zero by finance, correctly, and the credibility cost lands on the next request.
How accurate are staff estimates of how long a task takes?
Typically 40–60% wrong in both directions. People overstate tasks they dislike and understate tasks they do on autopilot. A five-day tally sheet settles it for free.
Is baselining worth the delay it adds?
Yes, and its main value is negative. Roughly half the time you discover the process runs twelve times a month rather than constantly, and the right decision is to build nothing.
Related insight
The AI Assistant That Does Everything Does Nothing
An agent's reliability collapses as you add systems it must be simultaneously correct about. The only agents that reach production…
AutomationYour Software Is Fine. The Gaps Between It Cost You Forty Hours a Week.
The recoverable waste in most operating companies sits in the transfers between systems, not inside any one of them. No vendor is …
AutomationAutomate a Broken Process and You Buy a Faster Broken Process
Automation makes a process permanent. Any step you encode without questioning becomes structurally harder to remove than it was th…
Where is your business still running manually?
We review your processes, identify the highest-impact automation opportunities and estimate their financial impact — before anything is built.