How to Track Roofing Lead Conversion Rate Over Time

Roofing companies often know how many leads came in last week. Fewer know whether those leads became qualified inspections, written estimates, sold jobs, good-margin jobs, and serviceable customers. That gap matters. A roofing company can have more calls, more forms, more ad clicks, and more storm inquiries while still losing money if the leads are unqualified, outside the service area, hard to schedule, or poor fit for available crews.

The useful question is not only:

How many roofing leads did we get?

The better question is:

What percentage of roofing leads moved from inquiry to qualified inspection, estimate, sold job, completed project, and healthy closeout over time?

Tracking roofing lead conversion rate over time means building a stage-by-stage record. You measure each step in the pipeline, keep channel labels clean, separate raw contacts from real opportunities, and review trends by source, service area, storm event, job type, and crew capacity. The goal is not to make a dashboard look good. The goal is to know where the roofing business is gaining or losing value.

RoofPredict fits this workflow because lead quality is connected to roof records. A better lead file can include roof age, storm date, property type, service area, photos, prior repair history, inspection outcome, estimate status, closeout records, and warranty-service notes. That turns lead tracking into a business feedback loop instead of a count of phone calls.

The Short Answer

Roofing companies should track lead conversion over time with these stages:

1. raw lead;
2. contact made;
3. qualified lead;
4. inspection scheduled;
5. inspection completed;
6. estimate issued;
7. estimate accepted;
8. job completed;
9. closeout packet delivered;
10. callback or warranty issue tracked.

Then calculate conversion rates between stages:

Review these numbers weekly for operations and monthly for strategy. Track them by source, service area, storm period, job type, salesperson, and crew capacity. A company should not optimize for more leads until it knows which stage is leaking value.

Raw Leads Are Not Roofing Opportunities

Raw leads include:

• phone calls;
• form submissions;
• chat messages;
• Google Business Profile calls or messages;
• referral introductions;
• canvassing contacts;
• storm-event inquiries;
• paid lead platform records;
• social messages;
• missed calls.

Some raw leads are valuable. Some are duplicates. Some are vendors. Some are wrong numbers. Some are outside the service area. Some want emergency help the company cannot provide. Some are price shoppers. Some are homeowners with a real roof issue but poor timing. Counting all of them as equal makes the business look better or worse than reality.

Start with a raw-lead intake table:

The lead is not useful until it has a status.

Define A Qualified Roofing Lead

A qualified roofing lead is not merely a person who filled out a form. Define qualification before reviewing conversion rates.

For many roofing companies, a qualified lead means:

• inside service area;
• property type matches company work;
• homeowner or authorized decision-maker can be identified;
• roof issue matches service offering;
• timing is realistic;
• contact information works;
• no obvious duplicate;
• job size or repair type can justify a visit;
• safety or access concern is understood;
• next step is clear.

Some companies will use different qualification rules. A repair-focused company may accept smaller jobs. A retail replacement company may require a stronger roof-age or replacement signal. A commercial company may require property manager authorization. The key is to write the rule down.

Use labels:

If the team changes labels from month to month, conversion trends become unreliable.

The Roofing Pipeline Stages

Use a pipeline that matches how roofing work actually moves.

Each stage should have one owner and one timestamp. If a stage has no timestamp, the company cannot measure speed. If a stage has no owner, follow-up slips.

Why Time Matters

Conversion rate over time is different from a one-month snapshot. Roofing is seasonal. Storm events can distort numbers. Crews get full. Salespeople change. Ads change. Google Business Profile visibility changes. A new service-area page may take time to produce qualified calls.

Track at least:

• weekly operational view;
• monthly channel view;
• storm-period view;
• quarter-over-quarter trend;
• year-over-year seasonal view.

Example:

At first glance, June looks strong because raw leads jumped. The stage view shows the opposite: qualification, inspections, estimates, and sold jobs fell. That may mean overload, poor source quality, slow response, storm-chaser competition, or capacity constraints.

