Enterprise Features Undermine Product-led Simplicity
David Peterson, early Airtable employee, on the future of product-led growth
The hard part of moving upmarket is that enterprise revenue usually comes from making a tool safer, more governed, and more legible to non builders, but each of those layers adds friction. In Airtable, that meant permissions, embedded documentation, admin controls, trainings, and services, all of which help large accounts stick, but also make the product feel less like a simple blank canvas that spreads on its own.
-
Airtable did not grow like a pure consumer viral product. It saw viral spread inside businesses, then had to add customer success before sales, with trainings, documentation, and champion building to turn usage into enterprise contracts. That is a very different machine from early Dropbox style self serve growth.
-
The product tradeoff is concrete. A mature base gets harder for a new employee to understand, easier to break, and more dependent on guardrails. Airtable responded with annotations, permissions, and services, because without that support, complexity can turn into stale data and then abandonment.
-
The newer winners in PLG try to solve this earlier. Peterson points to companies like Retool, Figma, and Webflow as products with a low barrier to entry but a high ceiling, and notes that newer SaaS products increasingly launch with SSO and admin features from day one.
This points toward a hybrid model where the product still lands bottom up, but growth increasingly depends on packaging complexity instead of hiding it. The next leg is more opinionated products, clearer interfaces for non builders, and enterprise readiness much earlier, so companies can keep self serve momentum without breaking the simplicity that got them in the door.