The job value is high
A single recovered roof job can be worth far more than a cheap follow-up sequence. That makes the follow-up worth doing carefully instead of sending a generic nudge.
Use these when a homeowner received a roof estimate and went quiet. The goal is not pressure; it is to make the next reply easy: scope, timing, budget, approve, or close the loop.
Replace bracketed fields with non-sensitive business context only. Do not paste homeowner names, phone numbers, email addresses, street addresses, payment identifiers, or private PayPal details into public URLs or issues.
Day 0: Hi [Name], checking that you saw the roof estimate for [project]. If the scope looks right, I can confirm the next step. If timing, budget, or one line item is the blocker, reply with that and I will make it clearer. Day 1: Hi [Name], quick follow-up on the roof estimate. Do you want me to hold the current scope, show a smaller option, or answer one question first? Day 3: Hi [Name], I know roofing decisions are not small. If you are comparing options, I can clarify what is included so the estimate is easier to judge. Day 5: Hi [Name], should I keep this roof estimate active? Reply "yes" and I will send the next step, or reply with the part you want adjusted. Day 7: Hi [Name], I will close the loop for now so I do not keep bothering you. If the roof project comes back up, reply here and I can reopen the estimate path.
A single recovered roof job can be worth far more than a cheap follow-up sequence. That makes the follow-up worth doing carefully instead of sending a generic nudge.
Silence can mean budget, timing, insurance, comparison shopping, scope confusion, or trust. A useful follow-up lets the homeowner name the blocker quickly.
Closing the loop politely gives the homeowner a no-pressure way back in and keeps the contractor from chasing forever.
The $5 rescue writes the Day 0, 1, 3, 5, and 7 sequence for one non-sensitive roofing estimate context, plus a PayPal note and order handoff.