Four WhatsApp groups and one rent sheet: when a PG outgrows its owner

Nobody buys PG software for their first property. Nor should they. One building, eighteen beds, an owner who is on site most days and knows every tenant by name — a spreadsheet and a phone genuinely is the right tool, and anybody who tells you otherwise is selling something.

The interesting question is not whether the spreadsheet works. It is where it stops working, and why, and whether you can see it coming. Because the failure is not gradual. It arrives on a specific week — usually the week you take on a second property, or the week your manager resigns — and by then you are trying to build a system during the exact month you have the least time to build one.

What the spreadsheet is genuinely good at

Be honest about this before you replace it, because if you cannot name what you are giving up you will pick badly.

• It costs nothing and it is already open
• It bends to exactly how you think — your columns, your names, your shorthand for the tenant who always pays late
• It has no learning curve for you and no per-user question to answer
• It is fast for a small number of rows; scanning eighteen names is instant
• It works offline, on a laptop, on a plane, in a power cut
• Nobody can take it away from you or change the price of it

That last one matters more to owners than software companies admit. A spreadsheet is yours in a way that a subscription is not. Any system that wants to replace it has to be worth more than that feeling, and the only honest way to be worth more is to do things the sheet structurally cannot.

WhatsApp deserves the same fairness. It is where your tenants already are, it costs nothing, everyone knows how to use it, and a photo of a broken geyser arrives in two seconds. No system will or should replace it as the channel. What it cannot be is the record.

The four failures that show up at property number two

The second property does not double your work. It roughly triples it, because on top of two of everything you now have coordination between them, and you are no longer physically present at one of them on any given day. Four specific things break, in this order.

• The sheet stops matching reality. With one building you correct it from memory within a day. With two, an entry is wrong for a fortnight before anyone notices, and every downstream number — occupancy, dues, deposits — inherits the error.
• Two people start committing the same bed. The manager at the new property tells a walk-in yes; you tell a broker yes; the sheet was accurate when each of you last looked at it. Double-allotment is not carelessness, it is what happens when inventory has more than one copy.
• Collection softens. Chasing eighteen tenants on WhatsApp is a Sunday morning. Chasing forty-five is a job, and the honest outcome is that the polite ones get chased and the difficult ones get avoided.
• You stop knowing things and start asking about them. Every question — is 204 free, did Rahul pay, is the geyser fixed — becomes a phone call to somebody else. That is the actual tipping point, and it has nothing to do with the size of the spreadsheet.

The spreadsheet did not fail. It was never the system. You were the system, and the spreadsheet was your notepad.

Complaints in a group chat: why nothing is ever closed

A tenant group is the most reasonable idea in PG management and the worst possible place to run maintenance. Not because people misbehave in it, but because of what a chat is: an ordered list of messages with no state.

A complaint posted in a group has no owner, no status and no closing event. It scrolls. Somebody replies will check, which reads as acceptance and commits nothing. Two days later the tenant re-posts, slightly angrier, and now there are two complaints about one tap and no way to tell whether either is resolved. Meanwhile eleven other messages that day are about a birthday and a parcel.

The specific harm is that unresolved complaints do not disappear — they queue up and get presented back to you on move-out day, as the reason a deduction is unreasonable. You cannot argue with that, because you have no record that the tap was ever fixed, and neither does the tenant.

What replaces it is not a fancier chat. It is a complaint that is an object: raised by a named tenant against a named room, assigned to a named staff member, carrying a status you can see, and closed with a date. Tenants can still send you the photo on WhatsApp. Somebody just has to put it somewhere it can be closed. Same for visitors: a paper diary at the gate and a message saying my cousin is coming at 9 is a security posture that works until the one night it does not.

Rent collection: reminders versus mandates

This is the difference that pays for everything else, so it is worth being precise about it. There are two fundamentally different collection models and most PG owners have only ever used one.

The reminder model: rent is due on the 5th, you message people on the 6th, you message the stragglers on the 9th, you call two of them on the 12th, and one pays on the 17th. The work scales linearly with tenants and the effort comes from you. Its real weakness is not the time. It is that it degrades — in a busy month you send fewer reminders, and the tenants who learn that nothing happens on the 6th start paying on the 15th permanently.

The mandate model: the tenant's agreement carries a monthly rent and a due date, and the tenant authorises a UPI AutoPay mandate once. On the due date the rent debits itself and a numbered receipt is raised against it. You are not in the loop and neither is your mood. Your work shrinks to the exceptions — the mandate that failed, the tenant who has not signed up — which is a short list you can actually clear.

