Follow Up After Sending a Roofing Estimate

Why estimates go quiet

You send a roofing estimate. The homeowner says they will review it. Then silence. A week passes. You assume they went with another company. Sometimes they did. Often they did not decide at all. They are comparing quotes, waiting for an insurance adjuster, or dealing with a work schedule that pushed the roof down the priority list.

The estimate is not a decision. It is a pause. The homeowner has the information but no reason to act right now. A follow-up sequence gives them that reason by asking a useful question, offering a next step, or checking whether something in the estimate needs clarification.

The goal is not to pressure the homeowner into saying yes. It is to keep the conversation open so that when they are ready to decide, your estimate is the one they are still thinking about. A homeowner who receives a helpful follow-up is more likely to tell you they went another direction than one who gets silence and assumes you forgot about them.

A purposeful follow-up sequence

The first follow-up should come one to two days after the estimate. Ask whether the homeowner has had a chance to review it and whether they have questions. This is a service message, not a sales push. It positions you as the estimator who is available to help, not the company that is waiting impatiently.

The second follow-up, a few days later, should offer something specific. Offer to adjust the scope, explain a line item, or schedule a call to compare options. Give the homeowner a concrete reason to reply instead of a generic check-in that invites no response.

The third follow-up, about a week in, should check on timing. Ask whether the homeowner is still planning the project and whether there is anything holding up the decision. This message respects their timeline while keeping the conversation alive.

Each message should be short, specific, and easy to reply to. A long email that restates the entire estimate is harder to respond to than a two-line text that asks a direct question.

When to stop the sequence

The sequence stops on reply. If the homeowner responds at any point, the automated sequence ends and the conversation continues manually. The sequence also stops on booking, sale, opt-out, or an explicit team decision to close the opportunity.

An opt-out is not a lost lead. It is a homeowner who told you they are not interested, which saves you from chasing a decision that will not come. Respect the opt-out immediately and move on.

A team decision to close the opportunity should be documented in the CRM with a reason. The reason tells you whether the loss was about price, timing, scope, or a competitor. That information is more useful than a generic closed-lost tag.

A sample sequence

Illustrative workflow. Estimate sent Monday.

Day 2, text: 'Hi Maria, following up on the estimate we sent for your roof replacement. Have you had a chance to review it? Happy to walk through any line items or adjust the scope if needed.'

Day 5, text: 'Hi Maria, wanted to check in. If timing is the question, we have some flexibility on the start date next month. Would a quick call help?'

Day 9, text: 'Hi Maria, are you still planning the roof project this season? If you went another direction, no worries. If you are still deciding, I can answer any questions.'

Each message is short, offers a specific next step, and gives the homeowner an easy way to reply or close the loop.

What to measure

Track follow-up coverage, the percentage of sent estimates that received the sequence, and progression, the percentage that moved from sent to booked or closed. Measure over a stated period, like 30 days from estimate send, so the numbers are comparable.

Do not claim that a fixed number of messages guarantees a sale. The sequence keeps the conversation open. The close rate depends on price, scope, timing, competition, and the homeowner's actual need. Follow-up improves the odds. It does not determine the outcome.

What you need

You need a CRM that records the estimate-sent event, a messaging channel that can send scheduled texts, and a rule that starts and stops the sequence based on reply, booking, or opt-out. If the estimate-sent event is not recorded in the system, the sequence has no trigger to fire from.