“We had the intention to change the password field, but we didn’t have a way to know how good it was effectively, and to be able to control it in-house, within our product team. Split allowed us to do all of that and more.”

"Split has been instrumental in our push to true agile processes. The ability to divorce deployment from release via feature flags has had an outsized impact in our ability to deliver new products to market faster than our competitors. With the addition of configurations we can externalize values and settings …

“Split provided the platform and integrations we needed to run full stack experiments for key technical and customer experience questions.”

"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."

"A/B testing is a side effect of controlled release. That’s what I love most about Split."

"It’s inherently collaborative and transparent, a rigorous and sound process based on the hard data we know about."

"Split is incredibly empowering for product managers. The web console consolidates and provides transparency into every release, while also enabling teams to make changes dynamically without relying on engineering. With Split, engineering and product teams can collaborate to more efficiently to create, manage, and complete rollouts that much faster.”

“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.”

"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 …

"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."

"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."

"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."

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