SaaS UX design for teams scaling past product-market fit
Pepperplane is a SaaS UX design agency. We redesign the interface that won your first thousand customers so it can carry the next ten thousand.
The SaaS interface that got you here won't get you there
Feature bloat crowds out the core
Every quarter adds surface area. The workflow that made customers love you is now several clicks deep, behind things most of them never use. Growth made the product harder to use.
Onboarding built for ten, used by thousands
Hand-held onboarding does not scale. Activation now has to happen inside the product, without a call, for users who arrive with far less context than your early adopters had.
Design debt slows every release
Without a system, each feature is a fresh set of decisions. Engineering rebuilds patterns that already exist, review cycles lengthen, and velocity drops quietly enough that nobody names the cause.
Enterprise demands pull against simplicity
Bigger customers bring permissions, settings and edge cases your first users never needed. Bolt them on and the product gets heavier for everyone. We design configuration so power stays available without cluttering the everyday.
SaaS UX case studies
SaaS UX design services
Journey and workflow design
We rebuild the core workflow around what your best customers do most, and move the rest out of the way without removing it.
Onboarding and activation design
Self-serve onboarding designed for the user who arrives cold, so activation stops depending on your customer success team.
Design systems
A documented component library your engineers build from, so new features ship consistent and design stops being the bottleneck.
Built for the next stage of growth.
We help SaaS teams simplify products that grew faster than their design. We protect the workflows customers love, clear out the clutter, and leave behind a system your team can extend.
Workflow first
We start from what your best customers do most, then design everything else around it.
Systems that scale
Documented design systems that let engineering ship new features without reopening old decisions.
Senior designers only
You work directly with experienced designers who understand the stakes in your industry. No account managers, just direct collaboration.
Our SaaS UX design process
We are a globally distributed team, which means we work across your hours rather than asking you to work across ours.
Assess
We start with a free UX assessment of what you already have. You get a clear read on where your product loses people, whether or not you work with us.
Define
Research, journey mapping and a scope we both agree on. No work begins until the problem is named and the outcome is measurable.
Design
UI, prototypes and iteration with your team in the room. You see the work as it develops rather than at a reveal.
Ship
Handover with a documented design system, and we stay reachable through build so questions get answered while they still matter.
What success looks like for SaaS teams
With Pepperplane as your partner, your product scales without getting harder to use:
A clearer core workflow
The work your best customers do most becomes the easiest thing to do in your product.
Self-serve activation
Onboarding that gets new users to value without a call from your customer success team.
Faster releases
A documented design system that lets engineering ship features without reopening old decisions.
A prioritised backlog
A ranked view of what to fix next, based on how users actually move through the product.
What our partners say.
Don’t just take our word for it, read what our partners have to say about working with us.
SaaS UX design FAQs
Do you work alongside our in house product team?
Usually, yes. Most of our SaaS engagements sit next to an existing product and design function. We take the work that needs dedicated focus, and we work in your tools and your rituals rather than running a parallel process.
Can you work in sprints alongside engineering?
Yes. We design a sprint ahead where that suits your cadence, and we stay available through build so questions get answered while the work is in flight rather than after it ships.
What happens after handover?
You get the design system, the source files and the documentation. After that, we can run development checks, join ad hoc sessions when questions come up, or provide ongoing support as the product is built and user feedback comes in.
Do we need a full redesign?
Rarely. Most scaling products need the core workflow rebuilt and the rest reorganised, not a rewrite. We start with an assessment, then plan the changes so the highest impact fixes ship first and existing customers never have to relearn everything at once.
How will we know the redesign worked?
We agree the measures before design starts, typically activation rate, time to first value, task completion or support volume on the flows we change. If an outcome cannot be measured, we say so during scoping.
Let's talk about your SaaS product
Start with a free UX assessment of your health tech product. You will get a clear view of what is costing you users, with no obligation to go further.