Redesigning a hotel CRM that only experts could use.
BnBerry is a full-service option for hotels and resorts looking to maximize their presence on lodging marketplaces like Airbnb & Vrbo — listing creation, guest communication, and full account management. Its operations team worked in a powerful but outdated CRM, and I was asked to design a modern replacement.
Where BnBerry sits
BnBerry connects a hotel to channel managers and pushes listings to platforms like Airbnb, Vrbo and Flipkey — with integration, listing optimization and guest support handled by the team.
The problem
Operations managers were using an outdated CRM with great functionality but poor UX. Because of the legacy, new features were layered on top of each other, designed by developers without a UX designer.
The interface kept getting more complicated, even for skilled users, and it took new users a few weeks to get used to everything. The product was also bloated with features nobody was using.
Goals
I had a very ambiguous task — create a new modern interface — which I broke down into four goals.
- 01Cut out the features that are not used
- 02Speed up or simplify the base scenarios
- 03Reduce reservation processing time
- 04Move all main functionality into a modern, simplified interface
Research
There was a lot of system analytics but almost no product analytics — nobody knew which features were used. After talking with developers and managers, I found an interface that was overloaded, hard to read, visually outdated, and didn't support users' main scenarios.
We ran a competitive analysis of modern SaaS and CRM systems to see how they handle complex nested data, navigation across many pages, and onboarding. Using these insights we built several concepts and tested them with hotel managers.
Information architecture
Conversations with operations managers turned into user stories, which shaped the main user flows and then the site map.
After reviewing the data structure, we reduced the number of items in the navigation menu from 27 to 9.
Prototyping for validation
Using high-fidelity mockups, I built a prototype in Figma. It let stakeholders interact with the product realistically and give constructive feedback.
Usability testing
The first round showed a critical issue: only 37.5% of tasks were completed successfully — the CRM was hard to understand and navigate without help. After UX changes, a later round showed most tasks completed by most users.
Design
After many iterations and rounds of testing, we launched a beta. The system now includes a central guest database, a reservation system, task management for guest requests, and reporting for key metrics.
To save resources, we built on ready-made Tailwind CSS components and added only a few new elements — much faster than creating our own library.
Addressing pain points
Listing creation is the main path in the CRM. Before, managers filled in about 30 fields per listing, taking around 15 minutes.
I reviewed the data structure with the product team and reduced it to 16 fields, combining property-wide fields so they're filled only once. Now the first listing in a property takes about 9 minutes, and each next one about 4.
- 0130 → 16 fields per listing
- 02~15 → 9 minutes for the first listing
- 03~4 minutes for each next listing
What's next
The product is in beta on real data, and our managers are solving business problems in the new interface. We're collecting feedback and preparing a version for external users, with its own onboarding.