Per-seat pricing creeping into a tool that promised it would not
A vendorâs pricing model isnât necessarily fixed forever at the terms you originally signed up under. Itâs worth understanding a specific pattern that happens periodically across software: a tool that starts on genuine usage-based pricing gradually introduces seat-based elements back in, through new tiers, specific feature add-ons, or enterprise agreements that donât follow the same structure as the core published pricing.
Why this drift happens
Vendors occasionally introduce seat-based elements back into an otherwise usage-based model as a way to capture more revenue from accounts that have grown significantly, particularly if usage-based pricing alone isnât scaling revenue as quickly as the vendor would like relative to a customerâs actual organizational size. This isnât necessarily a deceptive practice, pricing models evolve as businesses mature, but itâs a real pattern worth watching for if per-seat-free pricing was a specific reason you chose a particular vendor in the first place.
Where this drift tends to show up first
New premium features gated behind a per-seat add-on, even while the core product remains usage-based. A collaboration feature, an advanced analytics dashboard, or a specific integration might be introduced as a per-user charge layered on top of the existing usage-based core.
Enterprise agreements that donât follow the published pricing structure. A vendorâs self-serve, published pricing might remain genuinely usage-based, while custom enterprise agreements, negotiated separately, sometimes reintroduce seat-based components as part of a larger custom deal.
A pricing model change announced at a future renewal. This is the most direct form of drift, a vendor restructuring its entire pricing model, sometimes with existing customers grandfathered temporarily and sometimes not, depending on the specific terms of your agreement.
Why this matters specifically for organizations that chose a vendor for this reason
If avoiding per-seat pricing was a specific, deliberate reason you selected a particular vendor, perhaps because your usage pattern is genuinely uneven and per-seat pricing would cost considerably more, a drift back toward seat-based charges directly undermines the reasoning behind your original decision. This is worth tracking specifically, not just as a general pricing concern, but as a check on whether the vendor still fits the specific need that led you to choose them in the first place.
How to protect against this in your contract terms
Before signing a longer-term agreement, itâs worth asking directly what protections exist against a future pricing model change, whether your current terms are locked for a specific duration, and what happens if the vendorâs broader pricing structure changes during your contract term. Some vendors offer explicit grandfather clauses protecting existing customers from a pricing model change for a defined period. Others donât, which is worth knowing before youâre several years into a relationship and facing an unexpected restructure.
Why periodic monitoring is worth the modest effort
Even with reasonable contract protections in place, itâs worth periodically reviewing your vendorâs current published pricing page, not just at renewal time, to catch drift early rather than discovering it only once a new charge actually appears on an invoice. A quarterly or semi-annual check, a few minutes reviewing whatâs changed on the pricing page, catches this kind of drift while itâs still an early, general trend rather than something thatâs already affecting your specific account.
What to do if you notice this drift happening
If you notice new per-seat elements creeping into a previously usage-based tool you rely on, raise it directly and early with the vendor, referencing the specific terms you originally signed up under. Vendors are often more willing to honor original terms, or offer a reasonable transition path, for existing customers who raise the issue proactively and specifically, compared to customers who only notice and react after a change has already taken full effect on their account.
Why this is worth flagging to whoever owns procurement, not just the requesting team
If your organization has a formal procurement or vendor management function, itâs worth flagging this kind of pricing drift to them specifically, since they may have visibility into contract terms, or negotiating leverage as a larger account, that the original requesting team doesnât have on its own. This is exactly the kind of issue that benefits from centralized vendor management attention rather than being handled ad hoc by whichever team happens to notice the change first.
What a durable, drift-resistant commitment looks like
The strongest protection against this kind of drift is a specific, written commitment in your contract terms, locked pricing structure for a defined period, an explicit grandfather clause, or a clearly defined process for any future pricing model change. A vendor confident in the durability of its own usage-based model will typically be willing to commit to something like this in writing, rather than leaving it as an informal, unwritten expectation that offers no actual protection if the pricing structure does eventually change.
A realistic example of how this plays out over a few years
Consider a team that adopts a video platform specifically for its usage-based pricing, avoiding what would have been a considerably higher per-seat cost given their broad, uneven usage pattern. Two years later, the vendor introduces a new âteam collaborationâ tier that reintroduces a per-user charge for a feature the team now depends on daily. Individually, this might seem like a reasonable new feature with its own reasonable price, but cumulatively, over several similar additions, the teamâs effective cost structure can drift back toward something resembling per-seat pricing, just spread across several smaller add-ons rather than one obvious line item, which makes the overall drift easy to miss without deliberately tracking it.
Why this is worth discussing as part of any renewal conversation
At each renewal, itâs worth explicitly asking whether any part of your current cost has shifted toward seat-based elements since your last review, rather than assuming the pricing structure has stayed exactly as originally understood. A renewal conversation is a natural, low-friction moment to raise this question directly, and vendors generally expect and welcome a substantive conversation about pricing at that point rather than treating it as an unusual or confrontational ask.
Veloâs approach
Velo currently prices per account using a credit-based system, Free at 1,500 credits per month, Pro at $49 per month with 3,000 credits, Ultra at $200 per month with 30,000 credits, and custom Enterprise pricing, without per-seat charges across its published tiers. Confirm current terms directly with the team for any specific contract protections relevant to a longer-term commitment.
Watch for drift, and protect against it in writing
A usage-based pricing model isnât automatically permanent, and itâs worth watching for drift back toward seat-based charges, particularly if avoiding that structure was part of your original decision. Ask for specific written protections before a longer-term commitment, monitor periodically rather than only at renewal, and raise any concerns directly and early if you do notice a change, rather than waiting until itâs already fully reflected in your invoice.
Try Velo for free · See how it works
Related reading
- Video platforms that skip per-seat pricing entirely
- Per-account vs. per-seat: what each model actually costs at scale
- âNo contractâ claims worth double-checking before you sign
- The real trade-off behind annual billing discounts
About the author
Ritu Parakh is Growth Lead at Velo, the AI video messaging platform that turns a screen recording, a deck, or a URL into a polished, narrated video - and an editable written doc. She writes about video for demos, onboarding, training, and enablement. Connect on LinkedIn