Skip to content

A hotel CRM built around its processes

Parking, transfers and driver shifts in one interface: 114 screens for reception, the manager and the driver.

Parking screen in the hotel CRM: free spaces, cars in the car park and the day's revenue
Client
A hotel, name withheld by agreement
Industry
Hospitality: parking and transfers
Roles
Reception · manager · driver
Screens
114: 94 for desktop, 20 for mobile
Platform
Web CRM and mobile web
Status
Design approved, in development

How the interface is built

System first, then screens

The design system with shared components came first – every screen is assembled from its ready-made parts.

  1. Every screen state

    Every screen is designed not only for perfect data.

    • Empty lists and loading
    • Network errors
    • Input errors

    Stage result: an interface that holds up when things go wrong.

  2. Role-based permissions

    The manager's section is fully hidden from reception.

    • No ‘read-only’ mode
    • Each role has its own menu
    • No extra buttons to distract

    Stage result: everyone sees only what they need for their work.

  3. A separate layout for mobile

    The driver's area is built for 390 px, not scaled down.

    • Main actions within thumb reach
    • One column, no sideways scrolling
    • Nothing extra on a small screen

    Stage result: an area where the driver never hunts for the right button.

  4. Contrast and button size

    The driver works outdoors and on the move.

    • Field borders with at least 3:1 contrast
    • Buttons of at least 48 px
    • Text stays legible in bright light

    Stage result: fewer mis-taps and input errors.

Next step

Need a tool like this for your work?

Tell us how the process runs – we'll propose a set of screens and a work plan.

From task to implementation

A clear path from process to launch

We name the scope, timeline and support after reviewing your task.

  1. Process review

    Stages, people involved, sources and data quality.

  2. Scope agreement

    Responsibility, human review and acceptance criteria.

  3. Development and testing

    We build the solution and test it against scenarios.

  4. Launch and support

    We launch and support it within the agreed scope.