From Bases to Role Specific Apps
Airtable: The $7.7B Roblox of the Enterprise
The core move is turning Airtable from a place where a few builders manage a database into a place where everyone else can use finished apps built on that database. Salesforce did this by putting drag and drop app layers and reusable components on top of CRM records, so sales reps, managers, and service teams interacted with task specific screens instead of raw tables. Airtable needs the same separation between backend structure and everyday workflow surface.
-
Airtable’s original weakness in the enterprise was not data modeling, it was distribution to non builders. As bases get bigger, with more tables, fields, and automations, they become harder for newcomers to understand. That limits seat expansion because many employees only need a form, dashboard, or workflow screen, not the full base.
-
Salesforce solved a similar problem by making CRM data the system of record while letting admins assemble custom pages and apps from reusable components. That created a cleaner front door for employees who needed to update pipeline, review service cases, or approve work without understanding the underlying schema.
-
Airtable has since moved in this direction with Interface Designer, which creates custom interfaces on top of existing bases and can be shared with more targeted permissions. That makes the path more concrete, but the strategic prize is bigger, selling packaged workflows to teams like marketing or ops and then expanding across the company from that beachhead.
The next phase is a more productized Airtable where the database becomes infrastructure and the visible product is a set of role specific apps. If Airtable keeps improving interfaces, permissions, and vertical packaging, it can raise seats, ARPU, and retention the same way Salesforce turned a complex data system into a company wide operating layer.