Zapier Owning the Model Layer
Zapier: The $7B Netflix of Productivity
Owning the model would let Zapier move from passing data between apps to being the place where the workflow itself lives. Today, Zapier is strongest when it wires together long tail SaaS tools, but partners can still beat it on native UX because the real data and product context stay inside their own apps. If Zapier stores customer records in Tables and lets users act on them through Interfaces and workflows, it can remove some of that back and forth and make automation feel more like using one app than stitching together three.
-
The practical difference is simple. A classic Zap waits for an event in app A, pushes a generic payload through Zapier, then writes into app B. A model layer lets Zapier keep the record itself, apply logic to it, show it in its own UI, and trigger many actions from one shared data object instead of relying on two outside APIs every step of the way.
-
This is the same product convergence seen across no code. Retool added database and workflow layers around internal apps. Airtable added automations and interface tools around its database. The winner gets more than one feature, it gets the daily working surface where people view records, edit them, and run processes.
-
It also changes the power balance with partners. Interviews show SaaS apps tolerated Zapier for long tail connectivity, but preferred to build top integrations natively because Zapier creates extra setup friction and makes apps look interchangeable. If Zapier owns more of the data and workflow experience, it depends less on being just a marketplace of other apps' endpoints.
The path forward is a fuller stack where automation, data storage, and lightweight front ends sit in one product. That pushes Zapier closer to Airtable on the non technical side and toward Retool on app building, while preserving its core advantage, thousands of integrations. If that shift works, Zapier becomes harder to displace because users are no longer only connecting apps through it, they are running operating workflows inside it.