Artificial UsersJoin the waitlist
EARLY ACCESS · FOR FOUNDERS

Find the friction before your users do.

Describe your ideal customer and their goal. An AI stranger tries your web app in your own browser, and shows you where they get stuck.

10 to 14 minutes per run·every finding has its screenshot·runs on your machine, in your own browser
Finding 01Reproducible
Example task app
Launch checklist •••
To do
Done 0
No task found

The task vanished after refresh.

Evidence Replay steps
A stranger, not a friend A screenshot behind every finding Every claim checked against its own screenshot
HOW IT WORKS

Test your product through a customer’s eyes.

Choose who to simulate and what they should try to accomplish.

01 / Describe

Describe your target customer.

Say what your product is and who your customer is. Give that customer one goal, the one you want a stranger to reach.

Define a customer
Customer profile
Freelance marketerFirst time using your product
Customer goal

Organize my next launch.

Works independentlyShort on time
02 / Run

Start a run from your terminal.

When your invite arrives you install once, sign in once with au login, and start each run with au run. It opens your own Chrome on your own machine and your own IP. No source code access, no plan of yours is touched.

macOS, your own Chrome, and a terminal
Launch from your terminal
Your terminalLOCAL

au login

Signed in. 5 sessions.

au run

Chrome opened. Watching the stranger work.
Browser session
Launch checklist
Send launch email
AI user
Trying the customer’s goal
03 / Read

Read what the stranger hit.

Every finding carries the screenshot taken at the moment of the claim and the steps to reproduce it. Fix it, then run it again.

Review the evidence
Finding report
Bug foundThe saved task disappeared.
Task missing after refresh
Screenshot Replay steps
WHAT IT FINDS

Catch broken flows and frustrating experiences.

From things that break to things that make your product harder to use.

WHY TRUST IT

Two rules we follow, and two things it found on real products.

The screenshot is taken at the moment of the claim.

A finding that has no screenshot of its own does not reach you.

Every claim is checked against its own screenshot after the run.

Claims the screenshot contradicts are removed before you read them, and the counts are printed on the report, whatever they say.

On one real product it found a feature that had been silently broken for a month, from the outside, with no access to the code.
On another it surfaced the same complaints three real customers had already made, having never seen those complaints.
EVIDENCE, NOT GUESSWORK

Your report shows what happened and how to reproduce it.

Know what happened, why it matters,
and how to reproduce it.

  • Blockers first, however many, including none
  • A screenshot behind every finding
  • Exact steps to reproduce
  • Clear about the paths it never reached
  • The audit counts, printed on the report
  • It ends in what to do
Saved in your account. Ready to export as PDF.
Session reportExample run

An AI customer tests an online store.

Goal: buy a few items and place a second order.

SCOPE

Could not continue past checkout, because the cart total stopped matching the quantities.

BLOCKERS FIRST
HighCart totals do not match quantities.
THE REST OF THE RUN, BY KIND

Pricing · Sign up · Empty states

Every claim checked against its own screenshot. The removed ones are counted on the report.

Screenshot · Steps to reproduce · F36

Your code and logins stay on your machine.

What leaves it: the screenshots, the page text, the values the stranger typed, and the event log, redacted before they are sent, for the check, the audit and the report. Kept 90 days, deleted on request.

Read the privacy policy
FOUNDING BETA PRICING

Get your first report free.

First run free for accepted beta teams, on your real product. Full report.

Founding pack: $29 for five sessions. Sessions never expire. Another five for $29 whenever you need them.

A session is one run: one stranger, one motivation, one report. A run that fails, or never gets past your front door, does not use a session.

Runs on your machine, in your own browser. No terminal? Join the waitlist and tick the box; you hear first if a version without one ships.

Get your first run freeInvites go out in small batches.Founding beta pricing. If it changes, everyone on the waitlist hears first.
Keep learning Founding pack
$29 / 5 sessions

Each session is one run: one stranger, one motivation, one report.

  • Sessions never expire
  • Buy another five whenever you need them
  • A run that fails on our side does not use a session
What should I expect from a run?

One stranger explores one goal for 10 to 14 minutes. It is one user for one session, not an audit: it finds where a person gives up, not every bug. Two runs find different things.

What can it test?

Web apps in a browser. A run can create a real account and real data, so staging is the default target. It does not test native mobile or desktop apps. A run that never gets past your front door does not use a session.

Do I need a terminal?

Yes, on a Mac with Chrome installed. You install once, sign in once, and start each run from your terminal. No terminal? Join the waitlist and tick the box, and you hear first if a version without one ships.

Do I need a Claude or ChatGPT plan?

No. The model calls run on our own gateway. Nothing of yours is metered.

Can I point it at my live product?

Staging is the default. To run against production you confirm once, per project, that you own the product or have authority to test it, and you see exactly what the run will do before it starts.