Eppo

There is a common set of experiment functionality that suits the vast majority of businesses. This is especially true given secular trends of businesses towards cloud infrastructure, widespread adoption of product led growth strategies, and data teams using a homogenous data stack of SaaS products. The difference between each company's experimentation tooling is not a difference in requirements, but of their level of investment in internal tooling. We have experience building experimentation practices from scratch, multiple times. After contributing to the experimentation system at Airbnb, the CEO built the same tool at Webflow. Despite Webflow being a subscription SaaS business and Airbnb being a marketplace, the same Airbnb experiment architecture worked in both environments. But in both instances, much more engineering investment was needed to fully automate the operations work that analysts were doing. Since then, we have spoken with dozens of growth experimentation teams. Companies like Lyft and Facebook had tooling with over a decade of investment, others from earlier companies were trying to manage off of Google Docs. The common thread was a.) the market not having an adequate experimentation offering and b.) internal tools teams not having resources to build the features they know would be valuable. We came away from this experience believing that the ecosystem needs a team that is singly focused on building best in class experimentation tooling.