SELL MY SERVICE

Home / Guides / Remembered

How the Aftercare Engine Runs Itself

The theory is easy. Here's the proof: one trigger, five touches that fire on their own, the guards that keep it human, and how to get it built.

Antony Loomans

By Antony Loomans
3 July 2026 · 5 min read

The short version: you mark the job complete. That’s the only button you press. From there the system runs the follow-up on a schedule, holds every ask behind the fix-first check, and keeps itself human with a set of guards. Here is exactly how that works, and how to get it built on your business.

You’ve seen the seven touches. The idea is simple enough: follow up on every job, ask at the right moment, keep the customer. The honest question a tradie asks next is the one that matters: that sounds good, but who actually does all that when I’m flat out?

The answer is nobody. It runs itself. But “it runs itself” is a claim, and claims don’t earn trust. So here is the machine, with the panel off.

What you do

One thing. You mark the job complete.

That’s it. The two human moments stay yours, because they should: the handover on site, and the call if a customer flags a problem. Everything else, the asking, the timing, the reminding, the stopping, happens without you. You are not running a follow-up system. You are doing one job: marking work done.

In a bigger crew, every step here would be someone’s job. If you’re a one-person operation, every job is yours, and that’s exactly why the system carries five of the seven touches. It buys the hours back, and you spend them only where a human being is the difference.

How it works

This is the part nobody shows you, so here it is in full.

One trigger. When you mark a job complete, the clock starts. Every touch after that is counted from that date, so the timing is the same on every job, whether you did one this week or twenty.

The schedule runs on its own.

  • Day 1 to 2 the check goes out: is everything as it should be?
  • Day 3 to 7 the review ask, but only if the check came back clear.
  • Day 14 the value-add: care tips for the work, no sell.
  • Day 30 the referral offer, written so they can forward it in one tap.
  • Day 90 a seasonal nudge matched to the job.
  • A year on the repeat booking, or the service-due reminder.

The gate is automatic. A yes to the check opens the asks. A problem stops everything and pings you to ring the customer. No review ask, no referral ask, nothing goes out over an open problem. The fix-first rule isn’t a good intention you have to hold, it’s wired in.

The guards keep it human. This is why it reads as a tradesperson, not a robot:

  • It only texts in daytime hours. No 9pm pings.
  • The second a customer replies, the run pauses and you get told, so the system never talks over a live conversation.
  • Two review asks, ever. One ask, one reminder, then it stops.
  • Anyone with an unresolved problem is held out of the asks until it’s sorted.

The proof is in the restraint

When you look at how this runs, notice what it does NOT do: it doesn’t blast, it doesn’t pester, it doesn’t ask twice, it doesn’t message at night, and it doesn’t push an ask onto an unhappy customer. A follow-up system that knows when to stay quiet is the one customers don’t mind hearing from. That restraint is the difference between this and the spammy automation everyone has learned to ignore.

How you know it’s working

You watch a simple board. Not forty widgets, a handful of numbers checked weekly: new reviews this month, checks answered, flagged problems where the customer got a call inside 24 hours, and the share of completed jobs that entered the system. That last one has a fixed target: every one. A job that never enters the system is a customer the engine can’t keep. The numbers, not a hunch about whether it’s working.

Then you run it at a target. A simple one: one 90-day sprint, three numbers, ten per cent each against your own baseline. Review velocity up 10%. Referred enquiries up 10%. Repeat-job rate up 10%. Weeks 1–2 set the baseline. Weeks 3–10 the engine runs: the checks, the review asks, the follow-ups. Weeks 11–12 you review what held.

The honest bit: that’s a target you set against your own baseline, not a promise of results. Your numbers depend on your job volume and how cleanly the rules are held. What the board gives you is the difference between knowing and guessing.

How to get it built

You don’t wire this up yourself. That’s the point of it being infrastructure.

We build it onto your business: the trigger on your job board, the timed sequence, the gate, the guards, connected to your own review link, your booking link, your referral offer, written in your voice. Then it runs in the background while you’re on the tools. The human bits stay yours, with the scripts in the handover, the check and referral guides. The machine bits, we set up once.

A repeat customer costs nothing to win: no ad spend, no rented lead, no quote you might lose. At a $3,500 average job value, a customer who comes back once and refers one neighbour who also buys is worth around $7,000 in extra revenue at effectively zero acquisition cost (modelled: 2 × $3,500 average job value). Two of those a month is a second wage in work you didn’t have to chase. That’s the case for building it once and letting it run.

Book a call and we’ll map the engine to your business and set it up. Twenty minutes, and you leave knowing exactly what would run and what it would catch.

Common questions

Do I have to remember to send all seven touches?
No. You mark the job complete, and the two human moments are yours (the handover, and the call if something's flagged). The other five fire on their own on a schedule counted from the completion date. Nothing depends on you remembering, which is the whole point, because remembering is exactly what breaks down when you're flat out on the tools.
Won't automatic messages feel robotic or spammy?
Not the way this is built, and that's down to the guards. It only texts in daytime hours, never at 9pm. The moment a customer replies, the run pauses and you get told, so it never talks over a real conversation. Two review asks maximum, then it stops. Anyone with an unresolved problem is held out of the asks entirely. The restraint is what makes it read as a tradesperson who follows up, not a robot.
What do I actually have to do day to day?
One thing: mark the job complete. That starts the clock. After that the system runs the timed follow-up in the background, and the only time it pulls you in is the moment that matters: a customer flags a problem, and you get a task to ring them within 24 hours. Everything else happens without you.
Can I set this up myself?
The human parts, yes: the handover, the check, the referral offer all have their own guides with scripts you can use today. The automated sequence, the triggers, timing, branches and guards, we build for you and wire to your booking link and review link, in your voice. You don't touch the plumbing.