from storm-detected to ads-ready, on autopilot
Annual replacement at parity if you bought the equivalent tools and services separately. Custom-building this one feature alone would land in our Medium build band ($40k–$90k (the ingest + intersection pipeline)). Source ladder + per-line citations on methodology .
Concretely, what you get
- NOAA SPC storm events archive — daily backfill, hourly recent.
- NOAA SPC mesoanalysis + radar — real-time stream.
- weather.gov forecast API — hourly.
- Three-year historical events archive per ZIP, growing daily.
- Per-event severity, duration, ZIP coverage, neighborhood cross-reference.
- Intersection detection against your service-area polygon — in seconds.
- Public-domain data, no per-event fees, no rate-limit surprises.
- Storm Alert Settings inside the Homeowner Portal — homeowners opt in to address-specific alerts; when hail hits, they see your name before they Google "roofer near me" (see Homeowner Portal).
The shelf-of-tools this one offering removes
Categories, not brand names — pricing benchmarks observed from public pricing pages, agency proposals, and freelance rates current to the year. Every range is backed by a line-by-line worksheet you can audit once your trial is live.
| What you'd otherwise buy | Type | Typical price |
|---|---|---|
| A roofing-industry hail map subscription | SaaS | $99–$300/mo |
| A hail-event alerting service | SaaS | $200–$500/mo |
| A weather-API license (commercial grade) | SaaS | $500–$2,000/mo at volume |
What you'd pay elsewhere vs. what this costs you here
Vendor ranges observed from public pricing pages and agency proposals, current to the year. Full source worksheet shared with you once your trial is live.
What it adds to your business in dollars
The roofer who reaches a storm-hit homeowner first wins the job. The NOAA pipeline collapses the lag between event and action from hours to under a minute — and unlike the paid hail-map subscriptions, the data is public-domain, fed directly into every other module that needs it.
Three or four moves. Then you walk away.
You: Draw your service-area polygon at provisioning.
System: NOAA events are intersected with it in real time, forever.
You: Set your alert thresholds.
System: Email + in-portal notifications fire when a qualifying event hits.
The outcomes this feature feeds into
Before you ask
Why NOAA instead of a private weather API?
NOAA SPC is the source the private APIs themselves wrap. Going direct removes the markup, the rate limits, and the third-party dependency. Public-domain data, no per-event fees.
How fast is "real-time"?
NOAA mesoanalysis updates every 15 minutes during active events; we ingest each update inside 60 seconds and intersect against every client polygon in real time.
What thresholds count as a qualifying event?
Defaults: hail ≥ 1.0", wind ≥ 60 mph, tornado warning. Configurable per client — you can set up to 5 named alert rules.
Do you cover Canada / Mexico / international?
V1 covers the contiguous US (where NOAA data exists). Canada and Mexico are V2; international markets are out of scope at launch.
What if NOAA goes down?
The forecast feed (weather.gov) and the storm events feed (SPC) are independent — when one is down, the other carries detection. Both have been remarkably reliable; we’ve seen <2 hours/year of downtime.
See storm, hail, and wind alerts arrive in under sixty seconds — already mapped to your service area.
Then be on the door before the next call.
No credit card. No strings. We stand the whole platform up on a subdomain alongside your existing site so you can compare the numbers directly — leads, bookings, ticket size. The Standard guarantee covers cancellation between day 90 and day 180 at full refund.