What is Sthan?

Sthan is a modern customer relationship management (CRM) platform purpose-built for real estate developers, bundled with a complete lead-to-booking automation system. It covers six layers end-to-end: (1) Lead capture from Meta Lead Ads, Google Search Ads, project landing pages, website forms, WhatsApp click-to-chat, missed-call capture, and property portals including MagicBricks, 99acres, and Housing.com; (2) Instant response automation that fires WhatsApp, email, and SMS within 10 seconds of a lead arriving; (3) Lead qualification via chatbots, smart forms, and call automation based on budget, property type, location, timeline, and loan requirement; (4) A 15-day automated follow-up drip across WhatsApp, email, and retargeting; (5) Sales team automation with auto-assignment, no-response escalations, and site-visit scheduling; and (6) A reporting dashboard covering leads by source, cost per lead, qualified leads, site visits, conversion ratio, and ad spend versus inquiries. Sthan replaces the common patchwork of Excel, WhatsApp groups, and legacy CRMs such as DaeBuild, Sell.Do, and generic Zoho setups. Pricing is ₹8,000 per month per active project, or a flat ₹25,000 per month for unlimited active projects (₹2,40,000 per year on annual billing), with no per-user fees. Optional Sthan Growth Services for managed marketing are separate: Social Starter at ₹15,000 per month and Growth Concierge at ₹40,000 per month. 7-day free trial on the first project, no lock-in.

The platform · every module

The real-estate platform that runs the whole lifecycle.

Most CRM comparisons end up counting features. So count these. Nine stages from the first ad click to the final key, and sixty-plus modules underneath them — named, on this page, so you can check the claim rather than take it.

The lifecycle — ad click to final key
MarketCaptureQualifyPipelineSite visitsInventoryBookCollectPossession

A generic CRM covers stages two to four. Sthan covers all nine.

Inside the platform

Eight screens. One source of truth.

These are real captures of the running product, not mockups. Figures are redacted where a buyer's name or number would otherwise be visible.

The module map

Every stage, and what is inside it.

A builder's job does not end at a signed booking, so neither does the product. Here is each stage of the lifecycle with the modules that run it — named individually, because breadth that cannot be checked is just a number in a headline.

  • 9 lifecycle stages
  • 4 layers underneath
  • 60+ modules
  • 1 system of record
Stage 01 — Marketing

Demand you generate, not only demand you receive.

Campaigns are built against the projects and units already in the system, so the spend and the booking it produced end up in the same system instead of two.

Modules
Campaign managementAudiencesGoogle Ads campaignsMeta Lead Ads campaignsSource attribution at captureCost per lead by channel
Stage 02 — Capture

Every source in. One pipeline out.

A lead from a portal, a hoarding QR code and a walk-in all land in the same table, tagged with where they came from. Nothing sits in a salesperson’s phone.

Sources connected
Portal integrationsMagicBricks99acresHousing.comWebsite formsWhatsApp click-to-chatMissed-call captureWalk-in entryBroker submissionsQR capture
Stage 03 — Qualify

Scored, routed and answered before anyone reads it.

The first reply goes out in seconds and the lead is already on the right person’s list. A buyer who enquires at 11pm gets an answer at 11pm.

Runs automatically
AI intent scoringAuto-assignmentRouting rulesInstant response automationDrip sequences
Stage 04 — Pipeline

A pipeline that remembers everything.

Every call, every note, every stage change stays on the lead record. When a salesperson leaves, the history does not leave with them.

Modules
Kanban pipelineLead records with full historyActivity timelineCall logging with mandatory next stepFollow-up remindersNo-response escalationSales-associate day view
Stage 05 — Site visits

The visit that actually got logged.

Check-in happens at the site on a phone, not from memory at the desk two days later. Unlogged visits are flagged rather than forgotten.

Modules
Site-visit schedulingLocation check-inVisit outcome loggingUnlogged-visit alerts
Stage 06 — Inventory

Tower by floor by unit, always current.

One live grid across every tower and every project. A hold expires on its own, so a blocked unit cannot quietly stay blocked for a month.

Modules
Tower × floor × unit gridAvailability statesTime-bound holdsPrice and cost sheetsFloor plansMulti-towerMulti-project
Stage 07 — Booking

A booking is a record, not a WhatsApp message.

The unit changes state, the paperwork is generated from the booking, and the payment schedule exists from day one. Cancellations release the unit back to the grid.

Modules
Booking workflowAllotment lettersAgreement documentsMilestone schedulesCancellation and unit release
Stage 08 — Collections

Construction-linked money, chased on a schedule.

Demands are raised against construction milestones, reminders escalate on their own, and the accounts team works a chase list instead of a spreadsheet.

Modules
Construction-linked payment demandsDemand notesReceiptsAgeing bucketsChase listTiered remindersGST-compliant invoicingPayment recording
Stage 09 — Possession

Through handover — not stopping at booking.

In Indian real estate the booking is roughly halfway. The buyer keeps a portal through construction and the handover runs off a checklist.

Modules
Possession handover checklistPossession lettersBuyer portalConstruction-progress trackingBuyer document access
Underneath all nine

Four layers that run across every stage.

These are not stages, because they never stop. They apply to a lead on day one and to a possession letter three years later.