Source Labels Must Be Clean

Lead tracking breaks when source labels are messy. A roofing company may have:

• Google organic;
• Google Business Profile;
• Google Ads;
• Local Services Ads;
• referral;
• repeat customer;
• email;
• social;
• yard sign;
• canvassing;
• storm page;
• paid lead vendor;
• home show;
• partner;
• unknown.

Pick a stable source list and keep it consistent. Do not let one salesperson write Google, another write web, and a third write internet. Use source and subsource:

Google Analytics key events, Google Ads conversion tracking, and Google Business Profile performance reports can help measure website actions, ad actions, and profile interactions. They still need CRM discipline. A website event is not automatically a sold roofing job.

Track Calls Differently From Forms

Calls and forms behave differently.

Calls can include:

• missed calls;
• short calls;
• vendors;
• wrong numbers;
• existing customers;
• emergency requests;
• real prospects;
• duplicate follow-ups.

Forms can include:

• spam;
• duplicate messages;
• incomplete addresses;
• out-of-area properties;
• high-intent roof issues;
• low-detail price requests.

Measure each separately:

Do not let a surge in phone clicks hide missed calls. Do not let a surge in forms hide spam.

Track Speed To Lead

Roofing leads cool quickly, especially after storms. Track:

• time to first call;
• time to first text;
• time to appointment offered;
• time to inspection scheduled;
• time to inspection completed;
• time from inspection to estimate;
• time from estimate to follow-up;
• time from accepted estimate to production schedule.

Speed matters, but speed without qualification can waste effort. The right metric is not only "called in five minutes." It is:

qualified leads contacted quickly and moved to the right next step.

Use time bands:

These bands should be adjusted for business hours and lead type.

Track Reasons Leads Do Not Convert

Conversion rate improves when lost reasons are specific.

Use loss reason categories:

• outside service area;
• wrong service type;
• no contact;
• price objection;
• timing;
• chose another contractor;
• only wanted insurance advice;
• emergency response unavailable;
• roof too small for visit threshold;
• rental/owner authorization missing;
• duplicate;
• spam/vendor;
• crew capacity unavailable;
• no-show;
• estimate not followed up.

Avoid vague labels like lost or bad lead. They do not teach the business anything.

Example:

Track Job Type

Do not compare every roofing lead together. Track job type:

• leak repair;
• storm documentation;
• roof replacement;
• roof age report;
• inspection only;
• commercial maintenance;
• tile repair;
• metal roof repair;
• flat roof repair;
• gutter-adjacent issue;
• warranty callback;
• emergency tarp;
• real estate transaction.

Each type has a different conversion path. A real estate roof-age question may convert slowly. A storm leak may need immediate handling. A warranty callback is not a new lead. A commercial maintenance contact may take months.

Track Service Area And Drive Time

A lead can look good until drive time is added. Track:

• ZIP code or city;
• drive time from office or crew base;
• inspection route;
• production route;
• service callback risk;
• permit or HOA complexity;
• source page or campaign tied to location.

If a territory produces calls but low margin, distance may be the hidden leak. Tie conversion rate to geography:

RoofPredict can help link property location, roof record, inspection outcome, and service feasibility.

Track City, State, Storm, And Directory Cohorts Separately

City and state performance should not be collapsed into one average. Roofing lead conversion changes when the local market changes: storm timing, roof age, permit friction, drive time, roof material, insurance questions, local trust, directory profile quality, and crew capacity all affect the funnel.

Build local cohorts:

A Florida city page, a Texas storm page, a Colorado hail page, and a Midwest winter repair page should not be judged by the same raw lead metric. The right question is whether the page, directory profile, or market brief produces the kind of lead the company can inspect, estimate, install, close out, and service.

Examples:

