Case study · ImpactIQ
From RoofLink and scattered tools to one storm command center.
How a Dallas-area roofing company moved 14,439 job files and five people onto ImpactIQ, a custom AI roofing CRM built by Ward Tech Systems.
Storm Intelligence. Roofing Results.
01 The problem
Storm restoration is a race. When hail comes through, the company that knocks first, documents cleanest and files the tightest estimate gets the roof. Everyone else gets the leftovers.
This team was running that race on RoofLink and a pile of separate tools. Each tool held one piece of the job, and none of them talked to each other. The core system didn't fit how the crew actually works, and the company wanted things it couldn't get in one place:
- a canvassing map for working neighborhoods after a storm
- a calendar that knows where the storm hit
- a portal where homeowners can check their job
- measurement and Xactimate-grade estimating
- insurance supplements
The owner needed four answers every morning:
- Where did hail hit?
- Which of our addresses are inside it?
- Who is working them?
- Where does every claim stand?
The old stack spread those answers across different screens.
02 The solution
Ward Tech Systems built ImpactIQ: one system that covers the whole job, from the storm to the paycheck, designed by someone who has worked the roof around how this crew actually runs.
Find the work
- Storm and hail intelligence. NOAA storm history, National Weather Service Texas alerts every 15 minutes, and radar hail layers. Shows which addresses sat inside the swath and produces a storm evidence report as proof of the date of loss.
- Territory map and canvassing. Reps draw territories, see lead density, log door knocks in the field and see which neighborhoods are already worked.
- Property enrichment. Turns an address into owner and property facts, so reps knock the right doors.
Work the file
- The Storm File. Every job is one record: status, homeowner, carrier, adjuster, claim number, date of loss, notes, photos, documents and messages. Hot, warm and cold lists roll up into a pipeline board.
- Duplicate cleanup. Merges the same homeowner arriving from more than one source.
- Homeowner texting and in-app messaging live on the Storm File, not in a rep's personal phone.
Inspect and estimate
- AI photo damage detection. Upload roof photos and the AI flags hail and wind damage.
- Roof measurement and a 3D roof model, without buying a separate report for every job.
- Xactimate-aware estimating with 15,418+ codes built in, plus AI-drafted supplements for money the carrier left off.
Close and collect
- Phone e-signature. The homeowner signs on their phone and the contract lands on the Storm File.
- Invoices and pay links go straight to the homeowner.
- Homeowner portal with job progress, documents and messages, which cuts down "what's the status?" calls.
Run the team
- Roles and permissions (admin, team lead, rep), task assignments with notifications, and an owner dashboard for pipeline and rep performance.
- Rep motivation. XP, quests and leaderboards, plus a built-in Academy for new reps.
- Rep Card, a public page per rep with lead capture, and an Android app for the field.
03 The implementation
Built around the real workflow
Scope came from how the crew actually runs a storm: knock, inspect, measure, estimate, supplement, sign, collect. Not from a generic CRM template.
Phased, not all at once
The core CRM shipped first. Canvassing map, calendar and customer portal followed as separate phases, each scoped and quoted as its own change order. Bugs in covered work get fixed at no charge; new scope gets a price before anyone builds it.
Migration without starting over
Switching systems usually means losing history. A RoofLink import moved 14,439 job files for all five people in one bulk run in June 2026, so the team kept its book of business on day one.
Shipped at field speed
3,958 commits over about 8 months. In one 24-hour window in July, 52 changes went live. When the owner asked for task assignments in September, they were built and shipped that month.
Engineered to hold up
ImpactIQ runs on Cloudflare's edge platform (Workers, D1, R2, Durable Objects, Workflows, Vectorize, Workers AI): 93 database tables, 205 schema migrations, 11 scheduled jobs (storm alerts, AI photo analysis, enrichment, a daily AI brief for each user), 236 unit-test files and 35 end-to-end specs.
04 The result
- 5
- people run their storm pipeline in one system: owner, team lead and three reps
- 14,439
- job files moved over from RoofLink. Nobody started from zero
- 1
- Storm File per job: carrier, adjuster, claim, photos, estimate, contract and payment together
- 25
- production features across about 100 screens, from hail map to pay link
05 Why it worked
The software wasn't the hard part. Knowing the job was. A roofer doesn't need another dashboard. He needs to know where hail hit, who is on it, and where the money is. ImpactIQ was built by someone who has worked the roof, so the screens follow the job instead of a software company's idea of it.
Is your company running on texts and spreadsheets?
If your jobs live across a CRM, a spreadsheet, a measurement vendor and your reps' phones, you're losing leads and money in the gaps. Start with an Ops Teardown: we map your workflow, price the leaks and prototype the fix. The fee credits toward the build.