Snap a photo of any road hazard — pothole, debris, flooding, broken sign — and HazardWatch auto-routes it to the right authority with GPS precision. Municipalities see their backlog. Insurers get claim-before-it-happens evidence. Drivers get roads that actually get fixed.
The UK alone has a £2.2 billion pothole repair backlog. Councils rely on sporadic inspections and angry phone calls. Insurers process £400M+ in pothole-related claims annually — with zero pre-claim hazard intelligence. There is no real-time, crowdsourced layer connecting citizens, councils, and insurers.
Most road hazards exist for weeks or months before anyone reports them. Councils operate on inspection cycles measured in years. A pothole on a B-road might not be seen by an inspector for 18 months. Meantime, it damages vehicles daily.
To report a pothole to a UK council: find the right website, fill in a form with 12 fields, manually drop a pin on a map, upload photos (file size limited), wait 4-8 weeks for a response. Most people don't bother. The hazard stays unreported.
Pothole claims cost UK insurers £400M+/year. But claims are processed blind — the insurer can't verify whether the council knew about the hazard, how long it existed, or whether other drivers reported it. Every claim is a he-said-she-said with no data layer.
Potholes kill cyclists. 400+ cyclist casualties annually in the UK involve road surface defects. Cyclists have the most incentive to report hazards but the least usable reporting tools — digging through council websites while standing at the roadside.
FixMyStreet has UK reports. Waze has driver-reported hazards. Council portals are siloed per jurisdiction. Insurers have claims data. None of these talk to each other. There is no single source of truth for road hazard intelligence anywhere in the UK — or globally.
When a council gets sued for vehicle damage from an unrepaired pothole, the entire case hinges on whether the council "knew or ought to have known." Currently, the answer is almost always "no evidence either way." HazardWatch makes that answer data-driven — timestamped, geotagged, indisputable.
HazardWatch is the missing data layer between road users, road maintainers, and road insurers. Open the app, take a photo of the hazard, and submit. GPS location, timestamp, authority routing, and resolution tracking — all automatic. Three users, one platform, zero friction.
Open app → take photo → submit. That's it. GPS, timestamp, and hazard classification (pothole/debris/flooding/signage/surface) auto-detected. The entire report takes under 10 seconds. Works offline — queues for submission when back in coverage.
Every report auto-routes to the correct responsible authority based on jurisdiction mapping — council, Highways England, Transport for London, utility company, or private landowner. No user needs to know who's responsible. The engine knows.
Once reported, users can track whether the hazard gets fixed. The app monitors council repair databases, crowdsources "fixed" confirmations from other users, and maintains a public resolution timeline. Transparency creates accountability.
Insurers query the HazardWatch API when a policyholder files a pothole damage claim. Instant answer: Was this hazard previously reported? When? By how many people? Did the council acknowledge it? Claims that took 6 weeks now take 6 minutes — with evidence.
Councils get a real-time hazard map with heatmaps, repair backlog metrics, SLAs against reported hazards, cost-per-repair tracking, and public transparency reports. Replaces the annual inspection cycle with continuous, crowdsourced intelligence.
Delivery fleets, bus operators, and ride-share drivers cover every road daily. Dashcam integration auto-detects hazards and submits reports without driver interaction. One Amazon delivery van covers more road surface in a day than a council inspector covers in a year.
Mobile app, authority routing, insurance API, dashcam integration — HazardWatch is infrastructure, not just a reporting app.
HazardWatch monetises three distinct customers from one data asset. Every hazard report creates value for citizens, councils, and insurers simultaneously.
Free: 3 reports/month. Premium £4.99/mo: unlimited reports, resolution tracking, insurance evidence packs, priority routing. Target: 8,500 premium users by Y3. Revenue: £510K/year at scale.
£499-£2,999/mo per council based on road mileage. Real-time hazard dashboard, repair SLA tracking, public transparency portal, fleet dashcam programme management. Target: 65 councils by Y3. Revenue: £1.56M/year.
Per-query pricing: £0.10-£0.25 per claim lookup. Bulk licensing for top-10 UK motor insurers at £50K-£120K/year. Target: 4 insurer contracts by Y3. Revenue: £380K/year. 85% gross margin on API calls.
130+ comments analysed across infrastructure, civic tech, and insurance YouTube channels. The signal: pothole frustration is universal, monetisable, and completely unserved by existing tools.
Conservative projections. Consumer premium at £4.99/mo, municipality SaaS at blended £1,500/mo average, insurance API at £0.15/query average. UK-first, then EU expansion Y3.
| Metric | Year 1 | Year 2 | Year 3 |
|---|---|---|---|
| Premium Users | 2,000 | 5,500 | 8,500 |
| Consumer Revenue | £119,760 | £329,340 | £508,980 |
| Municipality Customers | 12 | 38 | 65 |
| Municipality Revenue | £216,000 | £684,000 | £1,170,000 |
| Insurance Contracts | 1 | 3 | 4 |
| Insurance API Revenue | £60,000 | £220,000 | £380,000 |
| Fleet Dashcam Licensing | £0 | £72,000 | £240,000 |
| Total Revenue | £395,760 | £1,305,340 | £2,298,980 |
| Operating Costs | (£220,000) | (£380,000) | (£620,000) |
| Net Profit | £175,760 | £925,340 | £1,678,980 |
| Funding Required | £95,000 (covers app development, authority mapping database, insurance API build, initial council sales team) | ||
| Breakeven | Month 10 | ||
| 3-Year ROI | 280% | ||
FixMyStreet, SeeClickFix, and Waze all do part of this. None do all of it. None connect to insurance. None monetise the data layer.
| Competitor | Reporting | Authority Routing | Resolution Tracking | Insurance API | Council SaaS | Dashcam |
|---|---|---|---|---|---|---|
| FixMyStreet | ✅ | ✅ | ⚠️ Partial | ❌ | ❌ | ❌ |
| SeeClickFix (US) | ✅ | ✅ | ✅ | ❌ | ⚠️ Basic | ❌ |
| Waze | ⚠️ Objects only | ❌ | ❌ | ❌ | ❌ | ❌ |
| Council Portals | ⚠️ High friction | ✅ | ❌ | ❌ | N/A | ❌ |
| HazardWatch | ✅ 10-sec flow | ✅ 450+ councils | ✅ Full timeline | ✅ REST API | ✅ Full analytics | ✅ Fleet auto-detect |
Everything you need to know about HazardWatch.
FixMyStreet is a reporting tool. HazardWatch is a data platform. The difference: FixMyStreet sends a report to a council. HazardWatch tracks whether that council fixes it, measures how long it took, and makes that data available to insurers for claims processing. Plus: premium consumer tier, AI hazard classification from photos, dashcam integration for fleets, and a council SaaS dashboard. FixMyStreet is a pipe. We're the intelligence layer on top of the pipe.
Councils don't want more reporting portals — they want better data. HazardWatch doesn't replace council portals; it feeds them higher-quality, pre-verified reports with photos, GPS, and AI classification. The pitch to councils isn't "use our portal instead" — it's "your existing portal just got a crowdsourced intelligence layer that fills the gaps between your inspection cycles." The SaaS dashboard shows them their actual repair performance against SLAs, which most councils can't measure today.
Pothole damage claims cost UK motor insurers £400M+ per year. Processing a single claim costs £150-£300 in adjuster time. If HazardWatch can answer "was this hazard previously reported?" in 2 seconds via API, the insurer saves £150 per claim and gets better liability assessment. At £0.15/query, that's a 1000x ROI for the insurer. The bigger play: insurers embed HazardWatch prompt in their claims flow — "Did you report this pothole on HazardWatch?" — driving consumer adoption for free.
Full 3-year financial model with all three revenue streams modelled separately, municipality partnership strategy with pilot programme design, insurance industry go-to-market (which insurers to approach first, what data they'll pay for), technical architecture including authority routing engine, competitor positioning matrix, 90-day launch plan with TODO list, and investor pitch deck.
HazardWatch queues reports locally when offline. GPS and timestamp are captured at the moment of reporting (even offline). Photo and metadata sync automatically when the user regains connectivity. This is critical for rural roads — where the worst hazards are and where signal is weakest.
Yes. Click "Build For Me" and Sovael Consultancy delivers the full implementation — iOS/Android apps, authority routing engine with UK-wide council mapping, insurance API, municipality dashboard, and pilot programme with 2 partner councils. Timeline: 120 days to MVP launch. Contact us for pricing.
If no buyer emerges within 30 days, Sovael Venture Studio evaluates it for internal launch. This opportunity qualifies: £2.2B addressable problem (UK alone), three monetisable customer segments, clear data moat (hazard intelligence with insurance API is patent-free but hard to replicate), strong regulatory tailwind (councils under increasing pressure to publish repair performance data), and cross-sell into Sovael's Insurance and Consultancy arms.
3-year financial model, municipality partnership strategy, insurance go-to-market, technical architecture, competitor analysis, and 90-day launch plan — all for £49.
Nobody claimed this opportunity. Sovael Studio launches internally in 30 days if no buyer emerges.