How to Prioritize Storm Leads When You Have Too Many

Two days after a supercell rakes a metro with golf-ball hail, the problem flips. For months you fought to generate leads. Now you have 380 of them sitting in a spreadsheet, your phone won't stop, three competitors from out of state just rented an office down the road, and your crews can physically inspect maybe 40 roofs a day if everything goes right. The math is brutal: you cannot get to everyone, the storm-chasers will skim the easy ones, and the longer a damaged roof sits unsigned, the more likely a homeowner forgets the storm ever happened.

Winning a storm market has almost nothing to do with how many leads you collect. It has everything to do with the order you work them. The companies that come out of a big event with healthy margins are the ones that decided, on purpose, which doors to knock first and which to let go. Everyone else burns daylight driving to roofs that have no damage, no urgency, or no money behind them.

What follows is the triage system used by storm crews that actually finish the season profitable: how to score a lead in under a minute, how to sequence routes so a salesperson isn't crossing town six times a day, how to read which roofs the storm actually wore out, and how to avoid the classic traps that turn a good storm into a refund-and-callback nightmare. There are worked examples, scoring tables you can copy, and the edge cases nobody warns you about. No fluff, because in a storm market the only currency is time.

Why "too many leads" is the most expensive problem in roofing

It feels like a good problem. It is not. A flood of leads is the single most common reason a contractor loses money on a storm that should have made the year.

Here is the trap. When 300 leads land at once, the natural instinct is to chase them in the order they arrived, or in the order they shout the loudest. The customer who calls four times gets seen first. The referral from your buddy's cousin jumps the line. The address closest to the office gets knocked because it's convenient. None of those signals correlate with whether the roof has real damage, whether the homeowner will sign, or whether the job will pay. You end up spending your scarcest resource, inspector hours during the two-week window when memory of the storm is hottest, on the roofs least likely to convert.

Three costs stack up when you work leads in the wrong order:

• Inspection waste. A no-damage inspection still costs you 45 to 90 minutes of a salesperson's day once you count drive time, the ladder, the conversation, and the write-up. Twenty wasted inspections is a full salesperson-week gone.
• Spoilage. Storm urgency decays fast. A homeowner who would have signed in week one talks themselves out of it by week four, especially once the sun comes out and the ceiling isn't leaking. Leads you fail to reach early don't wait, they rot.
• Cherry-picking by competitors. Out-of-market crews are good at one thing: speed on obvious damage. If you're slow to the high-confidence roofs, you hand them the easiest closes and keep the marginal ones for yourself.

The goal of triage is simple to state and hard to execute: get your best inspectors in front of the highest-probability roofs while the storm is still emotionally fresh, and stop pretending you can serve everyone. A 250-lead list worked in smart order will out-earn a 400-lead list worked in arrival order every single time.

The three numbers behind every storm lead

Strip away the noise and every storm lead reduces to three questions. Score each one and you have a number you can sort on. The whole system rests on this.

1. Damage probability. How likely is it that this specific roof took real, documentable storm damage? This is physics plus materials, not enthusiasm. A 22-year-old three-tab shingle roof under the densest part of the hail core is a different animal than a 4-year-old architectural roof on the edge of the swath.
2. Closeability. If the damage is real, how likely is this homeowner to move forward? This is about decision-making conditions: do they own the roof, is it their primary residence, is the home occupied, is there an active insurance relationship, are they the sole decision-maker.
3. Value and effort. What is this job worth, and how hard is it to do? A steep, cut-up, four-story roof with a leak over the master bedroom is worth more than a one-story ranch, but it also eats crew days and risk. Proximity to your other live jobs matters here too, because a tight route multiplies how many inspections each salesperson can run per day.

Notice what is NOT on the list: how loud the lead is, how it came in, or how close it is to your office. Those feel urgent and mislead you. The discipline is to ignore the noise and score on the three that predict revenue.

