ROI calculator · 7 main inputs
AI automation ROI calculator
Hours saved, annual savings and payback for one workflow, from your own volumes and quote.
AI readiness assessment
This AI readiness assessment scores one workflow on six things that decide whether automation will work: process, data, systems, volume, risk and people. Answer 12 multiple-choice questions (about three minutes) and you get a score out of 100, a readiness band, your top three fixes and the blueprint that fits. No email needed.
Score how ready your workflow is for AI
What the assessment measures
Six areas, two questions each. They map to what a workflow audit measures, because each one can stop a project on its own.
| Area | What we ask about | Why it matters |
|---|---|---|
| Process | How consistently the steps are followed, and how exceptions are handled | Rules come from a consistent process. Five versions of one workflow need five rule sets. |
| Data | The form inputs arrive in, and whether past cases have recorded outcomes | A pilot is tested on past cases. Without outcomes there is nothing to measure it against. |
| Systems | APIs and exports for each tool, and how fast IT can give test access | Access requests can take longer than the build itself, so they belong in the plan from day one. |
| Volume | Items per month and team hours per week | Volume decides whether the saving covers the running cost of the system. |
| Risk | Written approval rules, and how mistakes are caught today | A system can enforce approvals and controls, but people have to define them first. |
| People | A named owner with authority, and how the team feels about the change | Owners sign off pilots. The people running the workflow make the best testers. |
Scroll sideways to see every column.
How the score works
Each answer scores 0 to 3. Twelve questions make 36 points, shown as a score out of 100. The three lowest areas become your recommendations, lowest first.
80–100
Ready to build
This workflow is a strong candidate. An audit would mainly confirm volumes, measure the straight-through rate on past cases and set pilot thresholds.
60–79
Ready for a pilot
A scoped pilot on this workflow makes sense. Close the gaps below while the design work happens, so they do not hold up the build.
40–59
Groundwork first
A narrow pilot is possible once the gaps below are closed. Expect some weeks of groundwork on process, data or access before a build starts.
0–39
Not ready yet
Fix the process, the data or the ownership before building anything. Automating this workflow now would mostly encode today's problems.
The AI readiness checklist
The strongest answer to each question, as a list you can check a workflow against without the form. A workflow that meets most of these is a good first candidate.
- The steps are written down, and everyone follows them
- Exception types are listed, counted and each has an owner
- Inputs arrive digitally, ideally as structured data
- Months of past cases are on record, with their outcomes
- Every system involved has an API, an export or an integration connector
- IT can provide a sandbox or read-only access within weeks
- The workflow handles hundreds of items or more each month
- It takes at least one person's full week
- Approval limits are written down and enforced in a system
- A named control (reconciliation, QA or an audit trail) catches mistakes before customers do
- One owner has the time and the authority to change the process
- The team that runs it wants it automated and will help test
From self-assessment to an AI automation audit
The assessment tells you whether a workflow is worth a closer look. An AI automation audit replaces your judgment with measurements. The sample audit shows the full report on a fictional AP team.
| Compare | This self-assessment | Workflow audit |
|---|---|---|
| Time | About three minutes | One to two weeks for one workflow |
| Based on | Your own judgment | Interviews, a timed sample, your system data and a prototype run on past cases |
| You get | A score, a band, three fixes and a suggested blueprint | Workflow map, measured baseline, automation split, risks and controls, pilot thresholds, build plan and fixed price |
| Cost | Free, no email | A fixed fee, agreed before work starts |
Scroll sideways to see every column.
More free tools
Cost calculator · 5 steps, 9 cost lines
Cost per invoice calculator
Your cost to process one supplier invoice, step by step, today and after automation.
Questions about AI readiness
What is an AI readiness assessment?
A structured check of whether a workflow, and the team and systems around it, are ready for automation. This one scores a single workflow on process, data, systems, volume, risk and people, then points to the gaps worth closing before anyone builds anything.
How is this different from an AI automation audit?
The self-assessment takes a few minutes and runs on your own judgment. An audit takes one to two weeks: we map the workflow, time a real sample, test a prototype on your past cases and hand you a measured baseline, an automation split and a fixed build price. The sample audit page shows the full report format.
How is the score calculated?
Each of the 12 questions scores 0 to 3 points. Each of the six areas has two questions, so each area is out of 6, and the total is out of 36, shown as a score out of 100. Below 40 is Not ready yet, 40 to 59 is Groundwork first, 60 to 79 is Ready for a pilot and 80 or more is Ready to build.
Should we assess the whole company or one workflow?
One workflow. Readiness varies a lot inside one company: supplier invoices can be ready while sales outreach is not. Score the workflow you would automate first, then repeat the assessment for the next candidate and compare.
What if our workflow scores low?
Then you have learned something cheaply. A low score usually means the process, the data or the ownership needs work first, and fixing those is cheaper than automating around them. The recommendations show where to start.
Do you store my answers?
No. The assessment runs in your browser and the page does not send your answers anywhere. If you want to discuss the result, you choose what to tell us on the contact form.
Measure the workflow that scored well.
A 30-minute call with an engineer. You will leave knowing what a system could do for that workflow and what it would take to build.
What happens next
- 1
Strategy call
We learn how the workflow runs today and what a good outcome would be.
- 2
Workflow audit
We map the process and measure where a system would save the most time.
- 3
Proposal
A written scope, timeline and fixed price for your first system. No obligation to build.