Automation readiness
When a client follow-up workflow is ready for automation
A readiness test for deciding which agency follow-up steps can be automated and which decisions must remain human-approved.
The team wants automation before it can describe a repeatable follow-up rule or its exceptions.
Automate repetition, not uncertainty
Automation works well when the same input reliably leads to the same low-risk action. It works poorly when the team is still deciding what a qualified opportunity means, who should own it or whether another message is appropriate.
Start by observing 10–30 recent opportunities. The goal is to find a narrow repeated flow, not to replace the CRM or connect every tool.
Four readiness conditions
Treat the workflow as automation-ready only when all four conditions are visible in real records.
- Trigger: the event that starts the action can be detected consistently
- Input: the required fields are present and authorised for use
- Rule: the proposed action is predictable enough to explain
- Exception: missing data, opt-outs and unusual cases stop safely for human review
What can run automatically first
Begin with internal preparation: flag overdue actions, organise an approval queue, suggest a next-action date and prepare editable drafts. Keep sending, pricing, promises and relationship-sensitive decisions behind human approval.
Common questions
Should follow-up emails be sent automatically?
Not by default. First prove the trigger, audience, message rule and opt-out handling. Preparing an editable draft is a safer initial automation than sending it.
Does automation require replacing the CRM?
No. A narrow follow-up workflow can operate with existing tools if the required data and action states are accessible and reliable.
How much history is enough for a readiness review?
ClientMorrow begins with 10–30 recent opportunities because that is usually enough to expose repeated states and exceptions without turning the review into a data-migration project.