The problem
Coordination is where the week goes.
Leasing, resident issues, compliance, reporting, chasing the follow-through across buildings. Most of it is not the work anyone was hired to do, and none of it is the work anyone is promoted for. It is the tax on doing the real job.
The answer is not another system to log into. It is something that carries the coordination inside the systems you already run, and hands back to a person the moment judgement is required.
Who this is for
Three kinds of team, one kind of load.
Build-to-rent operators
Leasing follow-up, arrears, resident issues and the weekly report. Agents that carry the coordination alongside your property management system, never replacing it.
See howProperty
Owners, developers and asset teams: contractor onboarding, approvals and delegations, and the executive reporting that eats a fortnight of somebody's month.
See howConstruction
Estimators, quantity surveyors and contract administration: takeoff under time pressure, variations, requests for information, progress claims and time bars.
See how- Two decades of enterprise Microsoft delivery
- Federal government, civil construction, property and development
- You own the tenancy and the data
- Data resident in Australia
- A human always in command
What I build
Three sizes, depending on where you are.
Start at the smallest thing that is genuinely useful. Each size is a real answer, not a step on a ladder you are expected to climb.
- 01
An agent
One assistant doing one job for a team, inside the licensing you already hold. The smallest thing that is genuinely useful, and the fastest way to find out whether an idea survives contact with real work.
- 02
A workflow
An agent plus the connected steps and approvals around it. Work moves through the systems that already hold it, a person approves what matters, and the record of what happened is written as it goes.
- 03
An agentic system
Multiple agents with real authority inside real boundaries, built in your own subscription. Each has its own identity, its own bounds and its own audit trail, and the whole thing stays answerable to a person.
The reference build
See the method working before you commission anything.
BTR OS is a complete governed build-to-rent operations platform, built solo end to end to prove the method. It has no paying customers and no live operators: it is a reference build, not a product for sale.
Walk through BTR OSThe doctrine
- The human is always in command.
- Authority is delegated, bounded and auditable.
- The system is grounded in how the person actually works.
- Every interaction returns capability to the person.
- The measure of every build is one question: did this make the person more capable?
Start with a conversation.
Tell me where the week goes and I will tell you honestly whether this is worth building. If it is not, that is a useful answer too.