7 Signs Playbook
AI Readiness Assessment: Is Your Business Ready to Deploy AI Workers?
Most businesses that fail at AI automation were not ready for it — not because the technology did not work, but because the preconditions were not in place. This 5-question assessment tells you where you actually stand in under 10 minutes.
What Are the 5 Questions That Determine AI Readiness?
Answer each question honestly. Score 1 point for each yes. Three or more points means your business is ready to begin a pilot deployment. Below three, use the blockers section to identify what to fix first.
Q1
Do you have at least one workflow with documented steps?
Yes → You can hand the documentation to the AI Worker as its operating rules.
No → The workflow exists only in someone's head. Document it first — if you cannot write the steps in one hour, you are not ready to automate it.
Q2
Does that workflow run more than 20 times per week across your team?
Yes → The volume is high enough for the ROI math to work at standard AI Worker pricing.
No → Low-volume workflows do not generate enough savings to justify a monthly subscription. Start with a free tool like Zapier for simple triggers and revisit when volume grows.
Q3
Is the data the workflow needs accessible to software — via API, spreadsheet, or CRM?
Yes → The integration is technically feasible. The AI Worker can read and write the data it needs.
No → If critical data lives in a locked system, a paper filing cabinet, or a personal inbox with no API access, the integration will hit a wall. Identify the data access path before starting.
Q4
Is your monthly budget above $2,000 for automation tools?
Yes → You can afford the entry tier for a CC AI Worker (Maya Starter at $2,600/mo) and still have ROI headroom.
No → Below $2,000/mo, evaluate n8n (self-hosted, free) or Zapier ($20–$100/mo) for simpler automations before moving to an AI Worker subscription.
Q5
Do you have at least one team member who can flag when the AI Worker makes a mistake?
Yes → You have an escalation path. The worker routes edge cases to a human who can catch errors before they become client-facing problems.
No → Every AI Worker deployment requires a human-in-the-loop for escalations. Without someone to review the queue, errors compound silently. Identify that person before deployment begins.
Scoring
- 5/5: Ready to deploy. Start the scoping conversation.
- 3–4/5: Pilot-ready. Identify the 1–2 gaps and address them in parallel with the deployment scoping.
- 1–2/5: Pre-automation stage. Use the blockers section below to build the preconditions first.
- 0/5: Not yet. Focus on process documentation and volume measurement before revisiting.
What Does AI Readiness Actually Mean for a Business?
Readiness is not about technical sophistication. Most CC clients have no in-house engineers. Readiness means your business has:
- →At least one workflow that happens the same way every time (or with predictable variations)
- →Enough volume to make the ROI math work at your price point
- →Data that software can reach — in a CRM, spreadsheet, or system with an API
- →A budget that can sustain the subscription while the payback period plays out
- →One human who owns the escalation queue and can flag errors
These conditions are not requirements imposed by technology — they are requirements imposed by sound business practice. A business that cannot answer Q1 and Q5 above has a process problem, not an AI problem. Fixing the process first makes the business better regardless of whether automation follows.
What Are the Most Common Blockers — and How Do You Clear Them?
Blocker: Undocumented processes
Schedule a 60-minute workflow mapping session with the person who owns the task. Write every step on a whiteboard or in a Google Doc. If the steps change every time, document the decision tree — what factors change the path? That document becomes the AI Worker's rulebook.
Blocker: Data locked in a system with no API
Most major CRMs, email platforms, and project tools have Zapier or Make connectors that expose their data without a custom API build. If your data is in spreadsheets, Google Sheets has an API. The only genuine blocker is a legacy on-premise system with no connectivity path — which is rare but real.
Blocker: Volume below the threshold
Do not automate the low-volume workflow. Measure volume for 30 days before making the decision. Many businesses underestimate volume because the work is distributed — 5 people each handling 5 instances per day is 25 per day, which is well above the 20/week threshold.
Blocker: No budget for the subscription
Start with free or low-cost automation tools (n8n self-hosted, Zapier free tier) to build the documentation and integration habits. Once you have demonstrated value at low cost, the business case for a CC AI Worker subscription is concrete and fundable.
What Are the First Steps if You Score 3 or Higher?
A score of 3+ means your business is ready to begin the scoping conversation. The next three steps:
- Identify the highest-value automatable workflow. Use the Workflow Automation Checklist to score and rank your top 3 candidates. Bring this list to the scoping call.
- Measure actual volume for 7 days. Count how many times the workflow runs. This is the variable that most affects payback period and plan selection. A CRM activity log or email search makes this fast.
- Book the deployment scoping call. The CC team will confirm your readiness score, validate the workflow selection, model the payback period with your actual numbers, and define the integration path. No commitment required.
The full deployment playbook — from scoping to autonomous operation — is covered in the Workforce Deployment Playbook.
Frequently Asked Questions
What if we score 3 but one of our no answers is Q5 — no escalation owner?
Q5 is the non-negotiable. Every CC deployment requires a human-in-the-loop for the worker's escalation queue. Before proceeding, designate one person — even if they only review the queue 30 minutes per day. This person does not need to be technical; they just need authority to handle the cases the worker flags.
Can we start a pilot without scoring 5/5?
Yes. A 3/5 score is sufficient to pilot. The gaps at Q4 and Q5 can often be resolved during the deployment scoping phase. The critical blockers are Q1 (documented process) and Q3 (accessible data) — pilots that start without those in place consistently stall during integration.
How long does it take to get from 2/5 to 3/5?
The most common path from 2 to 3 is process documentation — which most businesses can complete in one or two working sessions. Volume measurement takes 7–30 days of data collection. Data access issues depend on the system involved; a Zapier connector can be activated in hours, a legacy system migration can take months.
Is there a version of this assessment CC runs during the qualification call?
Yes — the /start qualifier funnel collects the same information in 4 structured steps: business need, team scale, timeline, and contact. The CC team uses those inputs to run the readiness model and present a deployment recommendation on the first call.
Ready to stop doing this manually?
We map your workflows, deploy the right AI Worker, and guarantee the math pencils out before you sign.