Lead-to-possession process automation — the full sales workflow for Indian builders

Indian real-estate demand does not arrive through one channel. It arrives through a dozen, each with its own intent, velocity, and decay rate, and the first job of the workflow is to land all of them in one place.

The portal trinity — MagicBricks, 99acres, and Housing.com — produces high volume and high competition; the same buyer is usually enquiring with three other builders at once, so the lead decays in hours. Facebook Lead Ads spike around the festival season and NRI campaigns, often with softer intent that needs nurturing. Google Ads against project landing pages tend to carry higher purchase intent at a higher cost per lead. Then there are the channels a horizontal CRM's templates never anticipate: WhatsApp click-to-chat, missed-call IVR, walk-in registrations at the site office, and broker referrals.

A lead is not just a phone number. A MagicBricks festival-campaign inquiry for a three-crore flat behaves nothing like a missed call from a hoarding, and the rep needs to know which is which before the first call. Sthan auto-tags every lead on arrival by source, project, budget band, and city, and assigns it to the right rep before anyone has touched it. The rep opens a qualified context, not a blank row.

The product page describes this capture layer in detail. What matters for the workflow is that capture is the one stage where all of the later stages' data originates — a lead captured without its source and budget context is harder to qualify, route, and close at every stage that follows.

Speed at this stage is not a nicety; it is most of the outcome. Leads left unanswered for four or more hours convert far worse than leads answered in minutes — a buyer who has enquired with four builders books with the one that replies first and looks organised. These are typical industry patterns, not Sthan-measured data, but every sales head who has run a portal campaign has watched it happen.

The failure mode is mechanical. A MagicBricks lead lands at 9 p.m., the rep sees it at 11 a.m. the next morning, and by then the buyer has already taken two site-visit appointments elsewhere. The lead was never unqualified — it was answered late.

Sthan closes the gap with two automations that fire before a human is involved. The WhatsApp Business API sends an acknowledgment within seconds of the lead arriving — brochure, project intro, and a real reply the buyer can respond to — so the builder is in the conversation before the next brochure lands. In parallel, auto-assignment routes the lead to the right rep by project, source, and workload rules, and alerts a manager on the handoff.

The difference is in what the rep receives. Not "you have a new lead," but a lead with its context already attached: a Bandra inquiry from the MagicBricks festival campaign, budget two to three crore, English-speaking, weekend visitor. The first call is informed and fast. Instant response is described as its own layer on the package page; in the workflow it is the bridge between a captured lead and a qualified one.

Most Indian sales pipelines do not leak at capture. They leak at qualification — a large share of leads, commonly cited at around forty percent, are lost not because they were bad but because nobody worked out whether they were good. These are typical industry patterns, not Sthan-measured data, but the shape is familiar: reps spend their hours on whoever called most recently, and genuinely hot buyers go cold in the queue.

Qualification is really four questions every real-estate lead has to answer: what is the budget, what is the timeline, is the financing ready, and is this an end-user or an investor. A lead that has answered those four is worth a rep's time; a lead that has not is worth an automation's time, not a person's.

Sthan runs the pipeline by qualification state — New, Contacted, Qualified, Hot, Booked — so a lead's stage reflects how far it has actually progressed, not how long ago it arrived. A WhatsApp chatbot and smart forms can ask the four questions over the first twenty-four to forty-eight hours without a rep lifting a finger, scoring the lead on budget, property type, location preference, buying timeline, site-visit intent, and home-loan need. The qualification layer on the package page lists the full criteria.

The payoff is what the rep does not have to do. Instead of dialling a list of mixed-quality numbers, the rep opens a board where the leads that reached "Qualified" have already passed the four questions — and the ones that did not are still being nurtured by the drip, ready to promote the moment they engage. Qualification stops being the stage where leads quietly die and becomes the stage that decides where a rep's day goes.

The site visit is the hinge of the entire workflow. A large majority of real-estate buying decisions are made during or just after the visit — typical industry patterns put it well above seventy percent — because a flat is not something anyone commits a crore to from a brochure. Everything before the visit exists to get the buyer on site; everything after depends on what happened there.

