A Step-by-Step Sales Process for Insurance Restoration Roofing

Roofing contractor looking at a home's shingle roof from the yard after wet weather.

A reliable insurance restoration roofing sales process starts by separating the roofing decision from the insurance decision. Your team documents roof conditions, explains the proposed work, and helps the homeowner understand the next step without promising coverage. Track claim status separately from sales status, then move signed projects into production only when the scope and outstanding questions are clear.

That separation keeps an adjuster visit from being mistaken for a sale. It also gives your team a practical way to explain why a homeowner's project hasn't moved forward.

1. Find out what the homeowner needs before discussing a claim

Start with the property problem. A homeowner reporting an active leak needs a different conversation from someone requesting an inspection after seeing storm damage nearby.

Ask questions your team can use immediately:

  • What have you noticed, and when did you first notice it?
  • Is water entering the home now?
  • Has anyone inspected the roof or performed temporary work?
  • Have you contacted your insurer, and is an inspection scheduled?
  • Who needs to participate in decisions about the roofing work?

Record observations as homeowner reports, not confirmed findings. “Homeowner reports missing shingles” is more accurate than marking the opportunity “storm replacement.”

If there's an urgent condition, explain available assessment or temporary-protection options within your company's capabilities. Don't make an insurance decision a prerequisite for addressing a safety concern.

Assign an owner for the next conversation. An owner-operator may handle intake and inspection personally. A company with office staff should identify who schedules the visit and which salesperson takes over afterward.

Done when: the record contains the reported problem, urgency, claim status if known, and a named person responsible for the next action.

2. Document the roof without promising an insurance outcome

Use a repeatable inspection record. Include roof sections, observed conditions, relevant components, and areas you couldn't safely access. Pair overview photos with detail photos so someone reviewing the file can understand where each finding belongs.

Separate visible damage from conclusions about its cause. If a condition could involve wear, installation issues, or storm effects, document the uncertainty rather than selecting whichever explanation seems easiest to sell.

A contractor can explain observed conditions and proposed repairs. Insurance coverage depends on the policy and the insurer's determination. State rules also affect what contractors may do when discussing or assisting with claims, so verify your process with the applicable insurance regulator or qualified counsel. Don't interpret policy coverage or negotiate a claim unless you're legally authorized to do so.

For inquiries that arrive early in the claim process, the guide to storm damage leads before adjusters arrive covers preparation and inspection documentation.

Done when: another team member can locate the findings, understand the inspection limits, and explain the roofing recommendation without asserting that insurance will cover it.

3. Agree on the next decision before leaving the inspection

Avoid ending with “Let us know what insurance says.” That leaves the homeowner to decide what information matters and when to contact you.

Explain the findings in plain language. Show the relevant roof area, connect it to the recommended work, and identify anything that remains unknown. If the inspection doesn't support the replacement the homeowner expected, say so.

An adaptable script can keep this conversation grounded:

“These photos show the conditions we observed. This is the roofing work we recommend based on those findings. Your insurer determines coverage. The next step on our side is to review the proposed scope with you. Is anyone else involved in that decision?”

If the homeowner plans to contact their insurer, agree on a follow-up tied to a real event, such as receiving the insurer's written assessment. If they don't want to pursue a claim, ask whether they'd like to discuss the roofing options independently.

Done when: the homeowner understands your recommendation and has agreed to a specific next conversation or chosen not to proceed.

4. Keep claim status separate from sales status

A single CRM stage labeled “insurance pending” hides too much. It can contain an interested homeowner awaiting an inspection, someone comparing contractors, or a homeowner who has stopped responding.

Use separate fields:

| Record | What it tells your team |
| --- | --- |
| Sales stage | Whether inspection, scope review, or the homeowner's contractor decision remains open |
| Claim status | The latest insurer milestone reported by the homeowner or supported by documentation |
| Open dependency | The specific item preventing the next action |
| Next action and owner | Who will do what next, with an agreed date or trigger |

Here's a hypothetical: a homeowner has received an insurer's assessment but hasn't selected a contractor. The claim milestone has moved forward; the roofing sale hasn't. Your next action is a homeowner conversation about the proposed work, not moving the opportunity to production.

Use inspection and appointment stages to diagnose workflow. Track signed roofing jobs separately when evaluating acquisition performance. An adjuster meeting isn't a signed project, and a signed project isn't completed roofing work.

Done when: your team can explain the current blocker without using “waiting on insurance” as a catch-all.

5. Resolve scope differences with specific evidence

When the homeowner shares the insurer's assessment, compare the described work with your inspection findings and proposed roofing scope. Check affected roof sections, components, and any concealed conditions that remain unresolved.

Classify each difference before acting:

  • Missing observation: gather the relevant photo, measurement, or inspection note.
  • Different repair approach: explain the technical basis for your recommendation.
  • Coverage question: direct the homeowner to the insurer or an appropriately licensed professional.
  • Unknown condition: identify what further inspection could establish and what remains uncertain.

If additional documentation is appropriate, keep it factual and within your legal role. Don't describe a requested revision as already accepted. For code-related requirements, verify applicability with the relevant building authority rather than assuming every roof needs the same work.

A homeowner may decide to wait while a question is resolved. That's a legitimate choice. Record what they're waiting for instead of repeatedly asking whether they're ready to sign.

Done when: each material difference has supporting documentation, a responsible party, or an explicit unresolved status.

6. Ask for the roofing decision, then make a clean handoff

Once the scope is understandable, ask whether the homeowner wants your company to perform the work. Keep the conversation focused on the actual project, including materials, access, scheduling constraints, and known uncertainties.

Use agreements and required disclosures appropriate to your jurisdiction. Don't present an inspection acknowledgment as authorization to replace the roof. The homeowner should understand what they're signing.

Before production takes ownership, provide the executed agreement, approved roofing scope, material selections, inspection photos, and any unresolved dependencies. Identify who will update the homeowner if conditions change.

For an owner-operator, this can be a deliberate file review before scheduling work. With separate sales and production teams, the production lead should review the handoff and flag missing information before a start date is confirmed.

Done when: the roofing decision is documented and production can explain the work without reconstructing the salesperson's conversations.

7. Check stalled files for a missing decision

Review open opportunities by blocker, not just age. A homeowner awaiting documentation needs a different follow-up from someone who hasn't chosen a contractor.

The hail-storm lead timeline explains why inquiry timing alone shouldn't determine priority. For broader planning, use the storm and insurance roofing hub.

Copy this checklist into your CRM or job file:

```text
[ ] Reported property problem and urgency recorded
[ ] Next action assigned to a named team member
[ ] Inspection findings and access limits documented
[ ] Homeowner understands the roofing recommendation
[ ] Sales stage and claim status recorded separately
[ ] Scope differences classified and supported
[ ] Outstanding questions assigned to the right party
[ ] Homeowner's roofing decision documented
[ ] Production handoff reviewed before scheduling
```

Done when: every active opportunity has a concrete next action, a documented reason to wait, or an accurate closed status.

Start with your current open files. Find the ones labeled only “insurance pending,” identify the missing decision, and assign the next conversation to someone on your team.