Four real runs · nothing cut

Four real reports.
One of them judged us.

A landing page, an ad campaign, an email send, and an audience study. These are the full reports a customer gets. One is our own homepage. The simulation found five things broken on it. No login. Nothing cut.

No login· No form· Experiment AN-90670518· Run 12 August 2026
The conflict graph from WhyUser's simulation of its own homepage: five committee roles, seven handoffs, two of which snap. The End User cannot hand the case to the Technical Decision Maker without documentation, and the Champion cannot hand it to the Economic Buyer without inspectable proof.
whyuser.com · 50 agents · 5 roles · 3 behavioural states · 45 of 50 runs clicked forward · 0 submitted · 2 of 7 handoffs snapped
The library

Pick one. Open it. Nothing is gated.

Each one is the full interactive report. Click any finding, role or handoff to open its record.

Committee Simulation · landing page

whyuser.com, judged by its own instrument

Fifty agents. Five roles. All five ended up convinced. Forty-five of fifty clicked forward. None converted, because two of seven handoffs snapped. It told us our nav was hard to scan and our proof was thin.

Open report
Email Simulation · 360 agents

The subject line worked. The landing did not.

A compliance announcement pulled clicks, then lost people on arrival. One link carried 100 readers on and lost 39. Another got no clicks at all. No preheader was set, so the inbox preview fell back to the greeting.

Open report
Audience Discovery · 32 subverticals

Every blocked buyer held the budget or the veto.

Thirty of 140 titles cleared verification. Of the 17 that scored too low to target, 15 were economic buyers and 2 were guardians. Those are the two roles that stop deals.

Open report
Ad Simulation · 180 agents

The ad did its job. The page asked for too much.

Two LinkedIn creatives, read by three buyers across three moods. Both handed the click a page that kept their promise. Then the page asked for a demo. The ad had promised something far smaller. That gap, not the creative, was the drag.

Open report
Note: Customer runs are anonymised to Acme Corp, because a targeting map and a campaign's click data belong to the customer.
Anatomy

What every report gives you.

Same shape whichever run you open. A verdict per role, the handoff that breaks, and a queue you can hand to whoever does the work.

01 · The verdict

Where each role landed, and why.

Every role that has to approve, scored on its own. Convinced, blocked, or somewhere between, with the line that decided it.

02 · The conflict graph

Which handoff snaps.

Roles pass the deal to each other. The graph shows which pass fails. This is the failure an average score cannot see.

03 · Working and broken

Both sides, with counts.

The lines that landed and who they landed with, next to the ones that lost people, with how many buyers each affected.

04 · The fix queue

Ranked by handoffs unblocked.

Not ranked by page order. Each fix names the element to change and how many buyers it frees.

Every finding traces back to its source in Ground Reality, so you see why a buyer stopped rather than only that they did.

Why it reads handoffs

All five convinced. Nobody could hand it on.

In the committee run against whyuser.com, all five roles finished convinced at intent 7 out of 10. Forty-five of fifty passes clicked forward. None converted, because two of seven handoffs snapped: the End User had no docs for the Technical Decision Maker, the Champion had no proof for the Economic Buyer. No single role failed. An average would have called the page a winner.

Open that report in full

Your turn

Now point it at your page.

Send us the next campaign you have going live. You get the role that blocks it, the proof that is missing, and a ranked list of fixes. About thirty minutes, from a URL.

Plans from $12k/year · see pricing and credits