Running Short Stays on Systems, Not Spare Hours

A single property can be run out of an operator’s spare hours: answer every message personally, meet every tradesperson, restock every weekend. It works — right up until the second property, a holiday, or a demanding day job. Portfolios that survive are the ones that moved to systems before the spare hours ran out.

The instructive extreme is the operator who never had spare hours to begin with. One of our documented case studies scaled a Sydney portfolio past forty properties while working full-time as a doctor — a constraint that forced systems from early on, because a clinical roster leaves no room for being the person who answers every guest message.

The core stack is unglamorous: a property-management system as the single source of truth for bookings; standardised turnovers with cleaning teams working from checklists; message templates covering the questions guests actually ask; pricing managed across the book rather than listing by listing; and a weekly review of the numbers that decides what changes.

Our founders’ own Melbourne operation runs this way — a PMS, dynamic pricing, an operations warehouse, a full-time operations manager and a 25-person team across cleaning, errands and virtual assistance. The point is not the headcount; it is that every recurring task has an owner who is not the founder.

Earlier than feels necessary. The workload of a well-systematised portfolio grows much more slowly than the property count — several of our filmed clients describe running five properties on the same few hours a week that one property used to take. The system built for property one is what makes property five possible.