Note what changes structurally. Under reminders, collection is an activity. Under mandates, collection is a default and chasing is the exception. That is the difference between a PG that gets harder every property and one that does not.

Who has the data when your manager quits

This is the question that decides it for most owners, and almost nobody asks it until the week it matters.

Your warden knows which beds are free and which ones are promised. His phone has the tenant numbers. The maintenance history is in his head and in a chat thread on his handset. The token amounts he took in cash are in a diary. When he leaves — and in this business people leave — that all leaves with him, and his replacement starts by walking the building with a notebook, reconstructing what you already paid to know.

It is worse when the departure is not friendly. An owner who cannot independently verify who is on which bed, who has paid what, and how much deposit is held for whom is negotiating from a position of ignorance with someone who knows everything.

A system's most underrated function is that it is a place the business keeps its own memory. Not so you can distrust your staff — you need to trust them to run a floor — but so that trust is not the only thing standing between you and total loss of your operational picture.

What a PG system must do on day one to be worth it

Judge any option on this list. If it does these six things properly, the rest is decoration; if it does not, no amount of dashboards will save it.

• Inventory three levels deep — property, room, bed — with a live status per bed, so occupied, vacant, reserved and under maintenance are all visible and only one person's version exists
• A tenant record that carries KYC, the bed, the agreement period, the rent, the deposit and the notice period, moving through enquiry, active, on notice and vacated
• Rent that belongs to the agreement, invoiced monthly with separate lines for rent, food, maintenance and utilities, and a UPI AutoPay mandate so it collects itself
• Deposits tracked per tenant and adjusted at move-out against dues and damages, with the running total you are holding visible at any moment
• Complaints raised from a tenant portal and tracked to closure with an owner, plus visitors logged and pre-approved at the gate
• Gap-free numbered receipts and a GST-ready ledger, so your accountant gets clean books at year-end instead of a reconstruction project

Notice that none of these is exotic. They are the operational spine of a PG, written down. The reason a spreadsheet cannot deliver them is not sophistication — it is that a sheet has no notion of state, no notion of who changed what, and no way to be one shared copy that a warden, an owner and a tenant each see the correct slice of.

What you can safely not buy yet

Vendors will show you things that look impressive in a demo and do nothing for a forty-bed operation. Buy the spine first. Add the rest when a specific problem demands it, not because it was in the brochure.

• Biometric or smart-lock hardware — real value at scale, an expensive distraction while your rent sheet is still the source of truth
• Dynamic pricing — you need a year of honest bed-night history before variable pricing means anything
• A branded booking app for tenants — your tenants will use WhatsApp and a link; a portal for complaints and payments is enough
• Deep accounting inside the PG tool — clean numbered receipts and an exportable ledger for your accountant beat a half-built books module
• Staff attendance and payroll on day one — worth it when you run several properties, noise when you run one

The test for any add-on is simple: name the specific hour of your week it removes, or the specific rupee leak it closes. If you cannot, it is not time yet.

Moving your tenant list across without a bad month

The migration is where owners get hurt, and the mistake is always the same — trying to switch in the middle of a rent cycle. Do it in the gap.

• Pick a cutover date that is the 1st of a month, and treat the previous month as fully closed in the old sheet
• Build the inventory first — properties, rooms, beds — and physically walk the building to confirm it, because the sheet is wrong somewhere and you would rather find out now
• Load tenants next, with their bed, agreement dates, rent and deposit; a wrong deposit figure carried over is a future argument, so check each one against a receipt
• Reconcile deposits held as one number and make sure it matches what you think you owe back
• Run the first month in parallel — new system for real, old sheet as a shadow — and compare the two totals on the last day
• Only after that month reconciles, onboard tenants to the portal and start AutoPay mandates, in batches, starting with the tenants who already pay on time

Two weeks of overlap, one boring month, and you never repeat it. Compare that against the cost of the alternative, which is not zero — it is one double-allotted bed, one deposit argument you cannot evidence, and one manager departure away from a very bad quarter.

The honest summary is this. If you run one property and you are there every day, keep your sheet and read something else. If you are opening a second, or you have started asking other people questions you used to just know the answers to, you have already outgrown it. The only decision left is whether you replace it deliberately, in a quiet month, or under pressure in a loud one.