On this page10 sections
The best first process to automate is one that happens often, follows clear rules, takes structured inputs, and does little damage when it goes wrong. List the repetitive work in your business, score each task on volume, rule clarity, input quality, risk and time spent, then pick the highest-scoring task that one small automation can handle from start to finish. A modest first win that runs every day teaches you more than an ambitious project that stalls halfway.
This is the method we use in a first conversation with a business that wants to automate but does not know where to start.
Why does the first automation matter so much?
The first automation sets expectations for everything after it. If it works quietly and saves time every week, people trust the next one. If it breaks, produces errors nobody notices, or takes months to deliver, the whole idea gets labelled as "tried that, didn't work".
A good first project is therefore chosen for reliability and speed of delivery, even if a bigger opportunity exists elsewhere. You can go after the bigger one second, with experience and goodwill behind you.
Step 1: How do you list candidate processes?
Ask the people who do the work as well as their managers. A useful prompt is: "What do you do every week that feels like copying and pasting?" Typical answers:
- Copying new enquiries from a web form into a CRM or spreadsheet
- Sending the same follow-up email after a meeting or quote
- Creating invoices from completed orders
- Chasing approvals for expenses or purchase requests
- Producing a weekly report from two or three systems
- Moving files from email attachments into the right folders
- Updating stock or order status between a shop and an accounting tool
Write each down as a short sentence with a trigger and an outcome: "When a form is submitted, the lead is added to the CRM and assigned to a salesperson."
Step 2: How do you score each candidate?
Score each process from 1 to 5 on five questions:
- Volume. How often does it happen? Daily scores higher than monthly.
- Rule clarity. Could you write down every decision in it as "if this, then that"? A process full of judgment calls scores low.
- Input quality. Do the inputs arrive in a consistent, structured form, such as form fields or system records? Free-text emails and scanned documents score lower.
- Low risk. If the automation makes a mistake, how bad is it? A misfiled document is minor. A payment sent twice is serious. Lower risk scores higher.
- Time spent. How many hours a week does it take across everyone involved?
Add the scores. The top three or four are your shortlist.
Step 3: Which candidates should you drop?
Remove from the shortlist anything that:
- Depends on a system with no way in. If a tool has no API, no export and no integration, automation becomes fragile screen-clicking.
- Changes every few weeks. A process still being redesigned will break any automation built on it.
- Nobody owns. Every automation needs a person who notices when it stops and decides what to do.
- Is broken already. Automating a bad process makes it fail faster. Fix the steps first, then automate.
Step 4: How do you map the winning process?
Before building, write the process out step by step, including the exceptions:
- What triggers it?
- What information does it need, and where does each piece come from?
- What decisions are made, and on what rule?
- What does it produce, and where does the result go?
- What happens when something is missing or unusual?
The exceptions are where most of the work lies. A process that is simple ninety percent of the time may have a long tail of odd cases. Decide which ones the automation handles and which ones it hands to a person.
Step 5: How do you build it so it can fail safely?
A first automation should be small, visible and easy to switch off:
- Start with one path, the common case, and route everything else to a person.
- Log every run: what came in, what was done, and whether it succeeded.
- Alert a named person when a run fails, instead of failing silently.
- Keep a human approval step for anything that sends money, sends messages to customers, or deletes data, at least until it has a track record.
- Run it alongside the manual process for a week or two and compare the results before switching the manual work off.
Where does AI fit in?
Many processes fail the "structured inputs" test because the information arrives as free text: an email asking for a quote, an invoice PDF, a support message. Language models can now turn that kind of input into structured fields, which makes some of those processes automatable.
That is useful, but it adds uncertainty. A rules-based step either works or throws an error. A model can produce a confident wrong answer. For a first automation, prefer a process with structured inputs. If the best candidate needs AI, keep a person checking the model's output until you have measured how often it is right.
What are good and bad first candidates?
Good first candidates usually look like this:
- New web enquiries added to the CRM, assigned, and acknowledged by email.
- A weekly sales report assembled from two systems and sent every Monday.
- Signed quotes turned into draft invoices for someone to approve.
Weaker first candidates:
- Fully automated customer support replies.
- Anything involving payments without human approval.
- Processes spread across five departments with no single owner.
If your web enquiries are part of the plan, it is worth making sure the form is converting before automating what happens next. Our landing page checklist covers that.
What should you measure after launch?
Track three numbers: how many runs succeeded, how many needed a person, and how much time the process now takes compared with before. Review them after a month. If the automation is reliable, widen it to handle more of the exceptions, or move to the next process on your list.
Working with Syntora Ai
Syntora Ai maps business processes and builds automation for the steps nobody should do by hand, starting with a free 30-minute process audit. If you want help picking and building your first automation, write to hello@syntorahq.ai or see our automation practice.