Airtable must teach database thinking
David Peterson, early Airtable employee, on the future of product-led growth
Airtable’s real challenge is not teaching people a new feature, it is changing the default habit of using spreadsheets for jobs that are really small databases. Most knowledge workers already track projects, content calendars, leads, or intake forms in rows and columns. Airtable wins only when users realize they need linked records, filtered views, forms, and automations, not just another sheet, and that takes guided onboarding, training, and clear use case packaging.
-
Airtable first found traction where spreadsheet pain was obvious but buying a vertical tool was overkill, especially marketing, content operations, UX research, and cross functional ops. Those teams needed a flexible system of record that could change every week, which made database education easier when tied to a concrete workflow.
-
The main horizontal competitor was not another no-code product, it was Excel and Google Sheets. Dedicated tools like Asana or BambooHR were easier to understand because they came with a fixed mental model, while Airtable asked teams to design their own structure first, which raised the learning curve.
-
That education burden did not stop at signup. Larger deployments often needed customer success teams to design schemas, add permissions, document how a base worked, train champions, and prevent complexity from turning the base into something only one operator could safely touch.
Going forward, the winners in this category will make databases feel less like raw infrastructure and more like ready made software for a specific team. Airtable’s path is to keep the flexible database underneath, but present it as marketing, operations, or project workflows that ordinary users can adopt without ever needing to think about database design.