Automation Planning · Free Tool

Automation Readiness Scorecard

Answer eight quick questions about a manual process to get a 0-100 readiness score, what to fix first, and whether a workflow, an AI agent, or an RPA bot fits it best.

1. How often does the process run?
2. How much team time does it take per week?
3. How are the decisions made?
4. What do the inputs look like?
5. Can the systems involved be connected?
6. How often does the process itself change?
7. Does manual handling cause errors or delays today?
8. How many cases need special handling?

About this tool

Not every manual process is worth automating, and the ones that are don't all need the same tool. This scorecard rates a process on the eight factors that decide it in practice: how often it runs, how long it takes, how rule-based the decisions are, how structured the inputs are, whether the systems involved have APIs, how stable the process is, how costly mistakes are, and how many exceptions it has.

You get a score out of 100, a plain verdict, the specific weaknesses dragging the score down, and a recommended approach: a classic workflow automation (n8n, Zapier, Make) for structured, rule-based work, an AI agent for unstructured inputs and judgement calls, or an RPA bot when the systems have no API.

Common uses

  • Shortlist which of your team's manual processes to automate first
  • Find out whether a process needs an AI agent or a simple workflow before you pay for one
  • Spot the cleanup work (standardising inputs, documenting rules) that should happen before automation

Frequently asked questions

What makes a process a good automation candidate?

High frequency, clear rules, structured digital inputs, and systems that can be reached through an API. A process that runs dozens of times a week and follows the same steps every time is usually an easy win.

Can AI automate processes that are not rule-based?

Partly. LLM-based agents handle unstructured inputs such as emails, PDFs, and free text, and can make bounded judgement calls. They still work best with clear guardrails and a human review step for high-stakes decisions, which is why the scorecard recommends human-in-the-loop designs when errors are costly.

My process scored low. Should I give up on automating it?

Not necessarily. A low score usually points to specific fixes, such as standardising an input form or writing down the decision rules. Automating only the most repetitive slice of the process is often still worthwhile.

Is my data uploaded to a server?

No. This tool runs entirely in your browser using JavaScript, so nothing you type is transmitted, logged, or stored anywhere. You can even use it offline once the page has loaded.