What a Hotel PMS Actually Costs
Two quotes for the same thirty-room hotel can differ by a factor of ten, and both can be honest. Here is what moves the number, what is never in the quote, and the eight questions that make two offers comparable.
Why nobody publishes a price
Almost every hotel software website says “request a demo” and nothing else. The usual reason given is that every hotel is different. The real reason is that a price list would invite comparison, and comparison is the one thing a sales-led product cannot survive.
That leaves you with a worse problem than a high price: you cannot tell a cheap quote for a complete system from an expensive quote for half of one. The number on the email is not comparable to anything until you know what sits inside it.
The four ways it is billed
Same software, four different price shapes. Comparing a per-room quote with a per-user quote is how buyers end up confused rather than informed.
Per room, per month
The most common subscription model in hospitality. Predictable, and it scales with the property. Watch for a minimum room count, and for whether housekeeping, POS and the channel manager are included or priced separately.
Per user, per month
Common in systems aimed at restaurants and small properties. Cheap for a two-person reception, expensive the moment you add housekeeping, maintenance and a manager. Count your real staff before comparing.
Per module
Front desk is one line, POS another, housekeeping another, the channel manager another. A low headline price usually means the list is short — the total arrives as an addendum.
One-off licence, plus support
You buy the version you receive and pay separately for updates and support. Cheaper over five years, more expensive in year one, and it puts the maintenance risk on you. This is how desktop and self-hosted systems are sold.
What actually moves the number
In rough order of impact. Any vendor who cannot explain their price in these terms is pricing by vibes.
- Room count and properties. Thirty rooms and three hundred are not the same product, and a second property is not a discount — it is a second deployment.
- Which modules are in scope. Front desk alone is a small build. Front desk, housekeeping, POS, warehouse, rosters, payroll and invoicing is an operations system.
- Integrations. Channel managers, door locks, card terminals, fiscal printers, accounting exports, payment providers. Each one is a separate contract between two systems that were never designed to meet.
- Regulatory work. A fiscal bridge to a tax authority, or invoice grading, is not a feature — it is a compliance project with a testing cycle and a regulator who can change the rules.
- Offline requirement. “It must keep working when the internet drops” is one sentence and roughly doubles the engineering, because every write has to survive a crash and reconcile later.
- Languages and documents. Multi-language interfaces, OCR across alphabets, guest document capture, printed folios in the right format.
- Data migration. Ten years of guest history from an old system is a project of its own, and it is often quoted separately — or not at all.
- Hardware and deployment. Terminals, printers, scanners, the machine at reception, and the person who installs it.
Eight questions that make two quotes comparable
Send these to every vendor, including us. The answers take ten minutes and replace a month of demos.
What exactly is included, module by module?
A list, not a phrase. “Full PMS” means nothing until you see the module names next to the price.
What is the total for year one, and for year three?
Setup, migration, training, integrations and subscription. Three years is where per-user pricing and per-room pricing stop looking similar.
Which integrations cost extra, and how much per booking?
Channel manager, payments, fiscal, locks. Ask for the per-transaction figure, not the monthly one.
Does it work when the internet is down, and what exactly works?
“Offline mode” ranges from “the screen stays open” to “you can check a guest in and it reconciles later”. Ask which operations survive.
Who does the data migration, and who checks it?
Get a number of records, a format, and a named person responsible for the first night’s reconciliation.
What is the support response time outside business hours?
In hours, on a weekend, in writing. This is the number that decides how bad your worst night is.
If we leave, how do we get our data out?
Format, timeframe, fee. Refusing to answer is an answer.
What is fixed in scope, and what is billed by the hour?
Every project needs both. What matters is that the line between them is written before you sign, not discovered in month four.
What we do instead
We build VIKENTIS ONE — a hotel PMS and restaurant POS in one desktop application, in production for a working property. We do not publish a price list either, for the same reason nobody does: the honest range is too wide to be useful.
What we will do is answer all eight questions above before you commit to anything, in writing, and put the scope in a document you approve:
- A written specification first. Screens, data model, integrations, and an explicit list of what is out of scope — before a line of code.
- A fixed price for the build, with changes priced separately and agreed before they are done.
- No per-booking fees. The software does not get more expensive because your hotel got busier.
- Your data stays yours, on your machines, in a database you can open — and it leaves with you if you go.
- Source code and documentation on final payment, so a future developer is not held hostage.
What people ask next
Is subscription always more expensive than buying outright?
Over five years, usually yes — you are paying for the vendor’s continued development as well as the software. But a one-off licence leaves you responsible for updates, security and the machine it runs on, which is a real cost if you have no technical staff.
Should a small hotel use the same system as a large one?
Usually not. A twenty-room guesthouse needs front desk, bookings and a clean folio. Buying an enterprise system means paying for modules nobody opens and training staff on workflows they will never use.
How long does an implementation take?
For a single property with a standard scope, weeks rather than months. Anything touching a fiscal authority, a channel manager and a card terminal together takes longer, because you are waiting on three other companies as well as building.
Can we start with one module and add later?
Yes, and it is usually the sensible route — provided the data model was designed for it. Ask that question directly: “if we add housekeeping in a year, does anything need rebuilding?”
What if we already have a system and hate it?
Start with a paid audit rather than a replacement: what exists, what works, what is fragile, and what migration would actually involve. It is a small cost that regularly saves a large one.
Do you only work with hotels in one country?
No. The fiscal integration we built is specific to one tax authority because that is where our reference property operates; the rest of the system is not tied to a country. If your jurisdiction needs a bridge, that is scoped as its own piece of work.
Want a range, not a demo?
Tell us the room count, the modules you use today and the integrations you cannot lose. You will get an honest range and the eight answers above, before anyone asks for a meeting.
