# Introduction

> Simulated prospects walk your signup in a real browser and tell you where they gave up.

Leakdown sends simulated prospects through your signup in a real browser. They think out loud and quit the way people do. You get one page: where they stalled, in their words, and a fix for each.
Analytics tell you which page people leave from. Leakdown tells you what they were thinking when they left. It runs on the AI CLI subscription you already have (Claude Code, opencode or Codex), needs no API key, and keeps everything it records on your machine.

## What you get

[**The one number**How many finished, how many walked out and why, and how sure the report is.→](https://docs.leakdown.dev/reading-the-report)[**Fix these first**The three pages people left from, a quote, and the steps to see it yourself.→](https://docs.leakdown.dev/reading-the-report#one-page)[**Every session on film**Video, screenshots and a filmstrip of every step with the thought behind it.→](https://docs.leakdown.dev/reading-the-report#evidence)

## Try it

```
git clone https://github.com/0xSarnavo/leakdown-cli
cd leakdown-cli && npm ci && npm run build
npx playwright install chromium
node dist/cli.js your-site.com --ladder --yes --headless
```

When it finishes, open `runs/your-site.com/AGGREGATE.md`. Not sure which flags you want? The [Builder](https://docs.leakdown.dev/build-a-command) writes the command from what you want to know.

## What a run looks like

Six stages print in order. Prospects have one-word names and think out loud at every step.

```
leakdown your-site.com --ladder --yes --headless▸ stage 1/6 · site
  product   API for search over your own docs
  signup    /signup · email + 6-digit code · plan picker
  brief: runs/your-site.com/SITE.md

▸ stage 2/6 · map
  38 pages: docs 21, marketing 9, auth 4, pricing 2, payment 2
  payment  /billing — commit refused by the guard

▸ stage 3/6 · personas
  ✓ 10 persona file(s) written to personas/

▸ stage 4/6 · visit
  10 prospect(s) queued, one at a time: momus, egeria, felicitas, … | haiku, headless
  [momus] [1/12 · 2/10 confusion] Momus: "Pricing is clear. Starting on the free tier."
  [momus] [4/12 · 6/10 confusion] Momus: "This reads like a done page. Where is continue?"
============================================================
  [1/10] ABANDONED
  Where: step 4 on https://your-site.com/signup/step-2
  Why: "The plan selector looks like a confirmation page. I think I am done."
  Session: runs/your-site.com/2026-09-17/10-14-02/wide/haiku/momus
  [##----------------------] 1/10 agents finished
  ...
  filter: 3 replicated ref(s), 1 single-source; 3 session(s) go to the verifier

▸ stage 5/6 · report
  3 of 10 completed their goal. 4 walked out with a reason. 3 ran out of patience still trying.
  Fix first: your-site.com/signup/step-2 — 3 of 10 walked out here

  Full report: runs/your-site.com/2026-09-17/10-14-02/AGGREGATE.md, then REPORT.md beside it

```

## Explore the docs

[**Quickstart**From nothing to your first report in five commands.→](https://docs.leakdown.dev/quickstart)[**How a run works**The six stages, what each writes, how a session ends.→](https://docs.leakdown.dev/how-it-works)[**Builder**Pick the job, type your site, copy the command.→](https://docs.leakdown.dev/build-a-command)[**Goal tests in CI**A pass or fail on every deploy.→](https://docs.leakdown.dev/goal-tests)[**Commands**Every flag, filterable.→](https://docs.leakdown.dev/commands)[**Requested runs**Have us run it and email you the report.→](https://docs.leakdown.dev/requested-runs)

## Before you rely on it

Only test sites you own or have written permission to test

A run creates real accounts and triggers real emails and webhooks. Use a staging copy when you can.
Leakdown is in alpha. A finding is a risk to check on your own page, not a measurement of your traffic. Under three sessions the report says too few to call. [Safety](https://docs.leakdown.dev/safety) lists what a prospect never does.

---
Source: https://docs.leakdown.dev/introduction