A/B testing
A/B testing is a method where two versions (A and B) of a webpage or app are compared to see which performs better in achieving a specific goal, helping you make data-driven decisions.
What is A/B testing?
A/B testing works by splitting your audience at random: half of your visitors see version A (the control), the other half see version B (the variant with one change). You pick a single success metric in advance, such as trial signups or clicks, let the test run until you have enough data, then keep whichever version performed better. The randomness is the whole point. Because both groups are statistically similar, any difference in results can be attributed to the change you made rather than to luck, seasonality, or a traffic spike from one channel.
The technique comes from direct-response marketing and controlled experiments in research, where split tests have been standard for decades. Software made it cheap: instead of printing two versions of a mail campaign, you flip a flag in a testing tool and the software handles the split, the tracking, and the math.
Day to day, an A/B test looks unglamorous. You write a hypothesis ("a shorter signup form will increase completions"), build the variant, define the metric, and wait. The discipline is in changing one meaningful thing at a time and resisting the urge to call a winner after a day of promising numbers.
Why A/B testing matters for startups
For a small team, the biggest value is not squeezing out tiny gains, it is settling arguments. When two founders disagree about a headline, a pricing layout, or an onboarding step, a test replaces opinion with evidence and lets you move on. It also protects you from confidently shipping changes that quietly hurt conversion.
A/B testing has a real cost at startup scale, though: you need traffic. With a few hundred visitors a week, most tests will never reach a trustworthy conclusion. Early on, big qualitative bets (talking to users, fixing an obviously broken flow) usually beat micro-experiments. Testing becomes powerful once you have steady traffic to a page that matters.
A/B testing in practice
Say you run a bootstrapped note-taking app with about 6,000 weekly visitors to the homepage and a 3 percent trial signup rate. You suspect the headline is too clever, so you test it against a plainer benefit statement. After three weeks, version A converted 178 of 6,100 visitors while version B converted 244 of 6,050. The lift clears your significance threshold, so you ship version B. At that traffic level, this single test is worth dozens of extra trials every week, more impact than a month of small tweaks shipped on instinct.
Benchmarks and rules of thumb
- Most teams require roughly 95 percent statistical significance before declaring a winner; some accept 90 percent for low-risk cosmetic changes.
- Run tests for at least one full business cycle, typically one to two weeks, even when results look decisive early. Weekday and weekend visitors often behave differently.
- Detecting small lifts usually takes thousands of visitors per variant. If a page gets a few hundred visits a month, test only bold changes: the offer, the headline, the page structure.
Common mistakes
- Stopping the test as soon as it looks good. Early leads flip constantly. Decide duration and sample size up front and stick to them.
- Testing trivial changes on tiny traffic. A button color test on 500 monthly visitors will never conclude. Save testing for pages and changes with real stakes.
- Changing several things at once. If the variant has a new headline, image, and form, you will not know what caused the difference. One hypothesis per test.
- Optimizing the wrong metric. More clicks mean nothing if activation and revenue fall. Tie tests to a metric that connects to money.
- Discarding losing tests. A variant that loses teaches you what your users reject. Log every result so you stop retesting old ideas.
Related concepts
A/B testing is the core tool of conversion optimization and pairs naturally with landing page optimization, since landing pages concentrate enough traffic to test quickly. Shallow metrics like click-through rate make convenient test metrics, but deeper measures such as retention rate tell you whether a winning variant produced better users, not just more of them. If you are unsure what to test first, mapping your customer acquisition funnel will show you where the biggest leaks are.
See A/B testing in practice
Hundreds of startups launch on LaunchIt and put concepts like this to work. Browse them, or launch your own.