Automating quote follow-ups without sounding like a robot
Most quotes die of silence, not rejection. The follow-up rarely happens because you are up a ladder when it should be sent. Automation fixes the timing. This article is about fixing the tone, so the message that arrives still sounds like you.
Why follow-ups do not happen
Ask any builder how many quotes they sent last month and how many they chased, and the second number is usually a fraction of the first. Not because chasing does not work, but because chasing is admin, and admin loses to site work every single day. The quote goes out, the client goes quiet, and by the time you remember to call, another firm has already been round.
The uncomfortable truth is that a client who has not replied is usually not saying no. They are comparing prices, waiting on a mortgage adviser, or simply busy. A polite nudge at the right moment often restarts the conversation. The firm that nudges reliably wins jobs the others assumed were dead. That is why quote speed and follow-up discipline are two halves of the same advantage.
Automation is the honest answer to the discipline problem. A machine never forgets day three. The risk is that a machine also writes like a machine, and homeowners can smell a mail-merge a mile off. So the job splits cleanly: let software own the timing, and keep the words yours.
The sequence that works
You do not need a marketing funnel. You need three or four short messages spaced across two to three weeks, each with a genuine reason to exist. As a rule of thumb, a good rhythm looks like this:
| When | Message | Job it does |
|---|---|---|
| Day 0 | Quote plus a short cover note | Frames the price and what is included |
| Day 1 | Did it come through, any questions | Catches spam folders and confusion early |
| Day 4 | Offer a call to walk through the numbers | Surfaces objections while they are fresh |
| Day 10 | Diary is filling, when suits a start date | Gentle urgency without pressure |
| Day 21 | Close the file politely, door open | Ends the loop and often triggers a reply |
Notice none of these say "just checking in". Every message gives the client something: reassurance, an offer, useful information about your availability. That is the difference between following up and pestering.
Writing messages a robot could not have written
The automation platform sends the message, but you write it, once, in your own voice. A few rules keep it human:
- Write it like a text to a mate's parent. Polite, plain, first name. No "Dear Valued Customer", no corporate sign-offs.
- Merge in real details, not just a name. "The rear extension on Alder Road" beats "your project". If your quote tool holds the job description, use it.
- Keep it under four sentences. Long automated emails read as newsletters. Short ones read as a person.
- Send from your actual address, not noreply@. Replies must land back with you.
- Vary the channel. An email on day one, a text on day four. A text saying "Morning John, any questions on the quote? Happy to talk it through. Dave" is almost impossible to distinguish from a manual one, because apart from the timing, it is not.
The handoff rule: automation stops the moment they reply
This is the rule that protects your reputation. The instant a client replies, phones, or accepts, every remaining scheduled message must cancel. Nothing torches trust faster than answering a client's question on Tuesday and having your own software chase them "for a response" on Wednesday. Any decent automation tool supports a stop-on-reply condition. If yours does not, do not use it for follow-ups.
The same logic applies to edge cases. Job lost? Stop the sequence and send the gracious close-out instead. Client asked for a revised price? Pause everything until the new quote is out. Automation handles the default path; humans handle everything interesting.
Wiring it up
The plumbing is simpler than most builders expect. The trigger is "quote sent", the actions are the scheduled messages, and the stop condition is any reply. You can build this with the automation features in an email tool, a simple CRM, or a connector platform sitting between your quoting software and your inbox. If you already produce quotes in a structured tool rather than a Word document, the trigger is clean and reliable, which is half the battle. It also helps if the quote itself is clear enough that the follow-up has something worth discussing, which is where presentation earns its keep. QS Quoter, for example, produces an itemised client copy of every quote, so the day-four message can genuinely offer to walk through the numbers line by line.
Pair the sequence with a small library of saved templates so the wording stays consistent even when you do step in manually. If your enquiries, quotes and follow-ups live in three disconnected places, fix that first; AGMM installs this kind of joined-up workflow for trade firms as part of its commercial automation work, always piloted before go-live.
What to measure
Keep the scoreboard small. Track three numbers monthly: quotes sent, replies received within 21 days, and jobs won. Before automation, most firms have no idea what their reply rate is, because follow-up was sporadic. After a month or two of consistent sequences you will have a baseline, and you can test one change at a time: a different day-four message, a text instead of an email, a shorter close-out. Change one thing, watch one month, keep what works.
Do not expect miracles from the words themselves. The gain comes from the follow-up existing at all, every time, for every quote. Consistency is the feature. And resist the urge to add a fifth and sixth message when the sequence starts working; past the close-out, extra nudges stop reading as diligence and start reading as need. The robot's job is never forgetting; your job is making sure it never sounds like a robot doing it.
See what automation is worth in your business
AGMM installs custom automation into trade firms: a discovery call first, then a quantified business case, a week-by-week install and a pilot before anything goes live.
Book a discovery call