Airtable's Enterprise Packaging Gap
Airtable: The $7.7B Roblox of the Enterprise
This reveals Airtable’s real enterprise challenge was not product quality, it was packaging. A builder sees a blank canvas that can replace messy spreadsheets, forms, trackers, and lightweight apps. An executive who does not build sees a tool that still needs someone inside the company to design the workflow. That is why Airtable spread bottom up through operators, then had to reframe itself around concrete use cases like marketing, content operations, and other packaged workflows with no-code benefits.
-
Airtable originally expanded inside companies through operators and translators, the people close enough to the work to build systems and explain the budget impact. Sales often came later to clear IT and procurement after usage was already widespread.
-
The non-builder gap is visible in practice. At one agency, less than 20% of staff used Airtable directly, while most people interacted through a software layer built on top. The underlying base mattered, but the visible value came from the finished workflow, not the builder experience itself.
-
This is also why Airtable converged toward interfaces, automations, and pre-built vertical apps. The enterprise buyer is easier to convince when the product looks like a marketing calendar, intake workflow, or ops system, instead of a general purpose database that could do anything.
The next step is deeper productization. Airtable is moving toward more pre-configured apps, stronger interfaces, and AI assisted app creation so the person buying the software can understand the outcome before anyone starts building. If that continues, Airtable can keep its flexible core while selling enterprises something that feels much closer to a finished application.