⟵ All work

05 / HotelsPro

Creating and sharing hotel offers

Helping travel agents combine hotel options into one client proposal.

HotelsPro agent dashboard: a greeting with unread messages and payment deadlines, bonus balance, and tabs for waiting offers, waiting payments and finalised bookings

The problem

HotelsPro worked like a consumer booking site, but agents use it to build offers for clients many times a day.

My main decision

Build offer creation into search: pick several hotels, save them, and send one offer to the client.

What changed

Agents can build, save and share a multi-hotel offer inside the platform.

My role
Lead UX designer: audit, research, workshops, flows and wireframes, and support for prototype testing.
With
Business analysts, the CRO team, data scientists, product managers and engineers at Metglobal.

An agent’s working day

HotelsPro sells hotel rooms to travel agencies. Agents compare prices across several platforms and put together offers for their clients. The platform had been built with a consumer booking mindset, so it had no way to turn hotel results into an offer, save a search or come back to one. Agents copied data into spreadsheets and email instead.

Four workshops with the people closest to agents

Alongside analytics and usability findings, we ran four group sessions to map the experience before, during and after booking. The sessions surfaced pain points, regional differences and needs the platform didn’t meet. Together with the analytics, they pointed to the repeated job: building a proposal for a client, not booking a single room.

Building an offer: select, assemble, save, share

I mapped the new journey from the dashboard through search results to creating and sending an offer, then to booking confirmation. Selecting hotels happens in the search results the agent is already using, so an offer grows out of a normal search instead of a separate tool.

Design explorations

Journeys, workshops, search analysis, wireframes and the final dashboard.
Discovery
Current journey: agency staff move from homepage to hotel details, download PDFs and send e-mails by hand
Three audiences: agency owner, agency staff, agency client
New journey, versions 1 and 2: dashboard, search results, create and send offer, booking confirmation
Workshop wall covered in orange and pink sticky notes
Workshop session around a long table

To complement our analytics and usability findings, we ran a series of workshops to capture on-the-ground insights from those closest to the users.

We facilitated 4 focused group sessions to map out the pre- and post-booking experience, uncovering pain points, regional nuances, and unmet user needs.

Participants reading sticky notes on the workshop wall
Yellow sticky notes grouped under pre-booking, booking and post-booking
Click heatmap of the HotelsPro search results page
Click heatmap of the B2C search results page

Search Results Engagement Analysis

We analysed user interactions on the search results page of both the B2B (HotelsPro) and B2C platforms to identify engagement gaps.

HotelsPro’s (B2B) search result page showed significantly lower engagement compared to the B2C counterpart.

One key friction point was the "Our Picks" module, which users often skipped or ignored. It disrupted the scanning flow and added unnecessary noise to a task-focused experience.

Action taken: We removed the “Our Picks” module and prioritised surfacing the most relevant hotel options based on user preferences and filters—streamlining the experience for returning, task-driven agency staff.

Dashboard wireframe annotated: search module, loyalty points, quick access to-do, customer support
Search results wireframe annotated: our picks, map search, sticky tool bar, filters, booked and favourited hotels, product card
Six dashboard iterations from the old site to the final visual design
Final UI
Agent dashboard · Waiting payments
HotelsPro agent dashboard showing waiting payments with client, hotel, room cost, profit, deadline and a Complete payment button

The dashboard opens on what needs the agent today: unread messages, payments due soon and offers waiting on a client. Search sits on the left, so a new offer is one step away.

What the prototype changed

A separate change came from testing. The first prototype showed the whole search module at once, and we got a lot of feedback about its complexity. I changed it to a progressive search bar that takes the agent through one step at a time.