Skip to content
Built at #neatHack

Your first user.Before thereal ones.

Find out whether a stranger can actually use your product, before you spend money acquiring users.

Pick a goal next. First User opens your site and attempts it in a real browser.

A few minutesReal browserWatch it live
01 · Start a run

Tell it what
to try.

Test one journey now, or let it read your site first and suggest which journeys are worth testing.

What happens nextUpdates as you type
  1. 1Opens your site in a real browser
  2. 2Gets in with: public pages only
  3. 3Tries to reach the goal you write
  4. 4An independent check confirms whether it got there
  5. 5Report in a few minutes, with a fix prompt per finding

Leave it empty and the visitor works out what the product does and tries its main feature.

The independent check judges this, not only the wording of the goal.

4How should the visitor get in?

Apps that only offer Google or GitHub login: use a start link.

No QA team required. No pretending a click worked when it didn't.

02 · Demo run

One run,
start to fix.

Demo · an illustrative run on a made-up sitetaskpond.app · start link · 14 steps
1Goal

Create a project and add the first task.

Success looks likeA project appears in the dashboard.
Start linkReal browser
2What the agent observed

“Create project” showed a spinner, then the form stayed on screen with no message.

HighVerifiedSeen again · 8, 11
3The fix it recommends
What to change
Only clear the form after the create request succeeds. If it fails, keep the input and show the error next to the button.
Acceptance
☐ One click creates the project
☐ It appears in the dashboard
Retest
Create “Launch plan” once.
03 · How it works

How it works

  1. 01
    Understand

    Reads your public site and works out what the product does, who it is for and which journeys matter.

  2. 02
    Experience

    A first-time visitor attempts one goal in a real browser, one action at a time, with a screenshot of every step.

  3. 03
    Improve

    Each finding comes with evidence and a fix prompt you can paste into your coding agent.

  4. 04
    Retest

    Check again runs the same goal and tells you what is fixed, still present, new, or not reached.

04 · Trust

Why trust
the report

  • An independent check confirms the result. It never sees the agent's reasoning.
  • Every finding has a screenshot, a step number and the page it happened on.
  • Browser errors hidden from the visitor are captured and listed.
  • Our own failures are kept separate from your site's problems.
  • When we can't confirm something, the report says "couldn't confirm" or "not reached".
05 · Results

Results

Measured on v6, two rounds
7/77 of 7 test journeys completed and independently verified, in two consecutive rounds.
0/30 of 3 broken sites praised.
<1¢Under 1 cent per run, on average.
06 · Who it's for

Who it's
for

Anyone about to show a product to strangers for the first time.

07 · Questions

FAQ

Meet your
first user.

One goal, one real browser, one honest report. A few minutes.

Test my website