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 per staff seat: ₹6,999 per month for 1–3 staff, ₹14,999 for 4–8, and ₹24,999 for 9 or more, with every feature in every plan. Only your own staff count as seats — brokers, channel partners and buyers get unlimited free portal logins, so the bill does not move when you onboard a channel partner. Yearly billing charges 10 months, which is 2 months free. 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, no lock-in.

The Hidden Cost of Per-User CRM Pricing for Indian Real Estate Developers

Almost every CRM you'll evaluate is priced the same way: per user, per month. It's the default of the software industry, and on a demo it sounds reasonable — a few hundred to a couple of thousand rupees a head. The problem isn't the number on the slide. It's that real-estate sales teams don't stay one size — and that in this industry the people who need a login are not all people you employ. Per-user pricing quietly charges you for both.

This isn't an argument that per-user pricing is a scam. For some teams it's genuinely the cheapest option, and we'll say exactly when below. It's an argument for doing the full math before you sign, because the per-seat figure hides two things at once: how many seats you will really end up with, and whose seats they are.

What does per-user pricing actually cost?

Start with real, published numbers. Zoho CRM — one of the most popular choices in India — publishes its pricing at ₹800 per user per month for Standard, ₹1,400 for Professional, and ₹2,400 for Enterprise, with a free tier for up to three users. HubSpot's Sales Hub, for international context, runs from a $9-per-seat Starter to $150 per seat for Enterprise. Vendor comparisons of Indian real-estate CRMs commonly put the going rate somewhere in the ₹400 to ₹1,500 per-user-per-month band.

Standard ₹800, Professional ₹1,400, Enterprise ₹2,400 per user per month.₹800Standard₹1,400Professional₹2,400Enterprise
Zoho CRM list price, per user / monthStandard ₹800, Professional ₹1,400, Enterprise ₹2,400 per user per month.Source: Zoho CRM published pricing (as cited in post)

Now put a team on it. Ten people — a sales head, a few closers, a couple of tele-callers, a CP coordinator, a marketing hand — at the low end of that band is ₹5,000 a month, or ₹60,000 a year. At ₹1,500 a head it's ₹15,000 a month, ₹1,80,000 a year. Same team, same software, and a three-times spread depending only on which plan and provider you land on. That's before anyone has added a feature.

A ten-person team costs ₹60,000 a year at the low end of the per-user band and ₹1,80,000 at the high end — a threefold spread for the same software.Low bandHigh band10 users × 12 months₹60,000₹1,80,000
Same 10-person team, one year — low vs high per-user bandA ten-person team costs ₹60,000 a year at the low end of the per-user band and ₹1,80,000 at the high end — a threefold spread for the same software.Source: Worked example in post (₹400–₹1,500/user band)

The figure that gets quoted on the demo is almost always the per-seat one in isolation — "just ₹1,200 a user." Multiplied by a real team and twelve months, it's a materially different conversation.

What happens when the team flexes?

Here's the part the per-user model handles worst, and it's specific to how property actually sells. Real-estate sales headcount is not flat. It spikes for a launch and contracts after. You bring on closers for a new tower, hire seasonal staff for the festive buying season, add a few tele-callers when a campaign floods the top of the funnel — and then, months later, the team shrinks again.

Under per-user pricing, every one of those temporary people is a permanent-feeling line item while they're on. Add five launch-season closers to that ten-person team and your CRM bill jumps fifty percent overnight — for staff who might be gone in a quarter. Worse, the friction runs the wrong way: at the exact moment you want every closer in the system so no lead leaks during your busiest weeks, the pricing model makes adding them a cost decision. Teams respond by under-licensing — sharing logins, leaving the seasonal hires out of the CRM, working launch leads in a side spreadsheet — which quietly recreates the lead-leakage the CRM was bought to prevent.

The per-user model, in other words, taxes you most precisely when you're growing, and nudges you toward exactly the behaviour that loses leads.

+50%
jump in the monthly CRM bill from adding five launch-season closers to a ten-person team — for staff who may be gone in a quarter.
Worked example in post

What costs does the per-seat number hide?

The licence is only one line of the real bill. Four more rarely make it onto the comparison slide, and the first is the one that catches property companies hardest:

The users who are not your employees. A real-estate CRM does not only hold your staff. Your channel partners need a login to submit leads, see what happened to them and check what they are owed. Your buyers need one too, wherever the platform gives them a portal to follow construction, payments and documents. A per-user vendor makes no distinction between those people and your sales head — a login is a login — so the account you were quoted for on a ten-person sales desk is not the account you will be running a year later. And the growth lands at the worst moment: the bill rises exactly when the channel starts producing, which makes the cheapest-looking response "give fewer partners a login." That is precisely backwards for a business that sells through its channel, and it is the same self-defeating economy as leaving the seasonal closers out of the system.

Setup and configuration. A general-purpose CRM has to be shaped into a real-estate tool before it's useful — modules, layouts, stages, document templates. That's either your time or an implementation partner's fee, and it's a real cost the monthly per-seat figure excludes.

Integration. Connecting the portals, your WhatsApp number, your ad accounts, and telephony is often where "it's only ₹1,200 a user" turns into add-on tiers, third-party connectors, or developer time.

Training and adoption. Every seat you pay for only returns value if the person uses it. A complex platform with a steep learning curve means weeks before a tele-caller is productive in it — and seats that sit half-used are pure cost.