You do not need a data-science team to do this. You need a one-page rubric, a shared definition of each tier, and a manager who enforces the sort. The next sections turn each of the three numbers into something you can actually fill in.

Why all three have to be present

New sales managers often try to shortcut the system by scoring on a single factor. They sort the whole list by damage probability and call it a day, or they chase the biggest roofs first because the commission looks fat. Both fail, and they fail in predictable ways.

Sort on damage alone and you'll send a salesperson 40 minutes out to a beat-up roof owned by an unreachable out-of-state landlord. Real damage, zero closeability, a wasted morning. Sort on value alone and you'll put your A-player on a giant cut-up roof that turns out to sit on the fringe with no actionable damage, eating a full day for nothing. Sort on closeability alone and you'll fill your calendar with eager homeowners whose roofs the storm never touched, then spend two weeks explaining to them why you can't help.

The three numbers work because they're a chain. A lead has to clear all three to be worth a same-day knock. Multiply them in your head if it helps: a roof that's a 9 out of 10 on damage but a 2 on closeability and a 3 on value is not a 14, it's a marginal lead, because the weak links cap the whole thing. The additive 100-point model is easier to run on a porch, but keep the chain logic in mind when a single sky-high factor tempts you to jump a lead up the list.

Building your scoring rubric: a worked model

Keep the math simple enough that a salesperson can do it on a porch. A 100-point scale split across the three factors works well. Here is a model you can copy and tune to your market.

Damage probability (0 to 50 points)

This carries the most weight because everything downstream depends on real damage existing. Build it from signals you can know BEFORE you climb a ladder.

Closeability (0 to 30 points)

Value and effort (0 to 20 points)

Add the three sections. A roof at 80+ is a drop-everything lead. A 60-to-79 is a strong same-week target. A 40-to-59 goes in the second wave. Below 40 gets a phone screen or a polite decline. The exact cutoffs are yours to set based on crew capacity, but the principle holds: sort descending, work top-down, and re-score as new information arrives.

A worked example

Three leads come in within the same hour. Without scoring, you'd probably knock them in the order they called. With scoring:

• 123 Oak St. 21-year-old three-tab roof, dead center of the confirmed 2-inch hail core, owner-occupied, retired couple both home, simple one-story gable, three doors down from a job you already signed. Damage 45, Close 28, Value 16. Total 89. This is the first knock of the day.
• 88 Ridgeline Dr. 6-year-old architectural roof, edge of the swath where reports show pea-to-dime hail, owner-occupied, steep two-story with a turret, isolated 35 minutes from your cluster. Damage 14, Close 22, Value 4. Total 40. Second wave at best; the roof probably shrugged off small hail.
• 2200 Park Ave. Age unknown, mid-swath, but it's a rental and the tenant answered, owner lives out of state, large but cut-up roof. Damage 30, Close 9, Value 8. Total 47. Worth a call to the owner before you ever send a truck.

The loud lead isn't always the smart lead. Oak St. might have been the one that called once and waited politely while Park Ave. called four times. Scoring fixes that.

Tuning the weights to your market

The weights above are a starting point, not gospel. Markets differ, and a smart manager adjusts. A few examples of when to retune:

• A market full of new construction. If you work a metro where most homes are under 12 years old, roof age stops discriminating between leads because almost everything is young. Lean harder on core position and material vulnerability instead, and widen the points spread on those signals.
• A market with heavy investor ownership. In areas with a lot of rentals and out-of-state owners, closeability becomes the factor that separates winners from time-sinks. Bump the owner-occupied points and add a hard penalty for any address where you can't quickly identify and reach the decision-maker.
• A crew-constrained shop. If you have plenty of leads but only two installation crews, value and effort matters more, because you want to fill limited crew days with the most profitable, least-complex jobs. Raise the weight on job value and the complexity penalty.
• A talent-rich, crew-rich shop. If you can install everything you sign, push the weight back toward damage probability, because your bottleneck is finding real damage fast, not building it.

