The true cost of per-seat SaaS pricing (and how to model it)

Per-seat pricing sounds fair — pay for what you use. In practice it's a tax on the two things you most want to grow: your team and your tool adoption. This post walks through a concrete model for what a seat-priced tool actually costs over three years, and when a flat-priced alternative wins.

The three hidden multipliers

• Headcount coupling: your tooling bill compounds at the same rate as your hiring plan, with no relationship to the value each new seat extracts
• Adoption penalty: the more useful the tool becomes, the more seats you need — success is billed as an overage
• The SSO tax: security baselines like SAML are routinely gated behind enterprise tiers that double per-seat cost

A simple three-year model

Take a support desk at $49/agent/month with 8 agents today, growing 40% a year. Year one: $4,704. Year three: $9,220 — and cumulative spend near $21,000 for a tool whose marginal cost to the vendor rounds to zero. Against a flat self-hosted alternative at $99–$199/month all-in (including roughly $50/month of hosting), the crossover happens before the end of year one.

The counterargument is operational burden — someone has to run the self-hosted thing. That's real, and it's why managed hosting exists as a line item you can price explicitly instead of paying implicitly through seats. When the operations cost is a disclosed flat fee, the comparison finally becomes honest.

When per-seat is actually fine

Seat pricing is defensible when usage genuinely scales per person and the tool's cost structure follows — design tools rendering heavy files per user, for instance. It's indefensible for databases of shared records: tickets, analytics events, feature flags, dashboards. If the resource is shared, the pricing should be too.

That's the pricing rule every ResoluteX product follows: flat tiers by deployment size, never by seat, never by event. Costs should step, not slope.