Skip to content
Contact
Journal

Before you redesign a SaaS product

Before you redesign a SaaS product

A redesign is the most expensive way to fix a product that nobody has looked at closely. Most of the value comes from the work before the first new screen. This is what we do first, and what you can prepare before you talk to a studio.

Redesign, small fixes or a prototype first

A product needs a redesign when it works, people have used it, and it still looks dull, uniform or dated next to its competitors. Useful features are not enough if nobody enjoys opening the product. Technology is available to everyone today, AI products compete with each other, and a new competitor can copy your best features in weeks. What stays yours is a considered design and the habit of improving it. The difference is the one between an ordinary taxi and a premium car: the same route, a different reason to come back.

A redesign is too early when there is nothing to redesign. Before it comes a prototype: a simple wireframe, a clickable Figma prototype, or a live product in its old design, which is a prototype that already happens to be coded. Better still, a first version with real users and their first feedback. Without that, start with the prototype.

A redesign is also unnecessary when the product already looks as good as its competitors and has been tested with users. Then it needs support instead: regular reviews, feedback from customers and steady improvements. A product is a process, not a one time delivery.

Say what is actually wrong

“It looks outdated” is a symptom. Before anything else, write down where the product loses people: the step where trials stop, the screen support explains most often, the task that takes three clicks too many. If you have analytics or session recordings, they usually point to the same few places.

When we came back to Aimgod, nine years after the first version, the visual style was the smallest problem. The real work was structure: every task, habit and goal had to connect to the one question the product exists for. Is my time going where I want it to go?

The first version of Aimgod, a task manager web app from 2017
Aimgod in 2017. A capable task manager, but goals, tasks and progress lived in separate places.
The Aimgod productivity dashboard and day screen after the 2026 redesign, desktop and iPhone
Aimgod in 2026. The same product rebuilt around one question, with the web app and the iPhone app on one design system.

Start with a short UX audit

Before a full redesign we often suggest a short, paid UX audit. It takes about a week and ends with a ranked list of problems: what confuses people, what slows them down, what breaks trust, and which fixes are quick. Some teams stop there and fix the top ten issues themselves. Others use the list as the brief for the redesign, which is then smaller and cheaper because it targets what matters.

A good audit looks at the product from four sides:

  1. Flows. How many steps the main tasks take and where people drop off.
  2. Information architecture. Whether navigation matches how users think about the product.
  3. Interface. Hierarchy, contrast, states, consistency between screens.
  4. Copy. Labels, empty states and error messages, in the language of the user.

Research the job, then the screens

Talk to the people who use the product and watch them do the main task. For Spillsjakk, the chess tournament platform of the Norwegian Chess Federation, that task was running a tournament for pupils and students from start to finish.

On the first call the team told us they knew how the product should work, but development had turned into chaos. Some screens existed as separate pieces, some lived in Excel, some on a default WordPress theme. People were already using it, so it was a real prototype, just a very rough one. We started putting it in order on a Miro board: target audience, goals, a story map, a site map, information architecture and user flows for every step an arbiter takes. The federation’s CTO joined at every stage and confirmed where each function belonged. Only then did we move to wireframes.

Design process for Spillsjakk in three stages: strategy, discovery and solution
Spillsjakk design process. Strategy first, then discovery, then the solution. Each stage was confirmed with the federation's CTO.

A story map is worth the time. It shows the whole journey on one wall, and gaps that are invisible screen by screen become obvious.

Fix the flows before the visuals

Most redesigns that disappoint are new skins on old flows. Draw the shortest path for each key task first, cut the steps that exist for historical reasons and put the information people need on the screen where they need it. Only then move to interface design.

User flow for selecting and managing players on Spillsjakk
User flow for selecting players. Every decision point is drawn before a single screen is designed.

In Spillsjakk this meant one screen per tournament with players, pairings, games and results within reach. An arbiter no longer jumps between pages during a round.

Spillsjakk tournament management screen with pairings, results and quick tips
The tournament screen after the redesign. Pairings, results and help in one place.

Rewrite the copy with the design

Interface text is part of the design. Labels, empty states, error messages and hints decide whether a screen explains itself. We write and edit copy along with the layouts, in the language your users speak. A redesign is also the moment to remove internal names that leaked into the product.

When the client wants it like a competitor

It happens, though rarely in its pure form. Most founders want to look like the leader and still stand apart. We make two lists: what the competitor does that we will keep, and where we will be different, either an extra feature or the same task done another way.

Difference works on three levels. The smallest is visual: larger controls here, a function folded into a menu there. Better is functional, when the product solves the task in its own way. Best is a difference in vision. Aimgod is not one more to do app, it has its own philosophy of focus, and both its features and its interface follow from it. A product that differs at all three levels is hard to copy.

Build a system, not a set of screens

A redesign that is delivered as 80 static screens starts to fall apart the first week a developer adds a new one. Deliver a design system with it: tokens for color, type and spacing, components with their states, and rules for layout. For Aimgod that meant 17 type sizes and 6 weights, from small chart labels to large headlines, all documented as tokens. For Spillsjakk the system covers more than 150 screens in light and dark themes.

Aimgod typography tokens from H1 to micro labels
Aimgod type tokens. Every size, weight and line height is named, so developers never guess.

How long a SaaS redesign takes

It depends on the number of flows and roles, not on the number of screens. A focused redesign of one main flow with a design system can take four to six weeks. A full platform takes longer. Spillsjakk took more than 400 hours of design over eight months, across 150 screens and several user roles, because the product was growing while we worked on it.

Plan the release as part of the project. Decide early whether the redesign ships at once or in parts, how existing users will meet the new interface and what you will measure after launch. Prototype the riskiest flows and test them with real users before development starts. It is the cheapest moment to change your mind.

What to prepare before you call a studio

  1. Access to analytics, recordings or support tickets, even rough ones.
  2. Two or three users who would agree to a short call.
  3. The list of tasks your product exists for, in order of importance.
  4. Your current design files and the codebase stack, whatever state they are in.
  5. What success looks like six months after launch.

To shortlist a studio, open the products in its case studies, not only the pictures, and read what clients say on independent platforms. Creayou is listed and designrush verified among UI/UX design agencies.

With these, the first conversation is about your product, not about process. If you are planning a redesign, see how we work on SaaS product design or tell us about the project.

Read more

Rebuilding creayou.com

Rebuilding creayou.com

How we rebuilt our studio website as a fast static site. Why we moved off Webflow, how the liquid WebGL logo works, light and dark themes from one set of tokens, motion, performance, SEO and a second language.