Write your weights down, use them for a full event, then review the outcome data and adjust for the next storm. The worst thing you can do is change the rubric mid-surge based on a gut feeling; that just reintroduces the chaos the system exists to kill.

Reading the storm itself: where damage actually lands

A scoring rubric is only as good as the damage-probability inputs feeding it. Most contractors guess at this, and guessing is why so many inspections come back clean. Hail and wind damage are not random and they are not evenly spread across a "storm-affected" zip code. They follow physics you can read.

Hail is about energy, and energy is about size and density

Damage to a shingle is a function of impact energy, which scales sharply with hailstone diameter. Dime-size hail rarely does actionable damage to a sound roof. Quarter-size starts to mark aged or brittle shingles. Golf-ball and larger bruises and fractures even newer roofs. Because energy rises with the cube of diameter, the difference between 1-inch and 2-inch hail is not double, it's roughly eightfold in destructive potential. That is why the core of a swath matters so much more than the fringe.

The National Weather Service and the Storm Prediction Center publish storm reports and radar-derived hail estimates that let you map the core versus the edge. Insurance and weather-verification services do the same at finer resolution. The practical takeaway: a lead's address relative to the verified hail core is one of the strongest predictors you have, and it's knowable before anyone climbs a ladder.

Wind damage follows exposure as much as speed

Wind doesn't lift shingles uniformly. It peels them along specific paths: windward eaves, rakes, ridges, and any spot where the seal strip already failed from age or heat. Corner and edge zones of a roof see the highest uplift pressures. A roof that's losing tabs on the southwest-facing slope after a straight-line wind event is showing you exactly where to look, and a roof that's tight on the exposed slope probably came through fine. Age compounds this: thermally aged sealant lets go at lower wind speeds, so an old roof and a young roof in the same gust can have completely different outcomes.

Why two roofs on the same street differ

New salespeople assume that if one house on a block got hit, they all did. Not so. On the same street you'll find:

• A 20-year-old roof with bruising and a 4-year-old impact-rated roof next door with nothing, same hail.
• One roof shielded by a large oak that took half the impacts, and its neighbor in the open that took the full load.
• Different slope orientations catching different hail angles, so the back of one house is hammered and the front looks clean.

This is the whole reason house-by-house targeting beats zip-code canvassing. The storm picked winners and losers down to the parcel, and the contractors who can see that pattern before knocking waste far fewer inspections.

The aging-out roofs hiding inside the storm list

There's a second opportunity buried in every storm list that most crews miss entirely: the roofs that didn't take much storm damage but are simply at the end of their service life. A 23-year-old three-tab roof that caught only moderate hail may still be a sale, because it was going to need replacement within a year or two regardless. The storm is the conversation-starter; the age is the real driver.

This is why roof age earns its own line in the damage-probability score even before you account for the storm. Two roofs can sit at the same point in the swath and represent completely different opportunities: the 5-year-old roof is a probable pass, the 22-year-old roof is worth a careful look even on moderate exposure. The contractors who think only about "storm damage" walk past half their addressable market. The ones who think about "which roofs are due, storm or no storm" capture both the storm-hit and the aging-out roofs in a single canvassing pass, which is far more efficient than canvassing the same neighborhood twice.

The practical move is to keep two flags on every lead: a storm-exposure read and a roof-age read. A high-exposure young roof and a low-exposure old roof can both be strong leads, but they're different conversations, and your salespeople should know which one they're walking into before they knock.

Using per-roof intelligence to rank a flooded pipeline

This is where the manual rubric hits a wall. Scoring three leads by hand on a porch is easy. Scoring 380 leads by 9 a.m. so your crews can roll is not. And the single hardest input to fill in by hand, roof age, is usually unknown until someone is standing on the roof, which is exactly the inspection you were trying to avoid wasting.

