Airtable Needs Publishable Apps
Airtable: The $7.7B Roblox of the Enterprise
The missing piece was distribution, not creation. Airtable already let small groups build custom workflows on top of shared data, but most coworkers still had to enter the base itself or rely on a separate layer built around it. That kept Airtable strong as a builder tool and weak as a software publishing platform, where teams could package one workflow into a cleaner app, hand it to hundreds of users, and let others extend it with automations and integrations.
-
In practice, many Airtable deployments solved this by putting another product in front. One marketing agency used Airtable as the system of record, but said 20% or less of employees touched Airtable directly, while most used a software layer built on top of it. That is the exact gap between workflow builder and shareable application platform.
-
The closest comparables were converging on the same stack from other angles. Retool started with the interface layer, helping teams build admin panels and CRUD apps on top of live databases. Zapier started with the logic layer, then moved toward tables, interfaces, and an automation marketplace. Airtable had the data layer first, but needed a better way to expose and distribute what users built on top of it.
-
This mattered economically because per seat pricing limits spread when every viewer has to look like a full user. Broader interfaces and packaged apps make it easier to separate builders from consumers, which expands seat count, raises retention, and turns one ops team build into something multiple departments can actually use.
The path from no-code tool to enterprise software platform runs through publishable apps, reusable components, and simpler interfaces for non-builders. Airtable has since moved in that direction with Interfaces, Apps by Airtable, and AI generated app building, which pushes it closer to becoming a place where companies do not just model workflows, but ship and operate internal software on top of them.