Two hotel systems quote ₹4,000 and ₹9,000 a month. The cheaper one costs more. This isn't unusual — it's the normal outcome of comparing subscriptions when the subscription is the smallest component.
Quick answer (for the impatient)
Compute total first-year cost, not monthly subscription.
Per-booking fees are the largest hidden variable and scale exactly as you succeed.
Payment processing is frequently the biggest line of all, and it's often not mentioned in the software conversation at all.
The components
Subscription — the visible number, sometimes per room, sometimes tiered, sometimes per property.
Setup and onboarding — one-off, occasionally substantial, and sometimes quoted only after you've committed.
Migration — whether getting your existing data in is included or billed.
Training — included, or per session, or "self-service" which means your manager's time.
Per-user charges — a serious factor for a property with three shifts and a dozen staff.
Module unlocks — channel manager, booking engine, POS, accounting, each potentially separate.
Per-booking or commission fees on the booking engine.
Payment gateway charges on every transaction processed.
Support tiers — where responsive support is a paid upgrade.
Why per-booking fees deserve special attention
A booking engine charging a percentage per direct booking has a property that ought to alarm you: it grows precisely as your direct-booking strategy succeeds. You went direct to escape commission, and you're paying a smaller commission to a different party.
Smaller is still better, and this isn't an argument against booking engines. It's an argument for computing it. At 40 direct bookings a month at ₹4,000 average, a 2% fee is ₹3,200 monthly — potentially more than the subscription it sits alongside, and entirely absent from the comparison most hoteliers make.
Payment processing, the line everyone forgets
For a hotel processing most of its revenue electronically, gateway charges are often the largest technology cost in the business — larger than the software itself. The rate differs sharply by instrument, and UPI economics in India differ materially from card economics.
This is worth modelling on your actual payment mix rather than a blended assumption. A property whose guests predominantly pay by UPI has a very different cost structure from one taking mostly international cards, and a software comparison that ignores this is comparing the wrong thing.
Compute it properly
For each option, over twelve months:
Subscription × 12, at your actual room count and user count.
Plus setup, migration and training, one-off.
Plus every module you'll actually need — not the base tier if the base tier doesn't include the channel manager.
Plus per-booking fees × your realistic direct booking volume.
Plus payment processing × your revenue × your actual payment mix.
Plus any support tier you'll genuinely need at 2am.
Do this for two or three options and the ranking frequently inverts.
The cost that isn't on any invoice
Staff time. Software that requires double entry, or that nobody can operate without the manager, has a labour cost that dwarfs the licence. So does software that's down during check-in rush.
Hard to quantify precisely, easy to sanity-check: ask, during a trial, how long a check-in takes and how many screens a night audit needs. A system that saves twenty minutes a shift is worth more than most subscription differences.
A realistic hotel example: what the team sees during a working shift
Picture Lakeview Residency, an independent property where the same manager may answer a booking query, approve a rate, settle a guest account and help a new employee before lunch. The question behind The Subscription Is Not the Price: What Hotel Software Actually Costs does not arrive as a neat software task. It arrives while somebody is waiting, another department needs an answer and the record must still make sense at the end of the day.
The first useful observation is this: Compute total first-year cost , not monthly subscription. The manager should translate that statement into a visible hand-off. Who starts the action? Which record do they open? What information must already be present? Who checks the result? If any answer depends on one experienced employee remembering an exception, the process is not yet reliable.
The second observation is equally practical: Per-booking fees are the largest hidden variable and scale exactly as you succeed. At Lakeview Residency, the team would test this with one ordinary case and one awkward case. The ordinary case confirms the expected path. The awkward case exposes missing permissions, incomplete data, unclear ownership or a decision that still happens in a private message. Both tests matter because hotel operations rarely fail on the clean example shown in a demonstration.
The third observation is about the downstream record: Payment processing is frequently the biggest line of all , and it's often not mentioned in the software conversation at all. A completed action should leave enough context for the next person to understand what happened without reconstructing the story from calls and chat messages. That does not mean collecting every possible field. It means keeping the few facts that change the decision, the status, the responsible role and the next action together.
Rollout checklist: move from a good idea to a repeatable process
Use this checklist before the team treats the workflow as normal operating procedure. It deliberately separates product reachability from management discipline: software can make a record available, but the property still decides who owns it and how exceptions are handled.
Name the owner. Choose the role responsible for starting and completing the process. "The office" or "the front desk" is too vague when several people share a shift.
Confirm access. Test with the real role and tenant configuration, not an unrestricted demonstration account. Check enabled modules, feature permissions and the property or outlet context.
Define the minimum input. Agree which guest, room, date, amount, document or operational detail must be present before somebody can act.
Run the normal case. Complete one realistic example from beginning to end and ask the next team member to explain the result using only the saved record.
Run the exception. Try a correction, cancellation, missing value, late change or disputed instruction that genuinely occurs at the property. Record the fallback if the product path does not cover it.
Check the hand-off. Make sure the relevant people in front desk, reservations, housekeeping and accounts can see the status they need without receiving unnecessary access to unrelated records.
Write the fallback. If the system is unavailable or the case sits outside the verified path, state who records the temporary decision and who reconciles it later.
Review after live use. Ask staff where they paused, duplicated work or returned to a spreadsheet. Fix the process before adding more fields or automation.
Decision table: evidence to collect before you approve the workflow
A manager does not need a large transformation project to evaluate this topic. A short evidence review is enough to distinguish a reachable workflow from an attractive claim. Use the table during a property review and write the answer in plain language.
Review point What to verify Evidence to keep Decision if it fails
Reachability The responsible role can open and complete the path in the correct tenant and property context. A completed test record and the role used. Do not announce the workflow; check provisioning and permissions.
Data quality The minimum information needed for the decision is present, understandable and current. The input checklist and one reviewed example. Fix the collection step before adding automation.
Ownership One role owns the next action and another can review where separation is appropriate. The operating owner and escalation path. Assign responsibility before rollout.
Exception handling A correction, cancellation or disputed case has a documented path. The tested exception and fallback note. Keep the process in controlled trial use.
Downstream hand-off The next department sees the status it needs without manual re-entry or excessive access. A hand-off check by the receiving role. Use a documented interim hand-off and reconcile it.
The honest AXOIX limit and what to review after the first live cycle
The first review should focus on behaviour, not vanity metrics. Ask the people who performed the work where they hesitated, what they entered twice and which decision still escaped into a phone call or personal message. Compare the saved record with what actually happened. If they differ, find the earliest point where context was lost.
Then separate a training problem from a product boundary. A training problem means the verified path exists but the team did not understand the trigger, required input or next action. A configuration problem means the module, property context or permission is not available to that role. A product boundary means the audited path does not support the case. Those three diagnoses require different responses; calling all of them "user error" guarantees a repeat.
Keep the limitation visible while reviewing this article: Verify the workflow and its applicability before relying on it. That boundary is part of the buying and rollout decision, not a footnote to remove from the sales conversation. Where the workflow is usable, test it honestly. Where it is partial, keep the manual control explicit. Where applicability depends on law, policy or professional judgement, confirm it with the appropriate adviser.
FAQ
Is per-room pricing better than flat pricing?
Per-room scales with you, which is fair going up and painful once you're large. Flat favours bigger properties. Compute at your size, and at the size you'll be in two years.
Are free hotel systems real?
Some are, and they typically monetise through booking fees or payment processing. That's not dishonest — just make sure you've computed those lines, since that's where the cost moved to.
Should I pay annually for a discount?
Only once you're confident. An annual prepayment on software you abandon in month four is an expensive way to save 10%.
How should a hotel test this before rolling it out?
Use the real tenant, property context and staff role. Complete one ordinary case and one exception from start to finish, then ask the receiving role to verify the saved result without relying on a private message.
What should the team do if the verified product path does not cover its case?
Keep a documented manual control, name the person responsible for reconciliation and avoid describing the unsupported step as automated. Recheck module provisioning and permissions before concluding that a capability is absent.
The bottom line
Compare total first-year cost at your actual volume, including payment processing. It's an hour of arithmetic and it regularly changes the answer.
See the questions to ask vendors, how a five-tool stack adds up, or pricing.
Compare the real number. Start free →
Comments