About KeyMatrix
We build the system of record for Indian properties — the gate, the bill, the ledger and the complaint on one flat, so the committee, the manager and the resident are finally reading the same thing.
KeyMatrix is property operations software for Indian housing societies, rental portfolios and property businesses. It replaces the gate register, the billing spreadsheet, the accounting file and the WhatsApp group with one record per unit, so the committee, the manager and the resident all see the same facts.
Why we built KeyMatrix
Every housing society in India runs on the same six systems, and none of them talk to each other. A gate app the guards use, a billing sheet the treasurer maintains, a Tally file at the auditor’s office, a folder of PDFs on somebody’s laptop, a WhatsApp group where complaints are raised, and the memory of whoever has been on the committee longest. Each of them is individually reasonable. Together they guarantee that no two people can agree on what a flat owes.
The cost of that is not the software licences. It is the evening a treasurer spends reconciling a collections app against books kept somewhere else, the AGM that turns into an argument about whose figure is right, and the handover where two years of context leaves with the outgoing secretary. We have watched all three happen often enough to be certain the problem is structural rather than a matter of effort.
The structural fix is a single record per unit. When the gate log, the maintenance bill, the complaint and the ledger entry all point at the same flat, a change in one is a change in all of them, in the same second. Nothing has to be reconciled because nothing was ever separate. That is the whole product, and everything else on this site is a consequence of it.
- Committees are volunteers. The people running a society have day jobs. Software that assumes a full-time administrator will not be used.
- Turnover is annual. Committees change every year. Anything held in one person’s head is lost on schedule.
- The auditor is not optional. Statutory registers and audit-ready books are a legal obligation, not a reporting nicety.
- Residents judge by the app. If the resident-facing side is poor, the committee spends its time defending the system instead of using it.
What we believe about property management
Five positions that decide what we build and, more often, what we refuse to build.
The record is the product
Features are surfaces over data. A visitor log, an invoice and a complaint ticket are three views of one flat and its occupants, and the moment they become three databases the society is back to reconciling. We would rather ship one capability that writes to the shared record than three that maintain their own.
This is also why we are cautious about adding modules. Every new surface has to justify itself against the object model, not against a competitor’s feature list.
Residents are customers, not inventory
A resident app with advertising in it is a resident app that the society is paying for twice — once in subscription and once in the attention of its members. We do not sell resident data and we do not run third-party ads. The subscription is the business model, and it needs to stay the only one for the incentives to point the right way.
Volunteers should not need training
The person who takes over as treasurer next year will get, at best, an afternoon of handover. If a task cannot be worked out from the screen, it will be done outside the system in a spreadsheet, and the record will start drifting again. Ease of use here is not polish; it is what keeps the data true.
Compliance is a feature, not a report
Statutory registers, AGM records and audit exports are the reason a society can operate legally. They should fall out of ordinary work — a meeting held, a bill raised, a payment received — rather than being assembled in a panic before the auditor arrives.
Your data leaves when you do
Export of members, ledgers, bills, documents and logs in open formats is available on request, without a negotiation and without a retention clause designed to make leaving expensive. Software should be kept because it works, not because the exit is painful.
The team
KeyMatrix is built by people with backgrounds in property operations and in software, which is a deliberate mix rather than a coincidence. Product decisions get argued between someone who has run a billing cycle for a 400-flat society and someone who has to model it — and the argument is usually more productive than either view alone.
The work happens close to the people doing it. Managing committees, facility managers, accountants and brokers are involved while a workflow is being designed rather than after it ships, because the gap between how a process is described and how it is actually performed at a gate at eleven at night is where most property software goes wrong.
Onboarding and support are delivered remotely and through regional partners, so a society in a tier-two city is not waiting on a metro schedule to go live.
Work with us
If you run a society, a rental portfolio or a property business and something on this site describes your week too accurately, the useful next step is a demo with your own numbers in it — last month’s billing run and your arrears list. We would rather reproduce your figures than show you ours.
If you implement systems for properties — a facility management company, a security agency, an integrator, a CA practice — the partner programme is how that works commercially, with recurring revenue share rather than a one-time referral fee.
And if you have measured something about how Indian properties actually run, we would like to read it. Benchmarks that contradict us are more useful than ones that agree.
- Evaluating. Book a demo and bring real data — sales@keymatrix.co
- Partnering. Reseller and implementation enquiries — partners@keymatrix.co
- Already a customer. Support and onboarding — support@keymatrix.co
- Privacy and data requests. Our grievance officer — privacy@keymatrix.co