Zapier Commoditizing SaaS Integrations
Former Zapier partner on Zapier's commoditization of SaaS
The real issue was control. Zapier sat in the middle of the workflow, so it could see which triggers fired, which downstream apps got picked, and which patterns repeated across customers, while the SaaS partner still had to do the integration work and hand over part of the user relationship. That made the relationship feel less like a channel partnership and more like supplying inventory to a marketplace operator.
-
The integration was not just technical plumbing. Partners were pushed to build templates, surface Zapier widgets inside their own product, and pass marketplace review, which shows Zapier was shaping distribution and product merchandising, not simply offering an API connection.
-
The data asymmetry mattered because usage data tells a SaaS company which integrations are core enough to build natively. The interview says that information was not shared back, while broader Zapier analysis shows workflow data helped Zapier understand demand and expand its own native actions and recommendations.
-
This is exactly the gap newer embedded integration vendors were built to close. Companies like Prismatic, Tray.io, and Merge sell infrastructure that lets a SaaS product keep setup inside its own UI, own the customer data, and decide which integrations to promote instead of ceding that role to Zapier.
Going forward, more SaaS companies will treat integrations as a core product surface, not a side plugin. Zapier will remain valuable for long tail connectivity, but the most strategic integrations will increasingly be built in ways that preserve first party data, native onboarding, and control over which adjacent products get exposure.