Hotel software from Twinlite
Three products that run the parts of a hotel your property management system doesn’t. Halo looks after the building. Lark looks after the guest. Clocky looks after the shift.
Your property system holds the rooms and the stays. Your team is who does the work. All three products read from both, so nobody re-types what the hotel already knows and nothing goes stale in a second copy.
Reads Mews
Knows which rooms are in use, and does something about it.
Looks after
Reads Mews + your team
The tablet by the bed that replaced the in-room phone.
Looks after
Reads your team
Hours captured as they happen, on their own phone.
Looks after
Every line here is live. Nothing waits for a nightly file and nothing gets typed in twice. Lark sits under both because that is where the guest and the team meet.
Anyone can sell you three apps. What matters is what happens where they touch, and here they touch in three places that save your team a job each.
When a guest leaves, Halo puts the clean on the list. When a guest asks for the room to be made up, Lark puts it on the same list. Your housekeeper works from one list, in one app, and never has to be told which system it came from.
Mews stays the single record of the room and the stay. Halo reads it to know who is arriving; Lark reads it to show the guest their bill and writes back what the guest asks for. There is no second copy sitting somewhere, quietly going out of date.
The tablets in the rooms and the phones in your team’s pockets are set up the same way, from the same place. Opening a new floor, or starting someone new, is a few minutes of admin. Not an afternoon with a box of cables.
The easiest way to explain any of this is to walk through an ordinary day. Here is what happens, and what nobody has to do about it.
Looks after the building.
A hotel spends money on rooms nobody is in and time on rooms nobody has checked. Halo knows which rooms are occupied and which are not, and quietly acts on it: putting cleans on the list, getting rooms ready for the people arriving, and letting the air rest in the ones that are empty.
Looks after the guest.
The in-room phone costs money every month and gives the guest one thing to do with it: ring the desk and ask a question the desk cannot always answer. Lark is the tablet that replaces it. The hotel, the bill, the requests and reception, all in the guest’s own language.
Looks after the shift.
Hours are the biggest controllable cost in a hotel and usually the least visible until payroll. Clocky captures them at the moment they happen, on the phone your team already carries, and turns the end of the week into a download instead of an evening of chasing paper.
We are not going to quote you a savings figure we cannot yet stand behind. What we can name exactly is the work that disappears, and where it used to sit.
Lark is the phone. No handset in every room, no line to rent for each one, and nothing in a cupboard to maintain.
Rooms put themselves on the list when the guest leaves and take themselves off when they are clean. Nobody builds the list, and nobody walks the floor to check it.
Rooms nobody is in stop working. Rooms with someone arriving start early, so comfort on arrival costs you the hour before, not the whole afternoon.
It is in the room, live, and checkout is two taps. Your front desk keeps the conversations that are actually worth having.
Hours are captured as they happen. The manager reviews the handful that need a look, instead of transcribing all of them.
One record of the room and the stay. Everything else reads from it, and writes back to it, so there is never a second version to reconcile.
We run hotels, so we buy hotel software. And we kept finding the same gap between what was on the market and what the building actually needed. So we started building the difference, and we have not stopped looking for the next piece of it.
Every one of these runs in our own building first. If it makes a shift harder rather than easier, we find out ourselves, on a Tuesday, before anyone else has to live with it.
Connections drop and services have bad days. When that happens the guest should still get their towels and the shift should still start on time. Nothing waits on a perfect network.
A guest should see a tablet that does what they expect. A housekeeper should see a list. Nobody on the floor should have to know or care what sits behind it.
What changes between properties is a setting, not a rebuild. The second hotel takes an afternoon to configure, which is the whole point of building it this way.
We are not interested in clever for its own sake. Each of these exists because it removes a specific job somebody was doing by hand, and we can name the job.
Your property system should stay the single source of truth for rooms and stays. We read from it and write back to it rather than asking you to keep a second set of books.