Trades › Roofing

Estimate Follow-Up Sequence for Roofers

Five polite touches after every estimate — automatic, and it stops the moment they reply.

The Roofing version of this problem

Roof Replacement Quotes don't close on the day of the visit. The homeowner needs to think, talk to a spouse, compare. Your follow-up is what keeps you in the running while they decide — and what brings you back when they're ready.

You did the drive, the walkthrough, the write-up. You sent the estimate. Then you got busy. The estimate is still sitting in your sent folder — and so is the money. Most of the time the homeowner wasn't saying no; they were saying 'not yet' or 'I got distracted.' Silence isn't rejection, but we treat it like rejection, so we never follow up.

What the Estimate Follow-Up Sequence does

The Estimate Follow-Up Sequence fires a short series of check-ins after every estimate goes out: a thank-you the day you send it, a check-in a few days later, a nudge the next week, and a graceful last call after that. Polite, helpful, zero pressure. The moment the homeowner replies, the sequence stops and a human takes over. Estimates that finish the sequence with no reply get tagged for the reactivation pool instead of rotting in the sent folder.

How it works

Step 1: Define the 'estimate sent' trigger

Whatever marks an estimate as sent in your system — a pipeline stage, a tag, a status change. If there's no clean trigger, create one with your team first; automation on a messy trigger produces messy texts.

Step 2: Set the timing map

A common cadence: day 1 (thank-you), day 3 (check-in), day 7 (nudge), day 14 (last call), day 21 (breakup). Adjust to your sales cycle — a roof replacement decision takes longer than a drain cleaning.

Step 3: Write all five scripts

Short, plain, helpful: 'Any questions on the estimate? Happy to walk through it.' The homeowner approves the tone — these go out under your name.

Step 4: Wire stop-on-reply

Any reply cancels the remaining touches automatically and flags the contact as responded. Test this explicitly — a sequence that keeps texting after a reply is a failure, not a feature.

Step 5: Route dead estimates to reactivation

Contacts that finish all five touches with no reply get tagged and handed to the dead-lead system. The follow-up sequence ends; the relationship doesn't have to.

What your customer experiences

The homeowner gets the estimate, then a thank-you text the same day. A few days later a genuine check-in: 'Any questions on the numbers? Happy to walk through it.' Nothing pushy — just a contractor who seems organized and attentive. When they're ready, you're the one they reply to, because you're the one who stayed in touch.

What it costs to run

Most shops run their full automation stack for about $50–$97/month in tools — roughly the cost of a tank of gas. The Starter Pack lays out the exact tool setup with the honest cost picture, no upsell. And the first system — the Missed-Call Safety Net — is free: the PDF walks you through the 45-minute setup with the scripts, the registration steps, and a worksheet to run your own numbers.

Questions roofers ask

Won't five touches annoy people?

They're spread over three weeks, each one short and useful, and any reply stops the sequence instantly. What actually annoys people is a contractor who sends one estimate and vanishes.

What if they already said no?

Then they shouldn't be in the sequence — 'no' is an answer, and the system respects it. The sequence is for the silent majority who never answered at all.

How many touches is too many?

Five over three weeks is the tested default. Fewer and you leave money behind; more and you're nagging. Adjust to your trade's buying cycle and watch reply sentiment.

Our leads spike after storms. Can this handle the surge?

That's when it matters most. After a hailstorm every roofer in town is slammed, and the one whose system instantly acknowledges each caller and books inspections in order wins the week. The automation doesn't get overwhelmed — it just keeps working through the queue while you're on roofs.