There’s a moment, usually around 4pm when ZESA cuts and the whole suburb switches to mobile data, when the network goes from usable to useless. A WhatsApp message takes 90 seconds to send. A photo upload fails three times before going through. An email sits in the outbox for an hour and you only notice when you're already home.
For most office jobs this is a small irritation. For an estate agent showing a property in Borrowdale while three other buyers are texting questions about a different listing, it's the difference between a deal and a missed deal.
This is the reality we built Propertyzone for.
Before Propertyzone, the matching problem in Zimbabwean real estate was solved by hand, in WhatsApp groups. An agent would post "Looking for 3-bed in Mt Pleasant under 180k for a serious cash buyer" into a group of forty other agents. Sometime in the next six hours somebody who had a 3-bed in Mt Pleasant for 175 would reply. Or not. Often the listing had already gone under offer two days earlier and nobody had updated the group. The matching worked, sort of, but it ran on memory, on attention, and on whoever happened to be looking at their phone at the right time.
We didn't want to replace that workflow. We wanted to make it instant.
The way it works on Propertyzone now: when an agent registers a buyer or renter, they note what that lead actually wants. Suburb. Price range. Bedrooms. Buy or rent. The system holds onto it. The moment a listing goes live that matches the criteria, the agent who registered the lead gets a notification, with the listing reference and the listing agent's contact details. The reverse also works. When a new lead is registered that matches an existing listing, the listing agent gets pinged the same way.
What used to take six hours in a WhatsApp group now takes about thirty seconds. The agent who responds first wins the conversation, and the conversation moves to where it was always going to move anyway.
Which is WhatsApp.
We send those notifications through WhatsApp deliberately, not through email and not through an in-app push that the agent will see two hours later when they remember to open the app. Agents already live on WhatsApp. They negotiate on WhatsApp. They share photos and floor plans and bank confirmation slips on WhatsApp. Asking them to open a new app every twenty minutes to check for matches was never going to work. So the notification meets them where they already are, with the listing reference and a one-tap reply that opens a conversation with the other agent.
Nothing exotic about it. Just removing friction from a workflow that already existed and adding speed where speed was the missing piece.
The other half of the problem is the network itself.
A property viewing in Borrowdale at 4:30pm runs into the same connectivity wall everyone else does. The agent has the buyer in front of them, the buyer asks "what else do you have in the area," and the listings page won't load. By the time it does, the buyer has lost interest or is on the phone to a competing agent who happened to load their app five minutes earlier when the network was better.
We solved this by holding onto the data on the device. Listings the agent has looked at recently, the lead notes they've made, the draft messages they're composing, all of it stays accessible whether the connection is there or not. When the network comes back, everything syncs. Drafts go out. Updates pull in. The agent never had to know any of it failed.
This is the bit that took the longest to get right. Caching is easy. Caching the right things, expiring them at the right time, and resolving conflicts when two agents have edited the same listing from different phones on flaky connections, that's where the actual work was.
Building software for African markets isn't about porting Western SaaS and hoping it survives the trip. It's about looking at the conditions people actually work in and engineering around them on purpose.
Connectivity that drops three times an hour is one of those conditions. So is the fact that agents already collaborate on WhatsApp. So is the fact that a deal moves from "interested" to "signed" in two days if the agent responds inside an hour, and dies quietly if they take twenty-four.
Propertyzone is built around those conditions, not despite them. The matching engine wins the agent the lead. The WhatsApp delivery means they actually see it. The offline cache means they don't lose the next ten minutes to a loading spinner.
It's a less glamorous way to build software. Nobody writes case studies about cache invalidation. But it's the thing that makes the difference between a property platform that gets used and one that gets installed and forgotten.
Most of the agencies on Propertyzone today were running the manual version of this in their WhatsApp groups before we showed up. They didn't need to be sold on the idea of matching leads to listings. They needed it to be faster than what they already did, and to work on the days when nothing else does.
That's the bar.
Building something like this?
We build platforms, internal tools, and integrations for Zimbabwean and African businesses. Outcome-tied pricing, two-week paid discovery.