Why this experience matters
Property operations punish vague ownership.
A cleaner does not arrive because a task was missed. A guest cannot access the property because the right message was not sent. A compliance record expires because the date was sitting in a spreadsheet without a follow-up mechanism. A maintenance issue sits between the guest, owner, contractor, and property manager because everyone assumes somebody else is handling it.
Working inside those environments shaped the way I now approach automation: I pay attention to the gaps between the official process and what actually happens when something goes wrong.
UK serviced accommodation
I supported a serviced accommodation business for more than two years, covering guest communication, OTA activity, cleaners, vendors, booking changes, property records, and owner updates as the operation grew from two units to five.
The work was customer-facing and operational at the same time. A good guest experience depended on the backend being organised enough that questions could be answered quickly and issues could move to the right person without getting lost.
Persistent follow-up also helped secure a six-month long-stay booking, a useful reminder that good operations can have a direct commercial effect even when the task itself looks administrative.
Australian residential property administration
I later supported a portfolio of roughly 130 properties, working with lease renewals, invoices, compliance, CRM updates, property records, and administrative workflows using platforms including PropertyMe, Palace, and Realworks.
One of the larger clean-up tasks involved auditing around 200 compliance records in a week. That kind of work requires more than speed. It requires consistency about what counts as complete, what needs escalation, and what information can be trusted.
New Zealand room-rental operations
I also worked with room-rental operations using Airtable and OneDrive to organise property and tenant information. Different business model, same systems lesson: the operation becomes easier when information has a clear home and people do not have to hunt through messages to find the current state.
What I carried into automation work
The customer experiences the gaps between teams even when the org chart does not.
A workflow that only works when everything goes right is not an operations system.
Dashboards and automation become dangerous when source data is incomplete or stale.
Sometimes the difference between a missed opportunity and a six-month booking is simply having a reliable next action.
Why this belongs in an automation portfolio
Because automation without operations context becomes button-pushing. My property background gave me years of exposure to customers, urgent exceptions, vendors, compliance, scheduling, records, and business owners who needed accurate information. It is the layer underneath how I design systems now.