Automate quote follow-up as a short sequence with a built-in end: a delivery check soon after sending, a reminder halfway through the validity window, a final message before the quote expires, and then silence. Scheduling is the machine’s job. Judgement, price and objections stay with the person who owns the deal.
Lead follow-up is a different job. A lead is a question without an amount, and your first reply time decides it. A quote is an amount with an expiry date, and those two numbers set the rhythm instead. Everything that happens before the quote goes out sits in automate lead follow-up. This article picks up the moment it has gone.
Written for the founder or agency owner who sends a handful of quotes a month, runs sales alongside the delivery work, and has lost at least one deal to nothing worse than a week nobody was watching.
When do you send the first reminder on a quote?
Two working days after sending, and that first message is not really a reminder. It is a delivery check with three questions folded into it: did the quote land, is it with the person who signs off, and does the amount still match the conversation you had.
Send the same message on the day the quote leaves and it reads as impatience. Two days later the identical words read as service, because by then the buyer is asking themselves the same thing. The distinction is not cosmetic. One version is a message about your pipeline, the other is a message about their decision.
How many reminders follow is not a matter of taste either. It comes straight out of the validity period you printed on the document, which is why the next section counts them per window instead of per week. If you cannot say what a message is for on the day it goes out, it has no reason to exist.
How many follow-ups before you stop?
Three at most after the quote goes out, and the validity window decides the exact number:
- Valid for seven days: one message, two working days in. Nothing else fits before the date.
- Valid for fourteen days: the delivery check, then a single reminder three working days before expiry.
- Valid for thirty days: the delivery check, a reminder around the halfway mark, a last message three working days before expiry.
- Any length: a substantive reply ends the sequence, whatever number the counter is on.
- Past the expiry date: nothing automatic. Going back in is a sales decision, not the next step in a workflow.
| moment in the sequence | what the automation sends | what the salesperson does | what ends the sequence |
|---|---|---|---|
| day the quote goes out | the quote itself: expiry date, one amount, one named contact | nothing yet | confirmation that it arrived |
| two working days later | delivery check: did this reach the person who decides | nothing, unless a question comes back | any substantive reply |
| halfway through the validity window | a quote reminder with the expiry date spelled out | calls on every quote above the threshold | a reply, or a meeting in the diary |
| three working days before expiry | final message: this is the date the price lapses | calls on every quote still open | an answer, an extension or a no |
| the expiry date | sets the quote to expired and closes the deal with a reason | decides whether a new quote follows | the sequence is finished |
| after that | nothing | one separate attempt, timed by the owner | no sequence left to stop |
Row one is not follow-up, it is the condition for it: without a date, an amount and one named contact in a field, there is nothing for the sequence to count with. Row two carries a question and no pitch, so a one word answer is enough to shut it down.
The halfway mark is the only point where machine and person move at the same time. The message goes out on schedule; the owner picks up the phone if the amount justifies it. Three working days out, the final message works only because the date is in it, since a reminder without a date gives nobody a reason to decide this week. On the date itself a status changes and nothing else. After that the sequence is inert, which is the entire reason it was built this way.
The threshold amount in rows three and four is the one setting that is different in every company. A few thousand euros, or a few tens of thousands? That answer comes out of margin and capacity, not out of a tool, and it belongs on the table before anyone opens a workflow editor. WeAdapt puts choices like that on paper in a consultancy track first.
Want to know which part of your quote process can run by itself and which part belongs with your salesperson? Book a call.
When does a person take over from the automation?
As soon as the buyer says something back. Silence is something a system handles well on its own; a sentence from a human being is not. There are two kinds of signal in quote follow-up, and they split exactly along that line.
The first kind the sequence recorded itself: the message went out, the date is closing in, nothing came back, the deal status has not moved. Facts about time and about absence. A system can read them without interpreting them, which is why it can safely act on them.
The second kind sits in the buyer’s head. Doubt about the price. A decision maker who was never in the room. A competitor with a proposal on the same desk. A project that slid a quarter. These arrive as half a sentence in an email, or as a silence that means something specific, and no automation can tell those apart. A scheduled message landing in the middle of one of them does active damage.
So absence belongs to the sequence and presence belongs to a person. Any substantive reply switches the sequence off and hands the deal to its owner. Silence plus an approaching date is not a reason to call, unless the amount is above the threshold, and then the owner calls no matter what the system sent yesterday.
That also sets the content of the messages. They may carry information and a date. They may not carry a concession. No discount appearing by itself on day ten, no extension that grants itself, no alternative package the sequence invented on the spot. Explaining a price is a conversation.
What happens to a quote that expires?
You let it expire. That is the design, not an oversight. The sequence ends on the date printed on the quote, not after an agreed number of messages and not when somebody remembers to switch it off. The expiry date does three things at once: the quote goes to expired, the deal closes with a reason, and the contact drops out of the sequence. Nothing is sent after that.
Search this question and no page in the results tells you where to stop. That tracks. Most of them come from vendors, and an endless sequence still looks like activity in a dashboard. For a small business sending a handful of quotes a month the arithmetic runs the other way: follow-up that keeps simmering spends the goodwill you need to call that same buyer again in six months.
An expired quote is not pipeline any more, it is a work list. Three things can happen to it, and you pick one:
- Archive with a reason. Close as “no answer” and keep it searchable. The default, and in most cases the right call.
- Reopen when the buyer comes back. Write a new quote with a new date and a new amount. Never let the old one quietly run on, because the price on it was calculated in a different quarter.
- Make a fresh offer on your own timing. A quarter later, with a reason from your side: a new service, a changed rate, a smaller scope. That is a sales call, not a sequence step.
What you do not do is keep an expired quote inside the same sequence and bolt two more messages onto the end. The date on the document turns into decoration, and the next buyer will read it that way too.
One practical consequence: make the close reason a required field. A list of expired quotes without reasons is dead weight. The same list with “no answer”, “too expensive”, “went elsewhere” and “project postponed” next to each line tells you inside a quarter whether the problem is your cadence or your price.
What do you set up before you switch the sequence on?
A sequence can only count with what sits in a field. Seven of them, all in place before the first run:
- One expiry date, in a date field. A line of text inside the PDF is invisible to every system you own.
- One amount and one valid version. A revised quote replaces the previous one and restarts the count on the new date.
- One owner on the deal. The name that calls above the threshold and closes the deal when nothing comes back.
- One contact with an email address, plus the role of whoever signs. Not always the same person.
- A status the sequence can read and write: sent, in conversation, won, lost, expired. Five is plenty.
- A threshold amount above which a person always calls, whatever the system already sent.
- A stop rule in one sentence, and a named person for replies that land in a personal inbox instead of the CRM.
Add an alert on failed runs before you switch anything on, because follow-up that quietly stops produces no error on screen and no result either.
What does a follow-up sequence run on?
On the calendar, not on a button. A scheduled trigger runs a workflow at fixed intervals and times [S-005], and every production workflow needs at least one trigger to determine when it runs [S-030]. Inside a single execution, meaning one run of the workflow, a wait step can hold until a specified date and time before the workflow continues [S-105]. The branch the sequence takes comes from a conditional node that splits the workflow on a comparison, filtering for dates after a particular date for instance [S-106]. Writing the result back is ordinary work: the n8n HubSpot node creates, updates, deletes and gets contacts and deals [S-008].
That is deliberately the full extent of the tooling in this article. n8n, Make, Zapier: the pick changes nothing about the cadence or the stop rule, and a sequence that is wrong on content does not improve on a better platform. Connecting systems without a developer is covered in stop copying data between tools, and getting the CRM itself in shape in HubSpot and AI. WeAdapt builds workflow automation on the CRM you already run, not next to it.
Which leaves the thing that actually keeps quotes lying around: nobody agreed who calls when. That agreement takes half an hour and comes before any workflow. Once it exists, automating it is the straightforward part.
Want a quote process where nothing is left lying around and nobody gets called without reason? Book a call, or read how a WeAdapt project runs in the FAQ.