Building your own property management software is, on almost every axis, a bad idea. The tools that exist are mature, they are cheaper than the time, and "we built our own" is usually a sentence that means somebody enjoyed themselves.
We did it anyway, and it is worth being specific about why rather than claiming the general version.
What we were not solving
We were not unhappy with what exists. Off-the-shelf tools do calendars, messaging and cleaning schedules perfectly well, and for most operators they are the right answer.
We were also not chasing a feature. There was no single thing we wanted that we could point at in a comparison table.
What we actually could not get
An owner statement we could defend line by line. The thing an owner is really buying from a manager is the ability to check them. That requires a statement where every figure traces to something — a booking, a receipt, an export — and where last month's numbers do not quietly change when this month's arrive. Most tools produce a report. We wanted a record, and the difference only shows up in an argument.
Separation we could prove rather than promise. We run our own property and we manage for other owners. "Your data is separate" is easy to say and almost impossible to demonstrate from inside an application. We wanted the separation enforced by the database itself, so that being wrong about it would produce nothing rather than produce somebody else's numbers.
Those two are not features. They are properties of a system, and you cannot bolt either onto something you did not build.
Honesty about where numbers come from. Airbnb, Vrbo and Hipcamp publish calendar feeds, not full financial APIs. Availability syncs; earnings arrive in monthly exports and get reconciled. Plenty of software presents the result in a way that implies more than the channels actually give you. We would rather the screen say what it knows and when it last knew it — which is why the listings view shows the last successful sync per channel rather than a green tick.
The ability to see the thing we were relying on. When a calendar feed stops, nothing happens. No error, no alert, just a property that is quietly double-bookable. With someone else's tool you find out when two guests arrive. That was the one that decided it.
What it cost
More than it should have, as always. And it comes with an obligation most people underrate: software you build is software you maintain, forever, including the parts that are boring.
The honest accounting is that this only makes sense because we operate the properties too. If we were purely a software company we would have built something worse and sold it. If we were purely managers we would have bought something and lived with it. It is the combination that pays for it — every screen exists because somebody needed it during a real week, and the ones nobody needed do not exist.
What it does not do
It does not do the parts we do not do:
- It is not multi-tenant SaaS. It runs our properties and our client's, and it is not for sale.
- It does not do live financial sync across channels, because the channels do not offer that.
- It does not replace judgement. It shows you the property is unsold in August; it does not know why.
Why any of this matters to an owner
Because it is the difference between a manager who can show you and one who can tell you.
Everything above amounts to: when you ask a question about your property, there should be an answer with a source attached. What was collected, from where, when it last synced, what was spent and on what, and whether the figure you were sent in February still says the same thing today.
You can look at the actual screens on the platform page, including the console and all four sign-ins — owner, resident, contractor and staff, each seeing only their own view.
If you would rather see it with real data in it than read about it, ask for a walkthrough. We will screen-share the live console rather than a demo tenancy, which is a harder thing to offer and a more useful one to watch.