Seat-based pricing penalizes collaboration

Diving deeper into

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

Interview
seat based pricing has this perverse effect of penalizing people for inviting their teammates
Analyzed 4 sources

Seat based pricing puts a tax on the exact behavior that makes product led software spread. In Airtable, expansion depended on a marketer, ops lead, or product manager pulling coworkers into a shared base, but every added editor also increased the bill. That made the company rely on two harder levers instead, raising price per seat and using customer success to turn a small team foothold into a wider deployment.

  • Airtable’s product gave it very few natural usage meters to bill on. The core unit was an editor working in a base, so monetization centered on $10 to $20 per seat, then enterprise upsells. Internally, Airtable tracked rows, app and integration usage, and cross team sharing as signals of value, but those were sales cues more than billing units.
  • This is why seat pricing fits tools like Superhuman better than builder platforms like Airtable. Superhuman sells a personal productivity gain to each inbox user, so charging per user matches value creation. Airtable creates more value when one builder invites many collaborators into the same workflow, which makes each extra seat feel more like a collaboration toll.
  • Usage based pricing became attractive to later product led companies because it can subsidize collaboration. In product led messaging tools like Customer.io, pricing can rise with contacts, messages, or event volume while many teammates use the product. That lets companies widen adoption inside an account without charging every new person who logs in.

The market is moving toward hybrids where viewer seats are cheap or free, while charges attach to the scarce resource, data volume, automation runs, messages, or premium builder roles. For collaborative software, the winners will be the ones that let usage spread first and monetize the deeper workflow once it becomes business critical.