Process automatability test

The process

Question of 7

How it works. Think of one concrete process from your day-to-day — just one, the one that eats the most time. Answer each question based on how it works today, not how you wish it worked. We store nothing: the maths happens in your browser.

01 How often and at what volume it runs

The more it repeats, the more sense it makes to automate.

Very occasionally, almost never A few times a month Several times a week Daily, at high and steady volume

02 How clear the rules are

Does it follow fixed steps or depend on a person’s judgement?

It almost always relies on human judgement There are rules, but many judgement-call exceptions Clear rules with the odd case to interpret Explicit, deterministic rules with no ambiguity

03 How structured the data is

Data in systems vs. paper, emails or people’s heads.

Paper, phone calls or unwritten knowledge PDFs, emails and loose documents Spreadsheets or semi-structured forms Structured data in databases or systems with an API

04 How many systems or apps are involved

Hopping between many disconnected tools makes integration harder.

Many disparate, disconnected systems Three or four tools that don’t talk to each other A couple of systems with partial integration One or two systems already connected or with an API

05 How many exceptions and edge cases come up

Processes full of “this one is special” are harder.

Almost every case is an exception Many recurring exceptions Few exceptions, well identified Practically always the same flow

06 How much time it consumes for the team

The more time invested, the more room to improve.

Just a few minutes in total A few hours a week A big chunk of someone’s day It keeps several people busy almost full-time

07 The cost or criticality of an error

An expensive mistake strengthens the case to automate and control it.

A mistake has almost no consequences It causes rework and minor annoyances It can cost money or clients if it slips through A mistake is critical: legal, financial or safety

Your result

How it works. Think of one concrete process from your day-to-day — just one, the one that eats the most time. Answer each question based on how it works today, not how you wish it worked. We store nothing: the maths happens in your browser.

/

Automatability index

/ 100

The average of your answers, normalised from 0 to 100.

Estimated effort

A rough sense of project size, not a quote.

Verdict

→

Be honest. The index is only useful if you answer based on how the process is today, not on the goal. A good “no” saves you a bad project.

Automating is not all or nothing. Even when the index is low, there is almost always one part of the process — the most repetitive — that can be automated with good returns.

// Next step

Now you know it is automatable.

The logical next step is to put numbers on it: work out how much you would save a year and in how many months it pays for itself.

Calculate the saving

Shall we look together?

An hour of discovery is usually enough to tell you whether this process is the one to start with — or which one would be. Let’s talk.

Let’s talk