Home·Insights·The cost of the process you are about to automate

The cost of the process you are about to automate

Automating a process before pricing it is how companies buy robots for work they could have stopped doing entirely.

Digital & AI2026-10-017 min readAtlas Strategy Group

Every AI business case rests on a number almost nobody measures: what the process costs today. Not its salary line — its full price. The unmeasured process is unpriceable: the business case for automating it becomes an act of faith, the vendor's slides supply the arithmetic, and the company discovers the real cost of the process a year later, in the failure of the project that was supposed to remove it.

What the price of a process contains

  • Hands-on time — the minutes per case, per person, at honest frequency. Usually the only line anyone estimates.
  • The loops. Rework, escalations, the customer who received the wrong thing and the cost of receiving them again. Loops are where the simple processes hide their complexity — and where automation either pays or fails.
  • The waiting. Process cost is not only labor: the hours a request spends sitting in inboxes are not free; they price into customer patience, working capital and management attention spent chasing.
  • The error tax. The cost of wrong: corrected entries, refunds, apologies, the reputation discount of a process that fails visibly.
  • The knowledge concentration. The process that only two people can perform carries a premium: the risk-priced value of that dependency, visible the day one of them resigns.

Why the pricing changes the project

Pricing the process honestly changes the AI decision before any technology enters. First, it reveals where the money actually is: automation aimed at the visible time often misses the loops and the waiting where the real price sat — the robot automates the cheap part and the expensive part survives untouched. Second, it exposes the processes that should not exist: a surprising share of «automation candidates» are artifacts of an old constraint — approvals for exceptions that no longer happen, reports nobody opens — and the honest price of such a process is a deletion order, not a machine learning model. Third, it sets the baseline: the number the project will be judged against, agreed before the vendor's slides arrive and inflate it.

Half the automation business cases die not because the technology failed, but because the process was never worth what everyone assumed it cost.

The unglamorous discipline

The method is unheroic: follow the process for a week, count the cases, price each component at honest internal rates, and write the number where the business case can see it. This is the first step of use-case selection and the entry test of the P&L question; it is what keeps the portfolio built by an opportunity assessment honest, and what separates strategy from shopping. Companies that skip it are not choosing worse projects; they are choosing blind — and paying for the seeing later, at project prices.

All insights →