Skip to content

Blog

Per-seat pricing: how SSO upgrades multiply your bill

Per-seat pricing turns an SSO upgrade into a surcharge on every hire. How it compounds over three years, what idle seats cost, and what to negotiate.

· 9 min read

Per-seat pricing means you pay a fixed amount for each person who has an account, every month. When a tool puts single sign-on on a higher plan, per-seat pricing turns that one feature into a surcharge on every seat, so the cost of SSO grows with every hire: in our example below, from about $3,900 a year at 10 people to about $12,700 at 35.

That is the whole problem in one sentence. The rest of this post shows how it works, how fast it compounds across a few ordinary tools, and what you can do about it. Prices are from each vendor's pricing page as we read it on 27 October 2026.

How per-seat pricing works

A seat is a paid account for one person. The bill is the price per seat times the number of seats, usually per month, often billed a year in advance.

Most SaaS (software you rent online) is priced this way: Slack, Notion, GitHub, Figma, Zoom, HubSpot. Vendors like it for obvious reasons. Revenue grows as their customers grow, without anyone having to sell anything new. And it feels fair: a 5-person team pays less than a 500-person team.

For buyers, per-seat pricing is fine as long as the price per seat is fine. It goes wrong in two places.

The first is seats nobody uses. Leavers whose accounts were never removed keep costing money, month after month, and nobody notices because the invoice was already big. That is a license management problem.

The second is features locked to a higher plan. If one feature you need is only on the next plan up, you do not pay for the feature. You pay the difference on every seat.

SSO is the classic case of the second, and it makes the first one worse.

The upgrade multiplier

Single sign-on (SSO) lets your people log in to every tool through one account, such as Google Workspace or Okta. Most tools only switch on SAML, the standard behind it, on a Business or Enterprise plan. And on most tools the plan belongs to the whole workspace or organization: you cannot buy the SSO plan for the three people who need it and leave everyone else where they were.

So the real price of SSO in a per-seat tool is a multiplier on your whole bill for that tool. Using annual-billing prices:

ToolPlan without SAMLCheapest plan with SAMLMultiplierExtra per seat a month
SlackPro, $7.25Business+, $152.1×$7.75
NotionPlus, $10Business, $202×$10
GitHubTeam, $4Enterprise, $215.3×$17
FigmaProfessional, $16Organization, $553.4×$39

Sources: Slack, Notion, GitHub (shown "for the first 12 months"), Figma (full seats; Organization is billed annually).

A 2× multiplier on Slack means that, from the day you upgrade, every new hire costs you twice what they did in Slack. The feature you wanted, a login button, did not get bigger. The bill did.

Example over three years of hiring

Take a company that grows from 10 to 20 to 35 people over three years. Everyone uses Slack and Notion. Engineers use GitHub; designers use Figma. It upgrades all four tools to their SSO plans in year one.

YearPeopleGitHub seatsFigma seatsBill without SSOBill with SSOSSO tax that year
11042$2,646$6,528$3,882
22083$5,100$12,396$7,296
335145$8,877$21,528$12,651

Over three years, the SSO tax on these four tools comes to $23,829.

How the year-three line works, so you can redo it for your own tools: Slack ($15 − $7.25) × 35 × 12 = $3,255. Notion ($20 − $10) × 35 × 12 = $4,200. GitHub ($21 − $4) × 14 × 12 = $2,856. Figma ($55 − $16) × 5 × 12 = $2,340. Total, $12,651.

Three things to notice.

The tax more than triples while headcount grows 3.5×. Per-seat pricing passes your growth straight through. Nothing about SSO changed between year one and year three.

The ratio stays put. The bill with SSO is roughly two and a half times the bill without it, every year. That is the multiplier, applied to a growing base.

Four tools is a small stack. A real 35-person company runs many more, and several of them will have the same structure. How to calculate your SSO tax shows how to add up your own, and the SSO tax calculator does it with each vendor's prices.

The figures assume list prices stay the same for three years. They rarely go down.

Unused seats cost more on the SSO plan

The upgrade multiplier does not only apply to the people who work for you. It applies to every account you are billed for, including the ones held by people who left.

On the plans without SAML, a leaver who keeps a seat in all four tools costs $7.25 in Slack, $10 in Notion, $4 in GitHub and $16 in Figma: $37.25 a month, or $447 a year. On the SSO plans, the same forgotten accounts cost $15, $20, $21 and $55: $111 a month, or $1,332 a year. Upgrading for SSO tripled the price of every seat you forgot to remove.

That is the irony for small companies. Many upgrade for SSO because offboarding is messy, then pay the higher price on exactly the seats that messy offboarding leaves behind. Orphaned accounts explains where those seats hide, and SSO does not remove them, because SAML only controls login.

