How to choose society management software in India (2026 buyer’s guide)
A practical checklist for RWA and AOA committees evaluating society management software — pricing, security, billing, data ownership, and more.
Choosing society management software is one of the more consequential decisions an RWA or AOA committee makes. Get it right and you simplify collections, gate security, accounting, and resident communication in one place. Get it wrong and you’re either locked into a vendor for years or migrating all over again after 18 months. This guide walks through the criteria that actually matter, the red flags to watch for, and the questions every committee should ask before signing anything.
Pricing transparency
The standard pricing unit in India is per-flat per-month. Most reputable vendors publish a number; some refuse to until a sales call. If a vendor won’t show you a price without speaking to a salesperson first, treat that as a significant red flag — you’re likely to face surprise fees later.
Beyond the headline rate, ask what’s included and what’s an add-on. Common hidden costs include payment gateway fees, SMS OTP charges billed per-message, setup or onboarding fees, and annual contract lock-ins with cancellation penalties. GST at 18% is charged on top of the software fee for most vendors — confirm whether the published price is exclusive of GST.
A vendor with nothing to hide publishes their pricing page publicly. Tiers are fine — opaque “contact us for pricing” for a standard residential society is not. Ask specifically: is there a setup fee? a cancellation fee? what is the payment gateway pass-through rate?
For context: GateKeeperZero publishes its pricing openly. There are no setup fees, no cancellation fees, and no lock-in. The Standard plan is ₹9 per flat per month (plus GST); Premium is ₹15. For societies with fewer than 300 flats, custom pricing applies — they state this on the pricing page rather than hiding it. There is also a free plan with a 90-day free trial that requires no payment card.
Visitor and gate security
Gate management is often the feature that drives committee buy-in because it has an immediate, visible effect on security. The core workflow — visitor pre-approval, OTP or photo capture at entry, guard logging — is table stakes. The differentiating questions are about edge cases.
- Does the guard app work offline or with degraded connectivity? Apartment gate areas often have poor signal. A system that goes blank when the internet drops is a liability.
- How are deliveries and cab arrivals handled? These are high-volume, low-friction flows that need a separate path from visitor approvals.
- Can residents pre-approve frequent visitors (domestic help, family) without re-approving every time?
- Is there photo capture at entry, and is it stored in a retrievable log for incident review?
- Does the guard interface require significant training, or is it simple enough for any guard to use without a smartphone background?
GST-ready billing and accounting
Maintenance billing is the financial core of every society. An RWA is expected to issue GST-compliant invoices to residents and maintain auditable books of accounts. Many older or cheaper systems treat billing as a simple ledger without proper invoice formatting, which creates compliance headaches at AGM time or during a tax audit.
Ask specifically whether the system generates invoices that satisfy GST requirements — with the society’s GSTIN, HSN/SAC codes, and a proper tax breakdown. Then ask whether the accounting layer is a simple cash register or a double-entry general ledger. Double-entry accounting produces a proper trial balance, balance sheet, and income statement, which is what an auditor or AGM expects. A cashbook alone is not sufficient for statutory compliance in most states.
For online collection, confirm which payment methods are supported (UPI, net banking, credit/debit cards), what the convenience fee or gateway pass-through looks like, and whether reconciliation is automatic or manual.
A cashbook records money in and money out. Double-entry accounting creates matching debit and credit entries for every transaction, enabling a proper audit trail, fund-level reporting, and a statutory balance sheet. For an RWA with a corpus fund, sinking fund, and operating fund, double-entry is the right tool — ask whether the vendor supports it before assuming it does.
Data ownership and export
This criterion is under-asked and critically important. Your society’s financial records, resident directory, visitor logs, and communication history belong to your society — not to the software vendor. Before signing, establish three things clearly.
- Can you export all your data at any time in a usable format (CSV, Excel, PDF)? Not just on request to support, but self-serve?
- Where is the data hosted, and what are the backup and recovery arrangements? Clear answers here matter for practical recovery scenarios.
- What happens to your data if you cancel? Is there a defined offboarding window, or does your data disappear immediately?
Red flag: a vendor who makes data export difficult, charges for it, or has vague contractual language around data ownership after termination. Reasonable vendors make export easy because they’d rather retain you on merit.
Mobile apps for residents and guards
Almost every vendor claims to have a mobile app. Ask a more specific question: how long has the app been in production with real societies? A six-month-old app used by a handful of pilot societies is a different product from one that has been running at scale for years. Ask about the app’s release cadence, known limitations, and how bugs are reported and fixed.
For residents, the minimum useful feature set is: view and pay maintenance bills, raise service requests, receive notices, and manage visitor approvals. For guards, the minimum is: log visitors, handle deliveries, and use the app reliably without needing a data connection at every step.
An honest vendor will tell you what’s in beta, what’s planned, and what’s not yet built. GateKeeperZero, for instance, states clearly that both the resident and guard mobile apps are in active beta — they are included free once released, but committees evaluating those features today should factor in the beta status.
Support, onboarding, and migration
Software is only as useful as the committee’s ability to get it running. Data migration — importing your existing flat register, member directory, ledger balances, and outstanding dues — is the hardest part of any switch. Ask who does the import (vendor team or self-service), how long it typically takes, and whether it is included in the price.
- What are the support hours and channels? Is it email-only, or is there phone or chat support during business hours?
- Is there a dedicated onboarding manager for the initial setup, or are you handed a help centre link?
- How is ongoing training handled for committee members who rotate every year?
- What is the SLA for critical issues like billing failures or gate system outages?
Privacy: ads and data monetisation
A small number of free or low-cost society apps are subsidised by showing residents advertisements or by selling aggregated data. Your residents’ contact details, spending patterns, and movement data are valuable to third parties. Before recommending a platform to your residents, confirm whether it shows ads within the app and whether resident data is ever shared with or sold to advertisers or third parties. This should be addressed explicitly in the vendor’s privacy policy, not just verbally.
Trial and total cost of ownership
A demo is not a trial. In a demo, a salesperson controls the environment. In a real trial, your committee attempts to use the product to complete actual tasks — creating invoices, logging a visitor, setting up a notice — and discovers the friction points firsthand. Ask whether there is a self-serve trial that doesn’t require a salesperson to hold your hand.
On total cost: add up the per-flat monthly fee, GST, payment gateway pass-through on collections, SMS costs, any per-user charges for committee members, and the cost of support tiers. A plan that looks cheaper at the headline rate can end up more expensive once payment fees and per-message charges are included.
The committee that asks the hardest questions before signing will have the fewest regrets after going live. A vendor worth working with will welcome scrutiny, not deflect it.
Questions to take into any vendor demo
Print this list and use it as a checklist in every evaluation call.
- What is the all-in monthly cost per flat, including GST, and what exactly is excluded from that price?
- Is there a setup fee, a cancellation fee, or a minimum contract period?
- Can we export our complete data — financials, member list, visitor logs — at any time, self-serve?
- Where is our data hosted, and what is your data retention and deletion policy when we cancel?
- Does your accounting module produce a double-entry general ledger and a balance sheet, or is it a cashbook only?
- Are your invoices GST-compliant, and do you support online collection via UPI and cards?
- Does the guard app work offline, and what happens to gate logging during a network outage?
- What mobile apps exist today, and which features are in beta or on the roadmap?
- Who handles our data migration, how long does it take, and is it included in the price?
- Do you show ads to residents, or share resident data with any third party?
- Is there a self-serve free trial — not just a demo — so we can test before paying?
Want to see transparent, published pricing instead of a sales quote? Start here.
View pricing