Water-depth sensors that warn housing societies before basements and gates flood
TL;DR Waterdepth puts small water-depth sensors in basement ramps, gate dips and nearby drains, and pairs them with a rain gauge on the roof. Residents get a heads-up to move cars or switch off pumps before the water arrives. Housing societies and tech parks pay a yearly fee, and the pooled readings slowly build a street-level flood map.
Floods damage around 12 lakh houses in India in an average year, going by Central Water Commission records from 1953 to 2020[1]. In cities, a good chunk of that damage comes from rain that simply has nowhere to go. In Nagpur, water bodies shrank from 12.2 km² to 2.29 km² between 2000 and 2023 as built-up area more than doubled, and a single day of 145 mm in September 2023 flooded the city[2].
Public systems report rainfall, not the depth at your gate. So a society manager staring at a city dashboard still can't tell whether the basement ramp will take water in the next hour, and cars, lifts and pump rooms get wrecked in that gap.
Each site gets two to six depth sensors at the spots that flood first - the basement ramp, the gate dip, the drain outside and the pump room. A rain gauge on the roof measures how hard it's raining at that exact building. Readings go to a small gateway every minute.
When water rises past a set level, or when rain and drain readings together say it will within the hour, the system sends chat-app and app alerts to residents and the facility team. A simple model learns each site's habits, like how many minutes of heavy rain it takes before the ramp floods.
With the society's consent, every site's readings feed a shared street map. That's the "community network" bit of the seed, which pitched crowd-run sensors and AI forecasting for climate adaptation in general. I narrowed it to waterlogging because "adaptation in general" has no clear buyer, while a society that lost cars last monsoon very much does.
The housing society's managing committee pays from maintenance funds, or a tech park or warehouse operator pays from its facility budget. Residents get the alerts. There's no published Indian price for this kind of service, so a one-time install fee plus a yearly subscription per site is an assumption you'll need to test. A ward office could pay for the pooled map later.
Radio approval for Wi-Fi and similar low-power devices has been a self-declaration at ₹10,000 per model since 2019[3], so small hardware firms can certify sensors cheaply. Cities keep building over water bodies, as the 2025 Nagpur study shows[2], and short, heavy bursts of rain are turning streets that never flooded into ones that do.
I found no public figure for what Indians spend on private waterlogging alerts. The closest anchor is damage - average annual flood losses of about ₹6,428.67 crore across crops, houses and public utilities[1], and a reported ₹30,000 crore hit to Chennai builders after the 2015 floods[4].
That's the cost of the problem, not your market.
Karnataka's disaster monitoring centre runs weather monitoring and a city rain-alert app for Bengaluru[5]. One Bengaluru data startup sells hyperlocal environmental data APIs and lists disaster data, though its disaster-management product is marked "coming soon"[6]. Neither measures depth at a society's own ramp. I found no Indian product sold to housing societies for this, but web search was down when I checked.
| Difficulty | Moderate (50/100) |
| Starting capital | ₹60 L–1.1 Cr |
| Time to launch | 6–9 months |
The sensors aren't exotic. The hard part is keeping them alive in silt, sewage and heat and getting the warning out early enough to matter, because flood sensors need regular calibration and break easily[7], which makes field service a real cost. And you'll be selling to committees that meet once a month and approve spending at their own sweet pace.
No operating licence is needed, but every radio device needs approval and the alerts carry personal data.
Building this outside India? The categories above usually have a local equivalent, so check with your own regulator.
Don't trust AI forecasts to tell residents an area is safe. Alerts should warn early and err on the side of caution.
Want to work out the AI layer for Waterdepth? Talk to Yash →
Here's what can go south -
I like this as a practical business for a founder with IoT and field-service experience in one flood-prone city. If you want pure software margins then look elsewhere, because this one has trucks and spanners in it.
Prove two things first - that your alert gives at least 20 minutes of warning in real storms at ten sites, and that most of those societies renew after one monsoon.
Plan for roughly ₹60 L–1.1 Cr, mostly for sensors, gateways, field service staff and the alert software.
No operating licence, but each radio model needs WPC equipment type approval by self-declaration. You also need DPDP consent for residents' numbers and ward permission for public drains.
Possibly, if societies renew after a monsoon and field service costs stay low. Demand can dip in dry years, so test renewals before you scale.
The free Waterdepth validation kit has the line-by-line capital breakdown, the effort scoring, the radio and data-protection checklist, a 14-day validation sprint with pass/fail targets, a 90-day launch plan, 10 interview questions for society committees and facility managers, and 5 assumptions to test. Download the kit →
Thinking about building Waterdepth or something close to it? The make-or-break work is giving enough warning in a real storm and keeping sensors alive through the monsoon, and I'm happy to think that through with you. If you need a hand, you know where to find me. Talk to Yash →
For illustration only. Names are fictional and ideas hypothetical; sourced facts are real but may be out of date. Nothing here is legal, financial or professional advice, and Yash Khatri is not personally liable for any use of it. Read the full disclaimer.