Your PMS Is Great at Bookings. Here's What Hosts Still Do in Spreadsheets.

Ask any property manager how many spreadsheets they're running and you'll get a laugh — followed by a real number that's usually higher than they'd like to admit. Owners tracker, cleaner schedule, revenue by property, maintenance log, "didn't we already have a guest named this?" It's not that these people can't afford software. It's that their software doesn't cover these things.

Property management systems are excellent products. But they were built to solve a specific problem: get a reservation from inquiry to booking, manage the listing, collect the money. That problem is well and truly solved. The spreadsheets exist because everything that comes after — coordinating the team, reading the revenue, communicating across properties — is out of scope for the PMS.

What a PMS is built for

A PMS like Hostfully handles the things that happen at booking time: syncing calendar availability across OTAs, managing listing content, processing payments, generating invoices, and routing inquiries. It's the system of record for reservations. That's valuable and irreplaceable — if you've ever managed a multi-property portfolio without one, you know what double-booking chaos looks like.

The booking workflow in a modern PMS is genuinely good. Rate management has improved. Multi-channel sync is reliable. Automated message templates exist. For the core transactional workflow, there's no reason to build something custom.

The gap isn't in what a PMS does. It's in what it doesn't need to do in order to fulfill its core purpose.

The gaps it leaves

Cross-property guest comms

PMSs surface messages per-property or per-reservation. That's logical from a data model perspective — a message belongs to a lead. But your comms coordinator doesn't work that way. They need to see everything urgent across all properties: unanswered messages, pending maintenance requests a guest mentioned in passing, the thread where someone asked about the pool heater three days ago and never got a final reply.

The result is that teams build their own triage system. A Slack channel where the coordinator pastes message excerpts. A shared inbox. A running note in Notion that someone updates manually when they remember to. None of these have audit trails. None of them feed back into the PMS. They're workarounds, not solutions.

Revenue you can actually read

Your PMS has revenue reporting. The problem is it usually shows revenue by reservation — which is useful for accounting but not for operations. When you want to answer "which of my properties is underperforming this quarter and why," you need occupancy by property, ADR by property, RevPAR trends, lead time distributions. Most PMSs either don't surface these or surface them in reports that require export-to-CSV before you can do anything useful.

So hosts build spreadsheets. Monthly revenue by property, manually updated after every sync. Year-over-year comparisons that require copy-pasting. Occupancy calculations done by hand because the PMS reports "booked nights" but not "available nights after blocks."

It works, slowly, until someone forgets to update it. Then the numbers are wrong and nobody knows when the drift started.

Team coordination

Cleaners, maintenance contractors, property inspectors — they're not in your PMS. The PMS knows a guest is checking out at 11 AM. It does not know whether the cleaner is confirmed, whether the maintenance issue from the last guest was resolved, or whether the property manager has done a walkthrough since the deep clean.

That coordination lives in text messages and group chats. "Can you get to Oak Street by noon?" "Did anyone fix the dryer?" "Check-in at 3 but the door code isn't updated." It's informal, untrackable, and invisible to anyone who wasn't in the thread.

Why spreadsheets lose

Spreadsheets are the path of least resistance, and for small portfolios they're survivable. For anything over four or five properties, they create three compounding problems.

First, stale data. A spreadsheet is a snapshot of the moment someone last updated it. A reservation change, a cancellation, a maintenance task completion — none of these automatically propagate. The spreadsheet is always slightly wrong.

Second, no audit trail. When something goes wrong — a guest complains they got no pre-arrival message, a cleaner wasn't booked, a payment wasn't recorded — the spreadsheet can't tell you what happened or who was responsible. There's no history, no log, no accountability.

Third, no alerts. The spreadsheet doesn't know that you have a turnover tomorrow with no cleaner confirmed, or that a guest message has been sitting unanswered for six hours. It just sits there, silently wrong, until someone happens to look.

The operations-layer approach

The alternative to replacing your PMS is adding a thin operations layer on top of it. Keep Hostfully (or whichever PMS you're using) for what it does well: bookings, listings, payments, channel sync. Add a separate tool that reads from the PMS and surfaces the operational view: cross-property comms, revenue analysis, team coordination, alerts.

This approach doesn't require migrating your reservations data or retraining your team on a new booking system. The PMS stays in place. The operations layer adds the visibility and coordination that the PMS doesn't prioritize.

It also means you can adopt the operations layer incrementally. Start with revenue visibility. Add comms coordination when the team is ready. Layer in maintenance tracking over time. You're not signing up for a big-bang system change.

That's the design philosophy behind Pomello. Rather than competing with a PMS, it plugs into one — Hostfully specifically — and handles the operational surface the PMS doesn't own. Read more about the approach on the about page.

A short checklist

Before you decide whether you need an operations layer, audit what you're currently doing outside your PMS. Check each item:

• Where do you track whether a cleaner is confirmed for an upcoming turnover?
• Where do your comms coordinators see unanswered guest messages across all properties?
• How do you produce a RevPAR or occupancy report for a specific property over the last 90 days?
• Where do you log maintenance issues that aren't tied to a specific reservation?
• How do you know if a guest message went more than four hours unanswered?

If the answer to most of these is "spreadsheet," "text message," or "we don't really," that's your gap. If you can answer each one by pointing to a system with an audit trail and automatic updates, you've probably solved this already.

For a companion look at the specific numbers you should be pulling out of that gap, see our post on the vacation rental KPIs that actually matter.