Article
What to automate first when the CRM is ready
The fields are owned, the dropdowns are fixed, and the team finally trusts what the CRM says. Now the question changes from "can we automate?" to "what goes first?" Here is how we pick the first workflow, what we leave for later, and the order we build in.
Getting the CRM to a trustworthy state is real work. We have written about fixing the data before you add the agent, about where agents read bad CRM fields, and about what breaks when you automate on a messy CRM.
This post picks up after that. The data is in good shape. The temptation now is to automate everything at once, starting with whatever sounds most impressive.
That is usually the wrong place to start.
Four tests for a first automation
The first automation has two jobs. It should save your team real time, and it should prove the automation can be trusted. A good first candidate passes all four of these.
1. It happens a lot
Pick something your team does every day, or many times a week. Something that happens once a quarter is not worth automating first. Frequency is where the time comes back, and it is also how you find problems quickly instead of months later.
2. The rule is clear
If you can write the rule on a sticky note, it is a good candidate. "When a new enquiry comes in with service type X, create the record and assign it to Y." If the rule needs a paragraph of exceptions, or a person says "it depends", that step is not ready to run on its own.
3. A mistake is small
Ask what happens if it gets one wrong. A task assigned to the wrong person internally is a small fix. A wrong email to a customer, or a wrong amount on an invoice, is not. Start where a mistake stays inside the team.
4. It is easy to check and undo
Someone should be able to see straight away whether the automation got it right, and reverse it simply if it did not. If checking the result takes as long as doing the job by hand, or the action cannot be taken back, leave it for later.
Good first candidates
These are patterns, not promises. The first wins tend to look like this:
- Enquiry intake and routing. A form or email comes in, a record is created, and it goes to the right person based on a clean dropdown. High frequency, clear rule, easy to check.
- Internal tasks and reminders. When a stage changes, create the follow-up task or nudge the owner. Nothing leaves the building.
- Moving data between systems you already use. Copying details from a form, a booking tool, or a document into the CRM, so nobody re-types them.
- An internal summary. A weekly digest for the team, built from fields you now trust. Only your own people see it.
What they share: they mostly stay inside your team, they run often, and they are quick to check.
What to leave for later
None of these are off the table. They just should not be first.
- Messages that go to customers without review. Let automation draft them. A person still sends them, at least until the drafts have been right for a good while.
- Anything that touches money. Invoices, refunds, pricing, discounts. Keep a person approving.
- Workflows that move deals on their own. Advancing a stage, closing a job, or marking something lost should stay a human decision early on.
- Judgement calls. Who gets priority, whether a quote is worth chasing, how to handle an unhappy customer. Automation can surface the information. People decide.
- Long chains across several systems. One step that works is better than five steps where nobody can tell which one failed.
A simple order of operations
This is the order we follow, and it is the same idea as the pilot approach on our AI automation for Melbourne businesses page.
- Pick one workflow that passes the four tests above.
- Re-check the fields it reads. Clean last month does not mean clean today. Confirm each field still has an owner and a source of truth, as in our Data Intelligence work.
- Run it in suggest mode first. The automation proposes, a person confirms. You learn where it is wrong without anyone outside seeing it.
- Watch it for a few weeks. Look at what it got right, what it got wrong, and what the team quietly fixed after it.
- Then let it act on its own, with a log of what it did and a clear way to undo it.
- Only then add the next one. Each workflow you add should pass the same tests as the first.
It is slower than switching everything on in one go. It is also how the team ends up trusting the automation instead of working around it.
How Discovery sequences this
This is not a new package. It is how we already run Discovery for AI automation engineering.
We look at the workflows you want automated, check the fields each one depends on, and score every candidate before we build. You come out with an ordered list: what is safe to automate now, what should run with a person approving, and what is better left alone for the moment.
Next step
If your CRM is finally in good shape and you are not sure which automation should go first, that is a good conversation to have before anything gets built.
We look at the workflows you have in mind, sort them by frequency, clarity and risk, and suggest a sensible first one.
Text or WhatsApp 0481 347 115, or book a Discovery session.
Amir
Alphesda Interactive