Roofing CRM: Track Inspections, Estimates and Insurance Claims

A roofing CRM is where every job lives from the first phone call to the final payment. For a roofing company, that means more than a contact list. It has to track inspections, estimates, insurance claims, crews and money owed, and it has to make the next step obvious for every single roof.

Most roofing jobs don't die because the homeowner said no. They die quietly in the gaps: an inspection nobody followed up on, an estimate that sat in someone's truck, an adjuster meeting that never got scheduled. A good CRM closes those gaps by giving each job a stage, an owner and a next task.

Below: stages that fit roofing, insurance versus retail work, and follow-up habits that win more contracts.

What a roofing CRM needs to track

Roofing has more moving parts than most home services. Before you pick software or set one up, list what you actually need to know about each job:

• The property and the people. Homeowner name, service address, phone, email, and who referred them or which storm or campaign brought them in.
• The job details. Roof type, square count, material, photos and inspection notes.
• The insurance side, if there is one. Carrier, claim number, adjuster name, adjuster meeting date, and approved amount.
• The money. Estimate value, deposit received, balance due, and supplement amounts.
• The next step. Who owns it and when it's due.

Every item above becomes a field on the contact or the job. Custom fields carry the details, and tags handle quick labels like "storm lead," "retail," or "insurance."

Roofing pipeline stages that match how you sell

The pipeline is the heart of any roofing CRM. Each card is a job, and you drag it from left to right as it moves. The trick is to use stages that match what actually happens on your jobs, not generic sales labels.

A retail roofing pipeline

For homeowners paying out of pocket, a simple flow works well:

1. New lead: call, web form, or door knock
2. Inspection scheduled
3. Inspected: photos and notes in
4. Estimate sent
5. Contract signed
6. Scheduled for install
7. Installed
8. Paid

An insurance roofing pipeline

Insurance jobs take longer and have more waiting. Give the waiting its own stages so nothing hides:

1. New lead
2. Inspected: damage found
3. Claim filed: homeowner has called their carrier
4. Adjuster meeting scheduled
5. Approved: scope and amount in hand
6. Supplement pending, if you're asking for more
7. Contract signed
8. Installed
9. Paid: often in two parts, the first check and the final one

Some companies run both flows on one board, using a tag to separate insurance from retail. Others keep two pipelines. If more than a third of your work is insurance, two pipelines are usually easier to read. For a deeper look at designing stages, see how to build a sales pipeline.

A quick comparison

Follow-up after inspections and estimates

Speed and consistency win roofing jobs. The homeowner who had three companies on the roof this week will usually sign with the one who stayed in touch.

A follow-up rhythm many roofing offices use after an estimate goes out:

• Same day: a short email with the estimate attached and a line on what happens next.
• Day 2 or 3: a call to answer questions.
• About a week later: a check-in email. Mention material lead times or the install calendar if that's true.
• Two weeks later: a final, friendly note. Leave the door open.

The point is that this shouldn't depend on anyone's memory. When a job moves to "Estimate sent," create a follow-up task for the person who wrote the estimate. When the stage doesn't change, the task sits on their list until they deal with it.

For insurance jobs, the follow-up is different. You're mostly helping the homeowner keep the claim moving: reminding them to call their carrier, confirming the adjuster appointment, and letting them know when the approved scope comes back.

Handling insurance claim jobs without losing track

Insurance work is where roofing companies lose the most time. A few habits help:

• Record the claim number and adjuster on day one. Make them custom fields so they show on the job card, not buried in notes.
• Log every call with the carrier as a note. Date, who you spoke to, what they said. When a homeowner asks "where are we?", anyone in the office can answer.
• Use a stage for each wait. "Claim filed" and "Adjuster meeting scheduled" make it obvious which jobs are stuck on someone else.
• Watch the age of each card. A job sitting in "Claim filed" for three weeks needs a call, not more waiting.

Contracts, deposits and getting paid

Once the homeowner says yes, two things matter: a signed contract and a clear record of what's been paid.

Signed contracts. Sending the contract for electronic signature saves a trip back to the house. The homeowner gets a private link, reads it, and signs on their phone. You get a signed copy with a record of when and how it was signed. Our guide to getting a document signed electronically covers what makes an e-signature hold up.

Invoices and partial payments. Roofing jobs rarely get paid in one go. You may take a deposit, then collect the balance after install, or wait on a first and final insurance check. Your system should show each payment against the invoice, so you always know the remaining balance without opening a spreadsheet.

Choosing roofing CRM software

When you compare tools, test them against your real jobs. A short checklist:

• Can you rename stages and add your own fields, like claim number and square count?
• Does every email with a homeowner land on that homeowner's record?
• Can the office see who owns each job and what's overdue?
• Can you send contracts for signature and invoices from the same place?
• Does it connect to your accounting software so nobody types numbers twice?
• Will your crew leads actually use it, on a phone, in a truck?

How Everything Portal handles this

Everything Portal includes a ready-made Home services setup with customers, jobs and a Lead, Estimate, Scheduled, Done, Paid pipeline. For roofing, you'd start there and rename or add stages to match the retail and insurance flows above, then add fields like claim number, adjuster and roof type. See the industry setups.

Automations can tag, send an email, assign or create a follow-up task when something happens, such as a new website form, contracts go out for e-signature with a signing certificate, and invoices support partial payments, with a team chat alert the first time the homeowner views one. Built-in QuickBooks is coming, and we can build a custom connection to QuickBooks for your business in the meantime; see integrations. Two honest notes: online card payments and business texting aren't available yet, and our field service tools for scheduling and dispatching crews are coming. If you'd like to see it set up for a roofing company, contact us.

Frequently asked questions