← Back to data productsStorm-watch pings

Re-engage every lead the moment a storm hits.

Every address you enrich is auto-watched for 24 months. When NOAA flags a qualifying storm (≥1" hail, ≥60 mph wind, EF1+ tornado, or hurricane warning) we ping your webhook within minutes. The lead you sold 8 months ago becomes urgent again. Free with every enrichment.

Address you already enrichedDay 0 - sold to roofer
5701 W Loma Ln, Glendale AZ
Day 247 · 1.75" hail · NOAA
Webhook fires
POST your-webhook.com
{ "event": "storm.ping",
"address": "5701 W Loma Ln",
"hail_size": "1.75in",
"auto_claim_eligible": true,
"original_lead_id": "lead-9821" }
24 mo
free watch per address
≥1″
hail auto-claim threshold
< 5 min
from NOAA event to ping
$0
extra cost (included)

How it fits in

Day-to-day workflows our data slots into.

Lead-vendor re-sell

A lead you sold 3 months ago just had 1.5" hail. Webhook fires; you forward the alert to the roofer who bought it. They call the homeowner: "saw the storm hit, want me to check the roof?" Lead converts on the second touch, no new acquisition cost.

Solar installer re-pitch

Solar lead postponed because the roof was borderline-aged? Storm event accelerates the timeline. Webhook tells you the roof now needs replacement first → re-engage with a roof-then-solar bundle proposal. Higher close, bigger ticket.

Insurance restoration network

Your restoration contractors prospect storm-hit areas door-to-door today. Storm-watch points them at addresses where you already have the roof + property data, they call instead of canvassing. 10x dispatch efficiency.

Portfolio monitoring

Property managers, iBuyers, and insurance carriers upload address lists at signup. Every property in the portfolio gets storm-watched on the same terms. One central alert feed.

Auto-claim-eligible filter

We only ping on storms severe enough to trigger automatic insurance-claim approval: ≥1" hail, ≥60 mph wind, EF1+ tornado, hurricane warning. Every ping carries the implicit promise: "this homeowner has a real shot at a claim." High-signal, never noise.

Configurable thresholds

Defaults are insurance-grade. Enterprise customers tune higher (≥1.5" hail premium-only) or lower (≥0.75" for marketing-driven outreach). Per-customer, per-address-list overrides.

Without storm-watch vs. with

Storm pings turn one-time lead sales into 24 months of recurring revenue opportunities.

Capability
What happens after you sell a lead
Today (most vendors)It goes cold. You move on.
With RoofTap storm-watchIt's watched 24 mo. You get pinged when it heats back up.
Storm-event awareness
Today (most vendors)Roofer/installer hears from local news, days late
With RoofTap storm-watchWebhook within minutes of NOAA event publication
Geographic precision
Today (most vendors)ZIP-level coverage (half the ZIP missed the storm)
With RoofTap storm-watchProperty-level hit/miss via MRMS hail-swath polygons (~1km)
Trigger threshold
Today (most vendors)Every weather event → notification fatigue
With RoofTap storm-watchOnly storms severe enough to auto-trigger insurance claims
Repeat revenue per lead
Today (most vendors)None, single-sale only
With RoofTap storm-watchRe-sell to the same buyer or re-pitch with bigger bundle
Storage / setup
Today (most vendors)You'd need to build it from NOAA + a property DB
With RoofTap storm-watchFree, automatic, on every address you enrich
Per-ping cost
Today (most vendors)n/a
With RoofTap storm-watch$0. Included with enrichment. No metering.

Fields you'll use most

From the full API response, these are the fields this industry leans on.

FieldWhat you do with it
event_typehail | wind | tornado | hurricane. Drives downstream routing logic.
event_dateISO timestamp of the storm. Starts the homeowner's insurance-claim window.
hail_size_inchesLargest reported hail diameter. ≥1" damage-likely; ≥1.25" insurance auto-claim territory.
wind_speed_mphPeak measured wind. ≥60 mph triggers shingle uplift claim consideration.
auto_claim_eligibleBoolean, true if the event severity meets standard insurance auto-claim thresholds.
claim_window_expiresDate by which the homeowner must file (typically event + 24 months). Lets your buyer urgency-tier their outreach.
addressProperty at risk. Same address you originally enriched.
original_lead_idYour own ID from the original enrichment call. Lets you join back to the lead in your CRM.
noaa_event_idSource NOAA event identifier, auditable trail for downstream insurance claims.
swath_distance_metersHow deep into the storm swath the property sits. 0 = direct hit; ≥500 = edge of swath.

From signup to live

Typical timeline from first call to your first enriched record.

01

Enrich at lead intake

First /v1/enrich call attaches address to the storm-watch list automatically. No extra parameter needed.

02

Configure your webhook URL

One-time setup in the dashboard: paste your endpoint URL + select trigger thresholds. We'll send a test ping immediately.

03

Watch period: 24 months

Every address is monitored against NOAA storm-event feeds + MRMS radar swath polygons. ~1km precision, far tighter than ZIP-level.

04

Ping fires on qualifying event

Within 5 min of NOAA publication. Webhook POSTs the structured payload to your endpoint with HMAC signature for verification.

05

You re-engage the buyer

Forward the alert to the roofer/installer/restorer who bought the original lead. They call the homeowner. Lead converts on the second touch.

Common questions

Is this really free?

Yes. Storm-watch is included with every enrichment call, 24 months per address, no per-ping fee. We considered metering ping volume but most addresses never see a qualifying event, the math works better as an attached benefit that retains customers.

Why ≥1" hail and ≥60 mph wind specifically?

These are the standard thresholds at which most homeowner insurance policies auto-approve claim inspections. We default conservative so every ping carries the implicit message "this homeowner can probably file a claim." Tune higher or lower at Enterprise tier.

How do you handle properties on the edge of a storm?

We use NOAA MRMS hail-swath polygons (~1km resolution), actual property-level hit/miss, not ZIP-level radius. The swath_distance_meters field tells you how deep into the storm the property sits. Edge properties (≥500m from centroid) are still pinged but flagged as marginal.

What if my buyer doesn't want to be re-contacted?

Pings go to your webhook, not direct to homeowners. You decide who gets re-engaged and how. Use your existing opt-out logic + DNC lists.

Can I subscribe addresses I never enriched?

Yes, bulk storm-watch upload at Enterprise tier. Insurance carriers, property managers, and large contractors upload an address list at signup and get the same watch coverage. Pricing: $0.05/address/mo at 1k-10k; $0.03/address/mo at 10k+.

Do you compare pre- and post-storm imagery?

No. We notify on the event; we don't confirm damage. The honest framing: every ping is "worth a call to investigate," not "damage confirmed." Pair us with a damage-detection vendor (ZestyAI, Cape Analytics) if you need imagery comparison.

How fast is the ping?

Within 5 minutes of NOAA publication. NOAA's MRMS radar updates every 2-5 min during active events; our cron checks every minute and matches against your watch list.

One rate. Volume discounts apply automatically.

Once monthly volume crosses a threshold, the lower rate applies to every call that period. No retro-active surprises on the next invoice.

$3.95
0 – 5,000 / mo
$3.25
5,001 – 15,000 / mo
$2.45
15,001 – 30,000 / mo
$1.95
30,000+ / mo

Bad reads return billable: false and never bill. Enterprise (30k+/mo) gets negotiated rates and dedicated support, talk to us.

One sale. Twenty-four months of opportunity.

Storm-watch turns single-touch lead sales into a recurring revenue surface. Free, automatic, and built on the same NOAA + radar data underwriters use to validate claims.

Tell us what you're building

We'll review your use case, answer questions, and get you set up if it's a fit.

Goes straight to ben@rooftap.app. We'll never share your contact info.