Tell me about the UX review.

Onboarding UX Review

I go through your signup the way a new customer would, up to the first moment your product is useful, and rank what to fix first.
Price
$750 fixed
Scope
One flow Up to 8 screens
Devices
Desktop and mobile
Turnaround
7 business days from start

Who it's for001

B2B SaaS teams of 2 to 50 people with no in-house product designer.

New users sign up, then stall, and you’re not sure what’s putting them off.

What you get002

A review of one flow, up to 8 screens, each checked on desktop and mobile.

  • 01

    Ranked findings table

    Screenshot, issue, why it matters, fix, severity and effort.

  • 02

    Top five summary

    A one-page summary of the top five fixes.

  • 03

    Walkthrough call

    30 minutes to go through the findings together.

  • 04

    Follow-up

    One round of written questions within 14 days.

How it works003

Your time: about an hour in total, covering a scoping email, a test account and a 30-minute call.

  • 01

    Email me

    Your product URL and where users drop off.

  • 02

    We agree

    The flow, the screens and a start date.

  • 03

    You share

    A public URL or a test account.

  • 04

    I review

    The flow on desktop and mobile.

  • 05

    You get the report

    Within 7 business days, then we walk through it together.

Example deliverable004

A made-up product, to show what the report looks like.

Fictional example: project and time-tracking tool for agencies · Flow: signup → workspace setup → invite team → first billable hours logged · Devices: desktop and mobile

Where users hit friction

  1. Signup
  2. Workspace setup
  3. Invite teamFinding 1
  4. Empty project listFinding 2
  5. Start timerFinding 3
  6. First billable hours loggedFirst value
Highlighted steps have friction; numbers match the findings table. Fictional example.

Annotated screen: “Invite your team” on mobile

  1. Finding 1

    Setup blocks on inviting a teammate. Admins evaluating alone can’t reach the product without involving colleagues.

  2. Finding 2

    Next, an empty workspace. There’s no client or project and the timer is disabled, so users must build structure before seeing the core value.

  3. Finding 3

    No timer in the mobile tab bar. The timer is nested inside project detail, so logging time on a phone takes several taps.

Annotated “Invite your team” setup screen, mobile. Fictional example.

Before and after: fix 1

Before: the setup step is blocked until the user invites at least one teammate; the Continue button is disabled. After: inviting is optional, with “Log your first hours” as the main action and “Invite teammates” and “Invite later” as secondary options.

Before and after sketch of the invite step. Fictional example.

Top five fixes

  1. Let the admin skip “Invite your team” and log their own first hours before inviting anyone.
  2. Pre-fill a sample client and project so the first timer can start in one click.
  3. Move billing rates and currency setup out of signup; ask when the first invoice is created.
  4. Make the mobile timer reachable from the home screen, not three taps into a project.
  5. Replace the generic “Welcome!” email with one link back to the unfinished setup step.

Fix 1 is ranked first because it stops solo evaluators completely.

Findings (excerpt). Severity and effort are my judgment calls.
#ScreenIssueWhy it mattersSuggested fixSeverityEffort
1Invite teamSetup blocks on inviting at least one teammateAdmins evaluating alone can’t reach the product without involving colleaguesMake inviting optional; prompt again after first hours are loggedHighLow
2Empty project listNew workspace has no client or project, and the timer is disabledUsers must build structure before seeing the core valuePre-fill an editable sample client and projectHighMedium
3Mobile, timerTimer is nested inside project detailLogging time on a phone takes several taps, so it’s easy to abandonPersistent start-timer button on the mobile home screenMediumMedium

Your report includes screenshots like these, of your own product.

Questions005

Before you ask.

  • Do you implement the fixes?

    No. You get clear recommendations; your team decides what to build.

  • Will this increase conversion?

    I can’t promise results. I can show you where users are likely to struggle and what to try first.

  • How does payment work?

    I send an invoice once we agree the scope. Payment is due before the start date, with a full refund if you cancel before then.

  • What access do you need?

    A public URL or a test account. Never send production passwords or real customer data.

  • Is my product kept private?

    Yes. I don’t share your product, access or report. If I use any tools on your material, I’ll ask you first.

  • What’s not included?

    User testing, analytics, redesign files, code, copy rewrites, more than one flow, accessibility certification or legal advice.

Get started006

Losing new users before they see value?

Explore projects

EmailLinkedInGitHub