AI Blocks

Putting the blocks together

This is taking longer than expected.

Try againBrowse the library
AI Blocks · All skills by job · Minds · Mini tools · How it works · From a source · Apps

AI Blocks › Test changes to your store

Know which store change to test first, ranked by profit

Give it your store numbers and what shoppers do on key pages. Get a profit baseline and a ranked list of tests.

Find the store change most worth testing is a free AI workflow for the job "Test changes to your store". It guides your AI through several skills in order, passing each step's output to the next.

Free · No account · Made by AI Blocks · Thinking: high

What it does

When a store has traffic but no clear next move, the test list fills up with opinions. Someone wants a new button colour, someone wants a banner. Tests are slow and cost sales while they run, so a wrong pick is expensive. Conversion rate alone also misleads, because cold traffic pulls it down and says nothing about profit. The first step corrects your dashboard numbers for tax, shipping and bots, then works out revenue and gross profit per visitor. That becomes the baseline every idea is sized against. Then it pauses and asks you to watch about 20 recordings each on the product page and the cart, save heatmap screenshots and note any survey answers. The second step turns that into a list of friction, weighted by money. The third splits repairs from tests, writes each test as a hypothesis, drops ideas with thin evidence and picks the one or…

You give it

You get

Use it when

Steps

  1. Store profit per visitor calculator: Paste your Shopify and analytics numbers. Get corrected revenue and gross profit per visitor, and a trust score.
  2. Heatmap and recording reader: Paste your heatmap and recording notes. Get the friction found, a test idea for each, and a friction score.
  3. Test idea ranker: Paste your research findings. Get each test written as a hypothesis and ranked by evidence and profit.

How to use it

  1. Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
  2. Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
  3. Give it a store report for a recent range, with sessions, orders, tax and shipping.
  4. When it pauses, watch about 20 recordings each on the product page and cart. Save heatmap screenshots and write down what you saw.
  5. Make the repairs list first. Run only the tests it names, one at a time.

More for Test changes to your store

Every test changes to your store skill