You sent the roofing estimate. The homeowner said they’d think about it. Two weeks later, nobody on the team remembers who was supposed to follow up.
That isn’t necessarily a lead-generation problem. It’s a missing sales process.
Quick answer: A useful roofing estimate follow-up automation records when the proposal was sent, assigns the salesperson a next task, schedules appropriate reminders, and stops or changes the sequence as soon as the homeowner replies, declines or signs.
If you want this built and managed for your team, see roofing CRM setup and management or request a free Revenue Audit.
Step 1: Define the estimate status
A roofing CRM should distinguish at least:
| Status | Meaning | Next action |
|---|---|---|
| Estimate being prepared | Inspection complete, quote not yet sent | Owner prepares proposal |
| Estimate sent | Proposal delivered | Confirm receipt and assign follow-up |
| Decision pending | Homeowner considering options | Personal call or relevant reminder |
| Won | Agreement signed or agreed sales milestone | Stop sales reminders; hand off to operations |
| Lost | Opportunity declined | Record reason; stop sales reminders |
| Not now | Timing moved into the future | Set an appropriate future follow-up date |
Don’t create a new pipeline stage for every text message. Use tasks and workflow events for the activity within a stage.
Step 2: Make every estimate create a next action
A practical sequence could look like this:
- Immediately after sending: record the estimate date, assigned owner and delivery channel.
- After a suitable interval: create a salesperson task to confirm receipt and answer questions.
- A few days later: if there has been no response and follow-up is appropriate, send a brief check-in or prompt the salesperson to call.
- Later: ask whether the homeowner needs clarification or has decided on timing.
- After the active window: record the outcome or move the opportunity into a separate long-term nurture process, if appropriate.
The timing should reflect the project type, urgency, customer preference and your business’s communication policies. Emergency repairs should not use the same cadence as planned replacements.
Step 3: Use short, useful follow-up messages
Receipt check:
Hi [First Name], this is [Rep] with [Roofing Company]. Just checking that you received the estimate for [Project]. Happy to answer any questions.
Decision follow-up:
Hi [First Name], following up on the roofing estimate we sent. Is there anything about the scope, materials or timeline you’d like us to clarify?
Timing check:
Hi [First Name], are you still planning to move forward with the roofing work, or would a later check-in be more useful?
These are examples, not a substitute for consent requirements or company-specific review. Avoid misleading urgency and excessive messaging.
Step 4: Build stop conditions before activating reminders
This is where many automations fail.
Before each outbound step, check whether:
- The estimate has already been accepted.
- The opportunity has been marked lost or not interested.
- The homeowner has replied and a human is handling the conversation.
- The customer opted out of that communication channel.
- The estimate was replaced or materially revised.
- The assigned owner changed.
If a homeowner signs the contract, continuing to send “Have you decided?” texts is a poor experience and can damage trust.
Step 5: Keep the CRM and estimating system synchronized
If your team creates proposals in another platform, decide which system owns the estimate’s authoritative status.
For example:
Estimate marked sent in estimating platform → validated integration event → CRM opportunity updated → follow-up task created.
Use stable record identifiers, deduplication, error handling and periodic checks to prevent missed or repeated tasks. Avoid storing sensitive customer documents in unapproved automation logs.
Step 6: Track whether follow-up is working
Start with a small set of useful metrics:
- Estimates sent.
- Estimates without an assigned next action.
- Average time to first follow-up.
- Homeowner reply rate.
- Estimate-to-signed-job rate.
- Reasons for lost estimates.
Measure the outcome, not the number of texts sent. A workflow is successful when it supports a better customer experience and a more reliable sales process.
Common mistakes
Automating every message. High-value roofing projects often need a personal conversation. Use automation to ensure that conversation happens.
Ignoring replies. A reply should interrupt or redirect the sequence.
Mixing production and sales statuses. A signed roofing job belongs in operational handoff, not ongoing estimate nurture.
Never reviewing the workflow. Team changes, phone integrations and CRM edits can break a process that worked last month.
Get help setting this up
The Bot Man builds and manages roofing CRM pipelines, estimate follow-up, missed-call recovery and lead reactivation. See Roofing CRM Setup & Management for the service, Foundation pricing for the first-month cost, or request a free Revenue Audit and one free fix.
For the full lead journey, read Roofing Lead Follow-Up: A Practical System.