Travify / redesigning a tour operator’s booking system

I was hired as freelancer by a fast-growing tourism company in Spain to completely overhaul their internal booking management system. The support team uses this tool daily to manage reservations, tours and other data.
Note: To comply with non-disclosure agreements, the client name and proprietary data have been anonymized or deducted.

process.

the problem

The legacy software was outdated and cluttered, causing friction for the staff and requiring a long training period for new employees. My goal was to transform a complex database into a clean, modern SaaS experience.

research

The previous interface suffered from years of "feature creep." To understand what was actually necessary, I didn't just guess—I went straight to the source.
I conducted a deep-dive system walkthrough with the Operations Manager. Together, we audited the existing features and mapped out the team's daily workflows. We discovered that nearly 40% of the visible menu options were obsolete or rarely used.
Key Insight: The team didn't need more features; they needed less noise to perform critical tasks faster.

solution

Armed with this insight, I moved away from the chaotic legacy interface to a functionality-first design.
My strategy focused on three pillars:

Strict Prioritization: Removing the unused features identified in the audit.
Progressive Disclosure: Grouping secondary actions (like "Export" or "Delete") into menus so they don't clutter the view.
Visual Calm: Using a strict grid system and reducing the color palette to lower cognitive load.

key improvements

The following comparison highlights the transformation of two core workflows: Bookings Management and Analytics.

I moved from a rigid, spreadsheet-like interface to a flexible decision-making tool.

before

after

old chart vs new chart in Analytics

old data table vs new data table in Analytics

prototyping

Explore the live Bookings interface built in v0 and the Sales Report workflow in Figma.

impact

While the software is currently in the development phase, I conducted usability testing sessions with the internal support team using the high-fidelity prototypes.

The feedback was overwhelmingly positive, validating the shift to a cleaner UI.

⏱️ Reduced Friction: Users reported a significant drop in "time-on-task" for creating new bookings.

🎓 Lower Learning Curve: New employees found the "step-by-step" flows much easier to understand compared to the old complex tables.

🚀 Adoption Readiness: The team expressed excitement to switch to the new tool, citing that it felt "less tiring" to use for a full workday.

what I've learned.

I learned that effective design requires auditing utility to confidently remove clutter rather than simply polishing obsolete features

I discovered that whitespace is a functional necessity in data-heavy tools that actively prevents visual fatigue and user errors

I found that framing design choices around business efficiency—rather than just aesthetics—was the fastest way to build stakeholder trust