Small business automation: what to automate first, and who keeps it running

Small business automation pays off fastest on jobs your team does often, that take real time, and that cost money when they go wrong. Start with the automations already built into software you pay for. Move to a no-code tool such as Power Automate or Zapier when two systems need joining. And before you switch anything on, decide who will own it, watch it and fix it. That last step is the one most businesses skip, and it's usually why automations quietly stop working.

Ask three questions about each repetitive task and score each answer from 1 (low) to 3 (high):

1. How often does it happen? Monthly scores 1, weekly 2, daily 3.
2. How long does it take each time? A couple of minutes scores 1. Half an hour or more scores 3.
3. What does a mistake cost? A typo nobody notices scores 1. A missed invoice, a wrong price or an unhappy customer scores 3.

Multiply the three. The top score is 27. Anything around 12 or above is worth automating. Below about 6, the time you'd spend building and looking after the automation usually outweighs the time it saves.

Error cost matters more than people expect: a monthly job that's easy to get wrong, such as exporting hours for payroll, can beat a daily job that's merely boring.

One more filter before you build: only automate a process you could write down step by step. If three people do it three different ways, an automation just makes the confusion faster. Our guide to mapping a business process in an afternoon shows how to get it on paper first, and the map doubles as the spec for the automation.

Before buying anything, use the automation inside software you already pay for. It costs nothing extra and the supplier keeps it working.

• Accounts: Xero can email reminders for unpaid invoices before or after the due date, and create and send repeating invoices on a schedule. QuickBooks and Sage have similar features.
• Email and files: Outlook rules sort, forward and flag mail, and Microsoft Forms collects requests in a consistent shape.
• CRM and job systems: most can assign new enquiries, send follow-up reminders or move a job on when its status changes, often on higher plans only.

The honest limit: built-in automations stop at the edge of the product. Xero can chase an invoice, but it can't create that invoice from a quote sitting in your job system. As soon as the work crosses from one system to another, you need something to join them.

These are the no-code tools most small businesses reach for to join systems together. They all follow the same pattern: when this happens in one app, do that in another. Here's what each automates, what it costs and where it runs out of road. Prices were checked on each supplier's pricing page on 10 October 2026.

Power Automate is Microsoft's tool, and if you're on Microsoft 365 you probably have it already. Business and enterprise licences let each user build cloud flows with standard connectors (Outlook, SharePoint, Teams, Excel Online, Forms and more), up to 6,000 actions per user per day. Premium connectors, which cover many non-Microsoft systems, need Power Automate Premium at £11.50 per user a month (paid yearly, excluding VAT). Honest limit: by default a flow belongs to the person who built it and runs on their login. It fits best when your IT provider already manages your Microsoft 365 and can see the flows in your tenant.

Zapier connects thousands of apps and is the easiest to learn. The free plan gives 100 tasks a month with two-step Zaps only. Professional starts at $19.99 a month paid yearly ($29.99 monthly) for 750 tasks; Team at $69 a month paid yearly. Honest limit: every completed action counts as a task, so costs rise with volume. On Free and Professional, a Zap that keeps failing can be switched off without the warning email and grace period Team and Enterprise accounts get.

Make (formerly Integromat) lays flows out visually and handles branches and loops well. The free plan includes 1,000 credits a month and two active scenarios. Core starts at $9 a month paid yearly ($10.59 paid monthly) for 10,000 credits. Honest limit: each step uses credits for every item it processes, so a flow that loops over 50 invoice lines uses roughly 50 credits per step, per run. Big scenarios get hard for anyone but their builder to follow.

n8n appeals to more technical teams. Its cloud Starter plan is €20 a month (paid yearly) for 2,500 workflow runs, and Pro is €50. The self-hosted community edition is free for internal business use under n8n's Sustainable Use Licence. Honest limit: self-hosting means someone has to patch, back up and monitor the server. The software is free; the looking after isn't.

What none of these tools does is know your business. They move data between apps well, but rules such as how you price a job end up typed into conditions inside a flow, where few people will ever read them. Fine for simple hand-offs; a risk when the rules are the valuable part.

Building a flow takes an afternoon. Keeping it working for three years is the real job. Automations tend to fail in four ways.

Nobody sees the failure. In most tools, failure emails go to whoever built the flow. If that's a busy director, or someone who's left, the alerts land in an inbox nobody reads. You find out when a customer asks why they never got their invoice.

The login belongs to one person. Microsoft says a Power Automate flow becomes "orphaned" when its owner leaves and there's no co-owner, and connections that sign in as that person can start failing. Zapier and Make connections work the same way: each one is signed in as somebody. Disable that account during offboarding and the flow stops.

The other end changes. Software suppliers change their side without asking you. Microsoft retired the old Office 365 Connectors in Teams, and after several extensions they stopped working between 18 and 22 May 2026. Anything posting alerts into Teams that way had to be moved to the new Workflows app, and someone had to notice first.

Costs creep. Task and credit bills grow with volume. Zapier's pay-per-task option charges overage at 1.25 times the base rate on yearly plans and 2.5 times on monthly plans. Add a few personal subscriptions on company cards and nobody has the full picture.

So who should own them? Split it in two. The business owns the process: what the automation should do, and who signs off a change. Your IT provider is often best placed to own the platform: the Microsoft 365 tenant, shared service accounts, licences, who has access, and where failure alerts go. Many managed IT providers already look after Power Automate for their clients, so ask yours what they cover. Whatever you agree, write it down: who builds, who gets the alert, who fixes it, and how quickly.

Run through this for every automation that matters, new or old:

• Two named owners: one in the business, one technical (often your IT provider).
• No personal logins: it runs on a shared or service account, with at least two co-owners.
• Alerts that get read: failures go to a shared mailbox or your IT provider's ticket queue, not one person's inbox.
• A one-page note: what starts it, what it changes, which systems it touches, and what to do if it stops.
• A list of connections: every app it uses and which account each connection signs in with.
• A monthly look: check the run history and task or credit usage against your plan.
• Part of offboarding: when someone leaves, check which flows they own before their account is disabled.
• A test after changes: re-run it when a connected system changes.
• An off switch: how to turn it off safely, and the manual fallback.
• A data check: if any step sends information to an AI tool, make sure it fits your AI policy. Here's a free UK AI policy template if you don't have one yet.

No-code flows are the right answer for lots of jobs. A properly built and maintained connection makes sense when:

• It handles money. Quotes, invoices, prices or payroll, where a silent failure costs real money before anyone notices.
• The rules are the hard part. Dozens of branches, lookups into spreadsheets, or pricing logic that only one person understands.
• It keeps breaking. Someone spends hours every month nursing it back to life.
• Running costs grow with volume. Per-task fees climb every time the business grows.
• It's how you win work. If the way you price or run jobs is what sets you apart, it's worth owning rather than renting.

"Properly built" means tested, logged and documented code, with alerts going to a named team, hosted and looked after rather than running on someone's account. When we build one, the client owns the code and the data, we host it and give second-line support for what we built, and your IT provider keeps the Microsoft 365 tenant, licences and access. It's one piece of work at a fixed price, starting with the task that scored highest. For one UK specialist supplier, we replaced a one-person quoting spreadsheet with a tool the whole team uses: a quote went from about 1–2 hours to about 5 minutes.

And when it isn't worth it: if a built-in feature or a simple Zap does the job and someone owns it, keep it. For the costs of building, see how much bespoke software costs in the UK, and if spreadsheets are where the trouble started, our free guide Outgrown your spreadsheets? Buy, connect or build walks through all three options with real prices.