This is the gap RoofPredict is built for. It works the two hardest columns of your rubric at the scale a storm demands: it estimates a roof-age RANGE per address from aerial imagery, and it models the storm's physics per roof rather than per zip code, so a flooded list comes back ranked by which roofs are most likely due. Instead of a salesperson guessing whether 123 Oak is 8 years old or 21, you start the day with an age band on every address and a per-roof read on how hard the storm actually hit that parcel. The two columns that drive most of your damage-probability score get filled in before anyone leaves the office.

What that changes operationally:

• You sequence the whole list, not a sample. Sort 380 addresses by roof-due likelihood plus storm exposure and the first 40 knocks of the day pick themselves.
• You separate "old and aging out" from "young but storm-hit." Both are real opportunities, but they're different conversations and different routes. Seeing the age band lets you assign them deliberately.
• Your green salespeople knock like veterans. The instinct that takes years to build, knowing which roof on the block is worth the ladder, is partly handed to them in the morning briefing.

Now the honest limits, because this matters more than the pitch. An age RANGE is a range, not a birth certificate, and you confirm the actual condition on the roof, every time. Storm modeling gives you odds, not proof: it tells you which roofs the storm most likely wore out, and it never establishes that a given roof IS damaged or that any claim will be covered. The inspection still rules. What the data does is fix the ORDER you inspect in, so your ladder time lands on the roofs most likely to reward it. It ranks doors; it doesn't sign them. Treat it as the smartest possible starting sort, then let your inspector and the homeowner's insurer do their jobs.

Use it to decide where the trucks go first. Do not use it as evidence of damage, do not show a homeowner a forecast and call it a finding, and do not let anyone on your team turn an age band into a sales claim. The roof tells the truth; the data just gets you to the right roof faster.

The 48-hour mobilization playbook

The first 48 hours after a big event decide the season. Here is a sequence that keeps a flooded pipeline from turning into chaos.

Hour 0 to 6: lock the map

1. Pull the verified hail swath and wind reports for the event. Mark the core, the moderate band, and the fringe. Everything you do is layered on this map.
2. Define your service polygon. Do not chase the whole metro. Draw the area where you can realistically run routes without crews spending half the day driving.
3. Stand up a single intake system. One inbox, one form, one spreadsheet or CRM that every lead flows into. Leads scattered across texts, voicemails, and yard-sign call-ins are leads you will lose.

Hour 6 to 18: score and sort

1. Score every lead on the three-factor rubric. If you have per-roof age and exposure data, load it now so age and core-position are populated automatically.
2. Sort descending. Tier into Drop-Everything (80+), Same-Week (60 to 79), Second-Wave (40 to 59), and Screen-or-Decline (under 40).
3. Cluster the top two tiers geographically. The output is route packets, not a flat list.

Hour 18 to 48: deploy and measure

1. Assign your strongest closers to the Drop-Everything tier. Do not let your best inspector spend Saturday on second-wave roofs.
2. Run tight routes. A salesperson working a dense cluster can inspect far more roofs per day than one crisscrossing the metro.
3. Track outcomes per lead from the first knock: inspected, damage found, signed, declined, no-contact. You'll re-score off this within days.

The most common failure here is skipping straight to step 7 without doing 1 through 6. Crews that "just start knocking" feel productive and are actually running the least efficient possible search of the storm.

Who owns the sort

Triage breaks down when nobody owns it. During a surge, one person, usually the sales manager or a dedicated lead coordinator, has to own the scored list and the route packets. Salespeople do not get to cherry-pick from the master list, because the moment they do, everyone gravitates to the easy, convenient, or loud leads and the discipline collapses.

A clean division of labor during a surge looks like this:

• The coordinator runs intake, scores leads, builds the daily route packets, and tracks outcomes. This is a full-time job during a big event; trying to bolt it onto a salesperson's plate guarantees the sort slips.
• The salespeople work the packets they're handed, log every outcome honestly, and feed new information back so leads can be re-scored. They don't reorder their own day around personal convenience.
• The owner sets the capacity ceiling and the score cutoff, and makes the call on when to stop taking leads or shrink the service area.

