A person timing a queue of paper documents beside an empty chart marked with a question mark.

Process Measurement Before Rollout

Process Measurement, Before You Pay for Automation You Can't Evaluate Leadership has decided: we're automating process X. But nobody can say how many team-hours it costs today, or how often it ends in an error that needs fixing. Without those numbers, there's no way to later answer the simple question: did automation actually help?

Ready to publish without client-provided data. --- # Process Measurement, Before You Pay for Automation You Can't Evaluate

Leadership has decided: we're automating process X. But nobody can say how many team-hours it costs today, or how often it ends in an error that needs fixing. Without those numbers, there's no way to later answer the simple question: did automation actually help?

Someone on the board saw a presentation on AI automation and wants to start now. Words like "time savings" and "fewer errors" come up, but nobody can give a starting figure — how long the process actually takes today, or how often it even occurs.

Without a baseline, every future judgement of the automation's effect is an impression, not a fact. After go-live, someone will ask "is this actually better", and the honest answer will be a shrug, because there was nothing to compare against.

We measure today's process and give you a baseline in numbers — handling time, volume, error rate — before anyone proposes automation. We repeat the same measurement after go-live, so the before/after comparison rests on one consistent method.

We measure the process as it actually runs, not as an internal procedure describes it — we observe real execution and analyse available logs to capture true variability, not the textbook case. The result comes as numbers: average handling time, distribution of variants, the points where the process stalls.

What we don't do: we never sell measurement as a formality before automation. If the numbers show the process is too small or too irregular to be worth automating, we say so plainly in the report.

An analyst handing a manager a report with a warning flag beside a process chart.

What you get

  • Hard numbers to judge any proposalYou get data to assess the value of any automation proposal — including from a supplier other than us.
  • Realistic expectationsYou see which variants of the process are too unusual for automation to cover, avoiding disappointment after go-live.
  • A basis for measuring the resultAfter a pilot, you compare the same before/after numbers — not a supplier's claims.

This is a new service line, and we don't yet have published measurements to show — we say that plainly. We show the measurement method live in the first meeting: what the measurement sheet looks like and what data comes out of it.

Scope and pricing

Measurement covers one business process — each additional one is priced separately, since it needs its own observation.

  1. Mapping. We describe the process step by step with the people who run it.
  2. Observation. We analyse logs or observe execution to capture real variability.
  3. Numbers. We calculate average time, monthly volume, and error rate.
  4. Report. You get a verdict on whether the process qualifies for automation at its current scale.

Price depends on the number of process steps, the availability of historical data, and how many people need interviewing. You know the price before we start, not after.

A four-step flow diagram from process mapping through observation to a final report.

Our guarantees

A clear verdict. If the process is too small or too irregular, the report says so directly instead of bending the result to sell the next stage.

Open methodology. We present the counting method before we start, so you know exactly what the report is based on.

The same method before and after. We repeat the measurement after go-live using the identical method, so the comparison is credible.

Availability

Measurement requires observing the process as it really runs, so the timeline depends on how often the process occurs — a rarer process needs a longer observation window.

Order a process measurement

Send us a description of the process you want measured and the contact details of the person who runs it — we'll reply within a few business days with the scope and a firm price.

What waiting costs you

Every month without measurement is a month of deciding on automation by feel — including the risk of picking a process that would never have paid off anyway.

In short

Measurement of one process: mapping, observation, numbers · the same method repeated after go-live · a report with a clear verdict on whether the process qualifies · price known once the process is described · open measurement methodology.

Frequently asked questions

Is process measurement the same as the process-selection workshop?

No. The workshop helps choose which process to automate first among several candidates. Measurement covers an already-chosen process and provides the numbers needed for pricing and later evaluation.

How long does it take to collect the measurement data?

It depends on how often the process occurs — the rarer it is, the longer the observation window needed to capture real variability.

Can I measure several processes at once?

Yes, but we price them separately — each requires its own observation and its own set of numbers.

What if the measurement shows the process is too small for automation?

You get that as a conclusion in the report, and we don't propose further steps you don't need.

Can I use the measurement result in talks with another supplier?

Yes, the report is yours to use in conversations with any automation supplier.