Real estate CRM pricing in India: a transparent guide to cost and ROI for builders

Per-user pricing carries an assumption inherited from general-purpose software: that everyone with a login is on your payroll. Indian real-estate sales breaks that assumption, and it breaks it in the place that matters most.

Start with the channel problem. For many builders, brokers and channel partners produce a large share of qualified bookings, and a partner is only useful inside the system if they can log into it — to submit a lead, watch their own pipeline, and see what commission is owed. Under per-user pricing, every partner you onboard is another billed seat. So the bill grows fastest exactly when the channel is working, and the rational-looking response is to stop handing out partner logins — which is the opposite of what a channel-led sales motion needs. The same logic runs through the buyer side: a portal where a buyer follows construction progress, payments and documents is worth having, and worth nothing at all if every buyer costs a seat.

Put numbers on that, because it is the part a headline rate hides. Take a desk of five with twenty active channel partners submitting leads — an illustration, not a survey, but the shape a channel-led builder works in. That is twenty-five logins. At the ₹500 to ₹2,500 per-user band above, the bill runs ₹12,500 to ₹62,500 a month, and ₹10,000 to ₹50,000 of that is for partners rather than for anyone on your payroll. The same team on Sthan is the ₹14,999 Growth tier — five staff seats, twenty partner logins at no charge — and it does not move when the twenty-first partner signs up. Line up the five staff on their own and the per-user band lands at ₹2,500 to ₹12,500, under that tier, and we would rather say so than dress it up. The whole difference is the channel, and the channel is where a large share of an Indian builder's bookings comes from.

Then the launch-season problem. A builder might run an eight-person sales team through the quieter months, then scale to twenty-four or more reps for an October–November launch around the festival season, when buying intent peaks. Under per-user pricing, the CRM bill triples at precisely the moment marketing spend, inventory load, and site-visit volume are already at their highest. The tool meant to help close the launch becomes one more cost that scales against the builder.

There is also the phantom-user problem. Sales has high churn. Reps leave, but their seats often linger on the invoice for months, because nobody reconciles the licence count against the actual roster. Builders routinely pay for users who left two quarters ago.

Sthan is priced per seat as well — it would be dishonest to claim otherwise — but a seat is one of the builder's own staff: an owner, a sales head, a sales executive, someone in accounts or the back office. Brokers, channel partners and buyers get their own portal logins, unlimited and free, on every plan, and are never counted. The plans are bands rather than licence counts — ₹6,999 for 1–3 staff, ₹14,999 for 4–8, ₹24,999 for 9+ — so a rep who leaves does not leave a billed seat behind, and a desk that goes from eight people to twenty-four for a launch moves up one band, once, and then stops, because the top band is open-ended. The price is anchored to the size of your own team. It is never anchored to the size of your channel.

Sthan publishes three CRM plans. All three include the whole product; they differ in one thing only — how many of the builder's own staff need a login. The number of projects does not enter into it, and neither do brokers, channel partners or buyers.

The return on a CRM is not abstract. It reduces to one formula: additional bookings closed, multiplied by the average margin per booking, minus the cost of the CRM. Everything else is detail.

The mechanism behind those additional bookings is usually the same — fewer leads lost to follow-up gaps. In unmanaged Indian real-estate pipelines, 30 to 40 percent of leads leak, not because they were unqualified but because nobody followed up in time. Recovering even a fraction of that leakage pays for the software many times over. Three scenarios make this concrete. The numbers are typical industry patterns, not Sthan customer results.

The monthly licence is rarely the whole bill. Five costs tend to surface only after a contract is signed.

Implementation and onboarding fees are often quoted separately, or not at all, in the first pricing conversation. A low monthly rate can carry a one-time setup charge that dwarfs several months of subscription.

Per-user scaling, again. As the second section described, a per-login bill inflates through every launch-season hire and every channel partner onboarded, so the price agreed in a quiet quarter is not the price paid during the quarter that matters. Ask any vendor, in writing, whether a broker portal login and a buyer portal login are billed as users — the answer belongs in the comparison, not in the first invoice.

Data-export charges are the one that stings most. Some CRMs charge a builder to export the builder's own leads, bookings and payment records — which turns a switching decision into a literal fee and makes the data feel rented rather than owned.

Per-integration fees compound. A charge per connected source looks minor until it is multiplied across MagicBricks, 99acres, Housing.com, Facebook and Google, each billed as its own add-on.

Renewal repricing is the slow one. An attractive first-year rate that jumps at renewal is common, and the jump arrives after a year of data and habit have made leaving expensive.

Sthan's pricing page lists every fee a builder will pay. The three plan prices above are complete: there are no implementation fees, no export fees, no per-integration fees beyond what telecom providers charge for SMS and WhatsApp pass-through, and no charge at all for a broker, channel-partner or buyer login. On cancellation, the builder receives a full data export — the records belong to the builder, not to the software.

The right plan depends less on features than on the shape of your own team. A practical way to choose:

A founder-led desk — 1–3 staff who need a login

Look for monthly contracts with no annual lock-in, a genuine trial, native lead capture from MagicBricks, 99acres and Housing.com, and a clear path from inquiry to booking. Avoid anything that demands an annual commitment before the first project has proven out. Sthan's Starter plan at ₹6,999 a month, with a 7-day free trial, fits this segment — and the brokers who bring you most of the enquiries cost nothing to bring inside it.

A full in-house sales team — 4–8 staff

This is the point where the channel question decides the bill. Look for a broker portal that brokers will actually log into rather than a glorified spreadsheet, a buyer portal for post-booking engagement, and RERA filings and document generation — then ask what each of those logins costs. Sthan's Growth plan at ₹14,999 a month covers 4–8 of your own people, with the partner and buyer sides free however wide they get, and yearly billing saving 2 months.

Multiple site teams and a back office — 9+ staff

Reporting depth matters most at this scale — conversion and inventory data at project, source and rep granularity, so leadership can see which campaigns and which people are actually selling. Sthan's Pro plan at ₹24,999 a month covers 9+ staff with no upper limit, across any number of projects; builders who also want their campaigns managed can add Growth Services.

Multi-state operations, or a non-standard requirement

Custom enterprise arrangements, with custom integrations and dedicated support, may serve better than standard SaaS plans. This is not on the standard pricing page; the right step is a direct conversation with the team.

For most builders the decision is quick: count the people on your own payroll who need to log in, ignore every broker, channel partner and buyer, and check the published price against this guide. The pricing page has the standard plans; for anything outside them, talk to the team.