This separation matters because the incentives pull against it. A salesperson paid on commission naturally wants to knock the easiest close, not the highest-value roof for the company. Centralizing the sort with someone whose job is throughput, not their own commission, keeps the whole operation pointed at the roofs that matter. Without that ownership, you have a rubric on paper and chaos in the field.

Routing: turning a sorted list into a day plan

A sorted list is not a route. The difference between a good day and a wasted one is often just geography. Two salespeople with identical lead quality will have wildly different inspection counts if one is clustered and one is scattered.

Think in terms of inspections-per-day as your core productivity metric. Drive time is the enemy. A few rules that consistently raise the number:

• Cluster before you sequence. Group the top-tier leads into geographic pods of 8 to 15 addresses each. Assign one pod per salesperson per day. Within a pod, the order barely matters because everything's close.
• Anchor on signed jobs. When you already have a build going on a street, every lead within a few blocks gets a routing bonus. Social proof is real: a dumpster and a crew on the roof three doors down is your best closing tool, and the drive is free.
• Batch the fringe. Low-score, far-flung leads shouldn't pull a salesperson out of a hot cluster. Pool them and run a single "fringe sweep" day, or handle them by phone first.
• Re-cluster daily. As leads convert and new ones arrive, yesterday's pods are stale. Rebuild the route packets each morning off the current scores.

A worked comparison makes the point. Salesperson A works a flat list in arrival order: 11 stops across 38 miles, 6 inspections completed, 2 contracts. Salesperson B works a clustered pod: 14 stops across 9 miles, 11 inspections completed, 4 contracts. Same lead quality, same hours, double the output. The only variable was routing discipline.

Handling the no-contacts without losing them

A big chunk of any storm list is people who weren't home, didn't answer, or asked you to come back. These no-contacts quietly drain a pipeline if you don't have a rule for them. The temptation is to keep circling back to the same empty house, which burns drive time for nothing.

Set a fixed re-touch cadence and stick to it. A workable default: one knock, one door-hanger with a clear callback path, one phone follow-up within 24 hours, and one final knock timed for a different part of the day. If all four miss, the lead drops to a low-priority pool that gets a single phone sweep later, not repeated truck rolls. The point is to cap the effort per no-contact so a salesperson never spends a third of the day chasing ghosts while scored, reachable leads sit in the queue.

The re-touch rule also protects you from the opposite failure: giving up too early on a high-score roof. A 22-year-old roof dead in the core is worth four touches; a 6-year-old fringe roof is worth one. Tie the re-touch budget to the lead score, and your follow-up effort automatically flows to the roofs that deserve it.

Tracking the metrics that tell you the system is working

You can't improve a triage system you don't measure. Three numbers tell you whether your prioritization is paying off, and you should review them every few days during a surge:

• Damage-found rate. Of the roofs you inspected, what share had actionable damage? If this is low, your damage-probability scoring is off, you're climbing too many clean roofs, and you should tighten the core-position and age inputs feeding your sort.
• Inspections per rep per day. This is your routing health. If it's sliding, your clusters are too loose or your reps are chasing no-contacts. A clustered pod should comfortably beat a scattered list.
• Close rate on inspected, damaged roofs. This is your sales execution, separate from your targeting. If you're finding damage but not signing, the problem is the pitch or the documentation, not the prioritization.

Keeping these three separate is what lets you diagnose a bad week. A shop that only watches "contracts signed" can't tell whether a slump came from bad targeting, bad routing, or bad closing. Split the funnel and the fix becomes obvious.

Two leads, side by side: what triage looks like in practice

Consider how a disciplined shop and a chaotic one handle the same two leads on the same morning.

Lead 1: 19-year-old roof, dead center of a confirmed 1.75-inch hail core, owner-occupied, retired homeowner home all day, one-story walkable roof, sits inside a cluster of four other live leads.

Lead 2: roof age unknown, fringe of the swath where reports show dime hail, it's a rental with an out-of-state owner, three stories and steep, 30 minutes from anything else you're working.

