HailTrace Pricing Explained: What Storm Mapping Costs

The bill you get from a storm-mapping tool is not the bill you think you're getting

A roofer pulls up a hail swath the morning after a storm, sees a purple blob sitting over three suburbs, and feels like he's already won. Then he spends four days knocking doors in that blob and finds out two thirds of the roofs are already new, a quarter are tile shops he doesn't work, and the rest are rentals with absentee owners.

The swath was right. The storm did hit there. The problem is that a swath is a weather product, not a door list, and no amount of zooming turns one into the other.

If you're searching "HailTrace pricing," you're probably trying to work out whether a storm-mapping subscription is worth it before storm season. Here's the honest answer: what shape the bill takes, what these tools genuinely do better than anything else, and the specific gap they leave that you still have to fill yourself.

What storm-mapping subscriptions are actually priced on

Start with the thing nobody tells you up front: these vendors mostly do not publish a rate card. HailTrace included. As of writing, pricing is quoted per territory over a phone call, which means the number you pay depends on what you tell them about your operation and where you work.

That's not a knock. It's just how the category sells. But it means any "HailTrace costs $X per month" figure you read online is either somebody's quote from a specific territory at a specific time, or it's invented. Treat it that way.

What the reported quotes cluster around, based on what roofers say publicly and what vendors in this space generally charge on, comes down to four variables:

1. Territory size. Almost every storm-mapping subscription is priced by the geography you want covered. One metro, a multi-state footprint, or national coverage are three different products with three different numbers. This is the single biggest lever.
2. Seats. How many people on your team log in. Some plans include a handful of users, some charge per seat, some are effectively one-login tools.
3. Data depth and history. A tool that shows you last night's hail swath is cheaper than one that keeps a searchable archive of every hail event by date, size and location going back years. If you work insurance claims, the archive is the product.
4. Adjacent features. Property data overlays, storm-date reports you can hand to a homeowner, alerts when a new event fires in your saved territory, CRM or canvassing integrations. Each one moves the number.

The shape of the bill, then, is a subscription for access to weather intelligence over a defined area. Flat, recurring, and paid whether or not a single door in your territory is worth knocking that month. In a quiet season you're paying for the privilege of knowing nothing happened.

What these tools are genuinely excellent at

I'm not going to pretend storm mapping is overrated. It isn't. If you run storm work, a hail-swath tool does two things better than anything else on the market.

It tells you where hail fell, fast. Within hours of an event, you can see the swath, the reported stone size, and the date. That's a real edge over waiting for the phone to ring. Storm work is a race, and being first into a neighbourhood matters.

It gives you a defensible record of the event. When you're sitting across from a homeowner explaining why their roof is a claim and not a retail job, a dated hail report for their address is a useful document. It's the difference between "I think it hailed here" and "here's the event, here's the date, here's the size."

It scales across a wide geography. If you cover three states, no human can track storm events across all of them. Software can.

So the tool earns its money. The mistake is treating the swath as a work list.

The gap: a swath tells you where hail fell, not which houses are worth a door

Here's the structural problem. A hail swath is drawn at the scale of a weather system. It's a polygon over a map, and everything inside that polygon gets the same answer: hail fell here.

But a street is not uniform. On the same block, under the same swath, on the same storm date, you'll find:

• Four houses that were re-roofed after the last storm and have nothing to claim.
• Three rentals owned by people two states away who won't answer the door.
• Two commercial buildings and a church.
• One house with a tarp already on it.
• And maybe three houses with genuinely storm-damaged, claimable roofs.

A swath cannot tell you which is which, because a swath is not looking at roofs. It's looking at weather. That's the whole gap in one sentence: storm mapping knows the storm, not the house.

The result is the thing every storm chaser knows in his bones. You drive into the blob, you knock forty doors, you get two inspections, and you burn a day. The swath was accurate and the day was still wasted.

What per-roof assessment adds that a swath can't

This is where the two products stop competing and start stacking.

Per-roof assessment reads the actual roof from imagery, top-down and from the street, and scores it. Not the neighbourhood. The house. It can see a tarp, missing shingles, exposed decking, patched sections, rusted flashing, and how the roof compares to the houses either side of it.

Stacked on top of a hail swath, that changes the shape of your morning. Instead of "hail fell across these 4,000 homes," you get "hail fell across these 4,000 homes, and here are the 60 in the swath with visible active damage and a roof old enough to matter."

That's a filter, not a replacement. You still needed the swath to know the storm happened. You needed the per-roof read to know which doors to walk.

One more thing worth being precise about, because it's the opposite of how storm lists usually work: neighbourhood hail should not be allowed to inflate urgency on a per-home basis. If every house in the scan shares the same hail event, hail cannot separate one door from the next. It belongs in your pitch, not your ranking. A tool that hands you 400 "high urgency" leads because it rained ice on all of them has told you nothing.

What does separate one door from the next is what's actually on that specific roof: a tarp, missing shingles, exposed decking, a purchase in the last 18 months, patching already attempted, or neighbours who have visibly gone new while this one hasn't. Those are per-house facts. A swath can't produce them.

The payoff: the swath gives you the storm, the roof read gives you the homeowner

Here's the part that actually closes the loop, and it's where most storm workflows fall apart.

You've got a swath over a suburb. You've got 60 houses with visible damage. Now what? You still need to know who lives there, whether they own it, and how to reach them. That's the step where roofers end up buying shared leads from a marketplace, paying per lead for the same name four other contractors got, for a homeowner who filled in a form six months ago.