• A Tampa Bay hurricane-prep page may produce many storm-season calls, but the useful metric is serviceable inspections after active-leak triage, not raw calls.
• A Dallas-Fort Worth hail page may need a separate deductible/public-adjuster boundary label so insurance-only contacts do not inflate qualified demand.
• A Phoenix heat/roof-age page may convert more slowly but produce better retail replacement conversations if roof age, attic comfort, and material notes are captured cleanly.
• A Chicago winter leak page may generate repair-first leads that should not be compared with spring replacement campaigns.
• A contractor directory profile may look weak by raw calls but strong by qualified inspection rate if it filters out poor-fit homeowners.

This is also where RoofPredict can support local/state content quality. If the same market keeps producing the same real questions, those questions can become better pages. If a city page produces mostly outside-area or wrong-service leads, the page needs clearer service boundaries or should not be expanded.

Good fit for contractor directory CTA: use when conversion data shows profile completeness, service-area clarity, response time, closeout proof, and review/referral quality matter.

Good fit for state market brief CTA: use when conversion data shows local differences in storm timing, roof age, roof type, permit friction, labor capacity, material mix, or insurance-role questions.

Good fit for The Roofline newsletter CTA: use when conversion data produces recurring lessons about lead quality, storm response, service-area boundaries, estimate follow-up, or callback prevention.

Track Estimate Quality

Conversion rate is not only marketing. A company may lose at the estimate stage because estimates are late, vague, or poorly matched to the inspection.

Track:

• inspection completed date;
• estimate issued date;
• estimate version;
• whether photos are attached;
• whether scope is itemized;
• whether materials are clear;
• whether exclusions are clear;
• whether financing or payment terms are clear;
• whether follow-up happened;
• whether customer questions were answered.

Estimate conversion can be improved by better records, not only better sales scripts.

Use A Rolling Cohort View

Monthly close rate can mislead because roofing jobs do not all close in the same month they entered.

Use cohorts:

Leads created in April:
- raw leads: 120
- qualified: 72
- inspected within 14 days: 60
- estimates issued within 21 days: 48
- sold within 45 days: 18
- completed within 90 days: 16

That shows what happened to one lead group over time. Cohorts are especially useful when storms create a spike or when production backlog delays jobs.

Review Weekly, Monthly, Quarterly

Weekly review:

• new raw leads;
• contact rate;
• missed calls;
• scheduled inspections;
• capacity issues;
• urgent lost reasons.

Monthly review:

• source performance;
• qualified rate;
• estimate rate;
• close rate;
• service-area quality;
• sales follow-up issues;
• job-type mix.

Quarterly review:

• channel investment;
• territory expansion or cuts;
• content updates;
• CRM labels;
• lead vendor decisions;
• staffing needs;
• service callback trends.

Do not change everything weekly. Use weekly reviews for operations and monthly or quarterly reviews for strategy.

Data Quality Rules

Use these rules:

• every lead gets one lead ID;
• every property gets one property record;
• duplicates are merged or linked;
• source labels come from a controlled list;
• stage changes require timestamps;
• lost reasons come from a controlled list;
• sold jobs tie back to estimate ID;
• completed jobs tie to closeout records;
• callbacks tie to the original job if possible;
• privacy-sensitive data is limited to what the business needs.

FTC privacy and data-security guidance matters when customer information is collected. Roofing lead files may include names, addresses, phone numbers, emails, photos, claim details, and property information. Keep access limited and use lead data for the stated business purpose.

How RoofPredict Helps

RoofPredict can connect lead tracking to roof records:

• source and lead ID;
• property address;
• roof age signal;
• storm exposure note;
• photos;
• inspection status;
• estimate status;
• sold job status;
• closeout packet;
• callback history;
• service-area performance.

This makes conversion tracking more useful because the business can see which types of roof records become qualified opportunities and which channels produce poor-fit inquiries.

A Roofing Conversion Dashboard

A simple dashboard can show:

This view tells a better story than raw lead count. The company may need better qualification, scheduling, estimate follow-up, or production capacity before buying more leads.

