The SaaS Trap: How Per-Seat Pricing Pushes You Toward Self-Hosting

There is a particular moment, familiar to anyone who has run a small team, where you log into a tool you’ve happily paid for for years, go to add a new colleague, and watch the price quietly leap by another tenner a month. Do it five times and the friendly little subscription has become a line on the budget that someone, eventually, is going to question. That moment is when otherwise sensible people start googling “self-hosted alternative to” — and per-seat pricing is the reason.

I want to be fair to SaaS here, because I’m not an evangelist who thinks everything must run on a Raspberry Pi in a cupboard. Hosted software is often the right call. But per-seat pricing has a specific, structural flaw that turns a good deal into a bad one as you grow, and it’s worth understanding why before you reach for the self-hosting hammer.

1 Why per-seat pricing feels like a trap

Per-seat pricing is beloved by vendors because it ties their revenue to your success. As your team grows, so does your bill — automatically, with no renegotiation. That’s brilliant for them and tolerable for you, right up until the value stops scaling with the seat count.

The trap is that the marginal user costs the vendor almost nothing, but costs you full price. Adding the fortieth user to a chat tool consumes a rounding error of server resources, yet you pay the same per-seat rate as the first. You aren’t paying for compute; you’re paying for growth itself. And the more occasional, read-only, or peripheral users you have — the contractor who logs in twice a month, the stakeholder who just wants to see a dashboard — the worse the deal gets, because each pays a full active-user price for a fraction of the value.

2 The maths that tips the decision

Let’s make it concrete. Say a hosted tool charges £8 per user per month. Here’s how that scales against a self-hosted equivalent running on a modest £20/month VPS plus, generously, a few hours of your time:

At five users, SaaS wins comfortably — the convenience is basically free. Somewhere around fifteen to twenty users the lines cross, and beyond that the gap becomes absurd. The self-hosted cost barely moves because the bottleneck is rarely the server; it’s your attention, which is roughly fixed whether you have twenty users or two hundred.

3 What you’re really paying for at the crossover

When people justify SaaS at scale, they cite reliability, support, and “not being the on-call person at 2am.” Those are genuine and you should weight them honestly. But notice that none of them scale with seats either. The vendor’s uptime is the same whether you’re on five seats or five hundred. So if you’re being charged ten times more for the same reliability, you are, very specifically, paying a tax on the size of your team and getting nothing extra for it.

That’s the insight that makes self-hosting compelling at scale: the costs that genuinely justify a subscription are mostly fixed, while the price you’re charged is linear. The vendor has quietly decoupled what you pay from what it costs them to serve you.

4 When the trap isn’t actually a trap

Now the counterweight, because self-hosting to dodge per-seat fees can absolutely backfire:

• If the tool is mission-critical and downtime costs real money, paying the per-seat premium for someone else’s on-call rota is rational. Your time isn’t free either.
• If you have no one who wants to be the admin, the “saving” is illusory — you’ve just moved the cost from a budget line to a person who’ll burn out.
• If the seat count is small and stable, the crossover never arrives. Don’t self-host fifteen pounds a month of convenience.
• If compliance or data residency is handled for you, that’s a service with real value, not just a markup.

The honest framing is that per-seat pricing isn’t evil — it’s just misaligned past a certain size. Self-hosting realigns the cost with reality, but it hands you the bill in time and responsibility instead of money.

5 The honest verdict

Per-seat pricing is a fair deal for a small team and a worsening one for a growing one, because it charges you linearly for a service that mostly costs the vendor a fixed amount. The trap is real, but the escape isn’t free.

My rule of thumb: under ten seats, pay the SaaS and get on with your life. Between ten and thirty, run the numbers above with your actual rates and your actual appetite for admin. Above thirty, if there’s a mature self-hosted alternative and anyone on the team genuinely wants to own it, the savings are usually large enough to take seriously. Just go in knowing you’re trading a predictable invoice for an unpredictable evening — and make sure someone has actually signed up to be the person who fixes it.