Roofing Lead Conversion: Find Where Your Leads Stop Moving

The request came in. Then the trail went quiet.

The request came in. Someone on the team saw it. A few days later, nobody can say what happened next.

That is not one conversion problem. It is a break somewhere in the path: Request → booked inspection → completed inspection → estimate sent → signed work.

A roofing company can lose momentum at any one of those stages. The useful question is not simply, “Are our leads converting?” It is: At which stage are our roofing leads stopping?

Conversion is a path, not a single number

A homeowner request does not become revenue when the form is submitted. Someone still needs to review it, decide the next action, reach the homeowner, schedule the inspection, complete the visit, prepare the estimate, send it, and record what happened afterward.

Each stage leaves different evidence. Don’t try to fix every stage at once. First find where the movement stops.

Jim Leslie’s useful lens

In the Waste No Day episode The Mindset That Squeezes the Gold Out Of Every Lead, Jim Leslie discusses lead cost, customer follow-up, customer empathy, and the relationship between marketing and sales.

Those themes point to a useful distinction: generating an opportunity and converting that opportunity are different jobs. That does not tell a roofing contractor which stage is broken. You find that by looking at what actually happened to your own Requests.

If requests stop before the inspection

A request that never reaches an inspection may point to slow response, unclear ownership, poor service-area fit, or a handoff that nobody completed.

Start with three questions: who reviewed the request, did someone actually reach the homeowner or only attempt contact, and what was supposed to happen next? If nobody can answer those questions, the problem is happening near the beginning of the path.

For the initial handoff, see Roofing Estimate Request Handoff: From Form Submission to Next Action. For the broader routine around ownership and next action, see Roofing Lead Follow-Up: A Clear Process for Small Teams.

The goal is not to create a larger pipeline. It is to find the first missing decision.

If inspections are booked but do not happen

A booked appointment is not a completed inspection. The homeowner may reschedule. The estimator may be delayed. Nobody may answer the door. The visit may be cancelled without another date.

Those events do not automatically explain why the inspection didn’t happen. What matters diagnostically is whether the Request still shows who owns it, what happened last, whether another appointment was agreed, and what needs to happen next.

A calendar can show when an inspection was supposed to happen. It may not tell the team what to do after that appointment changes. For that specific handoff, see When a Roofing Estimate Appointment Changes: Keep the Next Step Clear.

If inspections happen but estimates do not go out

This is a different problem from an unsold estimate. The roof has been inspected. Photos may already exist. Measurements may already be in hand. The homeowner may already be expecting a proposal. But the estimate still has not gone out.

At this stage, inspect what is blocking the estimate, who owns the next step, whether a send date exists, and what happens if that date slips. The problem could be measurements, missing photos, supplement work, supplier pricing, scope questions, or simply unclear ownership.

But the diagnostic question remains the same: did the completed inspection actually move to an estimate? See After a Roofing Inspection: Don’t Let the Estimate Die on the Desk for the narrower inspection-to-estimate problem.

If estimates go out but no decision comes back

Once the estimate has been sent, the problem changes again. The homeowner may still be comparing contractors. Insurance timing may still be unresolved. Financing may matter. The scope may still need clarification. Or the homeowner may simply have stopped responding.

An estimate that has not produced a decision is not automatically lost work. The important distinction is between an action and an outcome. Sending the estimate is an action. Calling the homeowner is an action. Leaving a voicemail is an action. None of those tells you what ultimately happened to the opportunity.

For that stage, see Unsold Roofing Estimates: A Follow-Up Playbook for Roofers.

Activity is not the same as progress

A call attempt is activity. A voicemail is activity. An estimate sent is activity. A note in a CRM is documentation. None of those proves that the homeowner was reached, that an inspection was booked, or that the work is complete.

A useful diagnostic keeps three questions separate: what did the team do, what happened afterward, and what remains unresolved?

That distinction prevents one unanswered call from being treated as completed follow-up. It also prevents an estimate from remaining open indefinitely when nobody knows whether the homeowner postponed the project, hired someone else, or simply has not decided.

If your team cannot reconstruct those steps, How to Track Roofing Leads Without Another CRM covers the minimum information worth keeping visible.

Start with twenty recent roofing Requests

You do not need a complicated analytics system to find the first leak. Take twenty recent Requests. For each one, answer six questions:

Then look for the first missing stage. If most Requests stop before the inspection, inspect intake, ownership, contact, and scheduling. If inspections are booked but repeatedly fail to happen, inspect appointment changes and handoff ownership. If inspections happen but estimates do not go out, inspect the field-to-estimate handoff. If estimates go out but outcomes remain unclear, inspect the post-estimate decision process.

The point is not to create one giant “conversion problem.” The point is to locate the stage that actually needs attention.

• Was the Request reviewed?
• Did someone actually reach the homeowner, or only attempt contact?
• Was an inspection booked?
• Did the inspection happen?
• Was an estimate sent?
• What was the final outcome?

Where Kaldwick fits

Kaldwick helps roofing teams keep unfinished Requests visible and make the next stage clear. A team can keep the Request context, owner, recorded activity, next action, and current status visible in one place.

That can make it easier to distinguish work that still needs attention, an action that already happened, and a Request that has reached a clear outcome.

Kaldwick does not automatically measure signed-roof conversion. It does not make the sale. And it does not decide why a homeowner did not move forward. The first step is still the same: find where the path stops.

What Happens in Your Roofing Company?

Where do roofing leads usually stop moving in your shop — before the inspection, after the inspection, or after the estimate?

Every roofing shop handles these handoffs a little differently. If you want to compare notes with other contractors, share where the process tends to break in your shop.

Join the Kaldwick contractor community and compare notes with other contractors →

Frequently asked questions