What happens in the back office, and why it matters for guests
FAD started as our internal dashboard. It is now what the whole team runs on every day. A short look at what it does.
Most of what makes a stay feel good or bad happens before you arrive and behind a wall you can't see. The cleaning was scheduled or it wasn't. The maintenance request from the last guest was followed up or it wasn't. The team knew you were arriving at 11pm with a tired toddler, or they didn't. The version of property management that gets reviewed is the one in the lobby; the version that determines reviews is the one in the back office.
FAD is what we call our internal dashboard. Friday Analytics and Dashboards, eventually. It started as a way to see every booking across every property in one place, because the way we were doing it before (a shared spreadsheet, a WhatsApp group, a paper calendar in Bryan's truck) had run out of headroom around residence number sixteen. The first version of FAD was, honestly, a hacked-together Notion page. The third version is a real piece of software, and it is now the thing the team runs on every day.
What FAD actually does, in plain terms. Cleaning rotation, scheduled per residence and per turnover. Maintenance follow-up, with photos uploaded by the housekeeper at the end of every clean. Owner statements, generated automatically and reconciled against the invoices we issue. Guest communication, threaded across email, WhatsApp, and the booking platforms. Financial reporting, occupancy trends, the seasonal forecast we share with owners every quarter. Most of it is boring; all of it is where stay quality lives.
A small concrete example. A guest arriving at 11pm with a toddler. In the old setup, that detail lived in one person's inbox; if that person was off, it was lost. In FAD, the arrival time is on the booking, the toddler is on the booking, the residence has a pre-arrival checklist that pulls those details and triggers an extra item ('cot set up, nightlight on, kettle and bottle warmer plugged in, contact card on the table'), and a different person can pick it up if the original one is asleep. The system doesn't replace the warmth; it makes the warmth survivable in a team of five.
What this means for guests, in concrete terms. More reliable replies, more accurate availability, fewer 'sorry, we missed your message' moments. The systems behind the team are getting steadily better, and the team is the same warm, on-the-ground people they've always been. We don't replace humans with bots. We give the humans better tools, and we keep the bots out of the conversation with the guest, where they belong.
What it means for owners. Live numbers, not a PDF emailed at the end of the month. The same dashboard the operations team uses, with the owner's view restricted to their own properties. A clear thread of what was done, when, by whom, and at what cost. We've been showing the dashboard to owners we work with for nine months in beta; the typical question after the first walk-through is 'why isn't every operator doing this?', and the answer is that it is harder than it looks, and slower than it sounds.
For owners curious about the system, there's a longer walkthrough on the owners page covering the owner portal, the reporting cadence, and the commercial terms we offer when a property joins the catalogue.
