Built on public data, honest by construction.
Hail Trigger is the productized version of a storm-response system built from a real North Phoenix roofing workflow. We turn a radar-estimated hail footprint into the parcels it intersects — and a measurable campaign.
- Public sources
- Re-runnable
- Citable
- Operator-built
Storm response was a guessing game.
Roofing crews chase hail blind. Bought leads are weeks late and resold to five competitors. Door-knockers canvass whole ZIPs hoping they're inside the hit area. And "within ten miles of a hail report" is not the same as "the hail hit this roof."
We built the system for a real operator first — to run actual campaigns on actual storms — then productized it.
Built operator-first
- Run on real storms, not demos.
- Backed by live recon runs.
- Every claim traces to a deployment.
The sources we actually use.
Public, re-runnable, and citable. Every campaign includes an auditable source trail — an operator can show their work to an insurer or an attorney general.
NOAA MRMS / NEXRAD
Decoded hail-swath polygons — the maximum-estimated-hail-size footprint, in inches.
County assessor records
Property geometry and roof / structure attributes, per parcel.
Municipal permit data
Repair-permit history — a signal of whether a roof has already been fixed.
NOAA Storm Events
Re-runnable storm records so an operator can show their work.
Targeting evidence, not a damage finding.
HailTrigger shows when a verified storm path includes an address. It stops short of calling the roof damaged — the inspection still does that job. That restraint is the feature.
We surface
- The estimated hail size over the parcel
- Whether the radar-estimated footprint contained the parcel
- Roof age and missing repair permits
We don't claim
- That the roof is damaged
- An insurance outcome
- Anything an inspection hasn't confirmed
Want the methodology end to end?
Read how storm-response lead generation works, or request a pilot so we can prioritize your market.