That makes the choreography around the visit disproportionately important, and it is mostly logistics a busy rep forgets. Sthan handles it end to end: scheduling from the pipeline, an automated WhatsApp confirmation carrying the location pin, the sales-associate's name and contact, and the time; a day-before reminder so the slot does not evaporate; and a post-visit follow-up so the conversation does not go cold the moment the buyer drives away.

The part most systems miss is the outcome. A site visit is not done when it is over — it is done when its result is captured. Did the buyer actually visit, or no-show? Which unit did they see? What objection surfaced — the price, the floor, the possession date, the view? Sthan logs the visit outcome back onto the lead record, so the rep's next call opens with what happened rather than a cold restart.

Because the visit, the qualification before it, and the booking after it all live on the same record, the rep is never reconstructing the story from memory or a WhatsApp scroll. The sales-pipeline capability carries the visit through the same board as every other stage, so a visit done is visible to the manager, the rep, and the next automation at once.

Booking is where Indian real estate enters its own complexity, and where a generic CRM runs out of road. A booking is not one document or one event. It is an allotment letter, then an agreement to sell, a sale deed later, and — underneath all of it — a construction-linked payment schedule that will govern the relationship for years.

Sthan generates the allotment letter and the agreement draft from templates the builder controls, auto-filled with the buyer, unit, price, and milestone data already on the record. There is no copy-pasting from a Word file into a template into an email; the document is produced from the same data that ran the pipeline. RERA filings and document generation are handled at this stage, RERA-aware throughout — the engine and template library are Sthan's, while the legal review and sign-off stay with the builder's counsel.

The payment-milestone schedule is the spine of everything that follows. Sthan builds it from the construction phases the builder defines. A typical structure might be, for example, ten percent at booking, thirty percent at foundation, thirty percent at slab completion, twenty percent at finishing, and ten percent at possession — but that is only an example. Sthan lets builders configure their own milestone structure, because no two developers stage payments identically, and a CRM that hard-codes one schedule is useless to the next builder.

Setting this up correctly here is what makes the final stage possible at all. Every demand note, reminder, and aging report in the possession tail is generated from this schedule. Get it right once, and the next eighteen to thirty-six months of collections run off it automatically. The RERA documents and collections capabilities both originate at this stage.

This is the stage other CRMs simply do not have. Once the booking is signed, a sales-centric system considers the lead closed and moves on; the twelve-to-thirty-six- month tail of construction-linked collections and possession becomes somebody else's problem, usually an accounts team on a different spreadsheet. That gap is exactly where booked revenue quietly leaks.

Sthan runs the tail as part of the same workflow. Milestone reminders fire automatically as each buyer's next payment approaches, carrying construction photos that show real progress — a buyer who can see the slab they are paying for pays more readily than one staring at a bare demand note. Aging makes the leak visible: which buyers are behind, by how many days, and the total outstanding across a project and across the portfolio, in one number the MD can actually open. Reminders escalate on a ladder — WhatsApp, then email, then a call task for the rep — and every escalation is logged on the buyer's timeline.

Then comes possession itself: NOC clearance, fit-out coordination, possession-letter generation, and handover — the close of the arc the lead began two years and one MagicBricks inquiry ago. The possession letter is generated from the same record, the same templates, and the same data that carried the lead the whole way.

This is the stage where the "lead to possession" framing earns its definition. A booking-centric CRM would have archived this buyer eighteen months before the first demand note went unpaid. By keeping capture, qualification, booking, and collections on one record, Sthan makes the possession tail a managed process rather than a recovery operation — and builders who run it this way describe the difference in concrete terms on the customers page.

One honest boundary: Sthan tracks and flags. It surfaces who is overdue and chases on schedule, but it does not enforce payment or auto-penalise a buyer — when a buyer genuinely defaults, the workout between builder and buyer is a human conversation. The software's job is to make sure no overdue milestone is ever a surprise.