Eppo is the experimentation and feature management platform that makes advanced A/B testing accessible to everyone in your organization.
Pros
- Working on fun projects! We are building many 0->1 features so it's fun to innovate. - Company is growing so fast. - Design is equal partner with Product and Engineering. Designers drive projects strategically cause we don't have PMs yet. - Small company so people are friendly, collaborative. No politics. - Leadership is transparent. Roadmaps, strategies, OKR, board meeting learnings... are all shared with the entire company.Cons
- It can be hectic at times when we have customer requests coming in - Have to figure out direction can be difficult when projects are vague - Small amount of customers to research withAt Eppo, we are creating a next gen platform that fulfills the aspirations of experimentation tools teams, and brings those capabilities to companies of every stage and industry. Today, companies can't use any of the options on the market, and they can't run experiments until they devote multiple engineers and analysts to a function that is unrelated to their core product. We want to build a world where every team can have entrepreneurial, high experiment velocity culture. Eppo is an opportunity to change corporate culture everywhere. The mission of every business intelligence company is to bring the voice of users into decision making. As all data teams know well, nothing affects company decision making as much as introducing experimentation to product development.
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.
Our team has experience building experimentation practices at Airbnb and Webflow. We are backed by Amplify, the early team at Looker, and the CTOs of Optimizely and Webflow. Join us, and help unlock the creativity of a world of entrepreneur-employees.