MyHotelio
The problem
Independent hotels run on a spreadsheet, a booking inbox and a whiteboard. The software built to replace that is priced and designed for chains — dense, modal-heavy, and expensive to learn for a property with one person on the desk.
The solution
A console organised around what a property actually manages — room types, policies, rate plans, rate mapping, inventory — with a rate calendar that shows price and availability together, so a night's decision is one glance rather than three screens.
The result
A single operator surface covering rooms, rates, inventory and reservations, carried through to a mobile view for the manager who is not at a desk.
01
Overview
MyHotelio is a hotel management system: room types and policies, rate plans and rate mapping, inventory, guests and reservations, with user management and roles underneath.
02
Context
The buyer is an independent property — a resort or a small group — not a chain with an IT team. They evaluate the product on their own, they adopt it without training, and they abandon it the first week it is slower than the spreadsheet it replaced.
03
Challenge
Every hospitality product has the same trap: the data model is genuinely complex, so the interface becomes a mirror of the database. Rooms, room types, units, rate plans, mappings and inventory are all separate things, and showing all of them at once is how these products become unusable.
04
Approach
One object per screen, with everything else expressed as a relationship to it. The room-type list carries images, size, amenities, bed configuration and its linked rate plan in a single row, so the common question — what am I selling and for how much — is answered without navigating. The rate calendar puts availability and price on the same grid. The sidebar exposes the hierarchy rather than hiding it, so operators build an accurate mental model of the system in the first session.
05
What I did
- 01Information architecture for the operator console
- 02Interface design: room types, policies, rate plans, rate mapping, inventory
- 03The rate and availability calendar, the product's most-used screen
- 04Table, form, filter and empty-state patterns reused across every module
- 05Responsive treatment down to a phone-sized manager view
- 06Marketing surface aligned with the product it sells
Live
See it working.
This project is live. The best version of any case study is the product itself.
Next project
Buudhi