Operations
How to Automate Your Business Without Buying Another Tool
To automate your business, map how work actually moves today, then automate the handoffs — the copy-paste between people and tools — before you buy anything. Most “automation projects” fail because they start with Zapier, n8n, or a CRM and try to force the week into the product. Start with the week. The tools come second.
Most automation projects start in a pricing grid. Zapier versus Make versus n8n versus “we should just build an app”. By the time the cards are on the table the week has not been looked at, and the tool is being asked to invent a process the team does not have.
I design systems for operators — websites, automations, the unglamorous paths that turn an enquiry into a job. The work that holds is always the same shape, whether the stack is Zapier, n8n, or a custom CRM. This is that shape, without the product tour.
1. Map the week as it really runs
Sit next to the person who actually moves the work. Not the founder’s version. Not last year’s SOP. The Tuesday version, with the WhatsApp side-channel and the spreadsheet that “isn’t official”. Write every step, every tool, every wait. If a step only happens when someone remembers, write that down too. That is the process.
You are looking for a line from first contact to money-in-the-bank or job-done. Anything that does not sit on that line is a candidate for later, or for deletion. Automation loves a spine. It hates a pile.
2. Circle the handoffs, not the jobs
People are good at judgement, conversation, and craft. They are expensive at copy-paste. Automation should take the copy-paste: the field that moves from the form to the sheet, the status that should ping Slack, the PDF that should already be in the folder.
- Handoff: “I retype the quote into Monday.” Automate it.
- Handoff: “I email the same three paragraphs when a survey is booked.” Automate it.
- Job: “I decide whether this commercial site needs a different charger.” Do not automate it.
If you automate the job, you get a brittle bot that the team works around. If you automate the handoff, the job gets faster and the bot stays in its lane. That is the whole craft in one distinction.
3. Pick the thinnest layer that holds
Tools are layers, not identities. Use them in order of seriousness.
| Layer | Use it to | Do not use it to |
|---|---|---|
| Zapier / Make | Prove a handoff this week | Run the company at volume |
| n8n | Run branching, volume, or private data | Store the customer record |
| Off-the-shelf CRM | Hold leads and deals you actually have | Fake a job board into a funnel |
| Custom CRM | Hold objects no product sells you | Rebuild email, chat, and billing |
| A person | Exceptions, sales, craft | Re-type fields between two tools |
The operator I see most often tries to skip to the impressive layer because the first one feels unsophisticated. That is how you buy a CRM to avoid mapping a form. I have written separately about moving from Zapier to n8n, and from n8n to a custom CRM, because those moves are real — and they only work if the map came first.
4. Design the failure
Happy-path automation is how you create a new kind of outage: the quiet one. A Zap fails, a quote never lands, a customer waits, and nobody knows because the dashboard is green. Every path needs a place for exceptions and a named human who looks at it.
- When a run fails, it goes to a queue — not only to an email that will be marked read.
- Someone owns that queue the way they own the inbox. It is a shift, not a hobby.
- Replay is a feature. If you cannot rerun a job after fixing the mapping, you will fix it by hand forever.
5. Review monthly against the operation
Count cycle time and rework, not number of workflows. If the team still keeps a shadow sheet “just in case”, the automation is untrusted and you should either fix it or kill it. Systems should get quieter. If they get louder, you have added a product, not a process.
A useful monthly question: what did a person still have to carry between two tools this week? That list is the backlog. Not a feature request from a vendor. Not a new app. The remaining handoffs.
What this looks like in practice
On the waEV-charge work the spine was quote to completion. The site, the calculator, the sheet, the board, and the automations had to describe the same job. Once they did, marketing and firmware upgrades had a place to sit. Before they did, every new tool was another place for the truth to fork.
That is the unglamorous version of “how to automate your business”. It does not start with a logo grid. It starts with a week you can draw, handoffs you can count, and the humility to use a boring tool until the path is real. Then you earn the right to n8n. Then, maybe, a CRM. Not because those words rank. Because the operation ran out of room.
If the process only works when you are in the room, you do not have a business system. You have a habit with an audience.
Keep
- Start with a map of the live week, not a tool comparison.
- Automate handoffs. Do not automate judgement.
- Zapier proves a path, n8n runs it, a CRM remembers it. Use them in that order.
- If nobody owns exceptions, you have not automated the business. You have automated the happy path.
Questions operators actually ask
How do I automate my small business?
Write down how a job actually moves from enquiry to done. Circle every time a human copies data or pokes someone else. Automate those handoffs first with the simplest tool that works. Only then consider a CRM or a rebuild.
What should I automate first?
The step that is frequent, boring, and already rules-based: sending the quote PDF, creating the job on the board, chasing a missing field. Do not start with the politically important work that still needs a person in the room.
How much does business automation cost?
A first Zapier path can be tens of pounds a month. A serious n8n backbone is still cheap compared with a person copying fields. A custom CRM is a project. Cost follows ambition — which is why you should not start at the expensive end.
Do I need a developer to automate my business?
Not for the first handoffs. You need a developer (or a systems designer) when the path branches, talks to odd APIs, or becomes the thing the company runs on. Hiring one too early wastes money. Hiring one too late wastes a year of silent failures.
Keep reading
Need this done on your stack?
I design the system under the operation — site, automations, CRM, or the path between them.
mail@maxwinandy.co.uk