Hire an AI Shopify experiment readiness and results planner

Everything it can hand back

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

• A readiness call (repair first, research only, bold tests or regular tests) with the visitors and weeks needed
• Five bold tests in order, with the reason, main number and risk for each
• What your plan lets you test, which kind of tool fits, and what to ask about flicker and speed
• A one-change plan with fixed dates and what each result means
• A ship call with a trust score out of 100, the result as a range in money and a log entry

How it does the job well

• Work from the real catalogue, prices, stock and policies. Check variants and currencies.
• Judge changes by contribution margin, not revenue alone.
• Change one thing at a time on a live store and keep a way to roll back.
• Keep product claims consistent with supplier data and labels.

Mistakes it avoids

• Editing live products, prices or themes without approval or a backup.
• Ignoring shipping, returns and fees when judging profit.
• Copying competitor listings.

What a good result looks like

An example, not your task: You want to change a product page or checkout and need to know if the change really helps.

• STEP 1: READINESS. Your verdict, stage, smallest lift worth shipping, visitors and weeks needed, main number and guardrails, and a score out of 100.
• STEP 2: FIVE BOLD TESTS. Five big tests your traffic can prove, each with a reason, main number and risk, plus what not to test.
• STEP 3: SHOPIFY SETUP. What your plan lets you test, the route that fits, flicker and speed notes, and questions to ask any tool.
• STEP 4: ONE-CHANGE PLAN. The question, the one change, what stays fixed, a second check, the no-effect result and what each result means.
• STEP 5: VERDICT. A ship call, a trust score, split and length checks, the 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 and Demis Hassabis would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Check you can test. Decides whether to repair or test, places you by orders per month, sets the smallest lift worth shipping and works out the visitors and weeks needed.
• Pick the bold tests. Chooses five big changes your traffic can prove, puts them in order and names what not to test at your size.
• Fit it to your plan. Checks what your Shopify plan lets you test and which route fits, and lists the questions to ask any tool about flicker, speed and the stats engine.
• Plan the one change. Writes the question in plain terms, picks the one thing to change, fixes the rest and says what counts as no effect.
• Judge the result. Checks the split, the run length and what else changed, reads the lift as a range in money, and gives a ship, do not ship, re-test or inconclusive call.

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 run-one-store-test-and-know-whether-to-ship-the-change 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/run-one-store-test-and-know-whether-to-ship-the-change/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

• Orders per month, visits per month and conversion rate for the page
• The change you want to test and why you think it will help
• Your Shopify plan, and who will build the change
• Whether anything on the page is broken today
• The smallest gain that would pay for the work, and your gross profit per order (optional)
• Where your ads send traffic
• After the test, the numbers for each version and anything else that happened during it, such as a sale or an email send

Tools and access

• Any good chat AI: It does the sums and reads your numbers. Check the final sample size in a free sample size calculator.
• GA4: It gives sessions without most bot traffic, which Shopify's own sessions include.
• Any good chat AI: It picks and orders the tests from your numbers and findings.
• GA4: Sessions and landing page traffic without most bot traffic.
• Shopify: Its help pages show what your plan allows in checkout today. Check them before you buy anything.
• Any good chat AI: It sorts your ideas and turns vendor pages into the questions to ask.
• Any good chat AI: Listing factors and mapping results is text work any strong chat AI does well with this skill.
• A spreadsheet: Keeps the held-fixed list and the results side by side for each run.
• 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

• Shopify experiment readiness and results planner: Share store traffic, orders and Shopify plan details. Get test readiness, setup options, a one-change plan and later results review.
  • A readiness call (repair first, research only, bold tests or regular tests) with the visitors and weeks needed
  • Five bold tests in order, with the reason, main number and risk for each
  • What your plan lets you test, which kind of tool fits, and what to ask about flicker and speed
  • A one-change plan with fixed dates and what each result means
  • A ship call with a trust score out of 100, the result as a range in money and a log entry
• Store test readiness checker: Check if your store can run an A/B test. Give your orders, visits and the change. Get a verdict, weeks needed and a readiness score.
  • A verdict: repair first, research only, big swings, regular tests or full testing
  • Visitors and conversions needed per version, and the weeks needed at your traffic
  • The right main metric, with guardrails
  • A readiness score out of 100, now and after the fixes, with the sum shown
• Bold store experiment planner: Share store traffic, orders and page findings. Get ranked ideas for bigger tests, with metrics, risks and sample-size checks to complete.
  • Five bold tests in order, each with the reason, main metric, guardrails and risk
  • What not to test at your size
  • A month-by-month plan
  • A reminder to size each test before you run it
• Shopify test setup picker: Find out what you can A/B test on your Shopify plan, which testing route fits, and what to ask tools about flicker and stats. Get a setup score.
  • What is testable on your plan and what is not
  • A route for each idea: browser-based, or server-side and theme tests
  • Flicker, speed and stats engine notes, and a list of questions to ask every tool
  • A setup score out of 100, with the sum shown
• One-change experiment planner: Plan a one-change experiment. Tell it what you want to learn and get a test plan that changes one thing and says what each result means.
  • The question rewritten in plain terms, with each term defined
  • The one change to test and the list of things held fixed
  • A second check, the no-effect result and what each outcome means
• 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
• Demis Hassabis: Plan an AI research test using Demis Hassabis’s recorded approach. Choose the root problem, define a score and learn in a small test world.
  • Your problem worked on the way Demis Hassabis would: their questions, their method, their push-back
  • The answer or the work, in Demis Hassabis'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

• You want to change a product page or checkout and need to know if the change really helps.
• You have a test result and are not sure it can be trusted.
• You have low traffic and want to know what you can prove, and what to skip.

Limits to check before starting

• You have under about 30 orders a month: fix the page or talk to customers first, then use the Test idea ranker to pick what to change.
• You only want to know if your traffic can prove a test: use the A/B test traffic checker.
• You want to plan ad tests, not store page tests: use the Ad test brief writer.

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 pack. It holds HANDOFF.md and five skill files, in the order they run: Store test readiness checker, Big swing test picker, Shopify test setup picker, One-change experiment planner, then Store test verdict maker.
• Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
• Paste your orders, visits and the page you want to test. Say if anything on that page is broken today.
• Choose the one test to run first. Build it, then run it to the planned sample and dates. Do not stop early.
• Export the numbers for each version and bring them back, with a note of any sale or email send during the run.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/run-one-store-test-and-know-whether-to-ship-the-change 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.