The chaotic shop knocks Lead 2 first because the tenant called twice and sounded upset. The salesperson drives 30 minutes, can't reach the actual decision-maker, climbs a steep roof that took small hail, finds nothing actionable, drives 30 minutes back, and has burned a morning. Lead 1 sits until afternoon, by which point a competitor's crew has already signed two roofs on that cluster's street.

The disciplined shop scores both at intake. Lead 1 lands around 86, Lead 2 around 38. The salesperson spends the morning in the high-confidence cluster, inspects five roofs, signs two off the social proof of the neighbor's job, and the upset tenant at Lead 2 gets a phone call that surfaces the out-of-state-owner problem before any truck moves. Same two leads, completely different days.

What pros get wrong about prioritization

Even experienced storm shops make the same handful of mistakes when the volume spikes. Knowing them is half the cure.

Mistake 1: confusing urgency with priority

The loudest lead is rarely the best lead. A homeowner who calls five times might have a tiny one-story roof on the fringe with no real damage. Urgency from the customer is a closeability signal, worth a few points, but it does not override damage probability or value. Sort on the score, not the volume of the complaint.

Mistake 2: canvassing by zip code instead of by roof

"The whole 75002 got hit" is how you waste a week. The storm hit specific parcels, and within an affected area the difference between a 20-year-old roof and a 5-year-old roof is enormous. House-by-house targeting beats area canvassing because it concentrates ladder time where damage actually is.

Mistake 3: putting your best closer on easy roofs

There's a temptation to send your A-player to the slam-dunk obvious-damage roofs. But those close themselves; even a rookie signs a roof with a dumpster next door and a leaking ceiling. Your best people earn their keep on the 60-to-79 roofs where the damage is real but the homeowner needs convincing. Deploy talent where it changes outcomes.

Mistake 4: never declining anything

A team that takes every lead is a team that never gets to the good ones. Saying no, or "we'll call you," to sub-40 leads is not lost revenue; it's protected capacity. The opportunity cost of a wasted inspection is the high-confidence roof you didn't reach that day.

Mistake 5: scoring once and never re-scoring

A lead's score is a snapshot. New information, the neighbor just got approved, the homeowner finally answered, a competitor's sign went up, should move it. Re-score the active pipeline every morning. A lead that was a 45 yesterday might be a 70 today because the block just turned hot.

Mistake 6: letting documentation lag behind signing

In the rush to sign, crews fall behind on photo documentation and scope. Inconsistent documentation slows everything downstream and creates disputes. Build documentation into the inspection itself, not as an afterthought, so every signed roof has a clean, consistent condition record from day one.

Staying on the right side of the rules

Moving fast in a storm market is no excuse for cutting ethical or legal corners, and the contractors who do tend to get found out. A few guardrails that protect your license and your reputation:

• Document conditions and provide estimates; don't adjust claims. The roofer's job is to inspect, photograph, and scope honestly, and to give the homeowner an estimate. The insurer decides coverage. The homeowner owns the claim. Stepping into the insurer's role is how contractors run afoul of public-adjusting rules. Several states regulate this tightly; know your state's department of insurance position before your team talks claims.
• Never promise a covered claim or a no-cost roof. You can't know how an insurer will rule, and "free roof" pitches draw regulatory scrutiny and erode trust. Document what you see; let the process play out.
• Don't pay or rebate deductibles. Waiving or covering a homeowner's deductible is illegal in many states and is a fast way to lose your license.
• Keep storm data as targeting, not proof. Radar maps, hail estimates, and roof-age ranges tell you where to look. They are odds and ranges, not findings. The on-roof inspection establishes actual condition. Never present a forecast or an age band to a homeowner as evidence their roof is damaged.
• Mind solicitation and contract rules. Many jurisdictions have door-to-door solicitation registration, right-of-rescission windows, and storm-specific contract requirements. Train your canvassers on them before they knock.

