Ending brokerage disputes with a versioned lead-ownership engine

Ashray Developers builds residential projects in Delhi NCR and Jaipur — four live projects, about 1,900 units, and a sales motion that depends heavily on a network of 300+ channel partners (brokers). Leads arrive from nine sources: portals, Meta, Google, the website, walk-ins, referrals, and the channel-partner network itself.

The channel-partner network was eating itself

Two brokers register the same buyer, three days apart. The buyer books. Both brokers claim the brokerage — often lakhs of rupees. There was no authoritative record of who registered whom, when, or under what rule, so every dispute was settled by argument, seniority, and whoever shouted loudest in the sales head's office.

This is not an inconvenience. Lead-ownership disputes are the single most common reason a channel-partner network collapses, because good brokers stop bringing you their buyers the moment they conclude the brokerage is a coin flip. Ashray had already lost two of their top ten partners this way, and they knew exactly why.

And the inventory could be sold twice

• Unit availability lived in a shared spreadsheet. Two sales managers could — and did — block the same unit for two different buyers on the same afternoon.
• Demand letters were manual. Construction-linked payment plans mean a demand letter is triggered by a construction milestone. Someone was watching milestones in one spreadsheet and issuing letters from another, and letters were routinely late — which is late money, at scale.
• RERA obligations were being managed by memory. The 70/30 escrow split on every collection was calculated by the finance team by hand. Listings had been published without the RERA registration number appearing, which is an advertising violation, and it had happened more than once.

Launched internally first, then to the top 40 channel partners, then to the full network over six weeks. The brokerage ledger was backfilled with the previous two quarters so partners could see their own history on day one — which is why they logged in.

Results

• Duplicate-lead disputes fell 94%. The remaining 6% are genuine edge cases, and they are now resolved by opening the event log rather than by holding a meeting. Nobody argues with a timestamp they can see.
• Lead-to-site-visit conversion rose 41%. Not magic: the routing rules assign a lead to a named human within minutes instead of hours, and a residential lead that goes cold in the first hour mostly stays cold.
• Channel-partner-sourced bookings grew 2.3× in two quarters. Two of the partners who had walked away came back. When we asked one of them why, he said he could finally see his own pipeline without phoning anyone — which was, in the end, the entire product.
• Zero RERA advertising violations since launch, because a listing without a registration number cannot be saved, let alone published.

The quieter wins

Demand letters now go out on the day the milestone is certified rather than whenever someone notices. Across 1,900 units on construction-linked plans, moving collections forward by an average of eleven days is a working-capital effect large enough that the finance director brought it up before the sales director mentioned conversion.

And double-blocked units simply stopped existing. The lock made them impossible, and the sales floor — who had assumed this was just how spreadsheets worked — noticed within a week.