I build systems for developers, brokers and channel-partner networks: lead-to-booking CRM, unit inventory that tells one truth, payment schedules tied to construction milestones, brokerage reconciliation and RERA-aware document trails.
What breaks in a high-value, low-system trade?
Inventory drama that should not be possible. Two brokers “holding” the same 2BHK because the availability sheet is updated by phone call. A payment schedule tracked in Excel against milestones nobody updates, so demand letters go out late or not at all. Channel-partner brokerage disputed every quarter because attribution lived in someone’s memory. And buyer files that reveal their gaps only when a dispute forces the question.
The transactions here are among the largest an Indian family will make, and the tracking around them is frequently the least rigorous in this entire document. That mismatch is the opportunity: the fixes are not sophisticated, they are simply absent.
What does the system cover?
- Unit inventory, one truth. Available, held, booked, sold — with holds that expire automatically. The double-booking call stops being possible rather than being discouraged.
- Lead pipeline with attribution. Portal, partner and walk-in sources captured and deduplicated at entry, stages managed, follow-ups queued. Marketing spend finally answers for itself.
- Payment schedules. Milestone-linked demand letters generated, receipts posted, buyer ledgers kept clean, and an overdue report that is honest rather than optimistic — the ledger discipline applied to construction-linked collections.
- Channel partners. Registration, attribution at capture, brokerage computed by rule and reconciled on a schedule. The quarterly argument dissolves because both sides read the same arithmetic.
- Document trail. Bookings, agreements, receipts and communications organised per unit and per buyer, in the shape RERA disclosures draw on.
- Post-possession. Handover, snags and society transition tracked, because reputation is made after the sale.
Why does attribution deserve its own paragraph?
Because it is the single most expensive piece of missing data in this trade. When a lead arrives through a portal, gets a site visit from an in-house salesperson, and closes months later through a channel partner who also claims it, the brokerage question has no correct answer available — only positions — and whichever party argues hardest tends to win, which is a terrible way to price a relationship you need next quarter. Every developer I have spoken to has a version of this argument running with at least one partner.
Recorded attribution at capture, with the rule agreed in advance, converts that from a negotiation into a computation. It is unglamorous, it takes ten minutes to configure, and it removes a recurring quarterly conflict that costs both money and relationships.
The deployable build is the Real Estate CRM.
Related reading
/products/real-estate-crm — the productised build · /industries/contractors — the construction-side sibling · /products/whatsapp-automation — site-visit confirmations and demand reminders · /services/fintech — the collections discipline
The two-broker test
Can two people in your organisation, right now, independently hold the same unit? If the honest answer is yes, that is not a process gap — it is a system that has no concept of a unit’s state. /contact, and bring your live availability sheet.
Questions I actually get
Do you build for brokers or developers?
Both, with different cores. Brokers get the lead pipeline, attribution and brokerage tracking; developers add unit inventory, payment schedules and construction-milestone demands. Channel-partner networks sit between the two and get both halves, because that is what the arrangement actually requires.
Can it ingest leads from the property portals?
Yes, with deduplication — one enquiry becomes one record even when the same buyer enquires through three portals in a week. Without dedup, portal leads inflate your pipeline and corrupt every source-attribution number you might use to decide where to spend.
How does the unit-hold logic work?
A hold is a state with an owner and an expiry. When it lapses the unit returns to available automatically rather than staying blocked because someone forgot. That single rule ends the situation where two brokers are confidently selling the same flat.
Does it handle RERA requirements?
It maintains the underlying trails — bookings, agreements, receipts, buyer communications — that filings and disclosures draw on. Your compliance owner or counsel files; the system makes the evidence a query rather than an archaeology project.
How is channel-partner brokerage calculated?
By rule, with attribution recorded at lead capture rather than reconstructed at settlement. That is the whole fix: the quarterly brokerage argument exists because attribution is remembered instead of recorded, and rules applied to recorded attribution do not argue.
What happens after possession?
Handover tracking, snag lists and society-transition support close the loop. Post-possession is where developer reputation is actually made, and it is usually the least systematised part of the business.