Per seat, per active user, or flat

Not every per-seat price counts seats the same way, and the difference is worth knowing before you compare.

Plain per seat bills every account that exists, used or not, until someone removes it. Most tools in this post work this way.

Per active user bills only the people who used the tool in a period. Slack's fair billing policy, as we read it on 27 October 2026, stops billing a member who has not used Slack in over 28 days and credits the unused time to your account; the credits can go toward future charges but have no cash value. It applies to plans bought on Slack's website. That softens the cost of a forgotten leaver in Slack, but only after the 28 days, and only as credit.

Flat pricing ignores seats entirely, which the next section covers.

When you read a pricing page, look for which of the three you are buying. Two tools with the same list price per seat can cost very different amounts if one bills idle accounts and the other does not.

Flat-fee alternatives

Some vendors price SSO per account instead of per seat. Vercel lists SAML SSO on its Pro plan at $300 a month (Vercel pricing). PlanetScale sells an SSO add-on for $199 a month per organization (PlanetScale docs). Sentry and Mailgun put SAML on a higher flat-priced plan.

A flat fee can be expensive at 5 people and cheap at 50. What makes it different is that it does not move when you hire. Vercel's add-on is $3,600 a year in year one and $3,600 in year three. You can budget it once.

Plenty of tools you already use work the same way for everything, not just SSO: a flat platform fee, sometimes with usage on top. When you compare a per-seat tool with a flat one, compare them at the headcount you expect in two years, not the one you have today.

What to negotiate

Per-seat contracts have more give in them than their pricing pages suggest. These are worth asking for, especially on an annual renewal.

SSO on your current plan. The most direct request. Some vendors agree for annual contracts. If you do not ask, the answer is always no.

A lower price per seat on the SSO plan. If they will not move SSO down, ask them to move the price down. The multiplier is the thing to attack.

Cheaper seat types. Figma, for example, sells Dev and Collab seats for much less than a full seat; on Organization they are $25 and $5 a month against $55. People who only view or comment should not be on full seats. Figma SSO and the Organization plan shows how much that can save.

A price lock. If you commit to a year or more, ask for the per-seat price to be fixed for the term and the renewal.

Removing seats mid-term. Ask what happens when someone leaves. Some contracts let you reassign or drop a seat; some bill you for it until renewal.

Clean up before you count. Remove leavers and unused accounts before renewal, so you are not negotiating the price of seats nobody uses.

None of this is guaranteed to work. All of it costs one email.

Where SmashSSO fits

SmashSSO is not SSO, and it does not sit in the login path. If an auditor, insurer or customer contract requires login through an identity provider, you need real SSO and the upgrades that come with it, at least for the tools in scope.

What it replaces is the job most small companies buy SSO for: adding and removing people across their tools from one place. It reads your people from Google Workspace, shows who has an account in each tool and with what role, and flags accounts that match nobody in your directory, which is often where unused seats hide. Access bundles by role invite a new hire to every tool they need; when someone is suspended in Google Workspace, it shows where they still have access and removes them. Changes run through a tool's member API where you have added a token, otherwise through an agent in your own Chrome, which needs that browser open and can fail when a tool redesigns its screens. Any step that would add a paid seat waits for your approval, and every change is in an audit log. It does no spend tracking, so it will not total your seat costs for you.

Its own price is flat: from $199 a month billed annually, however many people and tools (pricing). It costs the same at 10 people as at 35. The SSO tax post covers the rest of the options.

FAQ

What is per-seat pricing?
You pay a fixed amount for each person with an account, usually per month and often billed a year ahead. Most work software, including Slack, Notion, GitHub and Figma, is priced this way.
Why do SaaS tools charge per seat?
Because revenue then grows as customers grow, without selling anything new, and it feels fair that a small team pays less than a large one. The downside for buyers comes when a feature like SSO sits on a higher plan: the difference is charged on every seat.
Is flat pricing cheaper?
It depends on headcount. A flat fee can cost more than per-seat pricing for a very small team and much less for a larger one. Its advantage is predictability: it does not rise when you hire, so compare both at the headcount you expect in two years.
Can I upgrade only some seats?
Usually not. On tools like Slack, Notion, GitHub and Figma the plan applies to the whole workspace or organization, so every paid seat moves up together. Some tools offer cheaper seat types, such as Figma's Dev and Collab seats, which is worth using for people who only view or comment.
Do unused seats cost more on an SSO plan?
Yes, because the upgrade applies to every seat you are billed for, including those held by people who left. A leaver still holding seats in Slack, Notion, GitHub and Figma costs about $447 a year on the plans without SAML and about $1,332 a year on the SSO plans, at list prices.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google