You put your dining, tours and everything a guest asks about on it, and change it in a
minute. They reach your front desk in one tap, and your offers go up when you say so.
No ticket, no developer, no waiting on me. You edit it and publish,
and every guest sees it the next time they open the app.
A minute
To change a photo, a price or a closing time. You do it yourself, from your phone.
They see it
Tonight’s dining, your offer, what is nearby. Not a menu of icons.
Booked with you
A guest taps your island tour and messages your desk about it — not an agency down
the road.
See it working
Open it on your phone.
A twenty-four-room beach house on Palawan — one hotel, no sister
property, no spa. The same app you would get, built the same way. It opens on the guest’s
stay, not on a menu of icons.
Both hotels are invented and their photography is licensed stock — yours would
be your own. Nothing you type into either is kept.
What you buy
Start where it pays for itself.
An agent booking costs you 15–20% in commission, so work the price
out from your own room rate: if this recovers one direct booking a month, it has paid for
itself. Moving up a package is a setting I switch on — nothing is rebuilt, and your guests
never notice.
Guide
A hotel with no restaurant, bar or tour desk of its own.
Opens on their stay — tonight, the offer, what is nearby
Home, Stay and Around one tap apart at the bottom
Room QR straight into the app — no download
Pick their hotel, see only that hotel's content
Dining, tours, spa, transport, nearby, policies
Photo galleries and full-screen viewer
One WhatsApp button to your front desk
Install to home screen, works offline after first open
English and 简体中文
What you run it with
Content editor — rooms, photos, offers, contacts
Publish to every guest at once
Guest list with CSV export
Everything in your own Google account
Bot protection on sign-ups
Perks and staff
An Offers tab in the app — Guide simply does not have one
Redeemable offers with a guest code
Front-desk console — approve and unapprove
Outlet console — validate and redeem
A PIN per hotel, plus one for outlet staff
Which sections and listings guests actually open
Perks dashboard — by range, hotel and offer
Complimentary perks given by reception
Before they arrive
Reservations list you or Cloudbeds can fill
Signed arrival link, details pre-filled
Self check-in with a code for the desk
Arrivals synced from Cloudbeds
Passport on file, auto-deleted after check-out
What it does not do.
Better said now than found in week three.
If you run Cloudbeds, it reads it and never writes back. Marking a guest
checked in on your own system is still your front desk’s job. If you don’t run one,
nothing here changes.
No payments, and no chat inside the app. A guest messages your front desk on
WhatsApp — there is no availability calendar and nothing is charged here.
It is a dark app, on purpose. That is what reads as expensive on a phone in a
dim room.
Arrivals is not sold without Perks. The check-in code and the perks code are the
same code.
Who builds it.
One person, and small hotels are the point. This is built for owner-run places
— a beach house, an inn, a small resort. It also runs in production across a nine-property
group in Palawan, which is how I know it holds up; that is not who it is for. I don’t name
clients publicly — I’ll offer you an introduction once we both want one.
Your data stays yours. The guest list, the photos and any passports sit in
your own Google account, not mine. I build it; I do not hold it.
If I disappear, your app keeps running. It is one file on your hosting and a
script in your own Google account.
One client at a time. I would rather deliver yours properly than sign three and
be late for all of them.