Final Rule

Track roofing lead conversion rate as a pipeline, not a scoreboard. A lead is useful only if it can become a qualified inspection, clear estimate, sold job, completed project, and serviceable customer. More leads are valuable when the company can respond, qualify, inspect, estimate, install, close out, and support the work.

If the numbers rise at the top and fall in the middle, fix the process before increasing spend.

Build The Data Dictionary First

Before a roofing company builds a dashboard, it should define the words used in the dashboard. A data dictionary prevents monthly arguments about what counts as a lead, what counts as qualified, and when a job is considered sold.

Minimum definitions:

The data dictionary should also define what does not count:

• spam forms;
• vendors;
• job applicants;
• wrong numbers;
• duplicate contacts;
• existing job updates;
• warranty callbacks;
• internal test submissions;
• homeowners outside the service boundary if the company will never serve them.

Some of those records still matter. A missed warranty call matters for service. A duplicate matters for customer experience. They just should not inflate new-lead conversion rate.

CRM Fields For Roofing Lead Tracking

A CRM or lead tracker should capture enough detail to make the pipeline explainable without forcing salespeople to write essays.

Use required fields:

• lead ID;
• property ID;
• contact name;
• phone;
• email if available;
• property address;
• service area;
• source;
• subsource;
• issue type;
• roof type if known;
• roof age signal if known;
• storm date if relevant;
• appointment status;
• salesperson or intake owner;
• inspection owner;
• estimate owner;
• stage;
• next action date;
• lost reason if closed lost.

Use optional fields:

• photo link;
• roof report link;
• insurance claim number if customer provides it and the company has a legitimate business reason to store it;
• permit question;
• HOA flag;
• financing interest;
• customer urgency;
• language preference;
• notes for access or pets;
• competitor mentioned internally if the company tracks it privately.

Avoid open-ended note fields as the only source of truth. Notes are useful, but structured fields make reporting possible.

Stage Entry And Exit Rules

Every stage should have an entry rule and exit rule.

Rules prevent pipeline inflation. If an inspection is scheduled but the homeowner no-shows, it should not become "inspected." If an estimate is verbally discussed but never sent, it should not count as "estimate issued." If a job is accepted but never produced, it should not count as completed revenue.

Roofing Lead Source Taxonomy

Use a source taxonomy that fits roofing.

Primary source:

• organic search;
• Google Business Profile;
• paid search;
• Local Services Ads;
• referral;
• repeat customer;
• canvassing;
• storm response;
• social;
• email;
• partner;
• paid lead vendor;
• direct;
• unknown.

Subsource examples:

• article slug;
• service-area page;
• campaign name;
• ad group;
• call extension;
• GBP call;
• GBP message;
• referral customer;
• storm date;
• neighborhood canvass;
• home show;
• real estate agent;
• property manager.

Do not overcomplicate the source list at first. Start stable, then add detail only where the team can maintain it.

Conversion Formulas For A Roofing Dashboard

Use formulas that managers can check.

Qualified rate = qualified leads / contacted leads
Inspection set rate = scheduled inspections / qualified leads
Inspection completion rate = completed inspections / scheduled inspections
Estimate rate = estimates issued / completed inspections
Close rate = accepted estimates / estimates issued
Production completion rate = completed jobs / accepted estimates
Closeout completion rate = closeout packets / completed jobs
Callback rate = callbacks / completed jobs

Also track time:

Average response time = sum(first response time) / contacted leads
Median inspection delay = middle value of days from lead to inspection
Estimate turnaround = days from inspection to estimate issued
Sales cycle = days from raw lead to accepted estimate
Production cycle = days from accepted estimate to completed job

Median often tells a clearer story than average when a few delayed jobs distort the numbers.

Example: Lead Volume Is Up, Business Quality Is Down

Suppose a roofing company gets these monthly numbers:

