How this list is ordered
Frequency decides the order, ahead of irritation. A job that runs many times a month returns more time than one that runs twice, however much the twice-a-month job grates. Each task below is one that repeats often in a business that sells to customers, follows a predictable shape, and produces output that can be checked before it leaves the building.
Three questions filter any candidate. Does it happen at least weekly? Does it follow the same shape each time? If it goes wrong, can you catch it before a customer sees it? A task that answers yes three times belongs on the build list. A task that fails the third question needs its review step designed first.
The five, in build order
- The first reply to a new enquiry. This runs more often than anything else on the list and it sets the tone for every deal that follows.
The pattern is the same everywhere. An enquiry arrives through a form, an inbox or a phone message. Something reads it, classifies it by service, writes a record, sends an acknowledgement that names what happens next and when, and notifies the right person. On a good build, the acknowledgement carries the answer to the two questions every enquirer has: are you the right firm for this, and when will I hear from a human.
Keep the classification honest. If the enquiry does not fit a known category, route it to a person and say so. The failure mode here is confident misrouting: a specialist job answered with a generic template, which reads worse than no reply at all.
One legal boundary matters. An acknowledgement of an enquiry is a transactional message. Adding that person to a mailing list is direct marketing, and the ICO's PECR guidance requires consent, or the soft opt-in that covers your own previous customers who bought or negotiated to buy a similar product, where you gave them a clear chance to opt out both when you collected their details and in every message since.
- Invoices, and the chase that follows. Money moves faster when nobody has to remember to ask for it.
Two UK rules shape this one. GOV.UK's guidance on Making Tax Digital for Income Tax, checked in September 2026, puts the start at 6 April 2026 for sole traders and landlords whose qualifying income from self-employment and property is over £50,000, requiring digital records and quarterly updates to HMRC through compatible software. The threshold drops to over £30,000 from April 2027 and to over £20,000 from April 2028. Businesses inside that population already need digital records, which removes most of the argument for a spreadsheet in the middle of invoicing.
The second rule is the one small firms use least. Under the Late Payment of Commercial Debts (Interest) Act 1998, a business can charge statutory interest on a late business-to-business payment at 8 per cent plus the Bank of England base rate, along with a fixed sum in compensation for recovery costs, as GOV.UK's guidance on late commercial payments set it out when checked in September 2026. Statutory interest cannot be claimed where the contract sets a different rate.
The reference rate is fixed twice a year. The Late Payment of Commercial Debts (Rate of Interest) (No. 3) Order 2002 sets it at the Bank of England official dealing rate in force on 31 December for interest that starts to run between 1 January and 30 June, and the rate in force on 30 June for interest that starts to run between 1 July and 31 December.
Automate the sequence, and keep the judgement. Issue on completion. Remind at seven days before the due date, on the due date, and at seven, fourteen and thirty days after. Escalate to a person before anything that mentions interest goes out, because that message changes a relationship and deserves a decision.
- Bookings, reminders and the diary. Every missed appointment is a slot you already paid for.
Automate the whole loop: the booking link that respects real availability, the confirmation, the reminder at the interval that suits your trade, the reschedule link, and the calendar write. Where a job needs preparation, have the confirmation collect what you need at the point the customer is already thinking about it, which is the only moment they will answer questions willingly. Reminders are transactional, so they sit outside the marketing rules, and the moment a reminder carries an offer it becomes direct marketing and needs the consent position above.
Decide what happens on a no-show before you build, because the automation will need a rule. Some trades take a deposit at booking and release it on attendance. Others offer one free reschedule and charge on the second. Whichever you choose, the sequence should handle it without anyone opening the diary to work out what stage a customer is at.
- Order, stock and delivery updates. The point here is that two systems stop disagreeing about the same number.
Both major store platforms give you the hooks. WooCommerce webhooks are event notifications sent to a URL you choose, covering order, product, customer and coupon events, with a secret key used to generate a hash in the request headers, and its documentation states that delivery is disabled automatically after more than five consecutive delivery failures. Shopify describes its webhooks as a way to receive near real-time data about shop events, delivered to a URL, a Google Pub/Sub topic or an Amazon EventBridge ARN.
Read the small print before you trust the stream. Shopify states plainly that ordering is not guaranteed within a topic or across topics for the same resource, so an update can arrive before the creation event it belongs to, and recommends using the timestamps in the headers or payload to sequence events yourself. Build for that, and your stock figure survives a busy Saturday. Ignore it, and you will oversell.
- The weekly numbers. The report nobody has time to build is the one that changes decisions.
Pick five numbers that actually steer the week: enquiries received, quotes sent, jobs won, invoices outstanding, and one operational figure specific to your trade. Have the automation assemble them from the systems that already hold them and deliver the same shape every Monday morning.
Push the numbers rather than parking them. A short message that arrives without being asked for is read by people who would never open a dashboard behind a login, so send the five figures rather than a link to them. Where a number moves outside a range you set, have the automation say so in the message rather than leaving it to be spotted.
What to leave alone for now
Anything where a wrong output reaches a customer before a person can intervene. Anything that touches a decision with legal or similarly significant effects on an individual, such as refusing credit or rejecting an applicant, which carries its own safeguards under UK data protection law. Anything held in a system with no API and no export, where the automation would be a person copying and pasting under a different name.
Also leave alone the task that only you can describe. If nobody else in the business can write down the steps, the process is not ready to be automated. Document it first, run it manually from the document for a fortnight, then build.
Who owns each automation
Every automation needs a named owner inside the business, and that person is rarely the one who built it. The owner answers three questions when something goes wrong: what should have happened, what did happen, and who is telling the customer. Write those three answers into the same document that describes the workflow.
Give each automation its own account rather than running it under a member of staff, so a leaver does not take three processes with them. Grant the narrowest permissions the job needs. Review the permissions whenever the job changes, which in practice means whenever you change a price list, a template or a supplier.
The tools, briefly
The connective layer is easy to change and rarely the hard part. Zapier links applications through triggers and actions across a catalogue its own how-it-works page, checked in September 2026, puts at more than 9,000 tools. Make assembles automations as visual scenarios built from modules, with routers, iterators and error handlers for the messy paths. Either will carry all five of the jobs above, as will a purpose-built integration where a platform's own API is the cleaner route.
Choose on two questions. Where does the data sit while a run is in progress, and who can read the logs afterwards. A cheaper tool that puts your customer records somewhere you cannot explain carries a cost you have not counted.
Sequencing the build
Build one, run it for two weeks, then build the next. Each of these five produces data the next one needs: enquiry records feed the quote, quotes feed the invoice, invoices feed the weekly numbers. Building them in order means the fifth has the least new work in it, because everything it reports on already exists in a clean form.
Write the baseline down before the first build. Count last month's enquiries, the average time to first reply, the number of invoices paid late, and the hours spent assembling the last report you produced by hand. Measure the same four numbers a month after each go-live. Those four numbers are the only argument for the next build that anyone in the business needs to hear.