Skip to content

Product-led SaaS, live product

Retention UX Rework

A rework of the flows people use every day in a live SaaS product, designed and built to ship in phases.

Industry
Product-led SaaS
Timeline
8 Weeks
Platform
Web App
Engagement
One-off project

Scope

  • 5

    Core flows

    Onboarding, the first key action, the daily view, settings and upgrade are the usual candidates for rework.

  • 8 wk

    Timeline

    Two weeks of research and audit, four of design and build, two for phased release and follow-up fixes.

  • 10

    User sessions

    Recorded sessions and short interviews with current users ground the audit in what people actually do.

  • 3

    Release phases

    Changes ship in three batches behind flags so each one can be checked before the next goes out.

People rarely leave a product over one bad screen. They leave after a hundred small moments of friction. Retention work means finding those moments in the flows people use daily and removing them.
Veoc TechProduct Design

A product that is already live carries its history in the interface: features added at different times, patterns that almost match, an onboarding flow written for an earlier version. New users get lost before they reach the part that makes the product worth keeping. This engagement starts with a user experience audit of the existing product. We trace the path from signup to the first useful result, watch how current users move through their regular tasks, and mark each point where the interface asks for more effort than the task deserves.

Sable Records new release page
Countersign Inspector: paste an email and get a verdict in fifteen seconds
Sable Records catalog page with vinyl release artwork

We work inside the product’s constraints instead of proposing a redesign that would take a year to build. After the audit, we agree with the product team on a short list of flows where friction is highest and the fix is within reach. Each flow is redesigned around the task it serves: fewer steps, clearer defaults, better empty and error states, and wording that says what will happen. Design engineers prototype in code against the real component library, so what gets reviewed is close to what will ship and edge cases show up early. Where patterns have drifted apart, we consolidate them into shared components as we go.

Release is planned from the start. Changes are grouped into phases, shipped behind feature flags and checked against agreed product metrics before the next phase goes out. We either build in the client’s codebase alongside their engineers or hand over production-ready components and specs, depending on how the team prefers to work. Each phase closes with a short review of what the data and support inbox are saying, and anything that needs adjusting is fixed before moving on. The final handover covers the updated components, the reasoning behind each change and a list of what we would look at next.

Lentisca thyme honey product page on a laptop and phone

How we work

  • The audit covers the product as it is used, through recorded sessions and interviews, not as it was specified.
  • Scope is a short list of high-traffic flows. Reworking five flows properly does more than restyling fifty screens.
  • Prototypes are built in code with the real component library, so reviews happen on something close to the shipped result.
  • Changes go out in phases behind flags, with product metrics agreed beforehand and checked after each release.

The product team ends the engagement with reworked core flows in production, a tidier component library and a clear record of why each change was made. The interface asks less of the people using it, and the team has a method for finding the next round of friction themselves.

Retention work does not finish with one project, so the handover is written to keep it going. It documents the patterns we consolidated, the measures we agreed on for each flow and the items we noted but left out of scope. Some teams continue with us on a retainer for new features and further rework; others take the backlog in-house. Both are reasonable outcomes. The figures on this page describe a typical scope for a web product with an established user base. A larger product or a mobile app changes the number of flows and the length of each phase, and we size that during the audit.

Lentisca mobile homepage with product jars
Ask Bright suggested questions and an answer on two phones

More Work