Raw leads doubled from March to May. Qualified leads barely moved. Inspections fell. Estimates fell. Sold jobs fell. Callback rate rose.

Possible causes:

• a broad campaign attracted poor-fit leads;
• service area expanded too far;
• storm inquiries overloaded intake;
• sales follow-up slowed;
• inspections were rushed;
• production quality suffered;
• the company counted unqualified contacts as success.

The answer is not automatically "buy more leads." The answer may be to pause poor-fit sources, tighten location targeting, fix missed calls, improve estimate turnaround, or reduce territory spread.

Lead Scoring Without Overclaiming

A simple lead score can help route work, but it should not decide everything. Use it as a triage tool.

Example score:

Score bands:

The score should be reviewed against outcomes. If low-scoring leads close profitably, adjust the model. If high-scoring leads no-show, the score is missing something.

Storm Week Tracking

Storm weeks need their own tracking view. A storm can create call spikes, duplicate reports, urgent leaks, out-of-area inquiries, and insurance questions. If those are mixed into normal weeks, conversion rates become hard to interpret.

Create storm-week fields:

• storm date;
• affected service area;
• issue type;
• emergency need;
• temporary protection request;
• insurance claim mentioned;
• inspection urgency;
• photos provided;
• source page or campaign;
• capacity status;
• ethical-response note.

Then review:

• how many inquiries were truly serviceable;
• how many were emergency-only;
• how many became inspections;
• how many were outside the service radius;
• how many were declined because capacity was full;
• how many produced callbacks later.

A storm can look successful in lead volume and still be harmful if the company accepts more work than it can document and service well.

Estimate Follow-Up Tracking

Many roofing companies lose value after the estimate is issued. Track follow-up:

• estimate sent date;
• first follow-up date;
• customer question received;
• revised estimate date;
• decision deadline if any;
• lost reason;
• salesperson owner;
• final disposition.

Use follow-up statuses:

If estimates are issued but not followed up, the company may blame lead quality when the real issue is sales discipline.

Closeout And Callback Tracking

A sold job is not the end of conversion tracking. Completed work can create referrals, reviews, repeat work, warranty questions, or callbacks.

Track:

• final invoice delivered;
• payment complete;
• final photos delivered;
• warranty documents delivered;
• permit closeout if applicable;
• customer satisfaction note;
• review request timing if the company uses one;
• callback within 30, 60, 90, and 365 days;
• callback type;
• callback cause if known;
• service cost.

This protects the business from optimizing for quick sales that create expensive service later. A source with a high close rate but high callback rate may not be a healthy source.

Meeting Agenda For Weekly Review

A weekly roofing conversion meeting should be short and factual:

1. Raw leads by source.
2. Qualified leads by source.
3. Missed calls and response time.
4. Inspection schedule capacity.
5. Estimates issued and overdue.
6. Lost reasons.
7. Territory or source problems.
8. Production capacity concerns.
9. Closeout backlog.
10. One process change for the week.

Do not spend the meeting debating every lead. Look for patterns. If one source produced 30 calls and 4 qualified inspections, review its message. If one salesperson has many overdue estimates, fix that workflow. If callbacks are rising from a territory, review service radius and production notes.

Monthly Channel Decision

At month end, decide what to do with each channel:

This prevents "the internet is bad" or "ads are good" conclusions. Channels are only good when they produce serviceable, profitable roofing work.

What To Publish From Lead Questions

Lead tracking can improve content. When the same real questions appear in calls, forms, or inspections, those questions may deserve stronger pages:

• roof age before selling;
• roof inspection before hurricane season;
• storm damage photos;
• emergency leak steps;
• repair versus replacement questions;
• roofing estimate terms;
• permit records;
• warranty service;
• service-area boundaries;
• insurance-role separation.

Do not publish pages only because a keyword tool lists them. Publish when the business keeps hearing the question and can answer it with useful records, source notes, examples, and boundaries.

Data Privacy And Access

