This is taking longer than expected.

Try againBrowse the library
AI Blocks

All AI specialists

Hire an AI store page experiment reviewer

Give it heatmap, scroll map and recording notes for the page, or screenshots of them. You get a friction list ranked by page and money at stake, with a friction score out of 100.

What you give

  • Heatmap, scroll map and recording notes for the page, or screenshots of them
  • Your funnel numbers, from visits, add to cart, checkout and orders, with traffic sources if you have them
  • After the pause, the exported results of the test you ran

What you get

  • A friction list ranked by page and money at stake, with a friction score out of 100
  • Every page issue sorted into fix now, investigate or test, with its proof
  • A ranked list of tests with the one or two to run first and the reasons the rest wait
  • A test readiness score out of 100, the visitors needed and whether it can finish in about four weeks

An example

Your store has steady traffic but few orders, and you want evidence before you change the page.

You ask: “Give it heatmap, scroll map and recording notes for the page, or screenshots of them. Use the material I attach and ask for anything essential that is missing.”

You get back:

  • Friction list. Friction ranked by page and money at stake, with a test idea for each and a friction score out of 100.
  • Sorted issues. Every issue with its proof, sorted into tracking faults, obvious fixes, causes to investigate and test ideas.
  • Test ranking. A ranked list of tests, the one or two to run first, and parked ideas with what would move them up.

An example, not your task.

Hire this specialist

It is free and needs no account. Download the pack, give it to your AI and tell it the job. Your AI asks for anything it is missing, then does the work and checks it.

Download the specialist

Related specialists

Skills and workflows for this job: Audit a landing page

Details

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

  • A friction list ranked by page and money at stake, with a friction score out of 100
  • Every page issue sorted into fix now, investigate or test, with its proof
  • A ranked list of tests with the one or two to run first and the reasons the rest wait
  • A test readiness score out of 100, the visitors needed and whether it can finish in about four weeks
  • A call on the finished test (ship, do not ship, re-test or inconclusive), a result as a money range and a log entry

How it does the job well

  • Write for one named audience and one action. Each asset has a single job.
  • Use the customer's own words from reviews, calls or surveys before inventing language.
  • Every claim needs proof the business can show. Leave unproven claims out or mark them.
  • Judge results against the business goal, such as profit or qualified leads, not clicks alone.

Mistakes it avoids

  • Generic copy that could fit any brand.
  • Comparing periods or campaigns that are not comparable, such as different dates, budgets or tracking.
  • Calling a test winner before there is enough data.

What a good result looks like

An example, not your task: Your store has steady traffic but few orders, and you want evidence before you change the page.

  • Friction list. Friction ranked by page and money at stake, with a test idea for each and a friction score out of 100.
  • Sorted issues. Every issue with its proof, sorted into tracking faults, obvious fixes, causes to investigate and test ideas.
  • Test ranking. A ranked list of tests, the one or two to run first, and parked ideas with what would move them up.
  • Traffic check. Revenue per visitor by source, visitors needed, days at your traffic and a test readiness score out of 100.
  • Test verdict. A ship, do not ship, re-test or inconclusive call, a trust score, a result as a money range and a log entry.
  • HAND-BACK SUMMARY. Each step's file, any step not run and why, and every MISSING line in one list.

How the work is checked

  • Each step passed its own checks, or the run stopped at the step that failed and says why.
  • The steps ran in order, and each one used the result of the one before.
  • Nothing was invented to fill a gap. Every gap is a MISSING: line.
  • Nothing was sent, published or paid for without a clear yes.
  • States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Peep Laja would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

  • Read the heatmaps. Reads clicks, scroll depth and recordings, weights friction by money and not raw clicks, and writes a friction list with a score out of 100.
  • Sort the page issues. Lists every issue with its proof. It tags tracking faults and obvious fixes, marks unclear causes to investigate and turns the rest into test ideas, ranked by gain and effort.
  • Rank the tests. Counts the evidence for each test idea, picks honest chances of winning and names the top one or two to run. The rest are parked with what would move them up.
  • Run the test. A pause. You run the top test on live traffic until it has enough orders, then export the results.
  • Check the traffic. Works out revenue per visitor by source, sizes a fair test with the standard sample formula, and says whether it could finish in about four weeks. It scores test readiness.
  • Give the verdict. Checks the traffic split, run length and early stopping, reads the result as a range in money, and gives a ship, do not ship, re-test or inconclusive call with a log entry.

How the role works

  1. Checks your task, context and available tools.
  2. Picks the methods needed and prepares a work plan.
  3. Carries out supported tasks, with each method's limits and review gates.
  4. Checks the real deliverables and corrects supported faults.
  5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id find-where-your-page-loses-buyers-and-prove-the-fix only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/find-where-your-page-loses-buyers-and-prove-the-fix/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

  • Heatmap, scroll map and recording notes for the page, or screenshots of them
  • Your funnel numbers, from visits, add to cart, checkout and orders, with traffic sources if you have them
  • Customer reviews or survey comments (optional)
  • After the pause, the exported results of the test you ran

