How Complex Is Your Process to Automate?
Eleven scored factors, about four minutes. Get an instant complexity score out of 100, see exactly which factors drive the effort, and compare document extraction options side by side.
Your result appears on screen straight away, with no form to fill in first.
Step 1 of 4 · Process information
Assessment result
Provisional result. Technical suitability has not been confirmed for every option shown below.
What is driving the complexity
The three factors contributing most to the effort, out of the eleven assessed.
Points to check before you commit
Feasibility and dependency notes. These are reported separately and do not change the score above.
All eleven factors
Where each factor sits for your process, based on the answers you gave.
If you are still choosing an extraction route
Only the extraction technology changes between these scenarios. Every other answer stays the same.
| Technology | Score | Classification |
|---|
This estimates automation implementation complexity, not business value, ROI, or how hard the process is for a person to perform.
What the Calculator Looks At
Eleven weighted criteria, grouped into the three things that actually drive automation effort.
Process inputs
How information arrives and how much it varies, and whether documents have to be read at all.
Applications and automation
Which systems are involved and how they can be reached: the single biggest lever on build effort.
Process complexity
What happens when things go wrong, how the rules behave, and how large the process really is.
Calculator FAQs
Questions About the Calculator
What the score means, how it is worked out, and what it deliberately does not measure.
What exactly does this score measure?
It measures automation implementation complexity: how much effort it takes to build and maintain the automation. It does not measure the business value of the process, the return on investment, or how hard the process is for a person to perform.
Do I have to give my details to see the result?
No. The score, your complexity drivers, the factor overview, the extraction comparison and the feasibility notes all appear on screen immediately. You only share contact details if you want the full report emailed to you.
How are Simple, Medium and Complex decided?
Eleven weighted criteria produce a score from 0 to 100. You will answer a few more questions than that: some are follow-ups that feed one of the eleven factors rather than adding a twelfth. Scores up to 30 are Simple, above 30 to 60 are Medium, and above 60 are Complex. These are calibration thresholds based on our delivery experience, not an industry standard.
Does using AI automatically make a process complex?
No. A single cloud model call for classification or extraction is low-effort integration work, and a process using one can still score as Simple. Advanced AI is different: autonomous decisions needing formal evaluation, monitoring or custom models are never a simple build, so selecting that option holds the result at Medium as a minimum.
Why are feasibility warnings shown separately from the score?
Because they are a different question. A mandatory one-time code can make an otherwise straightforward automation impossible to run unattended. Hiding that inside a complexity number would obscure it, so restrictions and dependencies are always reported on their own.
How accurate is the result?
It is an indicative first-pass estimate designed to guide prioritisation and conversation. A detailed technical assessment examines system access, data quality, exception volumes and integration constraints before anything is committed to a delivery plan.
Turn the Score Into a Plan
A complexity score tells you what you are dealing with. A technical assessment tells you how to build it: integration approach, exception design, extraction choice and a realistic delivery path.