Crack and tilt sensors on old buildings next to redevelopment digs
TL;DR Tiltwise fits crack meters, tilt sensors and vibration loggers to old buildings that sit beside excavation and piling for redevelopment. The developer pays, because it wants evidence and an early warning. Neighbours get alerts and a shared record, so a fight over new cracks runs on data instead of shouting.
India's older cities are packed with ageing buildings that are already fragile. In 2025 Navi Mumbai declared 527 buildings dangerous, and buildings over 30 years old there must be audited by a registered engineer[1]. But an audit is only a snapshot. In August 2026 a Bhiwandi building that had been rated repairable collapsed, and the city ordered every building in its unsafe categories to be inspected again[2]. Mumbai's own corporation admitted lapses in how it handles dangerous buildings in April 2026[3].
Then redevelopment turns up next door. Deep basements and piling shake and unload the ground beside old structures that nobody is watching between audits, which is a bit like hoping for the best.
What it does, in regulatory terms: structural monitoring only. Tiltwise records movement and sends alerts. It does not certify safety or replace a structural audit, which must come from a registered engineer[1].
The seed wanted AI listening for the sounds of failure, and I've reframed it. I found no evidence that acoustic sensing gives a reliable warning for ordinary concrete housing. Metro builders already use crack meters, tilt sensors and vibration monitors, so Tiltwise uses them too.
Before work starts, a team surveys each neighbouring building and photographs the cracks that are already there. Then it fixes wireless sensors to the walls and columns that matter most. Readings go to a dashboard with three thresholds agreed with the project's structural engineer - note, review and stop work. The developer's site team, its engineer and a named contact in each neighbouring society all get the same alerts. At the end, everyone gets a closing report.
The developer or its contractor pays from the project budget, for as long as the excavation and structure work runs. Why would it? Fewer stop-work complaints, evidence against inflated damage claims and a defence if something goes wrong. Neighbouring societies get the service free. Prices for small-site monitoring are not published in India, so pricing is an assumption you'll have to test.
The Bhiwandi collapse in August 2026[2] and Mumbai's admission of lapses earlier that year[3] have put building safety back on the civic agenda. Big projects already show the method works in Indian conditions. On Mumbai Metro Line 3, buildings in the zone of influence were surveyed and the sensitive ones were instrumented[4].
There is no public figure for building-monitoring spend on Indian redevelopment projects. The firmest signals are the 527 dangerous buildings in a single city[1], which tells you how many fragile neighbours sit near new work, and the routine use of building instrumentation on metro jobs[4]. Treat both as adjacent context, not market size.
One Indian instrumentation firm ran condition surveys on hundreds of buildings and monitored the sensitive ones for Mumbai Metro Line 3[4]. In New York, code changes in 2014 made instrumentation a requirement during construction, and that created a steady local market[5]. The gap in India is the small and mid-size redevelopment site - one or two basements, a few old neighbours and no budget for a metro-style contract.
| Difficulty | Moderate (43/100) |
| Starting capital | ₹60 L–1.2 Cr |
| Time to launch | 6–9 months |
You buy the sensors, you don't build them. The hard parts are trust and field service. A qualified engineer has to set the thresholds, the readings have to be right every single time and someone has to pick up the phone when an alert fires in the middle of the night. Developers will also push back on any cost that no rule forces on them.
No licence to sell monitoring, but audit, radio and data rules shape the service.
Building this outside India? The categories above usually have a local equivalent, so check with your own regulator.
Never let AI decide that a building is safe or set the stop-work threshold. Those calls belong to the project's structural engineer.
Want to work out the AI layer for Tiltwise? Talk to Yash →
I think this is a good fit for a founder with geotechnical or structural instrumentation experience who can sell to mid-size developers. If you want to stay away from site work then skip it. First prove that three developers will pay for monitoring on a live project without anyone making them.
Plan for roughly ₹60 L–1.2 Cr, mostly on sensors, field engineers and a night alert desk.
No sector licence. You need WPC approval for wireless sensors, DPDP compliance for photos inside homes and a registered engineer for anything that counts as an audit.
Yes. Some cities, such as New York, already require it during construction. Check your local building code and data protection law first.
The free Tiltwise validation kit has the line-by-line capital breakdown, the effort scoring, the audit, radio and data-protection checklist, a 14-day validation sprint with pass/fail targets, a 90-day launch plan, 10 interview questions for developers and societies, and 5 assumptions to test. Download the kit →
Thinking about building Tiltwise or something close to it? The make-or-break bit is getting developers to pay for monitoring before any rule makes them, and that's a pitch I'm happy to pressure-test 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.