WTFB

User testing for SaaS products

SaaS churn usually starts before the first invoice. If a new account cannot reach a useful result in the first session, the trial is already lost and no email sequence will recover it.

Testers sign up as genuine first-time users and document the exact step where the product stopped making sense.

What you get: measured facts separated from human judgement.

Start an audit

What we check

Time to first value

How many minutes and how many decisions between signup and the first useful output.

Empty state design

A new workspace with nothing in it is your real homepage. We check whether it teaches the next action.

Pricing comprehension

Testers state which plan they would pick and why. Confusion here is a direct revenue problem.

Onboarding drop points

Every field, permission request and verification step that made a tester consider quitting.

Measured performance

Load timings, layout shift and accessibility failures on the marketing site and the app shell.

Typical findings

  • Signup asking for company size before showing any value.
  • Empty dashboard with no sample data and no first action.
  • Plan comparison table that does not explain the limit that matters.
  • Verification email landing in spam with no in-app fallback.

Questions

Can testers use a sandbox account?

Yes, provide credentials in the task brief and testers will stay inside it.

How many testers do I need?

Three to five is enough to see repeatable patterns in onboarding.

Do I get prioritised findings?

Yes, each finding carries severity and is labelled as measured fact or human judgement.

See also

A roast is an automated audit plus reports from real testers, with evidence attached.