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.

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

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.

🔗 Prototype Validation

Navigational Ease: When clicking through the prototype's booking flows, users experienced noticeably less friction compared to their current, live system.
High Adoption Readiness: The team reacted enthusiastically to the prototype links. They specifically called out that the cleaner, grid-based UI felt "less tiring" to look at for long periods.

🚀 Projected Impact (Post-Launch)

Faster Onboarding: Because the prototype's "step-by-step" flows proved so intuitive, the company projects a massive reduction in the time it will take to train new employees.
Increased Efficiency: By stripping away 20% of the unused features, the finalized software is expected to save the team hours of manual work and reduce data-entry errors.

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