Counted honestly, the cost of a per-user CRM is every seat times twelve months — including the seats that belong to people who are not on your payroll — plus setup, plus integration, plus the adoption drag. The headline per-seat number is the smallest of those for many teams.

Is there an alternative to per-user pricing?

The alternative isn't a smaller multiplier. It's a different answer to the question of who the price counts. Sthan counts your own staff and nobody else: a seat is an owner, a sales head, a sales executive, an accounts or back-office person — anyone on your payroll who logs into Sthan itself. Brokers and channel partners get their own portal login to submit leads, follow what happened to them and see commission owed. Buyers get a portal to follow construction, payments and documents. Both are unlimited, both are free, and neither is ever counted as a seat. The published tiers are ₹6,999 a month for 1–3 staff, ₹14,999 for 4–8 and ₹24,999 for 9+ staff, with every feature in every tier — so the tier decides how many of your own people can log in, and nothing else.

That fixes the incentive in the place it does the most damage. Onboarding a partner costs nothing, so you onboard them and route the submission through the system instead of through somebody's WhatsApp thread, and a channel that is working never shows up as a bill that is growing. The top tier is flat above nine staff, so the launch-season closer and the seasonal tele-caller don't move it either — the people you were tempted to keep out of the CRM go into it. The full reasoning, and a like-for-like breakdown of what a CRM actually costs you across a year, is in our pricing and ROI transparency guide.

Which pricing model should you choose?

Be honest about your own shape, because per-user genuinely wins for some teams. If you have three or fewer users, Zoho's free tier is hard to beat and you should take it. If your team is tiny and stable — say two or three people who never flex with launches, selling direct with no channel network behind you — a low per-seat plan can work out cheapest, and you should run that math rather than assume otherwise.

Past that, the question that decides it isn't which model has the nicer name. It's who the price counts. Write two lists before you sign. The first is the people on your payroll who need a login: the sales head, the closers, the tele-callers, accounts, the back office. The second is everyone outside it who also needs one: every channel partner you work with today, every partner you hope to sign next year, and your buyers if the platform gives them a portal. A per-user vendor bills both lists. A staff-seat vendor bills only the first. The trap isn't that per-user pricing is dishonest. It's that it's quoted as a single small number against the first list, while the real bill is that number against both — and the second list is the one that grows when your sales are going well. Do the full math — seats times twelve, plus setup, integration, and the cost of the people you'll add at your busiest — and then ask each vendor the blunt version of the question: is a broker login a billed user? For a small fixed team selling direct, you might still pick per-user. For a real estate operation that sells through its channel, the model to want is the one that charges for your own staff and leaves the partners and the buyers alone.

Key takeaways

  • Per-user pricing is quoted as one small per-seat figure; the real bill is that figure times a team that never holds still.
  • Real-estate headcount spikes for a launch and shrinks after, so per-user cost climbs exactly when you grow — and tempts teams to under-license and leak leads.
  • The per-seat number hides setup, integration, and adoption costs that never reach the comparison slide.
  • Per-user wins for a small, stable team; three or fewer users fit Zoho's free tier.
  • The sharper question is who gets counted: a per-user vendor bills every login, and in real estate most logins are channel partners and buyers rather than staff — Sthan counts your own staff only and leaves partner and buyer logins free and unlimited.

Frequently asked questions

Is per-user CRM pricing always more expensive?
No. For a small, stable team — three or fewer users fit Zoho's free tier — per-user can be the cheapest option. It turns expensive once your headcount flexes with launches, because every temporary closer becomes a recurring charge.
Why does per-user pricing hurt real-estate teams in particular?
Real-estate sales headcount isn't flat; it spikes for a launch and contracts after. Per-user pricing charges you most when you're growing, and pushes teams to share logins or leave seasonal hires out of the CRM — which recreates the lead leakage the CRM was meant to stop.
What costs does the per-seat price leave out?
Three: setup and configuration; integration with your portals, WhatsApp, ad accounts, and telephony; and training and adoption. For many teams the licence is the smallest line of the real bill.
Do brokers and channel partners count as billed CRM users?
In a per-user CRM, yes — a login is a login, so every channel partner you onboard adds to the monthly bill, and so does every buyer where the platform gives buyers a portal. That is the point at which builders start rationing partner logins to hold the bill down, which is backwards for a business that sells through its channel. In Sthan a seat is one of your own staff; brokers, channel partners and buyers get their own portal logins, unlimited and free on every tier.
How should I compare the two models before signing?
Write two lists. First, the people on your payroll who need a login. Second, everyone outside it who also needs one — every channel partner you work with now, every partner you want next year, and your buyers if the platform gives them a portal. Then ask each vendor which list the price is charged on, and multiply by twelve, adding setup, integration and the people you'll add at your busiest month. A small fixed team with no channel network may still pick per-user; an operation that sells through partners should not be buying a bill that grows with its own channel.
Keep reading

More from the blog.

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

In Indian real estate the booking is roughly halfway. A CRM that stops at "won" hands inventory, construction-linked collections, broker payouts, RERA paperwork and handover back to spreadsheets — here is the nine-stage checklist to hold any vendor to.

Where this connects to Sthan.

Sthan charges for your own staff and nobody else — every broker, channel partner and buyer gets a free login. The full working is on the pricing and ROI page.