Pleks

The situation

South African property management is run by an agency in the middle of six different people who each need something different from the same facts. A landlord wants to know what their asset earned. A tenant wants a lease, a receipt and a repair. A prospective tenant wants an answer. A contractor wants a job and an invoice paid. The agent wants the day to close. The regulator wants to see that the trust money was never touched.

The incumbents — WeConnectU, PropWorx, RedRabbit — mostly serve the agent, and everyone else arrives by email, by phone, or not at all. That is not a gap in features. It is that the other five roles were never treated as users.

The second thing about this market is that compliance is not a report you run at month end. POPIA governs data about people who are not the agency's customers — applicants who were declined and never became anyone's tenant. The Property Practitioners Act governs money the agency holds and does not own. Get either wrong and the consequence is not a bad quarter.

I am founder and principal architect. This is my own product, not client work.

What I did

I put all six of them on one platform rather than building an agent tool with portals bolted to it. Each role gets its own namespaced workspace, over row-level data isolation and a three-layer security model, so what a tenant can reach is enforced in the database rather than in the interface that happens to be rendering it.

Compliance is enforced through the stack, not documented beside it. POPIA, PPRA trust-account rules and Rental Housing Tribunal standards are implemented as behaviour — retention that expires on a schedule, immutable audit trails, money that cannot move by a path the software does not permit. A policy a person has to remember to follow is a policy that gets followed until the week it is busy.

Around that: credit-bureau aggregation across five bureaux, digital signing and payments integrated end to end, and WhatsApp Business Cloud API and SMS carried through the platform rather than left to whichever phone the agent had.

AI routes tasks across Anthropic Claude models by complexity — document classification, financial extraction, applicant scoring, legal drafting — behind single-entry enforcement so there is one door into the models and one place the rules apply, with per-call cost tracking. An assistive feature that cannot be costed is a feature nobody can price.

The delivery model is the part that transfers. I work specification-first and delegate implementation to AI coding agents under direct review, committing as I go with explicit rollback paths. The specification is the artefact; the code is the output. That is the same discipline I take into a client's programme, tested on a system where I carry every consequence myself.

What changed

The platform exists and runs: six roles, the compliance behaviour enforced rather than described, and the bureau, signing, payment and messaging integrations working end to end.

The market outcome is not in, and this case will not claim one. Pleks is a product I am building against named incumbents, not a delivered engagement with a number attached. What it is evidence of is the method — a system where the regulatory constraints were designed in from the first schema rather than retrofitted, and where the audit trail exists because it was always going to be needed rather than because someone asked for it.

That is worth more to a reader assessing how I work than a figure I would have to qualify.

What I'd do differently

Pleks is going strong. The thing I would change is how much of it sits with one person.

Every compliance claim has to hold all the way through the stack, or you lose the thing you promised. That has to stay true while you are also making progress on features, thinking about whether the flow is efficient for the person actually using it, making it good enough to look at that people trust it, keeping it working — and staying ahead of incumbents who have more people than you do.

Those are not one job. They are four or five, and I have been doing them sequentially in a single head, which means each one waits while another has attention.

I would bring someone in earlier — not to write more of it, but to own one axis properly, most likely the compliance verification, because that is the part where being nearly right is the same as being wrong. Solo is the right way to start. It stops being the right way sooner than it feels like it does.