Client
SaaSly
Year
2024
SaaSly is a SaaS management application designed to help large organisations efficiently manage their software estate. The company is a global software provider serving enterprise clients, including Amazon, Bloomberg, Tesla, and Microsoft.
Note: Company name and some details have been altered to protect intellectual property.
Scope of Work
Redesigning SaaSly: From Legacy UI to Scalable SaaS Experience.
As a UX Engineer and later Senior Product Designer, I led the end-to-end product redesign for SaaSly, a SaaS management platform used by large enterprises to manage their software estate.
This case study walks through how I handled the full product lifecycle, from legacy UI overhaul and user research to prioritisation and collaboration with engineering.
A Functional MVP with a Fractured UX.
SaaSly’s MVP was built by an external agency. While it worked technically, analysing SaaS data uploaded via Excel templates and integrating with tools like Zoom and Microsoft, the UI deviated from our design system and lacked cohesion with the rest of our products. Time and budget constraints had led to a fractured experience.
Understanding our users.
To define a clear path forward, we used People for Research to recruit 12 participants, mostly IT managers experienced in SaaS and Technology Expense Management.
We created task-based interview prompts focused on how users navigated core flows and interacted with key features.
We synthesised the feedback using:
Rainbow analysis to spot patterns in pain points and mental models
Affinity mapping across taxonomy, iconography, user priorities, and bugs
This structured analysis helped us clearly communicate the most critical usability issues to stakeholders, assigning percentage weights to issues based on frequency and severity.
What We Learned
42% of users wanted a date picker on the Overview page, that became a top priority.
64% of navigation clicks (tracked through Heap) went through the Applications table, not the intended overview content.
Because of its limitations, users weren't interested in the trend data, so we were able to deprioritise this in the page hierarchy.
As well as this, we made fundamental taxonomy changes based on user feedback. The difference between pages such as Applications and My Applications wasn't clear.