Tools and access

  • Microsoft Clarity: Free heatmaps, area maps and recordings with the rage and dead click insights this skill reads.
  • GA4: Free funnels in the Explore tab, and sessions you can compare with your platform dashboards.
  • A store survey app: Gives you the 'why' behind what the heatmap shows, tied to order data.
  • Any good chat AI: Sorting and ranking a list with reasons is text work any strong chat AI does with this skill.
  • A spreadsheet or task board: Holds the ranked list and tracks what is done.
  • Any good chat AI: It writes hypotheses and does the profit sums from your pasted findings.
  • A spreadsheet: Keep the leaderboard there so you can re-sort it when new proof comes in.
  • Any good chat AI: The sums are simple, and the main chat AIs all show their working when asked.
  • Google Sheets: Keeps each month's numbers in one place, so you can check every sum and compare with your own past.
  • Evan Miller's sample size calculator: Free, and a quick second check on the visitors per version.
  • Any good chat AI: It does the checks and the money sums from your pasted numbers.
  • Your testing tool's export: Users per version, conversions and dates come straight from its results page or a CSV.

Functions and deliverables

  • Store page experiment reviewer: Review page behaviour, rank changes to test and check the real test data before deciding to ship, stop or keep running.
    • A friction list ranked by page and money at stake, with a friction score out of 100
    • Every page issue sorted into fix now, investigate or test, with its proof
    • A ranked list of tests with the one or two to run first and the reasons the rest wait
    • A test readiness score out of 100, the visitors needed and whether it can finish in about four weeks
    • A call on the finished test (ship, do not ship, re-test or inconclusive), a result as a money range and a log entry
  • Heatmap and session recording analyst: Share heatmaps, page data and recording notes. Get possible shopping problems, evidence gaps, repair ideas and a plan for what to watch next.
    • A friction list ranked by page and money at stake
    • A hypothesis and a test idea for each problem, and a fix list for repairs
    • A watch plan for recordings: which, how many and when to stop
    • A friction score out of 100, now and after the fixes, with the sum shown
  • Page issue sorter: Sort a long list of page problems into fix now, investigate, test or tracking, then rank them. Get a clear plan for your page issue list.
    • Each issue in one bucket with its reason
    • Test ideas written as: change, expected effect, why
    • A ranked order by likely gain and effort
    • A list of issues dropped for lack of proof
  • Test idea ranker: Paste your research findings. Get each test written as a hypothesis and ranked by evidence and profit.
    • Each idea written as a hypothesis with a main metric and a smallest lift worth shipping
    • A ranked leaderboard with evidence points and a profit estimate
    • The one or two tests to run first, and the rest parked with a reason
    • A fix list for anything broken
  • A/B test traffic checker: Check if your site has enough visitors for an A/B test. Paste visits, orders and revenue to get the weeks needed and a readiness score out of 100.
    • A numbers table with conversion rate, average order value and revenue per visitor, each sum shown
    • A short read of what moved and what the traffic mix explains
    • The test sizing written out, with visitors and weeks needed
    • A verdict (can test, test a bolder change, or ship and watch) and three next actions
    • A test readiness score out of 100, showing how much of the needed sample your traffic reaches in four weeks
  • Store test evidence reviewer: Check if your store test result can be trusted. Get a ship call, the lift as a range in money, and a trust score out of 100.
    • Pass or fail on the split, run length, early stopping and tracking checks
    • The lift as a range, and what it is worth per month in gross profit
    • One call: ship, do not ship, re-test or inconclusive
    • A trust score out of 100 with the sum shown, and a test log entry
  • Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
    • A folder of eight plain files, from a start file for your AI to a claims list and a change log
    • A tag on every fact, and every claim marked approved, pending or banned
    • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
    • A short slice for your next step, if you name one
  • Peep Laja: Review page messaging or an A/B test using Peep Laja’s recorded approach. Start with buyer evidence, clarity and a sound comparison plan.
    • Your problem worked on the way Peep Laja would: their questions, their method, their push-back
    • The answer or the work, in Peep Laja's voice, using their ideas by name
    • Anything that goes beyond their public record, marked
    • One suggested next step

Tasks you can use it for

  • Your store has steady traffic but few orders, and you want evidence before you change the page.
  • You ran a test and want to know whether you can trust the result.
  • Someone on the team wants to redesign a page and you want a ranked reason to change one thing first.

Limits to check before starting

  • Your store gets only a few orders a week, so a test cannot finish. Make the obvious fixes and watch your numbers instead.
  • You only want to check whether a finished test had enough traffic: use the A/B test traffic checker.
  • Your sales dropped and you need to know why: use the Ad sales drop analyst.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

  • Download the handoff pack. It's a zip with HANDOFF.md plus one skill file for each step.
  • Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
  • Give it the heatmaps, recording notes and funnel numbers for one key page.
  • Make the obvious fixes it lists before you test anything.
  • Run the top test until the traffic check says it has enough orders, export the results and give them back.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/find-where-your-page-loses-buyers-and-prove-the-fix for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.