What this scorecard is actually testing
Not enthusiasm, and not budget. The ten statements test whether the conditions exist for automation to compound rather than to create work. They fall into three groups: data foundations (a CRM, clean centralised records, defined lifecycle stages, source tracking), operational readiness(documented processes, conversion measurement, existing automated email, nurture content), and pressure and mandate (more leads than your team can personally handle, and leadership willing to invest in systems rather than headcount).
Businesses that struggle with automation almost always fail on the first group. Businesses that succeed and then stall usually fail on the third.
Why automating chaos makes things worse
A workflow is a rule applied without judgement. That is the entire value proposition and also the entire risk. When a person works from a messy contact list they notice the duplicate and merge it. A workflow enrols all three records in the sequence and emails the same person three times.
The same logic applies to process. If your follow-up sequence is inconsistent because nobody agreed what it should be, automating it does not produce consistency — it produces one arbitrary version of it, running at scale, that is now harder to change. Documenting first is not bureaucracy here; it is the specification.
What to fix first, by tier
- Foundation Stage (0–3). One CRM, one source of truth, and a written lifecycle. Resist buying automation software at this stage — it will sit unused and become evidence that automation does not work.
- Getting Ready (4–6). The gap is usually attribution, documented process, or content. Pick the one blocking the workflow you most want, close it, and build that single workflow rather than a platform.
- Ready to Automate (7–8). Start where delay costs the most, which for almost every inbound business is lead response time. Instrument it before and after so the lift is provable.
- Primed to Scale (9–10). Move from isolated workflows to a connected system: scoring, cross-channel orchestration, and handing judgement-light work off end to end.
Building the business case
Readiness answers whether you can. It does not answer whether it is worth it, and those are separate approvals. Two numbers usually carry the case: the labour currently going into manual, repetitive work — priced by the automation savings calculator — and the revenue lost to slow follow-up, which is generally the larger of the two and the one decision-makers respond to.
Lead with revenue recovered, support it with cost avoided. Efficiency arguments alone tend to lose to whatever is producing growth this quarter.
A low score is not a verdict
Most businesses score in the middle, and the ones that score lowest often have the most to gain — the gaps are precisely the things holding growth back, automation or not. A CRM everyone actually uses and a written definition of a qualified lead are worth having whether or not a single workflow ever gets built.