Guide · Automation · 7 min read · 27 October 2026
The order we use on every build — ranked by how fast each one pays back.
The usual automation mistake isn't building too little. It's building the wrong thing first — a clever twelve-step workflow nobody trusts, while the enquiry that came in at 6pm Friday still hasn't had a reply on Monday.
So we rank by payback. These are the five we build first, in order, on almost every CRM. Then the three we're usually asked for and usually talk people out of.
An enquiry arrives (form, email, missed call). Within a minute the person gets a short, personalised reply with a booking link, by email and SMS. A contact and deal are created, assigned, and a follow-up task is set.
Why first: the first business to reply usually wins the job, and most replies take hours. This one workflow changes your conversion rate before you touch anything else. It's also the simplest to build and the easiest to trust.
What not to do: don't make the reply sound like a robot. One real sentence, your name, a link. No "Thank you for your enquiry! A member of our team…"
Quote sent and no reply in 48 hours? A friendly nudge goes out and a task appears. Proposal opened three times? A call task for the owner. Still quiet at day seven? A different message, then a close-out at day fourteen so the pipeline stays honest.
Why second: most lost deals aren't lost — they're forgotten. Follow-ups are where the money leaks, and they're the task humans are worst at.
New work goes to the right person automatically — by territory, job type, capacity or round-robin — with the context attached. Nobody has to triage an inbox, and nothing sits unowned.
Why third: it only matters once there's more than one person doing the work. If that's you, it removes a daily chore and the "I thought you had it" conversations.
Deal marked won. A job is created with its stages, the kick-off is booked, the client gets a portal invite, the first invoice is raised in Xero, the delivery team is notified. One click — or none.
Why fourth: handover is where things fall through cracks, and where clients form their first impression of how organised you are. It's also where the integrations earn their keep.
Monday morning: pipeline value, what moved last week, overdue follow-ups, response times — in your inbox or Slack, pulled live from the CRM. Deal-rot warnings mid-week. No exports, no Friday spreadsheet.
Why fifth: once the first four are running, the data is clean enough to trust. Reporting before that just automates the wrong numbers.
Until you have a few hundred closed deals, there's nothing to learn from. A simple rule — source + job value + postcode — beats a model you can't explain. Revisit in a year.
For most service businesses a two-touch follow-up converts about as well as a twelve-touch one, and the long version is a maintenance burden. Start short; lengthen only when the data says to.
If two people on the team describe the process differently, automating it just makes the disagreement run faster. Draw it, agree it, then build it. Every automation we ship starts as a flow on a whiteboard that the client signs off.
Each workflow runs on n8n in your own cloud account, connected directly to your CRM's database and the tools you already use. Every one is documented, versioned, and sends an alert if it fails — so nothing silently stops. We switch them on one at a time, so your team notices the admin disappearing rather than chaos arriving.
Want to know which of these would pay back fastest for you? That's most of a scoping call.
Book a Scoping Call