Routine eats your day: 10 processes a small business should automate first
Which processes a small business should automate first — leads, bookings, documents, orders, reports — and how to calculate the hours automation frees up.
Short answer: automate first the processes that repeat daily, follow clear rules and cost money when they go wrong: sending leads to a CRM, answering routine questions, online booking with reminders, documents from templates, order processing, price and stock updates, payment reminders and reports. You don’t have to guess how much time it will free up — just calculate it: repetitions per week × minutes per repetition × number of people.
A typical day for a small business owner: copy an enquiry from a form into a spreadsheet, forward it to a colleague, remind a client about an appointment, raise an invoice, check a payment, update prices on the website, pull together a report for yourself. Each takes a few minutes; together they take hours. Below are 10 processes that usually make a visible difference, a method for measuring the time, and the order to tackle them in.
How to measure how much time routine takes
We don’t quote “industry average” savings — every business has different volumes. Instead, here’s a method that takes one week of observation:
- List repetitive tasks. Everything the team does the same way every time: moving data, reminders, documents, checks.
- Count the frequency. How many times a week it happens. Use the CRM, email and order history, not memory.
- Time it. Clock a single task a few times, including switching between apps — that’s often where most time goes.
- Multiply. Hours per week = repetitions × minutes ÷ 60 × number of people doing it.
- Add the cost of mistakes. How many lost leads, wrong invoices and missed appointments per month, and what each one cost. If nobody has been counting lost leads, this guide to where enquiries disappear shows how to find them.
- Compare with the cost of automation. Hourly cost × hours freed × 12 months plus avoided mistakes, against the one-off setup and any monthly subscriptions.
A worked example (illustrative numbers to show the method, not a client result): 40 enquiries a week × 5 minutes to copy and forward each = 200 minutes, over 3 hours a week on a single task. Plug in your own numbers and the starting point becomes obvious.
A worksheet template
| Process | Repetitions per week | Minutes each | People | Hours per week | Mistakes per month |
|---|---|---|---|---|---|
| Copying enquiries into a spreadsheet | … | … | … | = repetitions × minutes ÷ 60 × people | … |
| Appointment reminders | … | … | … | … | … |
| Invoices and receipts | … | … | … | … | … |
Fill it in with your team: the people doing the work every day know best where time leaks.
10 processes to automate first
| # | Process | Done by hand | After automation | What to measure |
|---|---|---|---|---|
| 1 | Leads from the website, messengers and ads | Copied into a sheet, forwarded to sales | The lead appears in the CRM and in a team chat automatically | Leads per week × minutes to copy; lost leads |
| 2 | Answers to routine questions | Same replies about prices, hours, shipping | A chatbot answers and hands complex cases to a person | Repeated questions × minutes per reply |
| 3 | Bookings and reminders | Phone calls, a paper diary, double bookings | Online booking, a clash-free calendar, automatic reminders | Booking calls; no-shows |
| 4 | Invoices, contracts, receipts | Copying a template, typing details by hand | The document is generated from the deal record in the CRM | Documents per week × minutes; errors in details |
| 5 | Online store orders | Re-entering into accounting, creating shipments, emailing the customer | The order flows to the CRM, accounting and shipping automatically | Orders × steps × minutes |
| 6 | Catalogue, prices and stock | Updating the website by hand from the inventory system | Scheduled import from inventory to the site | Changing SKUs × update frequency; sales of out-of-stock items |
| 7 | Payment reminders and repeat sales | Someone remembers when they can | The CRM reminds the customer and assigns a task | Overdue payments; customers never offered a repeat purchase |
| 8 | Owner reports | Pulling numbers from several dashboards into a sheet | A dashboard updates itself or a report arrives each morning | Hours per report × frequency |
| 9 | Moving data between systems | The same data typed into the CRM, accounting and a sheet | Entered once and synced | Duplicate entries per week; mismatches between systems |
| 10 | Tasks from email and chats, scheduled publishing | Creating tasks and publishing by hand | A message becomes a task, content goes out on schedule | Requests that get lost; hours spent publishing |
In which order to automate
Score each process from 1 to 3 on three criteria and start with the highest totals:
- Frequency — daily (3), weekly (2), less often (1).
- Cost of a mistake — a lost customer or money (3), an inconvenience (2), next to nothing (1).
- Simplicity — clear rules and systems with APIs (3), some exceptions (2), every case is unique (1).
Leads (item 1) almost always come out on top: they happen daily, every lost one is a lost customer, and the rules are simple.
Checklist before you automate
- The process is written down: who, what, in which system, what to do with exceptions.
- You know the source of truth: prices in inventory, customers in the CRM — not in five spreadsheets.
- You’ve checked whether your tools have APIs or ready-made integrations.
- Someone is responsible for receiving failure alerts.
- Current numbers (hours, mistakes) are recorded so you can compare in a month.
- Service accounts and access are registered to the business, not the contractor.
No-code tools or a custom integration
| Criterion | Make, Zapier, n8n | Custom integration or CRM |
|---|---|---|
| Getting started | Fast, no coding | Longer, needs development |
| Cost over time | Subscription grows with the number of operations | One-off build, then hosting and support |
| Complex logic and exceptions | Quickly gets tangled | Described in code and documentation |
| Data | Passes through a third-party service | Stays in your systems |
| When to choose | Simple links, low volume, testing an idea | High volume, core processes, specific requirements |
If most of your processes revolve around customers, consider a CRM as the hub — see custom vs off-the-shelf CRM. For tasks that need more than moving data — sorting enquiries, drafting replies — AI agents are a good fit.
What you can do yourself today
Some routine can go without a developer or a budget:
- Saved replies in messengers and email for your five most common questions.
- Email filters and labels so enquiries, invoices and newsletters don’t mix.
- Calendar reminders for recurring jobs: payment checks, price updates, reports.
- Scheduled reports from Google Analytics or ad platforms by email instead of collecting numbers by hand. For reports that show lead sources and not just visits, see lead source tracking for small businesses.
- One shared sheet or CRM instead of several personal ones — that alone removes some duplication.
If there’s still too much routine after that, you’ve reached the processes that need a real integration.
From our work
- Shopify store for a supplements brand. Orders and enquiries flow automatically into the CRM, the team’s Telegram and email; customers choose a delivery point and pay online without calling anyone (processes 1 and 5).
- Building materials store on WooCommerce. The catalogue is imported from the accounting system, so the range on the site matches inventory with no manual entry (process 6).
- University admissions website. An applicant’s enquiry goes straight into the learning platform, and an AI assistant answers common admissions questions (processes 1 and 2).
- Our own products. WorkPilot — AI agents that run projects and turn email, Jira and Telegram messages into tasks — and Autopilot Posts, a WordPress plugin for scheduled automatic publishing (process 10).
Common mistakes
- Automating chaos. If everyone works their own way, automation locks in the mess. Agree on one way first.
- Starting with the hardest thing. An accounting integration with hundreds of rules is a poor first project. Take a quick win on leads.
- No failure monitoring. Automation without error alerts quietly stops, and you hear about it from customers.
- Not measuring before and after. Without baseline numbers you can’t tell whether it paid off.
- Forgetting the team. If people don’t know what changed and why, they’ll keep a parallel spreadsheet “just in case” and nothing is saved.
How to tell it worked
A month after launch, return to the worksheet and fill it in again. Look at four things:
- hours per week now spent on the process;
- mistakes and lost leads, bookings or payments in the month;
- how quickly customers get a reply or confirmation;
- how often the automation failed and how fast you found out.
If the numbers improved, take the next process from the list. If not, look for where people work around the new flow by hand — usually there’s an awkward step to fix, not a bad idea.
When to bring us in
If “Your team is buried in manual work” sounds familiar, start with a short conversation: describe the 3–5 processes that annoy you most and we’ll help work out which will make the biggest difference. We do business process automation and system integrations (from €800), custom CRM development (from €2,000), online booking (from €600) and AI services (from €1,000).
Tell us what takes up most of your time and we’ll say what to automate first.
FAQ
Where should I start if the budget is tight?
With the process that repeats most often and where mistakes cost money — usually enquiries from the website and messengers that should land in a CRM and notify the team. It’s affordable, pays back quickly and doesn’t disrupt how people work.
How much does small business automation cost?
Our process automation and integrations start at €800, a custom CRM at €2,000, online booking at €600 and a chatbot at €500. The exact price depends on how many systems need connecting and whether they have APIs.
Make, Zapier or a custom integration — which should I choose?
Ready-made tools are good for simple connections and low volume. A custom integration makes sense when there are many operations, the monthly subscription keeps growing, the logic is complex, or the data shouldn’t pass through third-party services.
What if one service changes its API and everything breaks?
It can happen, which is why proper automation includes error alerts, an operations log and documentation. Then a failure is visible immediately, not a week later when customers complain.
Will automation replace my staff?
Usually not. It takes over copying, reminders and checks, while people focus on customers, sales and decisions. If a process is chaotic, automation only speeds up the chaos, so describe the process first.