The 5-Touch Estimate Follow-Up System: How One Roofing Company Closed $67K in "Dead" Proposals

Every roofing company has a folder like this: estimates that went out, got a polite "let me think about it," and then went silent. Most owners write that revenue off the second the silence stretches past two weeks. The data says that's premature, and expensive.

A fast first response gets a lead to the inspection appointment. What happens after the estimate goes out is a separate problem, with its own separate leak. This piece covers that second leak specifically: the proposals that already exist in your pipeline right now, sitting quiet, that aren't actually dead — they're just unfollowed.

Why "Send the Estimate and Wait" Is the Most Expensive Habit in Roofing

The standard roofing sales process ends at delivery: inspect the roof, write the estimate, send it over, and wait for the homeowner to call back. Industry data on contractor close rates shows the gap this creates clearly top-performing operators close 70-85% of estimates while median shops run 15 to 25 percentage points behind that, and a meaningful share of that gap isn't pricing or quality. It's the absence of a structured follow-up after the proposal goes out.

The reasoning behind why homeowners go quiet is rarely "no." It's usually one of: they're still collecting competing quotes and yours got buried in their inbox; they got busy and the decision slipped; they have a question they never asked because picking up the phone again felt like a hassle; or the price gave them a moment of hesitation they haven't resolved yet. None of those are rejections. All of them respond to a well-timed nudge which is exactly what most roofing companies never send, because nobody on the team has the bandwidth to manually track and re-contact every open estimate on a schedule.

What "Dead" Actually Means in a Roofing Pipeline

Before Peak Roofing Co. worked with AI Savvy, "follow-up" meant one phone call, maybe, within the first week after an estimate went out and only if an estimator happened to have a free moment. After that, the file sat. Multiply a $15,000-$25,000 average roof replacement estimate by even a modest number of stalled proposals sitting in a CRM with no further contact, and the number gets uncomfortable fast. That backlog is exactly where AI Savvy started.

The 5-Touch Sequence, Step by Step

The system built for Peak Roofing runs a structured five-touch sequence across SMS, email, and AI-driven voice calls, spaced to match how homeowners actually make a roofing decision rather than how a sales team wishes they would.

Touch 1 Same-day confirmation. Within hours of the estimate being sent, an automated SMS confirms it arrived and asks whether the homeowner has any questions, with a direct reply-to-text option. This catches the homeowner while the inspection and the conversation with the estimator are still fresh.

Touch 2 Day 3 value reinforcement. A short follow-up, by text or email depending on homeowner preference, reframes the proposal around what matters most at this stage of the decision: workmanship warranty terms, material specifics, and timeline not a price cut. This is the touch that answers the unspoken objection without ever sounding like a discount pitch.

Touch 3 Day 7 AI voice call. This is where the system shifts from passive to active. An AI voice agent places an outbound call, references the specific estimate by address and scope, and asks directly whether the homeowner has made a decision or has outstanding questions. Because the call references real details from their specific proposal, it doesn't read as a generic sales robocall homeowners engage with it.

Touch 4 Day 14 urgency and scheduling. If the homeowner is still undecided two weeks in, the system introduces a real scheduling constraint crew availability, material lead times, or a seasonal weather window and offers to lock in a start date. This isn't manufactured urgency; for roofing specifically, crew calendars and material costs genuinely do shift, and saying so accurately is both honest and effective.

Touch 5 Day 21 human handoff. Any estimate still open after three weeks gets flagged directly to a human estimator with full context: every touch attempted, every response received, every objection raised. The estimator's final call is a closing conversation with someone who's already been re-engaged, not a cold "just checking in" call into silence.

The $67K Number, and Where It Came From

Running this exact sequence against Peak Roofing's backlog of previously stalled estimates recovered $67,000 in jobs that the team had already mentally written off. None of those homeowners had explicitly said no. They'd simply gone quiet, and nobody had a system built to re-engage them on a schedule a human team could never sustain manually five timed, channel-appropriate touches across every open estimate, every single week, without anyone having to remember to do it.

Why This Works Better Than a Manual "Just Checking In" Call

A manually-run follow-up process depends entirely on someone remembering to do it, having time to do it, and doing it consistently across every open file in the pipeline which in practice means it gets done for the estimates someone happens to think about and skipped for the rest. An automated sequence treats every open estimate identically: same five touches, same timing, every time, with zero dependency on anyone's memory or workload that week. The other advantage is tone. An AI voice call referencing specific proposal details at day 7 doesn't carry the awkwardness a human rep sometimes feels calling a homeowner for the third time it's simply doing its job on schedule, every time, without fatigue.

Built on Top of Your Existing CRM

This sequence runs directly against whatever CRM already holds your estimate data AccuLynx, JobNimbus, ServiceTitan, or a simpler pipeline tool. Nothing about the estimate workflow your team already uses changes. The system reads the existing proposal record, runs the five touches against it, and writes every interaction back into that same record, so your estimators see a complete history the moment a homeowner is ready to talk.

Frequently Asked Questions

How is this different from a CRM's automatic email reminder?

A reminder email is one touch, sent the same way every time, with no voice component and no escalation logic. This sequence runs five distinct touches across three channels, references the specific estimate details, and escalates to a human only once genuine engagement has happened.

Will homeowners find an AI voice call calling about their estimate intrusive?

The calls reference real, specific details from the homeowner's own proposal rather than reading as a generic robocall, and every touch includes an easy way to opt out or request a human. In practice, homeowners engage with a call that clearly knows their address and their roof scope far more readily than a blind sales call.

What if the estimate truly is dead they already hired someone else?

The sequence is built to surface that quickly. A homeowner who's already committed elsewhere typically says so on the first or second touch, which closes the file cleanly rather than letting it sit in limbo, and frees the estimator's attention for files that are still genuinely open.

Does this replace the estimator's final closing conversation?

No by design, it doesn't try to close the sale itself. It re-engages the homeowner and surfaces real interest, then hands a warm, fully-briefed conversation to a human estimator for the actual close.

What's a realistic timeline to see results from a backlog like this?

Most of the recoverable value in an existing backlog of stalled estimates surfaces within the first three to four weeks of running the sequence, since that's the full cycle length of the five touches themselves.

The Bottom Line

Every roofing company has money sitting in estimates everyone assumes are gone. They're usually not gone they're unfollowed. A first-touch speed-to-lead system gets the lead to the table; a structured estimate follow-up sequence makes sure the proposal you already wrote doesn't die from neglect after the fact. See how the full Peak Roofing case study ties both systems together, or read about the speed-to-lead system that handles the front end of this same pipeline.