How it works

From simulated sessions to verified work items.

UserProof owns the browser, evidence, session limits, kanban workflow, and rerun history. Engineering agents or your team own code changes.

01

Create a project

Set the target URL, allowed hosts, and any explicit test-account notes.

02

Generate personas and missions

Model realistic users with goals, objections, device assumptions, and success criteria.

03

Run browser sessions

Playwright executes bounded browser actions and stores screenshots, URLs, visible text, console errors, and network failures.

04

Review findings

Deduped findings move through review, accepted work, fixed, and verified states.

05

Export and rerun

Accepted cards export JSON and markdown task packets. Fixed cards require rerun evidence before verification.