Airtable Team Workflow Expansion
Zoelle Egner, early Airtable employee, on customer success for product-led companies
This was the moment Airtable stopped behaving like a consumer app and started revealing itself as a workplace system that spreads team by team. Instead of one person bringing in friends the way Dropbox or Evernote did, Airtable usually entered through a concrete work problem, like a content calendar or ops tracker, then expanded as nearby teams copied the base, adapted it, and found their own workflows. That pattern naturally pulled the company toward B2B, customer success, and eventually enterprise sales.
-
Airtable had low barriers to entry but a high ceiling. A marketer could start with a simple launch tracker, then add views, automations, and shared workflows. That made it easy to land inside one team and then spread inside the same company as more people touched the process.
-
The internal spread mattered more than classic virality because the buyer was often not the first user. Airtable had to watch product signals, see which teams were active, then use customer success and training to turn scattered usage into a paid rollout and later an enterprise contract.
-
This is also why Airtable looked different from simpler PLG companies and from Retool. Airtable and Retool both moved from self serve entry toward enterprise motions, but Airtable spread through non technical teams solving messy workflow problems, while Retool spread through engineers building internal tools on top of production data.
Going forward, the winning pattern is clearer. Horizontal builder products that start with one useful team workflow and then expand across departments can grow into large enterprise accounts, but only if they add the layers that make that spread manageable, training, permissions, packaged solutions, and sales that formalize usage already happening inside the company.