The quote you were proud of is sitting unread
You measured the fence line on Thursday, priced it carefully that evening, and sent a clean quote before you went to bed. The homeowner replied with a quick thank you on Friday, and then nothing, and by Tuesday you were buried in other jobs.
Three weeks later you scroll past the thread and wince, because calling now feels awkward and letting it die feels worse. Multiply that one thread by every estimate you sent this quarter, and the pile quietly becomes one of the biggest leaks in the shop.
Silence is a queue, not a rejection
Most silent quotes are not rejections, they are decisions the customer has simply not gotten around to making yet. People collect two or three estimates, get busy, lose the email and wait for something to make the choice easy.
The contractor who checks in politely is often the one who wins, not because the price moved but because the decision finally had a prompt. Follow-up is a queue to be worked, and queues are exactly what software is built to hold.
Every quote already cost you a site visit, measurement time and pricing time, which is capacity you cannot bill twice. A follow-up system protects that spent capacity, the same way invoicing protects the work after the job is done.
Think of the follow-up queue the way you think of unsent invoices, as paperwork that finishes work you already did. Nobody calls an invoice pushy, and a courteous check-in on a real estimate sits in the same category.
Run your own numbers before you build anything
Take your average job value, your monthly quote count and your close rate, and run them before you build anything. Suppose your average job is worth $4,000, you send 20 quotes a month and 6 of them close today.
If a steady three-touch sequence rescues one additional job a month, that is $4,000 a month, or $48,000 across a year. Against a one-time build in the $1,000 to $5,000 range, one rescued job can pay for the whole project in its first month.
Your numbers will differ, so swap in your own job value and stay conservative about the rescue rate. Even at one saved job a quarter in this example, the year returns $16,000 on a build that cost at most $5,000.
Three touches, two weeks, then leave them alone
A good sequence is short, polite and finite, and it stops the instant the customer does anything at all. Every message should read like you typed it between jobs, because the customer should never feel a machine in the thread.
- Day two, the check-in: confirm the quote arrived, ask whether anything needs explaining, and leave it at that.
- Day seven, the useful nudge: answer the question this kind of job always raises, like timeline or options, and note the number still stands.
- Day fourteen, the courteous close: say you are planning the schedule, ask whether to hold a slot, and make it easy to say no.
The close matters more than owners expect, because an easy no today beats a maybe that haunts your pipeline for months. A dead quote marked dead is information, and information is what keeps the pipeline honest.
Wire it to the status your tools already track
The trigger is the moment an estimate goes out, which your CRM, invoicing tool or estimate software already records as a status. The sequence watches that status, sends on schedule during business hours, and logs every touch on the customer record.
Stop conditions do the real work here: any reply, an accepted or declined quote, a booked job or an opt-out ends the sequence immediately. Email is the default channel, and text is reasonable for the check-in when the customer has been texting you all along.
None of this replaces the tools you quote with today, and nobody re-enters data to keep it alive. If your current setup cannot fire a message on a status change, that is a plumbing job measured in days, not a migration.
Replies come back, so route them like work orders
The point of follow-up is replies, and replies only pay off when they reach a person quickly with context attached. Send every response to whoever wrote the quote, with the amount, the dates and the thread in one place.
Price objections, timing questions and scope changes are exceptions for a human, never branches in an automated script. Exceptions are where deals actually get won, so the system's job is to surface them fast, not to answer them.
While trust builds, run the whole thing in approval mode, skimming a short daily digest before anything goes out. Everything stays logged, so you can open any customer and see what was sent, when it went, and what came back.
Watch three numbers a month
You do not need a dashboard project to manage this, just three counts your existing tools can already produce.
- Quotes sent each month, so you know the size of the queue you are protecting.
- Quotes that got any response at all, tracked against your own history rather than a benchmark.
- Jobs won from quotes older than a week, the number this sequence exists to move.
Change one variable at a time, starting with timing rather than wording, and give each change a full month. Resist building reports until you have three months of counts, because the raw counts will already tell you plenty.
Start with the pile you already have
Before you automate anything, pull every open quote from the last 60 days and send each one a short personal note this week. That single pass tends to restart a few stalled conversations, and it shows you which words sound like you before you hard-code any of them.
- Clear the backlog by hand once, and note which messages actually got answers.
- Write the three touches in your own voice, capped at four sentences each.
- Wire the trigger and stop conditions in the tool that already holds your quotes.
- Run it in approval mode for two weeks, skimming the digest each morning.
- Review the three counts monthly, and adjust timing before you touch wording.
If you would rather have it mapped first, a free fixed-scope workflow walkthrough ends in a ranked plan and an impact estimate. A written quote and statement of work come before anything gets built, and the quotes you send next month can follow up on themselves.