A roofing company without lead scoring treats every inquiry the same. The homeowner with an active insurance claim for hail damage sits in the same queue as the homeowner wondering whether their 15-year-old shingles need attention someday. The sales team scrolls through a flat list of names and phone numbers, guessing who to call first based on gut instinct or the order submissions arrived. During storm season, when 30 leads come in during a single afternoon, this approach guarantees that high-value insurance-backed leads get buried under routine maintenance requests.
Lead scoring solves this by assigning a numerical value to each lead based on their answers to qualifying questions. The score determines which pipeline stage the lead enters, which email sequence they receive, and how urgently the sales team is notified. For roofing agencies using GoHighLevel, the scoring model is built around two factors unique to the industry: damage urgency and insurance status.
Why roofing scoring uses damage type and insurance, not just budget and timeline
Most lead scoring models in home services weight budget and timeline as the primary factors. A dental practice asks about insurance coverage and treatment urgency. A realtor asks about pre-approval status and move-in timeline. These are valid scoring inputs for those industries.
Roofing operates differently. The budget question is often irrelevant during storm season because insurance covers the cost. A homeowner with a $15,000 roof replacement approved by their insurer is not shopping on price. They are shopping on speed, trust, and whether the contractor can navigate the insurance documentation process. Scoring that homeowner on budget would place them in the same tier as a cash-pay homeowner considering the same project, even though the insurance-backed lead closes faster, at higher margins, with less negotiation.
The roofing scoring model prioritizes three inputs:
Damage type. Active leaks and structural compromise score highest because they represent emergencies that convert in hours. Hail and wind damage score high because they typically qualify for insurance claims. Age-related wear and cosmetic concerns score lowest because they indicate flexible timelines and cash-pay projects.
Insurance status. An active insurance claim is the strongest buying signal in roofing. The homeowner has already committed to the project. The budget is approved. The only question is which contractor gets the job. This single factor should carry 25 to 30 percent of the total score weight.
Timeline urgency. A homeowner who needs service this week scores higher than one planning for next quarter. Timeline interacts with damage type: an active leak with an immediate timeline is an emergency. An age-related replacement with a flexible timeline is a nurture lead. The combination determines the true urgency.
The scoring model: point values by damage type and priority
The following model uses a 100-point scale. Leads scoring 70 and above enter the hot tier. Leads scoring 40 to 69 enter the warm tier. Leads below 40 enter the nurture tier. Emergency leads bypass scoring entirely.
| Scoring Factor | Answer | Points |
|---|---|---|
| Insurance Status | Active claim filed | 30 |
| Insurance Status | Planning to file | 15 |
| Insurance Status | No insurance / not applicable | 0 |
| Damage Type | Hail or wind damage | 25 |
| Damage Type | Fallen debris or tree impact | 20 |
| Damage Type | Age-related wear | 10 |
| Damage Type | Cosmetic / curb appeal | 5 |
| Timeline | This week | 20 |
| Timeline | Within 30 days | 12 |
| Timeline | Flexible / planning ahead | 5 |
| Roof Age | 15+ years | 15 |
| Roof Age | 10 to 14 years | 10 |
| Roof Age | Under 10 years | 5 |
| Property Type | Single-family residential (owner) | 10 |
| Property Type | Multi-family or commercial | 8 |
| Property Type | Rental property | 4 |
A homeowner who reports hail damage (25), has an active insurance claim (30), needs service this week (20), has a 15-year-old roof (15), and owns a single-family home (10) scores 100. That lead gets an immediate internal notification, enters the hot pipeline stage, and receives the insurance storm damage email sequence.
A homeowner who reports age-related wear (10), has no insurance (0), is planning ahead (5), has a 12-year-old roof (10), and owns a single-family home (10) scores 35. That lead enters the nurture sequence with seasonal maintenance content and periodic free inspection offers.
Emergency detection: when scoring does not apply
Active leaks, structural compromise, and tarping requests are emergencies that bypass the scoring model entirely. These leads need immediate human contact, not a calculated score and a sequenced email.
The quiz configuration handles this with an early detection question. When the homeowner selects "active leak," "roof is sagging or buckling," or "need emergency tarping," the system routes them to the emergency pipeline stage and fires an internal notification to the on-call team. The remaining quiz questions still collect useful data, but the routing decision is already made. The emergency flag overrides whatever score the remaining answers would produce.
This design ensures that a homeowner with an active leak at 2 AM on a Saturday is not sitting in a queue waiting for their score to be calculated. They are in the emergency stage with a notification en route to the person who can dispatch a crew.
How the score connects to pipeline stages and email sequences
The score is not a standalone number. It is the trigger that determines three downstream actions: which pipeline stage the lead enters, which email sequence they receive, and how the internal notification is formatted.
Score 70 to 100 (hot). Pipeline: Hot Insurance Storm Damage. Email: aggressive follow-up focused on scheduling the inspection and positioning the company for the adjuster walkthrough. Internal notification: priority alert with full scoring data, sent to the senior sales rep directly.
Score 40 to 69 (warm). Pipeline: Warm Damage, No Claim. Email: educational sequence guiding the homeowner through the insurance claims process and offering a free damage documentation inspection. Notification: standard alert sent to the general sales queue.
Score below 40 (nurture). Pipeline: Routine Maintenance Nurture. Email: long-term sequence with seasonal content, maintenance tips, and periodic offers. Notification: daily digest summary rather than individual alerts.
The connection between score, pipeline stage, and email sequence is configured in GoHighLevel workflows. The workflow fires on quiz submission, reads the lead score from the custom field, and branches into three paths based on the threshold values. Each path moves the contact to the appropriate pipeline stage and enrolls them in the corresponding email sequence. The entire routing process completes in under 10 seconds after the homeowner submits the quiz.
Calibrating thresholds after the first 30 days
The initial threshold values of 70 and 40 are starting points, not permanent settings. After 30 to 60 days of live data, the agency should review which score ranges are actually converting to booked inspections and which are not.
If leads scoring 55 to 69 are booking inspections at nearly the same rate as leads scoring 70 and above, the hot threshold should drop to 55. If leads scoring 40 to 55 are not converting, the warm threshold should rise, compressing the warm tier and expanding the nurture tier. The goal is to match the scoring thresholds to the actual conversion behavior observed in the storm season data.
Calibration also reveals whether specific quiz questions carry their weight. If roof age has no measurable impact on conversion rates, its point allocation should be reduced and redistributed to factors that do correlate with bookings. The scoring model is a living system. The initial configuration gets it running. The calibration makes it accurate.
One common finding during calibration: response speed matters more than score precision. A warm lead contacted within five minutes often outperforms a hot lead contacted after two hours. The scoring model prioritizes the callback order, but the follow-up system determines whether the callback actually happens before the homeowner moves on to a competitor.
Regional adjustments for storm-prone areas
Scoring models should account for regional storm patterns. A roofing company operating in a hail corridor like the Texas panhandle or the Colorado Front Range will see a higher proportion of insurance-backed storm leads than a company in a region where most roofing work is age-related replacement. The model itself does not change, but the threshold calibration will differ because the score distribution shifts.
In storm-heavy regions, a larger percentage of leads will score above 70. If the sales team cannot process all hot leads within the five-minute response window, the hot threshold should be raised to 80 or 85, ensuring that only the highest-urgency leads trigger priority alerts while the rest still receive fast automated follow-up. In regions with less storm activity, the hot threshold may drop to 60 because fewer leads reach the upper score ranges and the ones that do represent a proportionally higher conversion opportunity.
Seasonal threshold shifts
Some agencies adjust their scoring thresholds seasonally. During peak storm season, when the pipeline is full and crews are at capacity, raising the hot threshold from 70 to 80 helps the sales team focus on the highest-probability closes. During the off-season, lowering the hot threshold to 60 ensures that the fewer leads entering the system still receive priority treatment. This adjustment can be automated in GoHighLevel by using a date-based workflow condition that modifies the threshold values at the start and end of each season.
The key principle is that the scoring model serves the business, not the other way around. If the thresholds are producing callback queues that the sales team cannot clear in a reasonable timeframe, the thresholds need to tighten. If the thresholds are so strict that qualified leads are languishing in the nurture tier, they need to loosen. The data from the first 30 to 60 days of operation provides the answers. The model just needs to be flexible enough to incorporate them.
How Origin deploys the complete scoring system
Origin's roofing niche ecosystem includes the complete scoring model described above, pre-configured and ready to deploy. The quiz questions, point values, threshold logic, pipeline stage routing, and email sequence enrollment are all built into the snapshot. The agency imports it, customizes the brand, and the scoring system is live.
The roofing setup guide covers the full deployment process. The scoring model is one component of the larger system that includes custom fields, pipeline architecture, email sequences, internal notifications, and booking calendar configuration. All components work together, and the scoring model is the decision engine that determines how every other component behaves for each individual lead.
Industry close rate benchmarks for roofing confirm that the difference between a good and a mediocre operation often comes down to who gets called first and how quickly. A scoring model that puts insurance-backed storm damage leads at the top of the callback list before a human makes a single decision is the infrastructure that makes that possible at scale.