Lead to possession: what a real-estate CRM should actually cover

In most industries the last stage of a CRM is called "closed won", and that is a fair name for it. The money arrives, the contract is signed, the salesperson moves on to the next account. Indian real estate borrowed the vocabulary and the software, and the vocabulary is wrong.

A booking here is a token amount, an allotment letter, and the beginning of a relationship that will run for years. Almost everything expensive happens after the word "won": the rest of the consideration arrives in instalments tied to construction milestones, a broker's commission accrues against those receipts rather than at the signature, the unit's status has to stay true across a sales team that can promise it twice, the authority expects the project page kept current throughout, the buyer wants to know what is happening at site, and at the end someone has to run a handover checklist and give a family their keys.

If your CRM's last screen says "Won", every one of those lives in spreadsheets, WhatsApp threads and one person's head.

This post is a checklist. It uses a nine-stage spine — marketing, capture, qualification, pipeline, site visits, inventory, booking, collections, possession — and for each stage gives the failure it prevents and the thing to make a vendor show you. We build a CRM on exactly this spine, so read the last section knowing that. The checklist is worth more to you than our answer to it.

Why is "closed won" the wrong finish line here?

Three reasons, and they compound.

The first is where the money is. At booking the buyer has paid a token; the rest arrives against construction milestones over the life of the project. The cash you actually run the company on is collected after the stage a deal-shaped CRM calls the end — which means your collections process, not your sales process, is what determines whether the project finishes on time.

The second is the obligations. Under Section 11 of the Real Estate (Regulation and Development) Act, a promoter keeps the project's page on the authority's portal current on a quarterly basis — including the number of apartments booked, sold or allotted and the percentage of work completed. ^↗ That makes your booked-versus-available split a compliance record, not merely a sales one. If it lives in a spreadsheet that one person maintains from memory, every quarterly update becomes an archaeology exercise, and the version filed is the version that person reconstructed on the day.

The third is the shape of the data. A CRM whose atomic records are a contact and a deal cannot represent a building. Real estate's scarce object is the unit: two buyers can want A-1204 and exactly one can have it. A deal record can be duplicated without anyone noticing; a unit cannot. Every builder who has run inventory as a text field on an opportunity has eventually discovered this the expensive way, on a Sunday, with two families in the office.

Stages one to four: the front half every vendor demos well

The first four stages are where the software industry has been for thirty years, so the bar is high and most tools clear it. That does not mean there is nothing to ask.

Marketing. The point of joining campaigns to the CRM is not prettier reports; it is that the spend and the booking it produced end up in the same place. Ask: can I see cost per lead and cost per booking by campaign without exporting anything to Excel? If the answer involves a spreadsheet, you do not have attribution, you have two systems and a monthly reconciliation.

Capture. Leads arrive from portals, website forms, WhatsApp click-to-chat, missed calls, QR codes on hoardings, walk-ins and broker submissions, and they all need to land in one table tagged with where they came from. The question that separates serious tools from casual ones is about duplicates: the same buyer enquires through two portals and is also submitted by a broker — what does the system do? Duplicate handling is where broker attribution fights start, and they are much cheaper to prevent at capture than to arbitrate at booking.

Qualification. Ask what fires when a lead arrives at eleven at night, and how fast. The evidence that first-response speed drives conversion is old and consistent ^↗, and no rep is awake at eleven — so this is a question about automation, not about staffing.

Pipeline. Every call, note and stage change should sit on the lead record. The test is not whether the timeline looks nice; it is what happens to that record when the rep who owns it leaves the company. If the history walks out with them, you did not have a pipeline, you had a filing habit.

Stages five to seven: the hinge, where generic CRMs start to fail

Site visits. Scheduling, a check-in at the site rather than a write-up at the desk, and an outcome logged while it is fresh. Ask how you find out about a visit that happened and was never written up — an unlogged visit is invisible unless the system knew a visit was due. This is the whole subject of our mobile-first field sales playbook, and it is the stage most often reduced to a calendar event.

Inventory. This is the fork in the road. You need a live tower-by-floor-by-unit grid with real availability states — available, held, booked, sold, blocked — plus time-bound holds, price and cost sheets, and floor plans attached to the unit. Two demonstrations to insist on: show me two salespeople trying to hold the same unit, and show me a hold expiring on its own. A hold with no expiry is how a unit sits quietly blocked for a month for a buyer who stopped answering in week one. The inventory management side of this deserves as much scrutiny as the lead side, and usually gets a tenth of it.

Booking. The booking is not a stage change; it is four things happening together. The unit changes state, the paperwork is generated from the booking rather than retyped, the payment schedule exists from day one, and cancellation is a first-class action that releases the unit. Ask the vendor to cancel a booking in front of you. More on that below, because it is the best question on this page.

Stages eight and nine: the half nobody demos

Collections. Payment demands raised against construction milestones, demand notes and receipts, ageing buckets, a chase list the accounts team works from, reminders that escalate on their own, and GST-compliant invoicing. Three things to make a vendor show: raise a demand against a milestone; show me the ageing view; show me what the system does on day thirty-one when nobody has paid and nobody has remembered. That last one is the difference between software and a filing cabinet.

