Five business processes worth automating first
The first automation should be boring, frequent and measurable. Five processes that fit in almost every company, and what to keep human.
The short answer
The first automation project in a company should be chosen for its odds of success, not for its ambition. That means a process that happens often, follows rules most of the time, annoys the people who do it, and can be measured before and after. Five processes meet that bar in the businesses we meet.
- Inbound email triage. Every message that lands in info@ or sales@ gets read, classified and routed: quote request, support question, invoice, spam, everything else. AI does the reading and sorting; automation creates the record and assigns it; a person answers. The win is that nothing waits unnoticed in a shared inbox.
- Quote and proposal follow-up. A proposal goes out and then depends on someone remembering to follow up. Automation checks after a set number of days, AI drafts a short, specific follow-up based on the original proposal, a person approves it in one click. Deals stop dying of silence.
- Invoice and receipt intake. Supplier invoices arrive as PDFs and photos in three inboxes. AI extracts supplier, amount, date and reference; automation matches them to a purchase order or a project and files them in the accounting system; a person approves anything that does not match. Bookkeeping stops being a monthly archaeology dig.
- Appointment confirmations and reminders. Booking made, confirmation sent, reminder the day before, a message when someone does not show, a rebooking link. Pure automation, no AI needed, and one of the fastest returns because no-shows are expensive.
- The weekly report. Someone spends a morning copying numbers from four systems into a document. Automation pulls the numbers on a schedule; AI writes the two paragraphs of commentary as a draft; a person adds what the numbers do not say. The report arrives on Monday morning without anyone building it.
What they have in common
| Process | Frequency | Rule share | AI step | Human keeps |
|---|---|---|---|---|
| Email triage | Daily | High | Classify, extract | The reply |
| Quote follow-up | Weekly | High | Draft the message | Approval, negotiation |
| Invoice intake | Weekly | Medium | Read the document | Approval of mismatches |
| Reminders | Daily | Very high | None needed | Exceptions |
| Weekly report | Weekly | High | Draft commentary | Interpretation |
None of them is impressive in a demo. All of them return hours every week, and each one teaches the team how to work with a system that does part of their job.
How to pick your first one
Measure the current cost in hours per week, with the people involved, before anything is built. After the automation runs for a month, measure again. That difference is the case for project two.
What this means for you
You do not need an AI strategy to start. You need one dull process, a clear map of it, and a month of measurement. The five above are the safest places to look. Once the first one works and the team trusts it, the harder and more valuable processes become possible, because the foundations, access, logging and the habit of checking, are already in place.
Frequently asked questions
Why not start with the process that costs the most?
Because the most expensive process is usually the most complex, with the most exceptions and the most people who need to trust the result. A first project has to succeed to earn the second one. Start where success is likely, then move up.
Do these need custom development or can I use a no-code tool?
The simplest versions work in no-code tools, and that is a fine way to start. They break when the process has exceptions, touches several systems, or needs an AI step with your own data. At that point custom automation is more reliable and cheaper to run.
How long does a first automation take?
Mapping the process takes a workshop. Building a single well-defined automation is a matter of days to a few weeks depending on the systems involved. The slow part is usually access: getting the right permissions to your email, CRM and accounting tools.
What if my team is worried about being replaced?
Involve them in the mapping. The people who do the work know where the exceptions are, and they are usually the first to point at the part they would happily never do again. Automating that part and leaving the decisions with them tends to be welcomed, not feared.