Skip to main content
SaaS · B2B Products

SaaS UX designer for B2B startups.

SaaS UX is the long game. Sign-up is easy; getting a user to day-30, day-90, then to renewal is the real design problem. I'm a freelance SaaS designer working end-to-end on onboarding flows, role-based dashboards, and design systems that hold together as the product grows from one feature to ten.

On Enrichplay I built a responsive design system across mobile and a 1440px desktop dashboard with one component library and two density tokens carrying the breakpoint. That same system thinking is what most B2B SaaS products are missing — and what I bring as a UX designer for SaaS products.

Available now · 1 slot open
Or email me
Why SaaS UX is hard

The job isn't the sign-up — it's the ninetieth day.

The first thing I tell SaaS founders on the discovery call: the metric you're actually designing for is retention, and retention is invisible. You can't see it in a Figma file. You can only design the conditions for it — a first-week experience that doesn't overwhelm, a primary surface that answers the question the user came in with, a billing screen that doesn't feel like a trap when they want to upgrade.

The second hard thing is the persona problem. A B2B SaaS product is almost never designed for one user. There's the founder who bought it, the PM who rolled it out, the end-user who has to live in it forty hours a week. All three open the same app and see the same UI. Designing for one usually breaks it for the other two.

The third is feature gravity. v1 is a feature. v2 is three features. v3 is a platform that needs a navigation rethink. Most SaaS UIs end up as accretions — every feature added a new tab, every tab added a new pattern, and now the IA reads like a Slack channel list someone forgot to clean up. The fix is a SaaS design system designed to absorb growth, not retrofit it.

The fourth — and this one is specific to dashboard-heavy products — is that the end-user is usually non-technical. They want the answer, not the metric. The dashboard I designed for a SaaS product should read like a sentence: this is good, this is bad, here's what to do about it. Numbers serve copy, not the other way around.

Where the hard work lives

What I focus on as a SaaS UI designer.

  • Onboarding that retains, not just signs up

    SaaS onboarding has two jobs — get the user to first value, and get them to come back. I design for time-to-first-value rather than form completion. Less "set up your workspace, your team, your billing, your integrations" upfront; more "do the thing you came here to do, we'll collect the rest as you need it."

  • Multi-tenant + role-based UI

    Most SaaS products have at least three personas in the same product surface — admin, member, viewer — and the UI either pretends they're identical or forks into three different products. I design role-aware components: same screens, different affordances, with one source of truth in the design system.

  • Information architecture for products that grow

    A SaaS product at v1 is a feature. At v2 it's three features. At v3 it's a platform with a navigation problem. I design IA that can accept new features without a full nav redesign every quarter — pattern-based hierarchies, not pixel-precise sitemaps that break the moment scope shifts.

  • Dashboards + data viz for non-technical users

    The end user of a B2B SaaS dashboard is usually not the one who bought it. I design data surfaces for the operator — clear primary metric, secondary metrics in context, drill-downs that don't require a tooltip to explain. Tabular figures, plain-language axis labels, defaults that answer the question the user came in with.

How it works

Four steps to shipped.

  1. Discovery call

    30-min free call. We figure out if we're a fit and what the engagement looks like.

  2. Fixed-scope proposal

    Within 48h, you get a written scope with timeline and price. No hourly billing.

  3. Kickoff + 6-phase build

    Research → Wireframes → Visual → Test → Handoff. Weekly Loom, async Figma.

  4. Handoff + 2 weeks Q&A

    Dev specs, animation specs, 2 weeks in your engineering Slack.

See the full 6-phase process
Featured case study

Enrichplay — one product, two surfaces, one system.

Enrichplay is a crypto product I designed end-to-end with founder Abdul Ahad Magsi — but the responsive system underneath it is the SaaS-relevant story. Two density tokens (compact for mobile, spacious for web) carry the breakpoint. The component library is identical between surfaces; what changes is the composition around it. That's the same problem a SaaS dashboard solves every time it scales from a phone to a 1440px monitor.

The pattern I'd carry into a SaaS engagement is the same: build the system before the screens, design density tokens that handle the breakpoint, push one-offs back into components before they calcify.

Read the Enrichplay case study
Solo
UI/UX designer, end-to-end
Mobile + Web
Responsive system, two viewports
2 tokens
Density tokens carry the breakpoint
1 library
Component library, both surfaces
Pricing

How to work together on SaaS.

