Early access. Every feature on this site carries its status. Where we are today
Website research that answers why

See what they saw. Ask them why. Know your fix worked.

RevealWhy is being built to show what every visitor saw, ignored and missed on each page, ask them why, and tell you whether your change worked, with the evidence for every answer.

Some of this is live and some is being built. Every feature on this site carries a tag. Where we are today →

finding · product page · mobileIllustration

[X%] of mobile visitors never saw the delivery line.

  1. ChangeMove it above the price.
  2. Watch3 moments that show it, at the exact second.
  3. Checkedworkeddidn'tcan't tell yet

An example of the shape of an answer, not a customer result. [X%] is filled only from real data.

Answers, not recordings

People don't want more footage. They want to know what's going on.

Recordings and heatmaps are included. They're not the point: the answer is, with the few moments worth watching.

What it does

See. Ask. Know. Hand it off.

See

See what they saw

For every element on every page: seen, ignored, hovered or missed. Attention counted only where people really looked.

  • For every element on every page: seen, ignored, hovered, missed, by device Building
  • Attention counted only where people really looked Building
  • Real eye tracking in the browser, in studies people join Building
How it works →
Ask

Ask them why

An interviewer that has seen what each person did and missed, and asks about those moments. With your real customers, not professional testers.

  • An interviewer briefed on what each person did and missed Building
  • Studies with your own customers, through your own link Live
How it works →
Know

Know it worked

Every change checked against your other pages: worked, didn't, or can't tell yet. No inflated wins.

  • Every change checked against your other pages: worked, didn't, or can't tell yet Building
  • No inflated wins Building
How it works →
Hand off

Hand it off

Your coding agent gets the fix, and the check runs itself. Agents try your key journeys on every release.

  • Your coding agent gets the fixes Building
  • The check runs itself after a fix Building
  • Release check: key journeys tried on every release, stopping before payment Pilot
How it works →

How a week looks

One question a week, answered with its evidence.

  1. 01

    Monday's question

    "Why do mobile visitors leave the product page?"

  2. 02

    The answer, with evidence

    What they saw and missed, how sure we are, and the moments worth watching.

  3. 03

    The fix

    To your coding agent, developer or agency.

  4. 04

    The check

    Against your other pages, so the season doesn't fool you.

  5. 05

    Worked, didn't, or can't tell yet

    Said plainly. No inflated wins.

  • Ask a question, or let us suggest one Building
  • One question a week, answered in your inbox Building
  • The 3–5 moments worth watching, at the exact second Building
  • Every change checked against your other pages: worked, didn't, or can't tell yet Building

Our promises

What we're committing to, and where each stands.

  • A price that doesn't move: one monthly price, bots never billed, no surprise overage Building
  • Evidence on every answer, and "can't tell yet" when we can't Building
  • Privacy by default: typed text never recorded Building
  • We'll tell you if you're not using it, and offer to pause billing Building

Ask your first question.

Start with one page and one question.