"It’s powerful to think about all features launched before Split and how many of those must have cost us money that we don’t know about."

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

“If we build it we have to test it to make sure it’s doing the right thing. When we conduct backend experiments, we have to know the system will remain reliable. We have to make sure the backend behaves in a way that doesn’t impact the user experience.”

"Without Split it was hard to time the release of our web app, API, and mobile app – given app store approvals. Now we can group a change behind a feature flag, do a production dry run, and toggle it on for users."

"Split gives us an easy and fast way to pull the plug if something goes wrong without a heavy involvement from engineers."

"At the point engineers make deployments live, they want to understand how the features are performing, from a customer experience, user value, and system standpoint. We know that one of the big challenges developers face in understanding impact is how to get all of the data in the first place. …

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

“We have in total about 14 teams working on our digital asset management platform. All of the teams are using Split."

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

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

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

"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 gives me a lot of confidence in our releases as we are able to customize our rollouts, and even roll back quickly if needed. It also allows us to target certain segments that we’d like to release to prior to others.”

“By decoupling experimentation decision-making from engineering Resources [with Dynamic Configuration], product teams become empowered to make fast and flexible changes to the product with little to no technical knowledge.”