The SSO tax is what you pay when a software vendor only offers single sign-on on a more expensive plan than the one you need. For a 20-person team on five ordinary tools, it comes to about $18,700 a year.
You want one feature, a login button that goes through Google or Okta, and the price of that button is moving every seat in the tool to Business or Enterprise. The numbers are below, with a source for each, followed by the ways out.
What the SSO tax is
Single sign-on (SSO) lets your people log in to every work tool through one account, usually Google Workspace, Microsoft or a dedicated identity provider like Okta. The tool has to support it, almost always through a protocol called SAML.
Most tools do support it. They just keep it off the plans small companies buy. Slack has it on Business+, not Pro. GitHub has it on Enterprise, not Team. Figma has it on Organization, not Professional. The feature is the same on every plan; the plan it sits on is the expensive one.
That gap between the plan you need and the plan with SSO is the tax. The name comes from a long-running public list of vendors doing it, and it stuck because it describes the feeling exactly: you pay more for the same product because you would like to manage it properly.
Here is the smallest worked example. Slack Pro is $7.25 a seat a month on annual billing. Business+, the first plan with SAML, is $15. That is $7.75 more per person per month. For 20 people, $7.75 × 20 × 12 comes to $1,860 a year. Nothing else about Slack has to change for you to want that login button, and nothing about the button costs Slack more because you have 20 people instead of 2. You pay it anyway, on every seat, every year.
How vendors charge it
There are three versions, and they hit a small company differently.
Per-seat upgrades are the common one. The SSO plan costs more per person, and you cannot upgrade only the people who need it, so every seat goes up. This is the version that grows every time you hire, and the one that makes up most of the figure above.
Flat add-ons are the second. Some tools sell SSO as an add-on for the whole account. Vercel lists SAML SSO as an add-on on its Pro plan; PlanetScale lists an SSO add-on on top of its base plan. You pay the same whether you have 3 people or 30, which is fairer, though rarely cheap.
"Contact sales" is the third. The SSO plan has no public price. Asana and Linear both keep SAML for Enterprise. You find out what it costs after a call, and the answer is rarely small. You also cannot budget for it or compare it, which is the point.
What it costs a 20-person team
Here are five tools most small companies use, with the plan you would normally be on, the cheapest plan that includes SAML SSO, and what the difference adds up to over a year for 20 people.
| Tool | Plan without SSO | Cheapest plan with SSO | Extra a year, 20 people |
|---|---|---|---|
| Slack | Pro · $7.25 a seat | Business+ · $15 a seat | $1,860 |
| GitHub | Team · $4 a seat | Enterprise · $21 a seat | $4,080 |
| Figma | Professional · $16 a seat | Organization · $55 a seat | $9,360 |
| Notion | Plus · $10 a seat | Business · $20 a seat | $2,400 |
| Zoom | Pro · $14.16 a seat | Business · $18.33 a seat | $1,000.80 |
| Total SSO tax a year | $18,700.80 | ||
That is the tax on five tools. A typical small business runs dozens. Not every tool charges it: the calculator lists the ones with a published SSO price, the ones that only quote on request, and the ones that include SSO on cheap plans or for free (Tailscale, PagerDuty and Cloudflare among them, credit where it is due).
Each of the five has its own breakdown if you want the plan details: which Slack plan has SAML, GitHub Enterprise against Team, Figma's Organization plan, Notion Business or Enterprise and what Zoom Business adds.
The table also assumes everyone has a seat in every tool. Your designers are not all in GitHub and your engineers may not all be in Figma, so your real number is probably lower. It is rarely low enough to shrug at.
How the tax grows as you hire
Divide the five-tool figure by 20 and you get about $935 per person per year. That number is the real shape of the SSO tax: a fixed surcharge on every hire, for as long as you keep the tools.
At 10 people the same five tools cost about $9,350 a year extra. At 50 they cost about $46,750. Nothing about single sign-on changed between those two companies. The login works the same way, takes the same setup, and breaks the same way when a certificate expires. Only the bill moved.
That is why the per-seat version is the one to watch. A flat add-on is a decision you make once. A per-seat upgrade is a decision you keep re-making, without noticing, every time you send an offer letter. How per-seat pricing multiplies an SSO upgrade runs the numbers over three years of hiring.
Why vendors do it, and why SSO is so expensive
SSO is the feature large companies cannot buy without. Their security teams require it, their auditors ask about it, and their IT departments will not manage two hundred separate logins. That makes SSO the most reliable way to sort customers by size: put it on the top plan and every big company has to buy the top plan.
The login button is the same for a team of 10 as for 10,000. The price is set by who is buying, not by what it costs to run. Small companies get caught in a fence built for someone else. Why vendors put SSO on the Enterprise plan goes through the pricing logic, and the SSO wall of shame ranks the tools that charge the most for it.
You can understand the logic and still object to paying it. Most small teams want SSO for a much smaller reason than an enterprise does, and it is worth being clear what that reason is.
The second fence: removing people
Even after you pay for SSO, one job is usually still undone. SAML handles signing in. It does not create accounts or remove them. When someone leaves and you disable them in your identity provider, they cannot log in again, but their account in each tool is still there, often still holding a paid seat.
Removing accounts automatically is a separate standard called SCIM, and vendors often put it a tier above SSO. Notion is the clean example: SAML on Business, SCIM only on Enterprise, which has no public price. So the company that paid the SSO tax to get clean offboarding finds it bought the login half and still removes leavers by hand. How SCIM provisioning works explains the difference, and why it matters more to a small team than the login does.
An identity provider does not get you out of it
A common assumption: "We will buy Okta and have SSO everywhere." Okta, Google Workspace, Microsoft Entra ID and JumpCloud sit on your side of the login. They vouch for who your people are. The tool still has to accept that, and it only does so on the plan with SSO.
So the identity provider is a second bill, not a replacement for the first. You pay Okta per user (from $6 a month, with a $1,500 yearly minimum, per our Okta pricing breakdown) and you upgrade Slack, GitHub and Figma. The SSO tax is the tool-side half, and no identity provider removes it. What single sign-on really costs adds both bills together for a 20-person company.
Four ways to stop paying it
Negotiate first. If you are already talking to a vendor's sales team, ask for SSO on your current plan. Some will, especially on annual contracts. It does not scale to forty tools, but it is worth asking for the two or three most expensive ones, and asking costs one email.
Then drop or consolidate tools. If a tool you barely use is one of the expensive ones, the cheapest SSO is not having it. A tool audit usually turns up a few, along with seats held by people who left months ago.
Or live without SSO for now. Plenty of small companies run perfectly well with Google sign-in where tools offer it, a password manager for the rest, and MFA everywhere. That is a legitimate choice, as long as you have a reliable way to remove people when they leave.
Finally, solve the job you actually wanted SSO for. For a company of 5 to 50 people, SSO usually gets bought for one reason: adding and removing people in one place, so that when someone leaves, they leave everything. That job can be done without upgrading anything.
Where SmashSSO fits, and when it does not
SmashSSO is not single sign-on. Your people keep logging in to each tool the way they do now. What it replaces is the reason most small companies want SSO: it gives and removes access to every tool from one place.
It reads your people from Google Workspace, finds who already has access to which tool, and then invites, changes and removes people for you. Tools with a member API are handled through the API; everything else is handled by an agent working in your own Chrome, through an extension, in tabs where you are already signed in as an admin. A change that would add a paid seat is built to stop and ask you first. The details, including the parts you should weigh carefully, are on the security page and in how it works.
It costs a flat fee for the whole company, from $199 a month billed annually (pricing), so it does not grow with every hire the way per-seat upgrades do.
When you need real SSO anyway: if a customer contract, an auditor or an insurer requires that people log in through an identity provider, a tool that manages access is not a substitute. Pay the tax for the tools that are in scope, and keep it to those.
Work out your own number
The formula is simple: for each tool, the price difference between your plan and the cheapest plan with SAML, times your seats, times 12. The SSO tax calculator does it with each vendor's published prices and links every source. Vendors change their prices without notice, so check the source before you rely on a figure.
If the number makes you wince, read SSO for small business: do you actually need it? before you sign anything.
More on what SSO costs
The posts below cover the SSO tax from every side. Start with the group that matches the question you have today.
If you are still deciding whether you need SSO at all, read whether a small business needs SSO for the short answer, the buyer's guide to single sign-on for small business for how to shop if you do, and whether SOC 2 requires SSO if an audit is what started the conversation.
If you want the numbers, SSO pricing adds the identity provider and the tool upgrades into one total, and how to calculate your SSO tax shows the method by hand. The SSO wall of shame ranks the tools that charge most, per-seat pricing shows how the gap compounds as you hire, and why SSO sits on the Enterprise plan explains the pricing logic behind all of it. Free SSO covers what you can get for nothing, and where that stops.
If you are comparing products, SSO alternatives for small businesses looks at cheaper ways to get the outcome, the best SSO solutions for small businesses and SSO providers compared by what small teams pay cover the identity providers themselves, and what you are buying with SSO software explains the categories so a sales call cannot blur them.
The tool-by-tool posts give the plan and the price for one product each. For chat and meetings, there is Slack SSO, who needs Slack Enterprise Grid, Zoom SSO setup and the plan it needs and what the Zoom Business plan adds. For engineering tools, read GitHub Enterprise pricing against Team, Vercel's SAML add-on, Linear SSO by plan, Atlassian Guard for Jira and Confluence and AWS IAM Identity Center for small teams.
For design, docs and project work, see Figma SSO and the Organization plan, Notion's Business plan against Enterprise, Airtable SSO and the Business plan and why Asana SSO is Enterprise only. For sales and support tools, read HubSpot's Professional plan tax and Intercom pricing and the cost of SSO.
Two posts cover the identity provider side of the same bill: using Google Workspace as your identity provider, which most small companies already pay for, and whether Microsoft Entra ID P1 is worth it for SSO if you run on Microsoft 365.