Plan the sample size and run time of an A/B test
Prompt that calculates the visitors needed per variant and the run time in weeks before an A/B test, with the calculation, a guardrail and test rules. Paste it into an AI tool of your choice, which then plans the test.
- Topic
- Deciding & analysing
- Type
- Prompt
- Level
- Intermediate
- Time
- about 8 min
Results depend on the tool, the model and what you enter.
Result preview
Example: written by our editors, not real AI output.
Hypothesis: a shorter form increases the conversion rate. Today 3.0% · smallest worthwhile difference: +15% relative (to 3.45%) Calculation (95% confidence, 80% power, two-sided) n per variant = 7.84 × (0.0291 + 0.0333) / 0.0045² ≈ 24,200 1,000 visitors per day → 500 per variant → 49 days → 7 full weeks Guardrail: return rate must not rise Rules: no stopping before day 49, no changes during the test Note: at +25% relative, about 3 weeks are enough.
Fill in
What you type stays in this browser window. We store and send nothing.
- shorter sign-up form
- new button text on the product page
- different price display
- new newsletter subject line
- reviews higher up on the page
- 3% conversion rate
- 12% sign-up rate
- 25% open rate
- 40% click rate on the button
- 1.5% enquiries per visit
- 1,000 per day
- 300 per day
- 5,000 per day
- 20,000 per week
- 150 per day
Your prompt
You have edited the prompt. Changes in the fields above no longer overwrite it.
This is an instruction for an AI, not the result itself.
Where this prompt works
These AI tools are a good fit for this prompt:
How to use it
- Fill in the fields or tap a suggestion. Leave out names, addresses and other personal data.
- Copy the finished prompt into an AI tool of your choice.
- Double-check the calculation with a sample size calculator and write down hypothesis, run time and guardrail before the start.
Why does this work?
Fixing the run time in advance protects you from an early lucky result. The guardrail stops a gain in one place from hiding damage somewhere else.
Tips
- With little traffic only big changes are worth testing; small wording changes often take months to give a reliable result.