It Works, Until It Doesn't
There's a property portfolio in Accra — forty-two units across six buildings, generating over $80,000 a month in rent — that is managed almost entirely through WhatsApp.
Maintenance requests arrive in a group chat. Rent confirmations are screenshots forwarded from tenants. Lease renewals are negotiated over voice notes. The property manager keeps a spreadsheet that's updated "when there's time."
This isn't unusual. It's the norm.
And for a while, it works. WhatsApp is fast, familiar, and free. Everyone already uses it. Tenants message when something breaks. The manager responds. Things get fixed, more or less.
The problem isn't WhatsApp. The problem is what WhatsApp can't do — and what happens when those gaps compound at scale.
What Disappears Into the Chat
A group chat has no memory in any operationally useful sense. Messages exist chronologically. They cannot be queried, filtered, assigned, or escalated. There is no way to know, at any given moment, how many open maintenance requests exist, how old the oldest one is, or which properties are generating the most friction.
When a tenant says "I reported this three weeks ago," you have to scroll. When a payment dispute arises, you have to reconstruct a timeline from forwarded screenshots with different timestamps. When the property manager is sick, the handover is: here's my phone.
This is the structural problem. WhatsApp is a communication tool masquerading as an operating system. It captures the conversation, but not the context. It records that something was said, but not whether anything was done.
The Moment It Breaks
Portfolios managed on WhatsApp don't fail gradually. They fail suddenly.
The trigger is usually one of three things: a staff change, a dispute that escalates to litigation, or a growth event — a new property added, an investor brought in, a second location opened. Any of these exposes the underlying brittleness.
The staff change is the most common. The property manager who "knows everything" leaves, and what leaves with them is the entire operating context of the portfolio: which tenants are difficult, which units have recurring issues, which payments always arrive late, which landlord prefers voice calls. None of that is in the system, because there is no system. It's in the chat history on someone else's phone.
What the Transition Looks Like
Moving from a WhatsApp portfolio to a structured operating system feels like a large change. In practice, it's a series of small ones.
Maintenance requests become structured records — assigned, tracked, and closed, with a history attached to the unit, not to a conversation thread. Rent collection becomes a ledger, not a screenshot archive. Communication between manager and tenant still happens, but it's logged against the lease, not lost in a group chat.
The portfolio doesn't change. The visibility into it does.
And visibility, it turns out, is what separates operators who scale from operators who plateau. You can't grow what you can't see clearly. And you can't see clearly through a group chat.