Honest test queue planner
A backlog of test ideas is not a plan. Capacity is set by the volume you actually send
through one arm: below the floor, a read-out is a progress report. This page turns volume into a queue —
the floor per arm, the days each test needs, how many tests fit before your date, and the day each verdict lands.
The same arithmetic runs in the published CLI
(npx marketing-mindset sample). Everything is computed in your browser; nothing is sent anywhere.
1. What you have
2. The queue
3. How to use the queue without lying to yourself
One test at a time, or two tests with two audiences
Two live tests in the same arm split the volume and neither reaches its floor. If two must run, give them disjoint audiences and halve the contacts a day in this form.
Peeking is not reading
Checking a test daily and stopping when it looks good inflates the error rate far above alpha. The queue assumes the test reads at its floor — which is the only look that was priced in.
The clock is a deliverable
A retainer that reports weekly movement on a test that reads in eight weeks is reporting the queue, not the result. Write the read-out date into the plan and the monthly report becomes a status against a known date.
4. Related
How many sends an email test needs · The stop rule written before the first send · Read a finished test honestly · What a monthly retainer has to buy.
Written by Axel Freeman — marketing engineer. Telegram · llms.txt