FlowKit

Automating quote follow-ups for tradespeople and construction businesses with n8n

By Clément Lacaille (Tech-Bharat) · Published 10 September 2026 · 6 min read · how we build and test

Complete FlowKit Bundle — €269

12 ready-to-import n8n workflows, setup guide in French, 14-day guarantee

See the bundle

A tradesperson's quote is almost never explicitly turned down — it usually just disappears into silence. The client compares several quotes, forgets one, or waits for something else to happen (another estimate, an incoming payment) without ever replying. Without a follow-up, that silence turns into a lost job, won instead by a competitor who called back. This guide builds an n8n workflow that automatically follows up on a quote left without a reply, with timing and a tone designed to invite a response rather than annoy — without requiring expensive management software.

The real cost of a quote with no follow-up

Most tradespeople and small construction businesses don't have a CRM: quotes go out by email or post, and tracking them lives in a notebook or in the owner's memory. Two research findings, taken together, explain why this dead spot costs real jobs.

First, the speed and persistence of contact matter more than most assume. A landmark study by Oldroyd, McElheran, and Elkington published in the Harvard Business Review in 2011 ("The Short Life of Online Sales Leads"), conducted across 2,241 US companies, shows that organizations that recontact a prospect within an hour are nearly seven times more likely to qualify them, and up to sixty times more likely than those that wait 24 hours or more — with 47% of the companies tested never calling back or taking more than 24 hours to do so. The same logic applies directly to following up on a quote already sent: the competitor who re-establishes contact quickly and consistently wins the race for attention, regardless of the intrinsic quality of their offer.

Second, a reminder works because it brings a decision back to the front of someone's attention. Karlan, McConnell, Mullainathan, and Zinman, in "Getting to the Top of Mind: How Reminders Increase Saving" (Management Science, 2016), show across three field experiments that simple reminders significantly increase follow-through, by making a decision salient again after limited attention had let it slide — not from lack of interest, but from being forgotten among other priorities. A client's quote follows the same mechanic: it isn't explicitly rejected, it just drifts out of view.

What the workflow should do — and nothing more

  • Log every quote sent: client, amount, date, status.
  • Follow up at fixed intervals (for example day 3, day 7, day 14) as long as the status stays "pending."
  • Check the status right before each send, and stop the moment the client has replied.
  • Adjust the message's tone based on elapsed time — factual at first, more direct later.
  • Escalate to a more direct channel (SMS) for high-value quotes, as a last resort.

Step 1 — Log the quote

The fastest solution to set up is a Google Sheet with a "Quotes" tab: columns for Client, Email, Phone, Amount, Date Sent, Status. A Google Sheets Trigger node in "row added" mode kicks off the workflow as soon as a row is added — manually, or automatically at the end of a PDF quote generation pipeline. Past a certain volume, a self-hosted n8n Data Table or a real database (Supabase, Airtable) takes over without changing the logic described here.

Step 2 — Pace the follow-ups with the Wait node

The Wait node in "After Time Interval" mode suspends execution without consuming resources, even across several weeks. The typical setup chains three tiers:

  1. Wait 3 days → read the row in Google Sheets → IF node: if status = "pending," send follow-up 1 (neutral tone, factual reminder of the quote and its date).
  2. Wait 4 more days (day 7) → same check → follow-up 2, more direct, offering a quick call to clear up any blocking point.
  3. Wait 7 more days (day 14) → final check → follow-up 3, noting that the quote won't be chased further and inviting the client to reach out if the project is still relevant.
  4. If the status is still "pending" after the last tier, an update node marks the row "no response" and the workflow stops, with no further outreach.

Step 3 — Never follow up on stale data

The detail that separates a reliable workflow from an embarrassing script: re-read the status at the exact moment of sending, not just when the workflow was triggered. A client may have replied by phone in the meantime, with no one thinking to update the spreadsheet before the automatic follow-up goes out. If quotes are already tracked through an e-signature platform like the one described in our guide to automating e-signatures with Yousign, it's far more reliable to trigger each step directly off the platform's status webhooks (viewed, pending, signed, expired) than off a box checked by hand.

Step 4 — Personalize the message with AI

A language model turns a generic reminder into a message that reads as hand-written: the client's name, the nature of the work, the amount, the number of days elapsed, and which follow-up it is (first, second, last) are enough as prompt variables to adjust the tone automatically — polite and informative at the first tier, more direct and decision-oriented at the last. This is exactly the kind of building block covered by the AI-drafted Gmail replies workflow from the Inbox AI Pack (€79); for wiring up the model itself, our guide to connecting Claude or GPT to n8n covers credential and system prompt setup.

Step 5 — Escalate to SMS for high-stakes quotes

For a job above a certain amount (€2,000, to adjust to your business), an IF node on the amount can trigger, as a last resort only, an SMS via the Twilio node detailed in our guide to automating SMS with n8n and Twilio: a channel that reaches someone who hasn't checked their inbox in days, reserved for quotes whose loss genuinely dents that month's revenue.

Mistakes to avoid

  • Following up too often or too soon. Three spaced-out tiers are enough; a daily follow-up annoys and damages the relationship, including for a future quote.
  • Ignoring a partial reply. A client who says "I'll get back to you" isn't a silent client: the workflow must distinguish no response from a pending response, or the next follow-up lands at the wrong moment.
  • A message that's too generic. AI only helps if it's given the real context of the job; an empty prompt produces an email that reads as robotic and gets spotted instantly.
  • No visible validity period. Stating a clear validity period on the quote itself gives a natural justification for the final follow-up, instead of leaving the deadline implicit.

Measuring effectiveness

Add a "follow-up that converted" column to your tracker: it quickly reveals whether it's the first, factual follow-up or the last, more insistent one that closes the most quotes — and lets you tune the tiers (day 3/7/14) to your actual business instead of an arbitrary value.

In summary

  • A quote with no reply isn't a rejection: it's usually just forgotten, and a well-timed reminder is enough to bring it back to mind.
  • Three follow-up tiers (day 3, 7, 14), with a status check right before each send, cover most cases without expensive tooling.
  • The Wait node paces the delays without consuming resources; an LLM personalizes the message; SMS remains a last-resort escalation for high-stakes quotes.
  • If your quotes go through an e-signature platform, trigger the tracking off its webhooks rather than a status typed by hand.

FAQ

Frequently asked questions

Do I need a CRM or paid quoting software to set up this workflow?

No. The simplest version runs on a plain Google Sheet with a few columns (client, amount, date sent, status): n8n reads and updates that sheet at each step. Dedicated quoting software or a self-hosted n8n Data Table can replace the spreadsheet once volume grows, without changing the workflow's logic.

How many follow-ups should I send before giving up on a quote?

Three tiers (for example day 3, day 7, and day 14) cover most cases: beyond that, each extra follow-up annoys more than it converts and damages the relationship for a future quote. The exact number matters less than the rule that must always apply: check the status right before sending, and stop the moment the client has responded, accepted, or declined.

Does a follow-up SMS require the client's explicit consent?

The client requested the quote themselves, which falls under legitimate interest for a one-off follow-up message — unlike unsolicited commercial prospecting. It's still prudent to offer a simple way to opt out and, as with any SMS sent from n8n, to follow the rules detailed in our guide to sending SMS with Twilio.

Does this workflow work if quotes are tracked through an e-signature platform?

Yes, and it's actually preferable when possible: instead of checking a status typed by hand into a spreadsheet, the workflow triggers directly on the platform's webhooks (quote viewed, pending, signed, expired), which is more reliable. Our guide to automating e-signatures with Yousign covers this mechanism.

Complete FlowKit Bundle

€269