How do I send an automatic follow-up a few days after I quote someone?

This page may contain affiliate links from which Blur Studio earns commissions.

A quote that goes unanswered for three days rarely means the customer decided no. More often they got busy, meant to reply, and now need a gentle nudge to actually do it. The businesses that follow up systematically close noticeably more of these than the ones that only follow up when someone happens to remember to check their sent folder.

Use your CRM first, if you have one

If quotes already flow through a CRM like HubSpot or Pipedrive, this is almost always a built-in feature, not something you need to build: both platforms support timed sequences or workflows that can send a follow-up email a set number of days after a specific event, like a quote being sent or a deal entering a certain stage. Set this up once inside your CRM's own automation settings, and every future quote gets the same timed follow-up without you doing anything per quote.

When you actually need a custom delayed job

If your quoting process runs through a custom-built app rather than a CRM, for example a quote generator you built yourself or a tool specific to your trade, you need a background job that can wait a set number of days and then fire on its own, independent of anyone actively checking or triggering it. That's what a system like Netlify's Async Workloads is for: a job that's created the moment the quote goes out, holds for three days (or however long you choose), then runs automatically to send the follow-up, with no person needing to remember or manually trigger it.

This kind of delayed job is the same underlying mechanism used for retrying a failed system call, just pointed at a calendar delay instead of an immediate retry: create the job, tell it how long to wait, and let it run unattended.

What a good automatic follow-up actually says

The follow-up that works best is short, specific, and easy to act on: reference the actual quote (the amount, the job, the date it was sent), ask a direct question ("still interested, or has anything changed?"), and make replying as easy as possible, ideally just hitting reply rather than filling out another form. A generic "just checking in" message with no specifics reads as a mass blast, even when it technically isn't, and gets ignored at a noticeably higher rate than one that clearly references their specific quote.

A worked example: a contractor recovering stalled quotes

A small remodeling contractor was sending roughly fifteen quotes a week through a custom quote tool built specifically for his trade, with no CRM involved. Before automating anything, he manually tracked a rough close rate on quotes he remembered to follow up on versus ones he didn't, and the gap was larger than he expected: quotes he personally followed up on within a week closed noticeably more often than ones that went untouched after the initial send, simply because busy weeks meant follow-up quietly stopped happening for whichever quotes weren't top of mind.

Building a three-day delayed job into his existing quote tool took a single afternoon. The job fires automatically referencing the specific job and amount quoted, with a direct question and an easy reply path, exactly the kind of specific, non-generic message that performs best. Within the first month, several quotes that would have gone cold under the old manual process got a response specifically because of the automated nudge, converting into booked jobs that otherwise would have simply been forgotten amid a busy week.

A practical note on tone across multiple follow-ups

If you're running more than one follow-up in sequence, vary the tone and angle rather than repeating the same message with a different date. A first follow-up can simply check in and reference the quote directly. A second, later one works better shifting angle slightly, mentioning availability ("still have a slot open this month if you want to move forward") rather than just repeating "checking in" a second time, which starts to read as nagging rather than helpful once a customer's already seen one reminder.

When to skip automating this

Use your CRM's own sequences first if you have one; building custom delay logic is only worth it for a genuinely custom app with no CRM in the picture. If your quote volume is low enough that you can reliably remember to follow up manually (a handful a week, say), automating this might be more setup than it's worth, though most people underestimate how often "I'll remember" quietly turns into "I forgot" once the week gets busy.

A practical note on stopping the follow-up once a deal actually closes

An automated follow-up that keeps firing after a customer already said yes, or already said no, is worse than no automation at all, since it signals you're not actually paying attention. Whatever system runs the delayed job needs a clear way to cancel it the moment the quote's status changes, whether that's a CRM stage update or a manual flag in a custom tool. Build that cancellation path at the same time as the follow-up itself, not as an afterthought once someone complains about getting a reminder for a job they already booked. A simple status check right before the message sends, confirming the quote is still open rather than assuming it is based on when the job was originally scheduled, catches most of these cases without needing a separate manual cancellation step every time.

Common mistakes with automated follow-ups

• Making the message too generic to feel worth replying to. A follow-up that could apply to anyone reads as automated even when it's accurate, and gets ignored at a higher rate than one referencing the specific quote.
• Setting the delay too short. A follow-up firing the next morning can feel pushy rather than helpful. Three days is a reasonable default precisely because it gives a genuinely busy customer time to actually get to it first.
• Forgetting to test what happens if the quote gets updated or replaced. If a customer requests a revised quote, make sure the original follow-up job doesn't still fire referencing outdated pricing.

How I'd approach this

If you already have a CRM, I'd point you at its own sequence feature before building anything, since it's free functionality you're likely already paying for and not using. If your quoting lives in a custom tool with no CRM involved, a delayed background job is a small, one-time build that then runs forever without maintenance, and it's one of the highest-value small additions I make to a custom quoting or sales tool, since it directly recovers deals that would otherwise just quietly go cold.