Notion, Airtable, and the Per Seat Creep

What causes per seat creep in Notion and Airtable?

Per seat creep in Notion and Airtable is caused by easy self serve adoption that adds paid seats faster than any process reviews them. Both tools are deliberately simple to spread: a team starts on a small plan, invites collaborators, and the seat count grows organically as the tool proves useful. That same ease is the problem at scale, because nobody owns the total. Seats accumulate for people who needed access for one project, for occasional viewers who could sit on a cheaper tier, and for employees who left without being deprovisioned. The per seat model turns every one of those into a recurring charge, and because each individual seat is inexpensive, the growth rarely triggers a review until the aggregate bill becomes visible at renewal. By then the tool is embedded across many teams and the count looks like a fact rather than a choice.

This is the collaboration tool version of a pattern that recurs across the portfolio, where small per seat tools quietly become major line items. The broader discipline for catching it lives in the SaaS Negotiation Guide.

Where does the wasted spend actually sit?

The wasted spend sits in idle seats, orphaned seats, and over provisioned tiers, and most organisations carry all three at once. Idle seats are paid licenses assigned to people who rarely or never use the tool, which a simple activity report exposes immediately. Orphaned seats belong to former employees or finished contractors who were never removed, and they are pure waste that also carries a security cost. Over provisioned tiers are users sitting on an expensive plan for features only a few of them use, where a viewer or a lighter tier would serve them at lower cost. None of this requires a hard negotiation to fix, because it is your own house to put in order, but it does require the activity data, and it is the foundation for every harder conversation with the vendor. You cannot credibly negotiate a seat count you have not audited.

How do you reclaim seats before renewal?

You reclaim seats by auditing usage, removing the dead weight, and right sizing every remaining user to the lowest tier that meets their need. The table below frames the three moves and the saving each unlocks.

For the structural problem behind this, read the app per employee problem, and for the same pattern in project tools, see negotiating Monday and Asana deals.

Why does the tier matter as much as the seat count?

The tier matters as much as the seat count because both Notion and Airtable sell their margin in the higher plans, where advanced features, automation limits, and administrative controls drive a meaningful step up in per seat price. The upgrade pressure is real: a single requirement, such as an advanced permission or a higher automation allowance, can push an entire workspace onto a more expensive plan even though only a handful of users need the feature. The buyer move is to separate the population that genuinely needs the top tier from the majority that does not, and to question whether the whole organisation must move up because of a minority requirement. Where a tier jump is driven by one team's need, the better answer is often a smaller paid group on the higher plan rather than an all seat upgrade, so the tier decision deserves the same scrutiny as the seat count.

How do you negotiate the renewal once you have the data?

You negotiate the renewal by bringing the usage evidence, committing only to the seats and tier you will genuinely use, and securing terms that stop the creep from returning. Lead with the audited active count rather than the inflated assigned count, because the vendor will anchor on the higher number if you let it. Commit to a realistic seat band, negotiate a capped annual uplift indexed to inflation so the rate cannot drift up, and secure seat reduction rights so you can shed licenses at each renewal rather than carry them. Where you run several overlapping collaboration tools, use a credible consolidation onto one as leverage, since the willingness to retire a competing tool is genuine negotiating power. Time the conversation ahead of the renewal date, not after the auto renewal has rolled, and disarm any automatic renewal so the count cannot lock in before you have reviewed it.

A worked example of reversing the creep

Consider an indicative example. A media company finds its combined Notion and Airtable spend has roughly doubled over two years without a deliberate decision. It runs activity reports and discovers a large share of paid seats are idle, a block belongs to people who have left, and most users sit on a premium tier for features only one department uses. It reclaims the idle and orphaned seats, moves occasional users to lighter tiers, keeps the premium plan for the single team that needs it, and consolidates a third overlapping tool into the two it keeps. It then renews on the audited count with a capped uplift and reduction rights. The bill falls substantially, mostly from its own cleanup before any vendor discount. These figures are indicative, but the pattern is common, and reversing the creep lands the buyer inside the 10 to 30 percent savings disciplined negotiation typically produces, by published market estimates.

What to do next

Before your next Notion or Airtable renewal, audit real usage, reclaim idle and orphaned seats, right size the tier, and renew on the count you can defend. The renewal mechanics are covered on the SaaS renewal negotiation service, and the full buyer method runs through the SaaS Negotiation Guide.

Last reviewed January 2026