Roofing lead data often includes private customer information. A lead tracker should limit access and avoid collecting unnecessary sensitive details.

Practical rules:

• keep customer contact data in approved systems;
• limit export access;
• avoid storing claim documents unless needed for a legitimate business reason;
• restrict photo access;
• delete test submissions;
• document who can see lead records;
• do not use customer data for unrelated purposes;
• train staff on handling personal data.

The FTC privacy and data-security sources are relevant because lead generation often involves personal data. Even a small roofing company should treat homeowner names, addresses, phone numbers, photos, and job details with care.

Final Worksheet

Use this worksheet for each source every month:

Source:
Raw leads:
Valid contacts:
Qualified leads:
Scheduled inspections:
Completed inspections:
Estimates issued:
Sold jobs:
Completed jobs:
Closeout packets:
Callbacks:
Average response time:
Top lost reason:
Top service area:
Decision: invest / fix / narrow / pause / stop

The worksheet forces the team to make a decision from the whole funnel, not one number.

Role Accountability

Lead conversion tracking fails when everyone can edit the pipeline but no one owns each stage. Assign owners:

Each owner should know what a clean record looks like. For example, the salesperson should not mark a lead as estimated unless a written estimate was sent. The project manager should not mark closeout complete unless final documents were delivered. The service manager should tie callbacks to the original job whenever possible.

This role map also makes training easier. If inspection completion rates fall, the company knows which handoff to inspect. If closeout packets lag, the issue is not marketing.

Lead Lifecycle Example

A homeowner fills out a form after reading a roof-age article.

Day 1:

• source: organic search;
• subsource: roof-age page;
• raw lead created;
• property inside service area;
• roof age unknown;
• homeowner has safe photos;
• intake calls within 12 minutes.

Day 2:

• lead qualified;
• inspection scheduled;
• roof age records requested.

Day 5:

• inspection completed;
• photos saved;
• roof appears repairable;
• estimate requested.

Day 7:

• estimate issued;
• customer asks warranty question.

Day 11:

• estimate revised;
• customer accepts repair.

Day 20:

• repair completed;
• invoice, photos, and warranty note delivered.

That lead should be counted as raw lead, qualified lead, inspection, estimate, sold job, completed job, and closeout complete. It should also teach the content team that roof-age content attracted a serviceable repair lead, not only replacement demand.

Another Example: Bad Raw Lead, Useful Signal

A form submission says:

I need a free roof from insurance. I am two counties outside your service area.

That is not a qualified lead. Still, it is useful data:

• source: storm page;
• status: poor fit;
• reason: outside service area and insurance-only request;
• action: add service-area boundary and insurance-role language to page;
• no inspection scheduled.

If ten similar inquiries arrive, the page may be attracting the wrong audience. The fix may be content clarity, location targeting, or storm-response messaging.

Dashboard Anti-Patterns

Avoid these dashboard mistakes:

• showing raw leads without qualified leads;
• hiding duplicates;
• mixing warranty calls with new opportunities;
• counting missed calls as good leads;
• reporting ad conversions without CRM outcomes;
• measuring close rate without estimate issue rate;
• measuring revenue without callback cost;
• mixing storm weeks into normal months without labels;
• changing source names every month;
• letting salespeople use custom lost reasons.

A dashboard should make management decisions easier. If it creates arguments about definitions, the data dictionary is not finished.

The 30-Day Rollout Plan

Week 1: define fields.

• choose pipeline stages;
• define qualified lead;
• define source list;
• define lost reasons;
• define job types;
• assign owners.

Week 2: clean intake.

• add required fields;
• remove duplicate source labels;
• train intake team;
• test call/form capture;
• review privacy access.

Week 3: connect outcomes.

• tie inspections to leads;
• tie estimates to inspections;
• tie sold jobs to estimates;
• tie closeout packets to completed jobs;
• tie callbacks to original jobs.

Week 4: review and adjust.

