What is available, right now, floor by floor.
Inventory draws the building the way your sales team already thinks about it — a stack, floor by floor, colour-coded by available, held, booked and sold. Each unit carries how many buyers are circling it and how many have a price on the table, so a rep in the lounge knows which flats to push today.
The building, drawn the way your team already thinks about it.
Floors down the side, units across. Colour is status. A rep standing in the sales lounge can see the whole tower without asking anyone, and a manager can see which stacks are moving and which are not.
Each cell also carries how many buyers are currently interested and how many have an offer on the table. That is the difference between “six flats left” and “six flats left, four of them with someone circling.”
When nothing matches, the worst answer is a blank screen.
Inventory is small, the good stacks sell first, and a buyer’s requirement is usually three constraints that have never all been available at once. So when an exact search returns nothing, Terra relaxes the requirement one axis at a time and says out loud what it gave up.
Identical layout and facing, one floor up — ₹25,000 more in floor rise.
Same floor and size, east-facing instead of north — same price.
Same facing and floor, 80 sq ft smaller — ₹4.2 lakh less.
The same requirement against the same inventory returns the same three flats in the same order, every time. A rep who says “the system suggested this” must be able to reproduce it in front of a manager. That rules out a black box.
The order of relaxation is a product decision: a different floor is a smaller ask than a different direction, which is smaller than a different size, which is smaller than a different part of the city.
A hold is a record, not a message in a group.
See it against your own project.
A walkthrough runs on your data — one real approval, one live tower, last week’s enquiries. Forty minutes, no slides.