PLG Virality Versus Enterprise Needs

Diving deeper into

David Peterson, early Airtable employee, on the future of product-led growth

Interview
the kind of bottoms-up, simple, viral product design that won them all of those initial users, that design is undermined by enterprise customer needs.
Analyzed 3 sources

This is the core trap in moving from self serve adoption to enterprise software, the features that help a big company buy and govern a product often make the product harder for the original champion to love and spread. In practice that means adding admin controls, permissions, documentation, onboarding, and services, which protects larger deals but slows the fast, intuitive sharing loop that powered early adoption for products like Slack, Dropbox, and Airtable.

  • The tension shows up at the product level. Airtable could land because one team could quickly build a workflow, but as bases got larger, schemas became harder to understand, performance degraded, and non builders struggled to interact without extra layers, permissions, and training.
  • The tension also shows up in go to market. Once many end users exist, sales no longer just pitches a buyer. It has to read usage signals, decide when an account is warm, then use success and services teams to turn scattered usage into an enterprise contract.
  • The next generation of PLG companies tries to solve this upfront. Peterson points to companies launching with SSO, admin features, SOC 2 readiness, and high touch onboarding from the start, so they do not have to bolt enterprise requirements onto a consumer shaped product later.

The winners from here are the companies that keep a low barrier to first value while packaging complexity behind clearer interfaces, onboarding, and enterprise infrastructure. That shifts PLG from pure virality to a hybrid model, where product opens the door and sales, success, and product design work together to widen it without breaking the original appeal.