Channel partners

A partner portal with PIN login, partner sign-up and approval, a commission rate per broker, commission accruing against the booking and its payments, a pay-commission action, broker statements, a leaderboard, channel mix and deal attribution.

Compliance and documents

RERA filing reminders, generated allotment letters, demand notes, receipts and possession letters, a document library, and an audit trail of every status, booking, payment and ownership change.

Reporting and export

Dashboards, sales funnel by stage, bookings by project, collections ageing, inventory status, broker performance, source attribution and cost per lead, scheduled reports, and Excel or PDF export on every report.

Platform and access

Native iOS and Android apps, WhatsApp Business API two-way messaging with templates, role-based access control, your data kept separate from every other builder, an English, Hindi and Gujarati interface, Indian phone-number normalisation, and full data export.

Where the difference is

Seven things a generic CRM cannot give you.

A horizontal CRM will sell you contacts, a pipeline and an automation builder, then leave the rest of the job to you and an implementation partner. These seven are the rest of the job.

Developer-only platform

Sthan sells to one kind of business. Nothing in it is a real-estate template laid over a generic contact database — the unit, the tower, the booking and the demand are first-class records.

Tower and unit inventory

A live tower by floor by unit grid with available, held, booked, sold and blocked states, time-bound holds, price and cost sheets, and floor plans attached to the unit.

Broker and partner payouts

Channel partners sign up, get approved, and log in to their own portal. Commission is set per broker and accrues against the booking and its receipts, so a payout is a record you open.

WhatsApp-native capture

Click-to-chat and missed-call capture create the lead. Two-way messaging on the WhatsApp Business API, with templates you control, carries the follow-ups and the payment reminders.

RERA and regulatory filings

Filing reminders, plus allotment letters, demand notes, receipts and possession letters generated from the booking record, and an audit trail behind every change.

Construction-linked demands

Payment schedules tied to construction milestones, with demand notes, tiered reminders, GST-compliant invoicing and an ageing view the accounts team works from.

Native mobile app

Sthan Sales on iOS and Android — leads, site visits, the inventory grid and call logging for the people who work at the site rather than at a desk.

AI, where it earns its place

Drafts the reply. Never invents the price.

AI in Sthan is bounded by the same records the rest of the platform runs on. That constraint is the feature.

  • Grounded in live inventoryA draft reply quotes the unit and the price the grid actually holds. If a unit is booked or a price is not set, it says so rather than inventing one.
  • Intent scored at captureEvery lead carries a score built from budget, timeline and what happened on the last call — so the day view opens on the people worth calling first.
  • Paperwork pre-filledAllotment letters, demand notes and possession letters come out of the booking record ready for review, not out of a Word template someone edits by hand.
The Sthan sales app drafting a WhatsApp reply with AI. The draft quotes unit A-1204 at ₹2.6 Cr and is labelled 'Grounded in: Rut Heights · unit A-1204 (live inventory). No price or RERA is invented.', with Edit and Approve & send buttons.
AI draft · grounded in live inventory
Sthan Sales · iOS & Android

The platform, at the site gate.

Real estate is sold standing in a half-built tower, not at a desk. The app is not a viewer — leads, site visits, the inventory grid, WhatsApp and call logging all write back to the same records.

A WhatsApp conversation inside the Sthan Sales app with a buyer asking whether a north-facing 3 BHK in Rut Heights is available, the reply quoting unit A-1204 at ₹2.6 crore, and a system line showing the floor-plan PDF was sent and auto-logged against the lead.
WhatsApp thread
A call-logging sheet in the Sthan Sales app after a 4:12 call logged from the phone's SIM, offering interested, thinking or not-now outcomes, a required next follow-up of tomorrow, in three days or a picked date, a note field, and a line reading that a call cannot be closed without setting the next step.
Call logging
The Inventory screen of the Sthan Sales app showing project tabs, a floor-by-unit grid colour-coded available, held, booked and sold, and a detail card for unit A-1203 that hides the buyer name, contact and price because the signed-in role is not permitted to see them.
Inventory in the field
  • The visit is logged where it happensLocation check-in at the site, with the next appointment and the distance to it already on screen.
  • A call cannot close without a next stepOutcome and follow-up date are required fields, which is why follow-ups stop evaporating.
  • Role-aware in the fieldA site executive sees the unit grid but not the buyer name, contact or price. The same rule that runs on the web runs on the phone.
Trust

Your data, handled properly.

You are handing Sthan your buyers' details, your inventory and your money. These are the four commitments that come with that — plainly, and without asterisks.

Separate from every other builderYour projects, leads, buyers and bookings are yours alone. No other builder on Sthan can see them, and you cannot see theirs.
Everyone sees only their partYour site executive, sales manager and channel partner each see what their job needs and nothing more — a partner sees their own leads, a site rep sees the unit grid without the buyer name, contact or price.
Every change is on the recordStatus changes, bookings, payments and ownership moves are all recorded with who made them and when — so a disputed commission is a question you can answer rather than argue.
Yours to take, any timeAsk and you get a full export of your leads, units, bookings, payments and documents. Month to month, no lock-in, and no fee to leave with your own data.

Count the modules. Then count the logins.

One platform, one price, published. No implementation partner, no nine-month rollout.