Is Your Business Ready for Automation?
The Automation-Readiness Signal Framework
Most owners don't need a consultant to tell them automation is possible — nearly anything can be automated with enough budget. The real question is whether it's worth doing now, for this process, in this business.
This framework gives you six signals to check against a specific process you're considering. It takes about ten minutes. Pick one process you do (or your team does) regularly, and score it honestly against each signal below.
The Six Signals
For each signal, score the process 0 (rarely true), 1 (sometimes true), or 2 (consistently true).
1. Repetition — Is this the same set of steps, done the same way, every time (or nearly every time)? A process that changes meaningfully each time it runs is a poor automation candidate — you'd be automating an exception, not a pattern. 2. Rules-based — Can you write down the decision logic in plain sentences, without "it depends on gut feel"? If you can explain exactly how a decision gets made ("if the order is over $500, route it to a manager"), that logic can usually be automated. If the real answer is "I just know," that's a judgment call — not yet a good fit. 3. Volume — Does this happen often enough that the time adds up — weekly at minimum, ideally daily? A process done twice a year, however annoying, rarely justifies the setup effort. A process done 30 times a week does. 4. Error cost — When this goes wrong, is the cost of the mistake real — rework, a customer complaint, a compliance exposure? High-frequency, low-stakes errors are often fine to live with. High-frequency, costly errors are exactly where automation's consistency pays off. 5. Data availability — Does the information this process needs already exist somewhere digital (a spreadsheet, a system, a form), even if it's messy? If the inputs only exist in someone's head, in a paper file, or in a dozen different email threads, that's a documentation problem to solve first — see "Process Mapping 101" and "Documenting a Process So Someone Else Could Run It" in this Resource Centre — before it's an automation problem. 6. Capacity drag — Is a person's time on this process actually keeping them from higher-value work? The real cost of a manual process often isn't the task itself — it's what the person isn't doing instead.Scoring Your Result
Add up your six scores (maximum 12).
| Score | What it suggests |
|---|---|
| 0–4 | Not yet. This process likely needs more structure (consistent steps, clearer rules, better data) before automation makes sense. That groundwork is worth doing anyway — it usually improves the process even without any automation. |
| 5–8 | Likely ready. This is a reasonable candidate. Your next step is prioritization against other candidates — see "Choosing What to Automate First" in this Resource Centre. |
| 9–12 | Overdue. If this scored this high and isn't automated yet, the manual version is probably costing you more than you've noticed. Worth moving to the top of the list. |
What This Framework Does Not Tell You
Be honest with yourself about the limits of a ten-minute checklist:
- It doesn't calculate your actual return on investment — it tells you whether a deeper look is worth your time. - A high score doesn't guarantee automation will be cheap or quick — effort and risk are a separate question (see "Choosing the Right Partner for an IA Project"). - Scoring a process yourself can carry some bias. If you can, score it with the person who actually does the work day to day — they'll usually catch exceptions you didn't know existed.
A "not yet" result isn't a dead end. It's a map of exactly what to fix first.
---
Want help applying this to your business? A short conversation can usually tell you in minutes whether a process is ready — and what to tackle first if it isn't. Book a free consultation →