Is this process ready to automate?
Seven questions about one job your team does over and over. You get a straight read: ready, ready for one piece of it, or not yet — and what to fix first. Nothing is sent anywhere.
Nothing here is sent anywhere. The score is worked out in your browser, and a low one is a useful answer: it means the money is better spent tidying the process first.
Why these seven questions.
Every one of them is a thing that has, at some point, decided whether a build held up or quietly fell over three months later.
Repetition and rules decide whether automation is possible at all. Connectable tools decide what it costs. Clean data decides whether the output can be trusted, since an automation moves bad records faster than a person ever would.
Failure handling and ownership are the two most people skip, and they are the two that decide whether the thing still works next year. An automation nobody owns, with no alert when it stops, is a silent single point of failure in a process you have stopped watching.
Questions we get a lot.
Straight answers, no sales layer. Anything else, ask us directly.
All answers →What makes a process ready to automate?
Four things, roughly in order: it repeats often, it follows rules rather than judgement, the tools involved can be connected to, and somebody owns it once it is live. Documentation and clean data make the build faster and cheaper. A process missing all of these can still be automated, but you are paying to encode confusion.
Is my score sent to you?
No. The questions and the scoring run entirely in your browser, and nothing is submitted anywhere. There is no email gate on the result.
I scored low. Does that mean automation is not for us?
It means this process is not ready yet, which is usually a documentation or ownership problem rather than a technical one. Write the steps down, agree who owns it, and decide what should happen when it fails. Those are worth doing whether or not anything gets automated.
What if my tools have no API?
It is the hardest case but rarely fatal. Options include scheduled exports, a database connection, browser automation for a legacy screen, or accepting that one step stays manual while the rest is automated. It costs more, so it is worth knowing before you start rather than halfway through.
What happens after the check?
Nothing automatic. If the result says the process is ready and you want it built, send it over and we will come back with an approach and a cost. If it says not yet, the useful next step is fixing the lowest-scoring answers, and we are happy to say which without selling you a build.
Want a second opinion on the answer?
Send us the process and the score. We will tell you what we would automate first, and what we would leave alone.