YMME PMS: one window for the whole hotel
A hotel management system built for independent properties. Room status chart, folio, housekeeping, rates, booking widget, reports, CRM, and loyalty — all in one product, not in a bundle of eight subscriptions that don't talk to each other.
The entire shift on one screen
The manager at the desk doesn't need to hold in mind which information lives in which tab. The room status chart shows your property's state on any date: vacant, occupied, dirty, inspecting, out of service, or offline. Check-in and check-out happen from the same place, including early arrival and cancellation if the guest changes their mind.
Group bookings are one operation: assign rooms from a file, create a master folio, check in the entire group together. Shared occupancy, when multiple bookings share a room, is tracked as a unit, not as three separate unlinked records — and they check in together too.
The arrival queue knows which rooms are ready. If housekeeping hasn't finished, a guest cannot be checked in by mistake: the room enters the queue and surfaces automatically once housekeeping marks it clean.
Money: a folio that holds up to scrutiny
A folio with windows and routing: some charges to the guest, some to the company, some to the event organizer. Move line items between accounts, split charges, assign a specific charge to a specific payer. Cash withdrawals, corrections, and reversals are all recorded with who did it and when.
Cash is not an exception to the system — it's a complete workflow: shifts, cash collection, and daily reconciliation. In many markets, this is not legacy thinking — it's standard practice.
Separately: operating accounts. Standing accounts for properties, companies, and events where you can record charges outside guest bookings.
Housekeeping you can manage
Rules and time standards, task assignment, quality inspection, overtime credits, room-type overrides. A readiness forecast shows how many rooms will be ready by when — that is, how many hours before peak arrival you need to shift staff around.
Out-of-service and out-of-sale are separate: the first is maintenance, the second is a temporary block. This distinction matters for reporting.
Rates, channels, direct bookings
Rate plans, price calendars, promo codes, management discounts with separate permissions. Restrictions — closures on arrival or departure, stop-sales, minimum stays — are sent to the channel manager along with prices and inventory.
A booking widget for your hotel website: a funnel with analytics, calendar view, cart, add-ons, room gallery, draft and publish. Direct bookings stay direct — the guest doesn't leave for another platform, and your data stays with you.
CRM and loyalty: built in
Guest profiles with full history, incoming requests, duplicate merging, segments with export. Your hotel manages its own guests from day one — no separate CRM, no integration setup.
Loyalty — earn, spend, tiers — runs in the same system that calculates the folio. This matters: points are credited from actual settlement, not from an export that arrives the next morning.
Reports and day close
Trial balance, transaction ledger, accounting export, receivables, cash reconciliation, daily summary, pickup forecast, segment breakdown, agent commissions, occupancy heatmap. Departmental budgets with plan and actual, cost allocation by cost center.
Night audit closes the operating day with a signature and a freeze. After closure, nothing changes retroactively — and if a change is needed, it's recorded as a separate transaction and logged. For an owner, this is the difference between a report you can trust and one that someone fixed on Wednesday for last Tuesday.
Data belongs to the hotel
Tenant isolation is built at the database level, not as code checks: rows from one hotel are physically inaccessible to queries from another. An audit log records significant actions. There's data export on request and automatic deletion after retention expires.
Deploying the system on your own infrastructure is technically possible — this is not a brochure promise, it follows from how it's built.
Ready for AI agents to find your hotel
Guests increasingly choose hotels in conversation with an AI assistant, not in a search feed. A property that cannot be read programmatically falls out of that chain.
YMME PMS exposes itself as a set of tools for agents: 38 operations on the same interface the staff app uses. Access is scoped to keys — a read-only key answers analytics questions and cannot change anything. Every agent call is logged. Any assistant that supports the protocol works, including one deployed inside your hotel.
Change or stay
If you have a working system, keep it. We integrate with any PMS in about 48 hours, and that's a promise we haven't withdrawn.
YMME PMS is for when you're building from scratch, when your current system has been outgrown and people work around it with spreadsheets, or when a corporate contract is sized for a chain but priced like a single property.
The target size is 20 to 110 rooms. The manager and owner work in the system themselves, not through a support desk.