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: Lead Capture Pro at ₹15,000 per month and Marketing Concierge at ₹40,000 per month. 7-day free trial on the first project, no lock-in.

Guide · RERA

Lead tracking audit trail for RERA compliance.

When a buyer dispute reaches RERA, it turns on records — who was told what, and when. A durable audit trail is how a real estate developer answers that with evidence instead of memory. Here's what to log, and what makes it defensible.

Why does an audit trail matter for RERA?

A lead-tracking audit trail is a durable, timestamped record of everything that happened on a lead and booking — communications, document versions, status changes, and who made them. It matters for RERA because disputes are resolved on the documentary record: a developer who can show exactly what a buyer was told, which demand notes went out, and when possession updates were sent, is in a fundamentally stronger position than one relying on recollection.

It's the evidentiary backbone of the RERA-compliant lead management this cluster covers — and the part a generic CRM, with loose editing and no version history, most often gets wrong.

What a compliant audit trail should capture

  • Communications. The WhatsApp, email, and SMS messages sent to and from a buyer, with timestamps — so what was promised is on the record.
  • Document versions. Every allotment letter, demand note, receipt, and possession letter generated, with the version and the data it was filled from.
  • Status and ownership changes. Each pipeline stage change, each reassignment, and who made it — the chain of custody on the lead.
  • Booking and payment events. The booking, the milestone schedule, and each demand and receipt, tied to the unit and the buyer.
  • Channel-partner attribution. Which partner was credited, when, and under what rule — the basis for resolving a commission dispute.

The principle: if it could be questioned later, it should be logged at the time.

Integrity and retention

A log is only evidence if it can't be quietly rewritten. A defensible audit trail is append-only or versioned — changes are recorded as new entries rather than overwriting the old — and retained for the life of the project and beyond, since RERA obligations and possible disputes extend well past the sale. It should be exportable, so you can produce it if an authority or a buyer asks. The actionable system requirements sit in the requirements checklist, and the filing workflow it supports is in automated RERA filing. This is general information, not legal advice.

RERA audit trails, answered.

Why does RERA make a lead audit trail important?

Because RERA disputes are resolved on the documentary record. A durable, timestamped audit trail lets a real estate developer show exactly what a buyer was told, which demand notes went out, and when possession updates were sent — evidence that is far stronger than recollection. It is the evidentiary backbone of RERA-compliant lead management.

What should a RERA audit trail log?

Communications (WhatsApp, email, SMS with timestamps), document versions (every allotment letter, demand note, receipt and possession letter with the data it was filled from), status and ownership changes (each pipeline move and reassignment, and who made it), booking and payment events, and channel-partner attribution. The rule of thumb: if it could be questioned later, log it at the time.

How long should audit-trail records be retained?

For the life of the project and beyond, since RERA obligations and possible disputes extend well past the sale. The trail should also be append-only or versioned — changes recorded as new entries rather than overwriting the old — and exportable, so it can be produced if an authority or a buyer asks. Confirm specific retention requirements applicable to you with a professional.

Can a generic CRM provide a RERA-grade audit trail?

Often not well. Generic CRMs frequently allow loose editing without version history, so records can be changed after the fact — which undermines their evidentiary value. A defensible audit trail needs append-only or versioned logging of communications, documents, and status changes, which is something vertical real-estate systems are more likely to model.

Keep a trail you can actually defend.

Published pricing, a 7-day free trial, and onboarding within 24 hours.