Travify / redesigning an ERP
I was hired as freelancer by a fast-growing tourism company in Spain to completely overhaul their ERP. The support team uses this tool daily to manage reservations, tours and other data.
NDA Note: To comply with confidentiality agreements, all interfaces, data, and company details have been completely recreated. The UX/UI solutions reflect real project work, but no proprietary assets are shown.
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 20% 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.
I also conducted an analysis of the key players in the booking software market, identifying major competitors such as Bokun, FareHarbor, and PeekPro. I created accounts to explore their interfaces firsthand, gaining insights into their structural approaches and design strategies.
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
Analytics
The Problem: Legacy Analytics
-
Cluttered Visualization: Users were forced into a rigid, heavy bar chart with constant data labels, creating unnecessary visual noise.
-
Poor Data Comparison: The data table duplicated columns across a massive horizontal span, forcing users to scan back and forth just to compare years.
-
High Cognitive Load: Dark headers, tight spacing, and an overwhelming amount of raw data made the interface exhausting to read.
-
Hidden Insights: With no clear indicators, users had to manually calculate the math to figure out if there was a growth or decline.
The Solution: A Flexible, Calmer Dashboard
-
Progressive Disclosure: Data labels are hidden to reduce clutter; users simply hover for exact numbers.
-
Customizable Views: A new toggle lets users switch between chart types (like line or bar).
-
Logical Grouping: Columns are grouped by category (not year) for direct, side-by-side comparison.
-
Clear Indicators: Color-coded percentages instantly highlight growth or decline.
-
Visual Calm: Increased whitespace and softer headers make the table much easier to scan.
prototyping
Dive into the interactive Figma Make Prototype to get a feel for the new Tours interface. Feel free to play around with the dashboard-try adjusting the filters on the Overview screen, walk through the flow of creating a brand new tour and test out the management actions by selecting and deleting it afterward.
impact
Because the software is actively in development, I validated the new experience by having the internal support team test interactive, high-fidelity prototype links. Testing these flows before handoff allowed us to gauge success and project future business impact without writing a single line of code.
💬 Qualitative Feedback
- Intuitive Navigation: Users reacted highly positively to the prototypes, reporting that the updated flows were significantly easier to use and that they could effortlessly find everything they needed without confusion. They reported that the cleaner, structured UI was much "less tiring".
📊 Quantitative Metrics
- Faster Task Completion: Efficiency improved dramatically. Depending on the complexity of the workflow, users saved between 3 to 6 minutes per task during testing.
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