TL;DR: An A/B rollout is not an A/B test. It's the practice of exposing a new feature to a controlled percentage of users to ship safely, not to optimize a conversion rate. Most early-stage founders conflate A/B tests, feature flags, and canary rollouts. At sub-100 user volumes, traditional split testing math doesn't work. Use sequential rollouts, single-variable testing, and diagnose before you test.