“Without Split, rollbacks could take a couple hours to a day. And after that, there might still be a lot of code cleanup. Split helped us increase our engineering velocity and code stability.”

"90% of our changes are behind a split (feature flag)."

"Leveraging Split with our existing tool stack, we’ve been able to consolidate our agile deployment strategies to deliver every three weeks from an original 1.5 months."

"One of our first experiments was a great learning experience. It prevented us from introducing something that we thought was good, but actually would have likely given us a negative impact. We’re now doing another iteration to get it right."

"We use feature flags and run experiments a lot more because it’s easier now with Split. We can target a random sample size. We can increment the size of that sample really easily, and we can toggle it off immediately if there’s an issue."

“The thing that’s great about Split is that you can change the behavior of the product outside of a code deployment.”

"Split allows us to safely merge code with confidence."

"Split plays a key role in Invoice2go's feature rollout process. By using their product for targeted rollouts, we have full control over any release and an increased confidence in our ability to easily scale over time. In addition, Split's collaborative nature and their focus on their customer's success have made …

"Using Split with FullStory allowed us to humanize our experiments and empathize with our customers by validating the quantitative results with real user sessions that revealed how customers felt when interacting with our features."

"As we improved our checkout process relying on Split to measure the impact of our changes, we saw an overall increase in conversion year over year, and that’s made a huge difference on our bottom line."

"Split has made us more confident in our release process and also more confident in our data decisions."

"With Feature Monitoring, our engineering team can deploy rapidly while ensuring that new functionality won’t negatively impact our core KPIs such as page load time and errors per user."

"The kill button is super easy. Now I just, ‘whoop’, kill it. If we are seeing something wonky, it makes it so easy to turn off. When we’ve triaged the feature we can go back and re-enable it."

"Thanks to Split, we were able to learn that the risky version actually had the highest adoption by our customers while keeping overall signup conversion steady."

“If we built this in-house, most engineers would look at this and say ‘feature rollout, it’s not that hard’. But when you think about having multiple environments, having a UI, conditional filters, an impression data pipeline, all that—it’s a whole team working for a very long time to be able …