Fast and clean is the only combination that survives a full season. Fast and sloppy gets you callbacks, complaints, and in the worst case, a regulator's attention.

A copy-ready triage checklist

Print this. Tape it to the wall of the war room. Run it every morning of the surge.

Setup (once per event)

• Verified hail/wind map pulled, core and fringe marked
• Service polygon drawn; out-of-range leads flagged
• Single intake system live; all channels funnel into it
• Scoring rubric printed and shared with every salesperson
• Per-roof age and exposure data loaded if available

Daily (every morning of the surge)

• Score every new lead on the three factors
• Re-score active pipeline for new information
• Sort descending; tier into Drop-Everything / Same-Week / Second-Wave / Screen-or-Decline
• Cluster top two tiers into geographic pods of 8 to 15
• Assign best closers to Drop-Everything tier
• Anchor routes on streets with signed jobs
• Pool fringe leads for a phone screen or sweep day

Per lead (every knock)

• Confirm actual roof condition on the roof; never rely on the age range alone
• Document conditions consistently with photos
• Log outcome: inspected / damage found / signed / declined / no-contact
• If declined or no-contact, set the re-touch rule before leaving

Guardrails (always)

• No covered-claim promises, no free-roof pitches, no deductible rebates
• Storm data used as targeting only, never as proof of damage
• State solicitation, rescission, and claims rules followed

Capacity math: knowing when to stop taking leads

The last piece of triage is the one nobody likes: deciding when your pipeline is full. More leads past your capacity ceiling don't add revenue, they dilute attention and slow your response to the good ones.

Do the arithmetic. If you have four salespeople, each can complete roughly 8 to 12 quality inspections a day in a tight cluster, and the surge window is realistically two to three weeks before urgency fades, your total inspection capacity is bounded. Suppose that's 4 reps times 10 inspections times 15 working days, or about 600 inspections across the surge. If your close rate on well-qualified roofs is 30 to 40 percent, you can productively work maybe 600 high-and-medium-confidence leads, not 1,200.

Once your scored pipeline of 60+ leads exceeds what your capacity can touch while urgency is hot, taking on more low-score leads is actively harmful. Better moves at that point:

• Tighten the score cutoff and let the bottom tier go.
• Add inspector capacity only if you can do it without dropping documentation quality.
• Shrink the service polygon to raise route density and inspections-per-day.

Discipline about capacity is what separates a profitable storm from a stretched, sloppy one. The shop that works 500 well-chosen roofs cleanly beats the shop that half-works 900.

Putting it together

A flood of storm leads is a sorting problem wearing the costume of an abundance problem. The contractors who win big events aren't the ones with the longest lists. They're the ones who decided, deliberately and every single morning, which roofs to knock first based on three honest numbers: how likely the roof took real damage, how likely the homeowner will move forward, and how much the job is worth relative to the effort to reach it.

Build the rubric. Read the storm by physics, not by zip code. Cluster your routes so ladder time isn't lost to drive time. Put your best people on the roofs where they change the outcome. Re-score every morning, document every inspection, and have the discipline to decline the bottom of the list so you can reach the top of it while the storm is still fresh.

The order you work your leads is the most important decision you'll make all season. Per-roof intelligence, which roofs are aging out and which the storm most likely wore out, gets you to the right starting sort faster than instinct alone, especially when your list is 400 deep by Tuesday. RoofPredict exists to hand you that sort. The roof still tells the truth, and your inspector still confirms it. The data just makes sure the truck shows up at the right roof first.

FAQ

How do I prioritize storm leads when I have too many to handle?

Score each lead on three numbers: damage probability (roof age plus position in the verified hail or wind core), closeability (owner-occupied, decision-maker present, active policy), and value-versus-effort (job size, roof complexity, route density). Sort the whole list descending and work top-down, putting your best inspectors on the highest-scoring roofs while the storm is still fresh. Ignore how loud or how recent a lead is; those signals don't predict revenue. Decline or phone-screen the bottom tier so your capacity goes to the roofs most likely to convert.

