One shared record of every message to a flat buyer, from booking to handover
TL;DR Bricknote is post-sale communication software for housing developers. Every call, chat message, email and demand letter to a flat buyer lands in one thread that sales, accounts, site and handover teams can all see. Developers pay per active unit, because a missing record of a promise has a habit of turning into a RERA complaint.
A flat buyer deals with a developer for three to five years after booking. In that time they hear from a sales executive, an accounts clerk sending demand letters, a site engineer, a legal desk and finally a handover team, and each of them keeps their own phone, inbox and spreadsheet.
The cost shows up at the regulator. MahaRERA alone has received 39,443 complaints and passed 33,304 orders as of October 2026[1]. Lawyers advise buyers to keep every piece of correspondence, because a brochure line or a salesperson's word can bind the developer[2].
Developers rarely hold the same record of their own side.
Bricknote sits on top of the tools a developer already uses. It pulls messages from the business chat number, email, call logs and the sales CRM, and files each one against a unit and a buyer. Anyone answering a buyer sees the full history first.
Three features do most of the work. An AI summary shows what this buyer has been told about possession date, payment plan and specifications, with links to the original message. A promise register flags any message that commits to a date, an amenity or a change, and routes it to the right team for sign-off. And bulk updates (a slab completed, a revised possession date, a layout change needing two-thirds consent[2]) go out once with each buyer's reply logged.
The seed was a general platform for joining up customer messages. That market is crowded, so I narrowed it to one industry where the record carries legal weight.
The buyer uses it but never pays. The developer's customer-relations or CRM head pays, usually with sign-off from the promoter. Today they pay for bits of this separately - one global helpdesk costs US$19–89 (about ₹1,840–8,610) per agent per month[3], and one Indian business-chat inbox costs ₹2,799–3,799 a month plus message fees[4]. My working assumption, still to be tested, is a per-unit monthly fee during construction.
Developers have moved buyer contact onto chat apps, which is fast but scattered across staff phones. The DPDP Rules notified on 13 November 2025 make developers responsible for buyer data held on those phones, with most duties enforceable from 13 May 2027[5]. A central, consented record answers both the dispute risk and the privacy duty.
There's no public figure for spending on post-sale buyer communication. The narrowest count I found is MahaRERA's 56,369 registered projects in Maharashtra alone[1], each with buyers to keep informed for years.
Adjacent - one Indian real-estate CRM says more than 1,500 real estate businesses use its sales CRM[6], which shows developers do buy software. Neither figure measures this market directly though.
Real-estate sales CRMs are the closest Indian players. It covers leads, site visits and cost sheets, and says it tracks deals to handover and automates collections, but I found no buyer thread or promise register on its site[6]. Helpdesks and chat inboxes handle tickets and messages for any industry, without unit-level context[3][4]. Large developers often build portals in-house.
The gap is a shared, unit-level history across every team after the sale.
| Difficulty | Moderate (36/100) |
| Starting capital | ₹60–110 L |
| Time to launch | 6–9 months |
The software is ordinary. The hard bits are getting messages off staff phones onto an official number, connecting to the many CRMs and ERPs developers run, and selling to promoters who see customer service as a cost. Sales cycles with mid-size developers can drag on for months.
Bricknote needs no licence of its own. Its customers are RERA-regulated, though, so the product has to keep records that hold up in a complaint.
Building this outside India? The categories above usually have a local equivalent, so check with your own regulator.
Don't let AI promise anything to a buyer or interpret what RERA requires. Those messages carry legal weight, so a person approves them.
Want to work out the AI layer for Bricknote? Talk to Yash →
Here's what can go south -
I'd say it's worth a shot for a founder who has worked inside a developer's CRM team and knows how disputes start. If you're hoping to sell a general inbox to everyone then it's a poor fit. Prove first that one developer with 500 or more units under construction will move all buyer messages to Bricknote for three months and pay for it.
Plan for roughly ₹60–110 L, mostly on integrations with CRMs and messaging tools and a long developer sales cycle. Launch takes 6–9 months.
No licence for the vendor. You'll sign processor agreements under the DPDP Act and use an approved business-messaging provider for bulk messages.
Yes, wherever flats are sold off-plan and buyers dispute promises. Check whether a local regulator plays RERA's role, since that's what gives the record its value.
The free Bricknote validation kit has the line-by-line capital breakdown, the effort scoring, the RERA and data-protection checklist, a 14-day validation sprint with pass/fail targets, a 90-day launch plan, 10 interview questions for developers and their CRM teams, and 5 assumptions to test. Download the kit →
Thinking about building Bricknote or something close to it? The make-or-break work is persuading a promoter that a full record of promises protects them more than it exposes them, and that's a pitch I can help you shape. 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.