UX audit
Mapped user flows, identified friction points, and documented usability gaps in the legacy system.
Envy
Growing an internal finance tool into a product other agencies could use, without breaking the work it already supported.
Role
Product Designer: UX, UI, interaction design and feature integration
Challenge
The existing system was business-critical and built for internal operations, while the next version had to work for external customers.
Goal
Make the product clearer, more scalable and ready for onboarding, while respecting its existing logic.
Project overview
The client approached me with a working internal financial management system used by their agency to track revenue, payouts, cash flow, and performance.
The tool was functional and business-critical, but it was designed for internal operations, not for external customers. As interest from other agencies started to grow, the team decided to evolve the product into a scalable, market-ready SaaS solution.
My task was not to redesign from scratch, but to carefully transform and mature the existing system into a clear, structured, and commercially viable product experience.
Goals
- Transform an internal tool into a scalable, product-ready platform without disrupting its existing logic.
- Improve overall UX clarity and navigation structure
- Elevate visual design to SaaS-level quality
- Simplify complex financial views
- Introduce missing product features
- Prepare the system for external onboarding
- Maintain operational stability during evolution
Challenges
- Evolve an already working system while respecting existing architecture and business processes.
- Work within predefined data structures and flows
- Identify what to keep, improve, or remove
- Reduce cognitive overload in financial dashboards
- Clarify terminology for external users
- Improve hierarchy without breaking workflows
Starting point
Starting point
This was the product before the redesign phase. It was operational, stable, and already used by real teams. However, it was built primarily for internal use, and the next step was to transform it into a polished, market-ready SaaS platform.
Product foundation
Structure and research first, visual after.
Scope definition
Aligned business goals with product direction and clarified what to keep, improve, or remove.
Legacy system review
Analyzed existing architecture, data structure, and technical constraints before proposing changes.
Competitor check
Reviewed similar SaaS finance tools to understand industry standards and differentiation opportunities.
Information architecture
Reorganized navigation, dashboard hierarchy, and module grouping to reduce cognitive load.
Visual direction
Defined typography, color logic, and scalable component patterns for a product-ready experience.
Final results
After research and alignment, I moved into iterative improvements: first the structure and navigation, then the individual modules and visual consistency. These screens show how the existing tool evolved into a more coherent product experience.
The main decision-making dashboard, redesigned to prioritize key financial metrics, improve hierarchy, and reduce cognitive load.
A structured view of financial accounts and cash movement, redesigned for clearer tracking and faster operational control.
Deals connect revenue with the work and people behind it, so the team can inspect more than a headline number.
The reporting views separate overall performance from the composition of revenue, making dense financial information easier to follow.
A dedicated revenue mix view helps people compare sources and see changes over time without rebuilding that picture from separate reports.
I also explored an AI copilot as a way to ask questions about the financial data. This was a design direction, not a claim of a shipped feature or measured result.
Summary
What this work changed
Envy is a story about product evolution: making an existing, operational finance system easier for a wider audience to understand and use while preserving the workflows already embedded in the business.