What's the single biggest mistake roofers make with a flood of storm leads?

Working them in arrival order or by how loud the homeowner is, instead of by damage probability. The customer who calls five times often has a young roof on the fringe of the swath with no real damage, while the high-confidence roof inside the core sits unknocked until a competitor signs it. Urgency from the customer is a minor closeability signal; it should never override damage odds or job value in your sort.

Why is canvassing by zip code a bad idea after a storm?

Hail and wind don't hit a zip code evenly. On the same street you'll find a 20-year-old roof with bruising next to a 5-year-old impact-rated roof with nothing, plus differences from tree cover and slope orientation. Damage follows physics down to the individual parcel, so house-by-house targeting concentrates your ladder time where damage actually is and dramatically cuts wasted inspections compared to blanketing an area.

How does roof age affect which leads I should prioritize?

Older roofs bruise, crack, and lose seal strips at far lower impact energy and wind speed than newer roofs. A roof in the 18-to-25-year band is much more likely to show actionable damage from the same hail than a 5-year-old roof, so age is one of your strongest damage-probability inputs. The challenge is that age is usually unknown until someone climbs the roof, which is why aerial roof-age estimates that give you an age range per address before you inspect are so useful for sorting a large list.

How can I estimate damage probability before climbing the roof?

Combine four ground-knowable signals: position in the verified hail or wind core (from radar-derived maps and storm reports, not the homeowner's guess), roof age, roof material vulnerability, and corroborating evidence like damaged gutters, vents, AC fins, or an already-approved neighbor. None of these prove damage; they estimate the odds so you inspect the most promising roofs first. The on-roof inspection still establishes actual condition every time.

What does RoofPredict do and what are its limits?

RoofPredict ranks a flooded lead list by which roofs are most likely due. It estimates a roof-age range per address from aerial imagery and models the storm's physics per roof rather than per zip code, filling in the two hardest columns of your scoring rubric before anyone leaves the office. Its honest limits matter: an age range is a range, not an exact date, and the storm model gives odds, not proof. It tells you which roofs the storm most likely wore out and where to send trucks first; it never establishes that a specific roof is damaged or that any claim will be covered. Your inspector confirms condition on the roof, every time.

How many storm leads can one salesperson actually work in a day?

In a tight geographic cluster, a salesperson can typically complete 8 to 12 quality inspections a day. Scattered across a metro in arrival order, that number can drop to 5 or 6 because drive time eats the day. Routing discipline, grouping top-tier leads into pods of 8 to 15 addresses and anchoring on streets where you already have signed jobs, is often the difference between single-digit and double-digit inspections per rep per day.

When should I stop taking new storm leads?

When your scored pipeline of high- and medium-confidence leads (roughly 60-plus on a 100-point rubric) exceeds what your crews can inspect while storm urgency is still hot, usually a two-to-three-week window. Past that point, adding low-score leads dilutes attention and slows your response to the good ones. Better moves are to tighten your score cutoff, shrink your service area to raise route density, or add inspector capacity only if documentation quality holds.

Can I show a homeowner a hail map or roof-age data as proof their roof is damaged?

No. Radar maps, hail estimates, and roof-age ranges are targeting tools that tell you where to look. They are odds and ranges, not findings. Presenting a forecast or an age band to a homeowner as evidence of damage misrepresents what the data shows and can create legal exposure. The on-roof inspection establishes actual condition, and that is what you document and discuss with the homeowner.

How do I prioritize leads ethically without making claims promises?

Keep your role to documenting conditions, photographing honestly, and providing an estimate; the insurer decides coverage and the homeowner owns the claim. Never promise a covered claim or a no-cost roof, and never pay or rebate a deductible, which is illegal in many states. Use storm data to decide which roofs to inspect first, not as proof of damage, and follow your state's solicitation, right-of-rescission, and public-adjusting rules. Prioritization is about the order you inspect, never about overpromising outcomes.