“In the past, it would take a full engineering squad of four to six developers plus a product manager one quarter to build and launch a single integration. Our customers took notice.”Įventbrite was also evaluating the impact of building customer integrations on its engineering resources.

And without the visibility to diagnose and solve problems, any progress was slow. Whenever we had issues with the integration, we had to go through the third party to get them resolved. While the integration they built worked well at first, it quickly became challenging to maintain. “We solicited a third-party vendor to build an integration between Eventbrite and a popular email marketing tool. In particular, while the team frequently solicited app feedback from customers, getting fixes or updates implemented required contacting third parties that didn’t always respond promptly and/or didn’t have the tools or resources to quickly diagnose the issues and make changes.Īfter a particularly challenging experience maintaining a third-party integration, Peterson and his team realized that Eventbrite needed to find a way to ensure that integrations on the marketplace met their high standard of quality without requiring considerable resource investment from the team. However, over time, the company’s third-party-driven approach made it challenging to maintain consistently high quality integrations. “These integrations help our users get the most out of Eventbrite by streamlining event-related processes and logistics.”

“Eventbrite’s App Marketplace is a place where creators can search for and set up integrations between Eventbrite and their favorite tools,” explains Peterson. Challenge Maintaining high-quality customer integrations at scaleĮventbrite’s customers need many integrations, so the company’s original approach was to have third-party builds via self-serve integrations in a public marketplace.

Eventbrite apps