Introducing the Hospitality OS Series: AssetOS and PunchlistOS for the Hotel Back of House
Hotels are well supplied with systems that face the guest: reservations, messaging, housekeeping boards. The harder questions are asked by owners, auditors and buyers, and they are about the back of house. Try three of them on your own property. What is in Room 1204 today, and what is it worth on the books? Who approved the last plumbing invoice, and was the price agreed before the work started? How much linen, china and glassware left the building last quarter? In most hotels the answers sit in three systems, a spreadsheet and a WhatsApp thread.
We are launching the Hospitality OS Series to close that gap. Like the rest of the OS Series, the systems are built by Xamun and delivered by BlastAsia. The first two, AssetOS and PunchlistOS, are new and built for hotels from the first line. Both have live demos, on invented data.
Where the Gap Is
Guest systems, facility management contracts and hotel accounting are mature markets. What they leave thin is the owner's side: an asset register that matches the books, control over contractor prices, and field tools that staff can use without training. Nothing here asks you to replace a system you already run. Your property management system runs the guest. Your CAFM tool or facility management contractor runs planned maintenance and its own technicians. Xamun's hospitality page describes the new systems as filling the owner's side those tools leave thin.
Three leaks show up quietly and are found late. The register and the books disagree, because engineering and housekeeping know where things are while finance holds cost and depreciation in a module nobody walks. Repair prices are agreed in chat, so who is approved for which trade and what a job should cost lives in email and memory. And operating equipment walks away, because linen, china, glassware and uniforms are counted twice a year against a spreadsheet.
AssetOS: A Register That Agrees With the Books
AssetOS keeps one record of everything a hotel owns: where it is, what condition it is in, what it has cost to keep running, and what it is worth. A scan in Room 1204 and a line in the month-end journal come from the same event, so the two cannot drift apart.
Setup works by describing each room type once. A pre-defined kit, such as the TV, bed, minibar and safe in a Deluxe King, is stamped across every room of that type, so the team confirms expected contents with a phone scan instead of typing items in. The design goal is a property live after one setup session and one scan walk. The field app opens on one button, keeps working without signal, and needs no download.
For linen, china and glassware, AssetOS counts pooled stock against par, using blind counts that flag a variance above a threshold, and logs breakage with a reason where it happens. Finance chooses the book treatment per category. At month end the depreciation run, under IAS 16 with USALI departments, produces a balanced journal that exports to your general ledger. It does not replace the ledger or your maintenance system, and it can take repair costs from the one you already run.
PunchlistOS: No Repair Price Without an Approver
PunchlistOS runs one operation: getting a reported defect fixed by an accredited contractor, at an approved price, verified and closed. A guest, resident or staff member scans the QR code in the room and reports a problem with a photo and a line of text. No account and no app download. The supervisor assigns it to an accredited contractor or an in-house technician, who quotes against the rate card the property has already agreed. The right person approves by value before work starts, and the ticket closes only on after-photos and sign-off.
That makes "who agreed to this price?" an answerable question. Contractors work inside the property's rules: accredited for the trade, with licenses and insurance tracked to expiry, priced against the rate card, and scored on every job. In branded residences, the same flow also answers who pays, because a repair charged to a resident is agreed with that resident before the work starts. PunchlistOS covers defects in occupied buildings; it does not do handover snagging on new developments. Where a hotel has no maintenance system, AssetOS and PunchlistOS pair natively: AssetOS owns the rooms and assets, PunchlistOS owns the repair ticket and its charges.
The Cheapest Day to Start
An asset register is cheapest to start before the first guest. The UAE had 103 hotel projects and 24,985 rooms in its construction pipeline in the second quarter of 2026, 13,828 of them in Dubai, according to Lodging Econometrics. Each opening unpacks thousands of items in a short window. A pre-opening team can stamp the kits first, and the first scan walk then proves what arrived.
The Rest of the Hospitality Set
AssetOS and PunchlistOS are the two systems built for hotels from the first line. Four more OS Series systems, already built for neighboring industries, fit around a property, and each has a live demo:
CommunityOS runs the owners' association behind a residential building once it is handed over: dues and sub-metered utility billing, service requests and work orders, visitor QR gate passes and a resident app. It is live for the Philippines, with a UAE pack next, which makes it relevant to branded residences.
RosterOS covers onboarding, certificate checks, the weekly roster, GPS clock-in, timesheets and payroll export. Its live demo is set up for care providers, and hotel shift teams run the same lifecycle.
KitchenOS serves a central kitchen supplying several outlets, with pull orders, production slots, costed recipes, batch and expiry tracking, and cost by outlet against standard, without an ERP rollout.
CafeteriaOS is for contract caterers running staff cafeterias inside client companies. The client sets who is entitled to which meals, the counter scans a signed meal pass even offline, and each client gets an invoice backed by every scan.
You can see the whole set on Xamun's hospitality page.
How to Start
Start with one property. The first step is a written requirements document for that property, drawn up with your chief engineer, director of finance and housekeeping lead: what you own, where it leaks, and the two numbers you want to move. After that comes a scan walk of one floor in AssetOS, or a month of repairs through PunchlistOS.
These are new products, and the demos use invented data, so the first property is how we earn the rest. You can open the AssetOS demoor the PunchlistOS demo, or book a walkthrough with Xamun and BlastAsia.
Comments