You don't need that. You need the county record and a DNC-scrubbed phone number.

On every roof scanned, the full property record comes back free: owner name, whether they live there or it's an absentee or rental, estimated market value, year built, last sale date and price, beds and baths, living square footage, lot size, stories, garage, annual property tax, and mortgage lender. Alongside it sits an owner-equity estimate, because equity is what decides whether someone can actually say yes to a $14,000 roof. When the deed record can't support an estimate, it says so instead of guessing.

Only the phone and email sit behind a one-click unlock. Every number is DNC-scrubbed and labelled: clear means it was checked against the federal Do Not Call registry and is safe for a manual sales call, DNC means don't call it, verify means the scrub couldn't confirm either way. Manual dialling only. No texts, no auto-dialler. And a lookup that finds no contact never costs you a credit.

That's the difference between a swath and a work list. The swath told you the storm hit. The per-roof read and the property record tell you which house, which owner, and which number to dial.

How to run the two together

1. Storm fires. Pull the swath first. Confirm the event, the date, the reported size. That's your pitch material and your claim documentation.
2. Before you draw anything, ask which blocks in the swath are worth the trip. Not every block under a swath is worth a morning. Scattered acreage on long driveways is bad canvassing even under a perfect storm, because a morning is measured in doors per hour. You want density, older housing stock, and a high share of roofs that read as weathered.
3. Filter the swath down to homes with a live trigger. Active damage visible, roof old enough to matter, claim window still open. Where a hail event is on record, you can see roughly how long the homeowner has left to file based on the typical notice deadline in that state. That's an estimate of the deadline, not a legal ruling, so verify with the carrier before you say it at a door.
4. Pull the property record and the equity estimate before you knock. An absentee owner with low equity is a different conversation from an owner-occupier who's been in the house 19 years and has paid most of it off. Sort by that.
5. Unlock the contact details and work the list like a CRM. Filter on owner-occupied vs absentee, live trigger, active damage, claim window open, minimum equity, and contact state including callable. Tag, export, print door hangers for the route.
6. Note what you ruled out. Roofs already replaced, the wrong material for your shop, not homes at all. Knowing which quarter of a street is dead is worth as much as knowing which quarter is hot, and it stops you re-walking the same dead block next storm.

The honest cost comparison

A storm-mapping subscription is a flat recurring fee for weather intelligence over a territory. You pay it in quiet months too. It answers "where did it hail." It does not answer "which door."

Roofbird is priced on a single meter: credits. Looking is free and unlimited, including asking questions about the roofs in your area and opening the photographs to answer them. Acting costs. Reading ground nobody has read is 1 credit per 150 roofs. Looking at the photographs from above and from the road is 1 credit per 20 roofs. Property data in bulk before you open anything is 1 credit per 4 roofs. Opening a house completely, with the full roof read, the address, the owner's name and mailing address, occupancy, DNC-flagged numbers, email where one exists, and the whole property record, is 1 credit.

The trial is 10 credits, free, no credit card, no expiry. Hunter is $199/mo for 350 credits, with top-ups at $25 for 37. Hunter Pro is $499/mo for 1,000 credits, with top-ups at $25 for 50. Nothing is gated by plan. The only difference is how many doors a month you can open. Never per lead, and no quota.

Run them together and the arithmetic is simple. The swath tells you a storm happened across 4,000 homes. The per-roof read tells you 60 of them are worth a knock. The property record tells you which of those 60 own the place, have the equity, and have a number you're allowed to call.

FAQ

Q: Does HailTrace publish its pricing? A: As of writing, no. HailTrace and most storm-mapping vendors quote per territory over a sales call rather than publishing a rate card. Any specific monthly figure you see online is either one contractor's quote from one territory or an invention, so treat it as a reported range rather than a fact.

Q: What is a hail-swath subscription actually priced on? A: Reported quotes cluster around four variables: the size of the territory you want covered, how many user seats you need, how much historical storm data you want access to, and which adjacent features you add such as property overlays, storm-date reports, alerts or CRM integrations. Territory size is usually the biggest lever.

Q: Can a hail swath tell me which houses have damage? A: No. A swath is drawn at the scale of a weather system, so every home inside it gets the same answer: hail fell here. It cannot distinguish a re-roofed house from a claimable one, a rental from an owner-occupier, or a home from a church. You need a per-roof read for that.

Q: Should neighbourhood hail raise a lead's urgency score? A: No, and this is where most storm lists go wrong. If every home in the scan shares the same hail event, hail cannot separate one door from the next. It belongs in your pitch, not your ranking. What separates doors is per-house evidence: a tarp, missing shingles, exposed decking, recent patching, or neighbours who have already gone new.

Q: How do I get the homeowner's contact details for a storm-damaged roof? A: The full property record, including owner name, occupancy, value, last sale, taxes and lender, comes back free on every scanned roof. Only the phone and email sit behind a one-click unlock, and every number is DNC-scrubbed and labelled clear, DNC or verify. Manual dialling only. A lookup that finds no contact never costs a credit.

Next steps

If storm season is coming, don't cancel the swath. It's the fastest way to know an event happened and it's your documentation when you sit at a kitchen table.

But stop treating the swath as your door list. Next storm, pull the swath, then ask which blocks inside it are worth your morning and which specific roofs have a live trigger, an owner who lives there, and equity to say yes. Sign up free, get 10 credits with no card, and run one real swath through it before you commit to anything. You'll find out in about twenty minutes whether the gap between "where it hailed" and "who to knock" was costing you a day per storm.