• run first source report;
• identify top leak stage;
• correct bad labels;
• choose one process fix;
• schedule monthly channel review.

Do not try to solve every tracking problem in the first month. The first win is making the pipeline honest.

What Good Looks Like After 90 Days

After 90 days, the company should know:

• which channels produce qualified inspections;
• which sources create poor-fit leads;
• which service areas convert and which drain time;
• whether estimates are issued fast enough;
• whether sales follow-up is consistent;
• whether storm leads are profitable or chaotic;
• whether closeout packets are being delivered;
• whether callbacks are concentrated by crew, source, job type, or territory;
• whether content pages answer real lead questions.

The output should be a decision list:

This is where conversion tracking becomes operational intelligence.

RoofPredict Record Design

In RoofPredict, a useful lead record should connect:

• lead ID;
• property ID;
• source;
• roof record;
• customer question;
• stage;
• owner;
• timestamp;
• next action;
• estimate link;
• job link;
• closeout link;
• callback link.

The record should answer:

Where did the opportunity come from, what did the homeowner need, what roof evidence existed, what happened next, and what did we learn?

That question is more useful than "how many leads came in?"

Final Quality Check

Before using conversion data for budget decisions, ask:

• Are duplicates controlled?
• Are sources stable?
• Are stages defined?
• Are lost reasons specific?
• Are salespeople entering estimates consistently?
• Are sold jobs tied back to leads?
• Are completed jobs tied to closeout?
• Are callbacks visible?
• Are privacy rules followed?
• Are storm periods labeled?

If the answer is no, the report may still be useful for operations, but it should not drive major spend decisions yet.

What To Exclude From KPI Reports

Keep some records out of new-lead conversion KPIs:

• existing customer service calls;
• warranty callbacks;
• current project updates;
• vendor pitches;
• job applicants;
• spam;
• test submissions;
• duplicate forms from the same property;
• customer uploads requested after inspection;
• insurance document uploads after a job is already active.

Those records still belong somewhere. They just belong in service, recruiting, vendor, customer-support, or active-project reporting. If they stay inside the new-lead funnel, the team may punish a good source or reward a bad one.

The Executive View

Owners do not need every field each week. They need the few measures that reveal business health:

If raw leads are up but qualified leads are flat, marketing may be noisy. If qualified leads are up but inspections are flat, scheduling may be constrained. If inspections are up but estimates are flat, estimating is the bottleneck. If sold jobs are up but callback rate rises, production quality or job fit may be weakening.

The Sales Manager View

Sales managers need a different report:

• lead owner;
• first response time;
• scheduled inspections;
• inspection completion;
• estimate turnaround;
• follow-up overdue;
• close rate by salesperson;
• lost reasons by salesperson;
• estimate revision rate;
• customer question themes.

This report should be used for coaching, not only pressure. If one salesperson closes fewer jobs but handles harder repairs, the raw close rate may be unfair. If one salesperson has many no-shows, the issue may be qualification or scheduling. Context matters.

The Marketing View

Marketing should see:

• source;
• subsource;
• page or campaign;
• raw leads;
• valid contacts;
• qualified leads;
• qualified rate;
• inspection set rate;
• sold jobs;
• closeout quality;
• top customer questions;
• top poor-fit reasons.

This view helps decide which pages to update. If a page attracts many questions about roof age, add clearer roof-age records. If a storm page attracts insurance-only questions, clarify the contractor's repair role. If a service-area page attracts outside-area leads, improve boundary language.

The Production View

Production should see the pipeline before jobs hit the calendar:

• accepted estimates by service area;
• expected start dates;
• job type;
• roof type;
• permit needs;
• material availability;
• project manager owner;
• crew capacity;
• distance from crew base;
• closeout requirements.

Lead conversion tracking should warn production before the schedule breaks. If the sales team is about to sell outside a healthy service radius, production needs to know.

Keep The System Boring