Possession. A handover checklist, possession letters, a buyer portal, construction-progress tracking and buyer document access. The question here is about your own team's time as much as the buyer's experience: what does the buyer see, and does it reduce the number of calls your team takes about construction status? A buyer with no visibility phones. A buyer with visibility mostly does not, and the ones who do phone about something real.

Underneath both sits the part that is neither sales nor accounts: channel partners. Commission set per broker, accruing against the booking and its actual receipts, with statements a partner can see themselves. Commission handled outside the system is the most reliable source of arguments in this industry, because two parties keep two records and neither is wrong from where they are sitting.

And underneath everything, the paper trail: generated allotment letters, demand notes, receipts and possession letters, RERA filing reminders, and an audit trail behind every status, booking, payment and ownership change.

The seams are where the money leaks

Here is the argument that matters more than the module list.

Any missing module can be replaced by a spreadsheet and a diligent person. Builders do it every day and some do it well. What a spreadsheet cannot replace is the join between two modules — and a checklist read as "does it have feature X" misses that entirely.

Every seam creates two versions of the truth and a human arbitrator. The booking is in the CRM and the unit status is in a sheet. The receipt is in the accounting system and the commission is in a broker's email thread. The visit is in a rep's notebook and the lead stage is in the CRM. None of these is a disaster on any given day. The cost is paid in two currencies: the hours somebody spends every week making the copies agree, and the occasional expensive failure — a unit sold twice, a commission paid twice, a demand note sent to a buyer who cancelled in March.

Which gives you the single best test I know for a real-estate CRM.

Ask what happens when a booking is cancelled. A system that cannot answer in one action has a seam, not a lifecycle.

Ask what happens when a booking is cancelled. In a genuinely joined system, one action does all of it: the unit returns to available, the future demands stop being raised, the commission accrual reverses, the generated documents are marked void, and the audit trail records who did it and when. In a seamed system, the answer becomes a description of a process — the sales head tells the CRM person, who tells accounts, who tells the broker coordinator — and one of those five people is on leave. Listen for the moment the demo stops being a screen and starts being a story. That moment is the seam.

Five things to make a vendor show you, live

Take these into every demo, including ours. Insist on watching rather than hearing.

One. A unit through its whole life: available, held, booked, cancelled, available again. One system, no exports, no "that would normally be done by our support team".

Two. A payment demand raised against a construction milestone — and what the system does on day thirty-one when it is unpaid and nobody has intervened.

Three. A broker's commission on the booking you just watched them make, and what that number looks like when the buyer has paid only half the schedule.

Four. What a site executive sees on their phone. Specifically: can they see the unit grid, and can they see the buyer's phone number and the price? You want the first answer to be yes and the second to be no, and you want to see it rather than be told it.

Five. A document generated from that booking — an allotment letter, a demand note, a possession letter — and the audit trail behind the status change. Then ask them to export everything and show you the file. Data you cannot export is data you have rented.

There is a sixth question that is commercial rather than functional, and it is worth asking early: what does the bill look like in launch month when you add five closers? Per-user pricing charges you most exactly when you are growing, which is the subject of our pricing and ROI guide.

What if you cannot buy the whole thing?

Most builders cannot replace everything at once, and the honest advice is not to try. Rank the gaps by money at risk times frequency, and close them in that order.

For most developers the order comes out the same way. Inventory truth first, because double-promising a unit is the one failure your buyer experiences directly and cannot be smoothed over. Then collections ageing, because it is your cash and a month of drift is a month of interest. Then broker payouts, because it is an argument you are definitely going to have and the only defence is a record. Then possession, because it is your reputation, your handover cost, and the source of the next project's referrals.

Running the other half on spreadsheets is perfectly workable if it is deliberate rather than accidental. That means one named owner per register, a fixed weekly slot for reconciliation instead of an emergency when something breaks, and — the rule that actually matters — no third copy. What kills builders is not the spreadsheet. It is the fourth version of the spreadsheet, on somebody's laptop, that three people are quoting from.

Where Sthan fits

We wrote the product against this checklist, so of course it scores well on it. That is a reason to be more sceptical of us, not less, and the right response is to make us do the five live demonstrations above rather than take a list on trust.

For completeness, here is what the nine stages look like in Sthan. Marketing campaigns run against the projects and units already in the system, with source attribution at capture and cost per lead by channel. Capture from the portals, website forms, WhatsApp click-to-chat, missed calls, QR and walk-ins. Scoring, routing and instant first response on qualification. A pipeline where call logging cannot be closed without a next step. Site visits with scheduling, location check-in, outcome logging and unlogged-visit alerts. A live tower-by-floor-by-unit grid with time-bound holds, cost sheets and floor plans. A booking workflow that generates allotment letters and agreements, sets the milestone schedule, and handles cancellation with unit release. Construction-linked demands with demand notes, receipts, ageing buckets and tiered reminders. A possession handover checklist, possession letters and a buyer portal. Alongside them, a channel-partner portal where commission accrues against the booking and its payments, RERA filing reminders, and an audit trail behind every status, booking, payment and ownership change. It is all on the platform page, and the price is on the pricing page rather than behind a call.

None of that is the point of this post. The point is that the booking is not the finish line — it is the moment your obligations start getting expensive — and that the software worth paying for is the software that knows it. Take the nine stages, the cancellation question and the five live demonstrations into every conversation you have with a vendor. The ones who can do them will show you. The ones who cannot will tell you about the roadmap.