Real estate inventory management software for builders and brokerages.

The double-sale problem, and why spreadsheets cause it

The classic Indian project inventory system is a shared spreadsheet, updated by whoever remembers, mirrored into three WhatsApp groups and a printed chart on the sales gallery wall. On a quiet week it works. On a launch weekend, with four channel partners and an in-house team all pitching the same corner units, it fails predictably.

The failure is expensive in a specific way. Two families are told the same flat is theirs. One of them has to be moved, usually with a discount, occasionally with a legal notice, and always with a story that travels through the local broker network faster than any marketing campaign.

Live inventory with enforced states removes the race. When a broker blocks A-1104, it is blocked for everyone in the same instant, on the same board, whether they are in the sales gallery or on the ninth floor of a partner's office in Andheri. Holds expire on their own, so the other classic failure — a project where forty units are "held" by nobody in particular — does not accumulate.

• One live board across in-house sales, partners and management
• Holds with an expiry, released automatically
• Blocks that are enforced rather than advisory
• Every state change stamped with who and when

Inventory is where pricing actually lives

A unit is not just available or not. It has a saleable area, a carpet area, a floor, a facing, a view premium, a parking allocation and a rate that may differ from the flat directly below it. That data is what makes a cost sheet correct, so inventory and pricing belong in the same place rather than in two systems that disagree.

SaudaFlow holds the rate card against the tower — base rate, floor-rise slabs, PLC by facing, parking, club and corpus — and cost sheets read from it per unit. Change the rate card with an effective date and new sheets pick it up while previously issued quotes stay exactly as they were sent.

It also makes the commercial questions answerable. Which configurations are moving and which are stuck. Whether the east-facing premium is holding or being discounted away deal by deal. How much of the tower is sitting in holds that never convert, which is usually the first honest signal that a launch is slower than the weekly meeting suggests.

What a builder sees versus what a partner sees

Builders and channel partners need the same availability and different everything else. A partner should see what is available, what it costs, and what they can pitch. They should not see the builder's internal margin notes, the discount ceiling, or another partner's pipeline.

Inventory visibility is therefore scoped. A builder publishes availability and pricing to the partners working that project; each partner sees the live board and their own leads against it. Blocks made by any party are honoured by all parties, because that is the entire point, while commercial internals stay on the builder's side of the line.

The same scoping is what makes attribution survivable. When a partner's buyer blocks a unit, the block record names the partner, the date and the broker — the same evidence the brokerage ledger later uses to justify a payout, rather than a screenshot war six months after registration.

• Availability and pricing published to partners; internals are not
• Blocks honoured across every party looking at the project
• Partner attribution recorded at the moment of the block
• Per-project scoping, so a partner never sees a rival's pipeline

Fitting the RERA-era reality

Post-RERA, a project's inventory position is not a private matter. Registered projects report on units and bookings, buyers ask harder questions about what is genuinely unsold, and a sales team quoting "only two left" that turns out to be untrue is a compliance risk as much as a credibility one.

Keeping inventory in a system with a stamped history means the answer to "what was actually available on 12 March" is a query, not a memory. The registration clock that follows a booking — agreement, stamp duty payment, sub-registrar appointment — is tracked against the unit rather than living in one coordinator's diary.

All of it is tenant data held encrypted at rest in the Mumbai region, isolated per workspace, with staff access writing audit rows you can read. Your inventory position is commercially sensitive information, and it is treated that way.