How to choose a PMS without overspending on budget

Choosing a PMS (property management system) is one of the technology decisions with the most impact on the day-to-day operation of an accommodation. Badly chosen, it shapes the next several years: integrations that do not fit, modules paid for and never used, reporting that does not answer the owner’s questions. Well chosen, it disappears into the background and lets the team focus on the guest.

This note does not recommend brands (Lares is vendor-agnostic). It lays out the practical criteria we apply when we help an accommodation decide.

The most expensive mistake: copying the neighbor

The most common way to choose a PMS badly is to copy the accommodation next door. “It works fine for the campground in Cazorla” is the worst possible basis for the decision, because your campground is not theirs: you have different pitches, different seasons, a different team, a different tax structure.

A PMS either fits the specific case or it does not. What is essential for a 200-room chain (automated revenue management module, native multi-property) is overspending without benefit for a 14-room hostel. And the other way around: a PMS designed for individual vacation rentals usually falls short in a rural hotel with parallel services (restaurant, massages, activities).

Question zero: do I really need to change?

Before evaluating PMSs, it is worth closing the question of whether the change adds real value. Signs that yes, the change is warranted:

The current PMS does not integrate natively with your channel manager and you force the team to duplicate inventory.
The PMS does not support SES Hospedajes (the Spanish Ministry of the Interior’s mandatory guest reporting system) and you fill in the reports by hand every night.
The PMS is not certified for Verifactu (the Spanish Tax Agency’s real-time invoicing scheme) and you have to comply with the 2026 calendar.
Your PMS charges a per-room fee that is disproportionate to your actual volume.
Support takes days to respond to incidents that affect daily operations.

If none of those is true, the problem is most likely not the PMS, but the configuration or the processes around it.

The five criteria that actually matter

When the change really is needed, the evaluation criteria we apply, in order of priority:

1. Fit with the type of accommodation

A PMS designed for traditional hotels (rooms, ADR, occupancy) does not work well at a campground (pitches, slots, seasonal calendar). One designed for vacation rentals does not work in a hostel with shared dorms. Before looking at prices, you have to verify that the tool understands your unit of inventory.

2. Native integrations, not plugins

The critical pieces of the stack have to connect natively with the PMS, not through third-party plugins that break whenever someone updates:

Channel manager (Booking, Airbnb, Expedia and whichever are relevant to your vertical).
Booking engine on your own website.
Access control system (electronic locks).
SES Hospedajes and Verifactu.
ERP or invoicing software.

Every non-native integration is a future failure point. The more connected out of the box, the less manual maintenance later.

3. A scalable pricing model

Professional PMSs charge in three different ways:

Per room/pitch per month: between 4 and 20 euros monthly per unit, depending on features. Linear with size.
Percentage of revenue: a percentage of monthly volume, typically between 1% and 3%. Heads up: in high season this model can get very expensive.
Flat fee: a fixed monthly or annual price. Usually the cheapest, but only scales well up to a certain size.

The right question is not “how much does it cost”, it is “how much does it cost at my size three years from now”. You have to project the cost across growth scenarios.

4. Real support, not a generic chat

When something fails in production (an overbooking, an OTA sync failure, an invoice issued incorrectly), the support response time matters more than almost any other feature. Verify before signing:

Is there a direct support channel with humans, not a bot?
What language do they operate in and during what hours?
What is the real SLA for critical incidents on your plan?
Can you talk to current PMS clients of your type of accommodation before signing?

If support is just a web form with a 48-hour response window, it is not a PMS fit for production.

5. Exportable data without lock-in

Your guest database, booking history and invoicing are among the most valuable assets the accommodation has. They have to be yours, not the vendor’s.

Verify before signing:

Can you export your full database in standard formats (CSV, JSON) at no extra cost?
How long does the export take and in what format?
What happens to your data if you decide not to renew the contract?

If the answer is vague, assume the worst.

What gets sold and almost nobody uses

During the evaluation, it pays to identify the features the salesperson demos but that, in practice, rarely get activated in small or mid-sized accommodations:

AI-driven automated revenue management: for under 30 rooms, a weekly review with human judgment delivers the same or better.
Advanced CRM with complex segmentation: for accommodations without a dedicated marketing team, a clean database inside the PMS is enough.
A dedicated mobile app for guests: almost no one downloads it. WhatsApp and a mobile browser cover the same ground.
Event and banquet management: only relevant if you have function rooms or catering as a business line.
Multi-property with financial consolidation: only applies from 3 distinct properties upward.

Paying for these features when they are not used is one of the most common recurring costs in small accommodations. Spotting them during the evaluation often saves between 50 and 200 euros a month.

A change process without surprises

Once the decision is made, a well-executed PMS change follows a clear pattern:

Audit of the current PMS: what data is in there, which integrations are in production, which processes depend on it.
Selection of the new one: applying the criteria above, with a closed written proposal from the new vendor.
Migration with an overlap window: two weeks running in parallel where both systems receive bookings and the new one is verified to lose nothing.
Clean cutover on a defined date: the new PMS becomes the single source of truth. The old one stays in read-only mode for six months in case historical data needs checking.
Team training: on site, with real scenarios. “Here is a video tutorial” does not cut it.
90 days of post-launch support: the window where the cracks show up. It pays to have someone resolve them before they turn into bad habits.

Skipping any of the steps usually ends up costing more than doing them.

Closing

The PMS choice shapes an accommodation’s operation for years. Making it on intuition or by copying the neighbor is expensive. Making it on judgment, with an honest evaluation of the real case, frees up time and money in the long run. The 30 minutes of the initial diagnosis are enough to understand where your accommodation stands and whether a PMS change solves a real problem or whether the right conversation is a different one.

Tags: PMS · tech stack · investment decisions · software evaluation