Bulk-enrich impacted properties. Dispatch faster than the competition.
When a storm rolls through, your network needs property data on thousands of addresses, fast. Pipe a list in, get enriched data back in minutes. Sort by roof complexity, age, and material so contractors hit the highest-value inspections first while the leads are still warm.
How it fits in
Day-to-day workflows our data slots into.
Bulk address ingest
Upload a CSV of impacted addresses. Get roof + property data appended on every row. Sort, filter, and route to your contractor network in your existing workflow.
Rapid lead routing
Score addresses by roof age, complexity, and owner-occupied status. Push the highest-value prospects to top contractors first while the storm is still trending in the news.
Pre- and post-storm comparison
We capture imagery date on every enrichment. Compare baseline pre-storm reads to current state where insurance carriers need verification.
Storm-track filtering
Combine NWS storm tracks with our enrichment. Only push leads where roof age + storm severity exceed your contractor's interest threshold. Cleaner pipeline, fewer wasted calls.
Insurance-claim assist
When homeowners file claims, give your contractor network roof measurements + age data so they can advocate for full replacement vs partial repair. Higher claim payouts = happier customers.
Fields you'll use most
From the full API response, these are the fields this industry leans on.
| Field | What you do with it |
|---|---|
| roof.area_sqft | Total square footage drives the contractor's bid + the homeowner's expected claim payout. |
| roof.complexity | Cut-up roofs take more labor. Route them to crews that can handle it. |
| property.estimated_roof_age_years | Old roofs hit by storms = total replacement candidates. Highest value leads. |
| property.owner_occupied | Owner-occupied homes file claims faster than rentals. Prioritize them. |
| imagery.imagery_date | Compare pre- vs post-storm imagery dates to validate damage timeline for insurance. |
From signup to live
Typical timeline from first call to your first enriched record.
Pre-season setup
API key + integration before storm season. Most networks set up in summer (calm period), then run live during peak hail / hurricane months.
Storm trigger
When NWS issues a severe-weather advisory in your coverage area, your system pulls impacted ZIPs and posts addresses to our bulk endpoint.
Enrichment + scoring
We return enriched records in 30-60 seconds per 1k addresses. Your scoring engine ranks them by your contractor-tier criteria.
Dispatch
High-value leads route to top-tier contractors via SMS or your CRM's dispatch tool. Lower-tier leads queue for the rest of the network.
Post-storm review
After 30 days, review which enriched leads converted. Adjust the scoring + tier rules for the next event.
Common questions
How fast can you turn around 10,000 addresses?
About 30-45 minutes on the bulk endpoint. We parallelize within rate limits so you don't wait sequentially for each call.
Do you have damage detection from imagery?
Not yet. We give you pre-storm baseline data; damage detection from post-storm imagery is on our roadmap but not currently part of the API. Pair us with a vendor like ZestyAI or Cape Analytics if you need that today.
What about hail, vs wind, vs hurricane events?
Same data, different signal weights. For hail you weight roof age + material heavily (older asphalt is most vulnerable). For hurricane wind, you weight pitch + complexity. Your scoring engine chooses; we just supply the inputs.
Can we replay enriched data when the same address gets hit twice?
Yes. Cache our results 60-90 days. Subsequent hits to the same address can pull from cache instead of re-billing.
Speed wins storm season
The networks that enrich fastest dispatch first. Plug into our API once, ride out every storm with confidence.
Tell us what you're building
We'll review your use case, answer questions, and get you set up if it's a fit.