Three engagements — most B2B SaaS work fits a Sprint or Full Project; long-term roadmap work fits the Retainer.

  • D
    1–2 weeks

    Design Sprint

    Quick win, ship in 2 weeks.

    $450

    A focused engagement to fix a specific flow, audit an existing product, or design a single feature end-to-end.

    • 1–2 weeks of focused design time
    • 1 specific flow OR a heuristic audit
    • Hi-fi screens for desktop + mobile
    • Interactive Figma prototype
    • Async Loom walkthrough at delivery
    • 1 round of revisions
    Best forFounders who need a specific thing done well, fast — landing page, onboarding flow, settings redesign, or an audit before raising.
  • Most chosen
    F
    4–8 weeks

    Full Project

    End-to-end, research to handoff.

    $800–$1,200

    The full engagement — user research, wireframes, hi-fi screens, prototype, usability testing, and developer handoff.

    • Discovery interviews + research synthesis
    • Wireframes for every flow
    • Hi-fi design (iOS + Android OR desktop + mobile)
    • Design system + reusable components
    • 5-person moderated usability test
    • Interactive prototype + walkthrough
    • Dev handoff specs + 2-week Q&A office hours
    • Up to 3 rounds of revisions
    Best forFounders shipping v1 or doing a serious v2 redesign. The work that needs to feel right, not just look right.
  • M
    Rolling, 2-month min

    Monthly Retainer

    Ongoing design partner.

    $500/mo

    Reserved hours every month for ongoing design work — new features, iteration, system maintenance, async reviews.

    • 40 reserved design hours / month
    • Weekly 30-min sync
    • Async Figma + Slack throughout
    • Design-system governance + extensions
    • Roll-over up to 8 hours / month
    • Priority response (< 24h on weekdays)
    Best forFunded startups (seed to Series B) with a roadmap that needs a consistent design hand — and a founder who values speed over RFP processes.

Full pricing breakdown, side-by-side comparison, and add-ons live on the pricing page.

SaaS-adjacent work.

See all case studies
10+
Products Shipped
4+ Years
UI/UX Experience
5
Industries Designed For
4+
Countries Served
Services

What else I design.

SaaS-specific questions.

  • Yes — alongside the consumer and crypto work. My Enrichplay engagement is the closest reference point I can point to publicly: end-to-end UI/UX, a responsive design system spanning mobile and a 1440px desktop dashboard, role-aware components, density tokens that hold the system together across breakpoints. The patterns transfer directly — most SaaS products have the same shape (a dashboard, a settings area, a billing surface, role permutations, an onboarding funnel). Some B2B SaaS engagements are under NDA, so I'll walk through them on the call.

  • Three things. First, the buyer is usually not the end-user — so the marketing site sells to one person, the product retains a different one. Second, retention is the metric, not signup; consumer apps die at install, SaaS dies at day-30 churn. Third, the feature surface compounds — v3 has ten times the screens v1 had, and the IA has to absorb that without a full redesign every release. I design with all three in mind from week one.

  • Often the better path. Most live SaaS products don't need a system rebuild — they need someone to extend the system that's already there, fix the drift between teams, and document what was never documented. I'll spend the first week reading your Figma the same way I'd read a codebase — what's a real component, what's a copy-paste pretending to be one, what's the migration plan. The output is usually a smaller system that does more work, not a bigger one.

  • Both, but I'd rather scope them as two engagements than blur them into one. SaaS marketing sites have a job (convert) and SaaS products have a different job (retain) — the design language can echo, but the patterns shouldn't. If you need both, the usual order is product first, then a marketing site that honestly reflects what the product feels like. Painted Juttay (ecommerce) is the closest marketing-site reference in the public portfolio.

  • I design role-aware components rather than role-specific screens. The same SettingsRow renders for admin, member, and viewer — what changes is which affordances are live, which are disabled with an explainer tooltip, and which are hidden entirely. The rule I hold: never silently hide a feature a role can't use — show it disabled with a reason, or upsell it. Silent absence reads as a bug; explicit absence reads as a product choice.

  • Depends on scope, but the honest range is 6–10 weeks for a serious v2 of a product that's already in production. Less than that and you're skipping research; more than that and you're probably designing screens that'll be stale by ship date. The first two weeks go to audit + IA, the next four to system + key flows, and the last two to edge states, handoff annotation, and the first wave of dev Q&A. I'd rather scope a tight v2 we can ship than a sprawling v3 that lives in Figma forever.

Related

Also explore.

Available now · 1 slot open

Got a SaaS thing to ship?

Or email me
Based in
Karachi, PakistanUTC+5