OPERATIONS·APR 27, 2026·10 MIN

ANATOMY OF A MODERN ROOFING CRM WORKFLOW

What a CRM workflow actually needs to look like to support an agentic operation. Beyond "deals" and "pipelines."

BY Yael Rabinowitz·Head of Storm Operations

Most CRMs were designed for B2B SaaS. They model the world as deals moving through a pipeline. That model breaks down in roofing because a roofing "deal" is not a single thing — it's a customer, a property, a scope, a crew assignment, an invoice, and a warranty obligation, all related to each other.

A modern roofing CRM workflow respects this complexity. It also gets out of the way when an agent needs to take action.

The object model

Six top-level objects, related but distinct:

**Customer.** A person or business that has an ongoing relationship with the company. Customers persist across multiple jobs.

**Property.** A physical address with a roof. Properties persist across multiple customers (rental properties, sold homes).

**Lead.** A potential job for a customer at a property. Leads have a finite lifecycle — they convert to jobs or get archived.

**Job.** A signed contract for work on a property. Jobs have crews, materials, schedules, milestones, and invoices.

**Invoice.** A document requesting payment for a job milestone. Invoices have payment status and aging.

**Warranty.** An ongoing obligation tied to a completed job. Warranties have expiration dates and claim history.

Most legacy CRMs collapse two or more of these into one. Lead and job into "deal." Customer and property into "contact." The collapse causes pain at the seams.

The state machine

Each object has its own lifecycle. The leads lifecycle is straightforward (new → contacted → qualified → quoted → won/lost). Jobs are more interesting:

Pending production

Material ordered

Scheduled

In production

Complete (production)

PART OF

12-STEP ROOFING JOB WORKFLOW

Every roofing job runs through twelve steps from lead to final payment. Here's the canonical workflow and where to automate each step.

Frequently Asked Questions

Do I need to migrate off my current CRM to run this?

Eventually. The seams between a legacy CRM and an agentic operation are real and they cost money. Some operators migrate at the start; others run dual systems for 90 days and migrate once the data quality issues are surfaced.

What about customers from before the migration?

Bulk import with cleanup. Most legacy CRMs have export tooling. We've helped operators migrate 5,000–80,000 customer records with no data loss; it takes a focused week.

Can I keep using my existing CRM and just bolt on agents?

Partially. The agents can read and write through the legacy CRM's API but you'll be limited by what the legacy schema supports. Most operators eventually find the constraints intolerable.

What's the right pipeline structure for roofing?

Stage by stage, not by funnel. "In-progress lead → quoted → contracted → in-production → complete" is more useful than the SaaS-style "awareness/consideration/decision" hierarchy.

How do I handle commercial vs residential in the same CRM?

Separate pipelines, same customer/property model. A commercial lead has different qualifying questions, different cycle times, and different decision-makers. Don't try to force them into the same shape.