The "3-day rule" that's closing more roofing estimates

The 3-day rule that's closing more roofing estimates

Quick question: after you send a roofing estimate, when do you follow up?

Most roofers I talk to say "a few days" or "whenever I remember." Which means the real answer is: almost never consistently. You get busy, a new storm comes in, you're on a job — and that estimate you sent on Monday is still sitting in someone's inbox with no reply, and you haven't thought about it since Tuesday.

Here's what the data says about roofing estimates specifically. Unlike a $300 gutter cleaning where the homeowner decides in 24 hours, a roofing job — especially one going through insurance or costing $15,000+ — has a decision window of 7 to 30 days. The homeowners aren't ignoring you. They're in the middle of a slow decision.

The "3-day rule" is simple: if you haven't heard back in 3 days, send one message. Not to push. Not to sell. Just to check in and stay visible during the decision window.

That's it. 25 words. No pressure. No discount. No desperation. Just presence.

The businesses using this consistently (automated, so it actually happens) are seeing 15–25 point improvements in estimate close rate. That's not a rounding error — on a $14,000 average job, recovering 2 extra estimates per month is $28,000 in additional revenue.

How to automate this in 30 minutes

If you use Jobber: when an estimate status changes to "sent," Zapier picks it up and waits 3 days. If the status hasn't changed to "approved," it sends the check-in text via SimpleTexting. That's the whole automation.

• Jobber → Zapier → SimpleTexting (or GoHighLevel if you use that)
• Trigger: Estimate marked "sent"
• Delay: 3 days
• Filter: Only fires if estimate is still in "sent" status (meaning no booking yet)
• Action: Send the 25-word text

The filter step is important — you don't want to send "any questions?" to someone who already booked. That Zapier filter step is this week's Tool Tip (see below).

How Jorge got his evenings back

Jorge runs a solo HVAC operation in central New York. For 11 years, he ended every workday the same way: sitting in his truck in the driveway, texting back the leads and customers who had messaged him that day. He estimates it was taking 2–2.5 hours every evening.

"My wife started calling it 'truck time,'" he told us. "I'd come inside but I wasn't really there because my phone was always going."

He signed up for GoHighLevel in January, followed the Home Services Playbook, and had his Lead Bee live in an afternoon. It now handles all first-contact texts — every form submission, every missed call — within 90 seconds. The Estimate Bee follows up on open quotes automatically on Day 1, Day 3, and Day 7.

Jorge's results after 60 days: response time dropped from 4–6 hours to under 2 minutes. Lead-to-estimate rate up from 38% to 61%. Close rate up from 44% to 59%. He figures he's recovered about $8,400/month in jobs that would have previously gone to competitors who responded faster.

"I still check my phone. But now it's to see the bookings, not to do the follow-ups. That's the difference."

The free Zapier filter feature most people don't know exists

Here's a scenario: you automate your Estimate Bee so it follows up at Day 3. But a customer books on Day 2. Now your automation sends them a "any questions?" message the next day — awkward. They just paid you.

The fix is Zapier's Filter step — and it's free on every Zapier plan. A Filter sits between your trigger and your action. It says: only proceed if this condition is true.

In the estimate follow-up context, the filter checks: "Is the estimate still in 'sent' status?" If yes → send the follow-up. If it's been approved, declined, or converted → stop the automation. Nothing goes out.

• In Zapier: add a "Filter" step between your delay and your text action
• Set condition: Estimate Status → Exactly Matches → "Sent"
• That's it. The automation becomes self-aware of whether the customer has already acted.

You can use this same logic for any time-based follow-up: only send the review request if the job is marked complete, only re-engage a lead if they haven't booked, only send the seasonal upsell if the customer is still active. One feature, infinite use cases.