The best tracking system is boring enough that the team actually uses it. Use stable labels, short required fields, weekly cleanup, and clear owners. Avoid building a dashboard so complicated that no one trusts it.

Start with one truth:

Every lead should have a source, stage, owner, next action, and final outcome.

Everything else can improve over time.

If that one truth is reliable, a roofing company can make better decisions about content, ads, staffing, territories, sales training, and production capacity without pretending every inquiry has the same value. The result is a cleaner pipeline, better follow-up, and fewer expensive surprises.

It also helps managers say no to sources that only look busy on reports that flatter volume without profitable roofing work after the month ends.

Source Notes

Sources checked: June 9, 2026.

Google Analytics Help, "About key events": https://support.google.com/analytics/answer/9267568

Google Ads Help, "Different ways to track conversions": https://support.google.com/google-ads/answer/1722054

Google Ads, "Conversion Tracking": https://ads.google.com/intl/en_us/home/measurement/conversion-tracking/

Google Business Profile Help, "View your Business Profile performance": https://support.google.com/business/answer/9918094

Google Business Profile Help, "Service-area businesses": https://support.google.com/business/answer/3038177

FTC, "Privacy and Security": https://www.ftc.gov/business-guidance/privacy-security

FTC Business Blog, "Lead generation: When the product is personal data": https://www.ftc.gov/business-guidance/blog/2017/07/lead-generation-when-product-personal-data

FAQ

What is roofing lead conversion rate?

Roofing lead conversion rate is the percentage of leads that move from one stage to another, such as raw lead to qualified lead, inspection, estimate, sold job, completed project, and closeout.

What conversion rate should a roofing company track first?

Track qualified-lead rate first. Raw lead count can be misleading if many inquiries are duplicates, vendors, outside the service area, or poor fit.

Should calls and forms be tracked together?

Track them separately and together. Calls and forms often have different qualification rates, response needs, spam issues, and close rates.

How often should roofing conversion rates be reviewed?

Review operational rates weekly, channel performance monthly, and territory or budget decisions quarterly. Storm periods may need separate review.

What is a qualified roofing lead?

A qualified roofing lead fits the service area, service type, timing, contactability, property type, and authority requirements written by the company.

Why did leads increase but sales fall?

Possible causes include poor lead quality, slow response, outside-area traffic, scheduling limits, weak estimate follow-up, crew capacity, pricing mismatch, or storm-event overload.

How should lost roofing leads be labeled?

Use specific labels: outside service area, no contact, duplicate, price objection, no-show, wrong service type, timing, chose another contractor, or capacity unavailable.

What is speed to lead?

Speed to lead is the time between lead arrival and first response. It should be reviewed with qualification, not as a standalone vanity metric.

How can RoofPredict help with lead conversion tracking?

RoofPredict can connect lead source, roof age, property record, storm note, inspection outcome, estimate status, closeout packet, and callback history.

Should every website form be counted as a conversion?

No. A form can be spam, duplicate, outside-area, or poor fit. Count it as a raw lead first, then qualify it before using it as a performance signal.

What is a cohort view?

A cohort view tracks leads created in one period and follows them through inspection, estimate, sale, completion, and closeout over time.

How should Google Ads conversions be used?

Use Google Ads conversion tracking for measured ad actions, but tie ad conversions back to CRM stages so the company can see which actions became real roofing opportunities.

What should be tracked after a job is sold?

Track production scheduling, completion, closeout packet, payment, review or referral, callback, warranty question, and service cost.

How do service areas affect conversion rate?

Farther service areas may produce leads but lower margin, slower response, more missed appointments, and higher callback costs. Track geography with conversion rates.

What privacy concerns apply to roofing lead tracking?

Lead records may include names, addresses, phone numbers, emails, photos, and claim details. Limit access, use data for business purposes, and follow applicable privacy and security duties.

What is the biggest tracking mistake roofers make?

They optimize for raw leads instead of qualified inspections, estimates, sold jobs, completed work, and healthy closeout.