Is Your Business Actually Ready to Automate?
Automation projects rarely fail on technology. They fail because the process was never documented, the data was a mess, or nobody owned the outcome. Fourteen questions will tell you whether to start building or to spend a fortnight preparing first.
Answer for the business as it is today, not as you intend it to be after the project. Optimism here produces a comfortable score and an uncomfortable build.
Automation Readiness Assessment
Fourteen questions. Answer for today, not for the plan.
A self-assessment intended to structure an internal conversation. It is not an audit, and nothing you enter is recorded or transmitted.
What Readiness Actually Means
Readiness is not about how sophisticated your technology is. Plenty of low-tech businesses automate successfully, and plenty of well-resourced ones fail. What separates them is whether the inputs to an automation project already exist.
Documented beats sophisticated
A business that can describe a process on one page will automate it faster than one running expensive software but relying on institutional memory. Documentation is the single strongest predictor in this assessment, because everything downstream is built from it.
Data quality sets the ceiling
Automation applied to inconsistent data reproduces the inconsistency at speed and scale. If your customer records contain three versions of the same company, automating anything that touches them will surface that problem immediately and publicly.
Someone has to want it
Projects with a named owner whose working week visibly improves get adopted. Projects sponsored only from above get politely ignored, and the automation quietly falls into disuse within a couple of months while everyone reverts to the spreadsheet.
The Five Dimensions Assessed
Fourteen questions across five areas. A serious weakness in any one of them will slow a project down regardless of how strong the others are.
Process clarity
Whether your processes are written down, consistent between people, and stable enough to encode without being rewritten mid-build.
Data foundations
Whether the data an automation would consume is structured, accessible, reasonably clean and stored somewhere a system can reach.
Systems and integration
Whether the tools you run today can be connected, and whether anyone knows what those connection points look like.
People and ownership
Whether there is a named owner, whether the team has been involved, and whether anyone has capacity to support the rollout.
Governance and risk
Whether you have decided what the automation is permitted to do unattended, and who reviews its output.
The Four Preparation Steps That Pay for Themselves
If you score poorly, these are the fixes worth doing before you approach any vendor. All four make the eventual project cheaper and faster, and all four are worth doing even if you never automate anything.
Write the process down on one page
Sit with the person who actually performs the process and document what they do, including the exceptions and the judgement calls. This routinely takes two hours and routinely reveals that three people do it three different ways, which is information you badly need before anyone quotes on automating it.
- Document the real process, not the official one from the procedure manual
- Capture exceptions explicitly. They usually drive the build cost
- Note every judgement call, since those are candidates for human review
- Have a second person who does the same task check the document
Fix the worst of your data first
You do not need perfect data, but you need to know where it is bad. Run a duplicate check, look at how many mandatory fields are empty, and check whether the same entity is recorded consistently. Automating on top of known-bad data guarantees an expensive discovery later.
- Count duplicates in your core customer or supplier records
- Measure completeness on the fields the automation will depend on
- Standardise formats for dates, phone numbers and identifiers
- Decide which system is authoritative when two disagree
Find out whether your systems have an API
Before scoping anything, establish whether the systems involved can be connected programmatically. Most modern Australian business software can. Some legacy and industry-specific systems cannot, and discovering that after a project has been approved is an expensive way to learn it.
- Check each system’s documentation for an API or export capability
- Confirm your licence tier actually includes API access, many do not
- Identify anything that only produces PDFs or requires manual export
- Ask your vendors directly rather than assuming from the marketing site
Decide the rules before you need them
Agree in advance what the automation may do without a human checking, what requires approval, and who reviews outputs in the first months. These decisions are quick to make calmly and painful to make after something has gone wrong in production.
- Define the value or risk threshold above which a human must approve
- Name who reviews automated output and how often, especially early on
- Decide what gets logged so a decision can be traced afterwards
- Start in recommend-only mode before allowing unattended execution
Next Steps
Process Automation Priority Scorecard
Ready to go? Score your candidate processes to work out which one to do first.
Prioritise processes →Automation ROI Calculator
Model the return on a specific process, including payback period.
Run the numbers →Automation Implementation Checklist
The step-by-step rollout plan once you have chosen a process.
Open the checklist →Frequently Asked Questions
No, and waiting for a high score is its own failure mode. What matters is that you know where you are weak, so the project can be scoped around it. A business with excellent process documentation but messy data can still automate successfully by starting with a workflow that does not depend on the messy data. The score is a map of where the friction will be, not a gate you must pass. The businesses that get into trouble are the ones that never looked.
Undocumented process variation. The project is scoped against how the process is believed to work, then during the build it emerges that there are four exceptions nobody mentioned, two of which happen weekly. Scope grows, the timeline slips, and the automation ends up handling the simple cases while humans still handle everything interesting. This is why the documentation questions carry the heaviest weight in this assessment, and why writing the process down beforehand is the highest-return preparation available.
Not at all, but it changes the sequence. If your data is inconsistent, either choose a first automation that does not depend on it, or make data clean-up the explicit first phase of the project rather than an unpleasant surprise in week three. Automation frequently improves data quality over time, because it enforces consistent capture at the point of entry. The mistake is assuming existing data is clean, discovering mid-build that it is not, and then having to re-scope.
For most small and medium businesses, a fortnight of deliberate effort makes a substantial difference. Documenting two or three core processes takes a few hours each. Running a duplicate and completeness check on your main data set is an afternoon. Confirming which systems have usable APIs is a morning of emails. None of it is difficult, and all of it reduces the eventual build cost, because you are no longer paying a vendor to discover your own business on your behalf.
The dimensions apply to any automation, but two of them matter more when AI is involved. Governance carries greater weight because AI systems make probabilistic decisions rather than following fixed rules, so deciding what runs unattended is a more consequential choice. Data foundations matter slightly less for AI in one respect. It handles unstructured inputs such as emails, documents and free text far better than traditional rules-based automation, but far more in another, because AI trained or grounded on inconsistent data will confidently reproduce that inconsistency.
No. The assessment runs entirely in your browser, nothing is transmitted, and there is no email gate. You can screenshot the result if you want it for an internal discussion. If you would like to talk through what your score means for a specific project you are welcome to get in touch, but the tool is genuinely usable without giving up any contact details.
Know Where You Stand?
Tell us your weakest dimension and the process you had in mind. We will tell you whether to prepare first or start building, and we will say so plainly if it is the former.