Most small businesses do not need SSO. What a 5 to 50 person company usually wants from SSO for small business is one place to add a new hire to every tool, and one place to remove someone from every tool when they leave. SSO does not do the second part, and it is an expensive way to get the first.
There are real cases where you need SSO. This post covers what SSO does, what it costs once every tool is counted, when it is worth it, and what to do instead when it is not.
What SSO actually does
Single sign-on means your people log in to every tool through one account. Usually that account is Google Workspace or Microsoft 365, or a dedicated identity provider such as Okta or JumpCloud. When someone opens Slack, Slack hands them to the identity provider, the identity provider checks who they are (password, MFA), and sends them back signed in. How SSO works, step by step shows the handoff in detail.
That gives you three things.
One login for employees. Fewer passwords to remember, reuse and leak. People stop keeping a note of thirty logins.
One place to enforce login rules. MFA, password strength and which devices can sign in are set once in the identity provider, and they apply to every connected tool.
One switch to block future logins. Disable someone in the identity provider and they cannot log in to SSO-connected tools again.
What SSO does not do
Read the last point again: future logins. SSO controls the front door. It does not empty the house.
Existing sessions keep working. If someone is logged in to a tool when you disable them, many tools keep them signed in until the session expires.
Their account also stays in the tool. They are still a member of the Slack workspace, the GitHub organization and the Figma team. They still hold a paid seat. Their API tokens and integrations still work.
And anything not connected to SSO is untouched. Every tool that does not support SSO, or that you have not paid to connect, carries on as before.
Removing the account itself is called deprovisioning, and it is a separate feature, usually built on a standard called SCIM, often on an even more expensive plan (what SCIM is). Without it, someone still has to go into each tool and remove the person by hand. That is the job most small companies were trying to get rid of in the first place.
Why small companies end up looking at SSO
From the outside, the reasons usually fall into three groups.
The first is offboarding. Someone left, and three weeks later you found they were still in a tool. Or you realized you have no list of what they had.
The second is a security questionnaire. A bigger customer sent a spreadsheet asking "Do you use SSO?" and you would like to say yes.
The third is password chaos: shared logins, reused passwords and nobody sure who has admin rights.
Only the second one is really about SSO. The first is about access management. The third is mostly solved by a password manager and MFA, and SSO against a password manager explains which problem each one solves.
What SSO costs a small business
SSO has two bills, and the second one is the one people miss.
The identity provider. If you are on Google Workspace, you already have one: every Business edition can act as a SAML identity provider once your domain is verified. Microsoft 365 comes with Entra ID Free, and Entra ID P1 is $7 a user a month paid yearly. Dedicated identity providers cost more. JumpCloud sells SSO on its own at $3 a user a month billed annually. Okta lists its Workforce Identity Starter suite at $6 per user a month, billed annually, with a $1,500 yearly minimum (Okta pricing). All of those are list prices as we read them on 27 October 2026, with sources in what single sign-on really costs.
Every tool's SSO plan. This is the SSO tax. Most tools only accept SSO on their Business or Enterprise plans, so connecting them means upgrading every seat. For a 20-person team on five common tools:
| 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 five tools, before the identity provider and before the rest of your stack. The full breakdown of the SSO tax explains why vendors price it this way.
A 5-person company against a 50-person company
Size changes the answer, in both directions.
At 5 people, the same five tool upgrades come to about $4,675 a year. The identity provider is where small numbers hurt. Okta's $1,500 minimum on Starter works out at $300 a person a year, or $25 a month each, against the $6 on the price list. A 5-person company on Okta pays what about 21 users would.
At 50 people, the five tool upgrades come to about $46,750 a year. Okta Starter is now $3,600 a year at list price, a rounding error next to the tool side. The identity provider stops being the question; the upgrades become the whole bill. At that size, the case for real SSO also gets stronger on its own merits, which is the honest part of the trade-off.
Contractors, guests and shared accounts
Small companies are rarely as tidy as an SSO diagram.
Contractors often work from their own email address. SSO only covers people who have an account in your identity provider, so a freelancer invited to Slack with their own address is outside it, and there is nothing in your directory to disable when they finish. Either you give them a company account, which is usually another paid account in your directory, or you track them separately. Contractor access management covers the options.
Guests and client users in shared channels or workspaces sit outside your identity provider for the same reason.
Shared accounts are the awkward case. A single "marketing@" login used by three people does not fit SSO, which exists to identify one person. If your stack depends on shared logins, SSO will not tidy them; a password manager and a list of who knows each password will. Shared accounts at work goes through what to do with them.
When you genuinely need SSO
Be honest with yourself here, because sometimes the answer is yes.
A customer contract requires it. Some enterprise buyers require that your staff log in to systems holding their data through an identity provider. A process document will not satisfy that clause.
An audit or framework names it. If your auditor or insurer specifically asks for SAML SSO on certain systems, a process will not satisfy them. SOC 2, for example, does not name SSO; it asks you to control and review access and remove it promptly. SSO is one way to show that, not the only way, and whether you need SSO for SOC 2 goes through what auditors look for.
You are growing past 50 people. At some size, centralized login enforcement becomes worth its price on its own.
If one of those applies, buy SSO for the systems in scope and stop there. You do not have to pay the tax on every tool to satisfy a requirement about three.
What is the best SSO for a small business?
If you do need it, the best identity provider for a small business is usually the one you already pay for. On Google Workspace, that means using Google as your identity provider, at no extra cost. On Microsoft 365, it means Entra ID, with P1 if you need Conditional Access rules about who logs in from where.
A dedicated identity provider such as Okta or JumpCloud earns its price when you have a mixed directory, devices to manage, or more apps than your Workspace edition can provision into. For a side-by-side look, see the best SSO solutions for small businesses and the buyer's guide to single sign-on for small business. Whichever you pick, the tool-side bill above does not change.
Cheaper ways to get the outcome
If what you want is control over who has access, there are cheaper routes.
Use what you have. Turn on "Sign in with Google" wherever a tool offers it for free, and enforce 2-step verification in Google Workspace. You get much of the login benefit for nothing. It is usually optional rather than enforced, so it is not real SSO, but it cuts the number of passwords that matter.
Add a password manager for everything else. It makes shared and individual passwords manageable and lets you rotate them when someone leaves.
Keep an access list. Know who has access to what. A spreadsheet is a start; it goes stale fast, usually the week after you make it.
Automate adding and removing people. That is the job SSO was going to do for you, and it can be done without upgrading any tool.
Where SmashSSO fits
SmashSSO does that last job. It reads your people from Google Workspace, discovers who already has access to each tool, and invites, changes and removes them from one place, through a tool's member API where you have added a token, and otherwise through an agent in your own Chrome, in tabs where you are signed in as an admin. When someone is suspended in Google Workspace, it alerts you and shows where they still have access. Steps that would add a paid seat wait for your approval.
It is not SSO: people keep logging in the way they do now. It costs a flat fee for the whole company, from $199 a month billed annually (pricing), and the FAQ is blunt about its limits, such as needing your browser open for agent-run changes and having no SOC 2 report.
How to decide
Work through the questions in order, and stop at the first yes.
First, does a customer, auditor or insurer require SSO? If so, buy it for the systems in scope, and only those.
If not, is your real pain removing people when they leave? Then you need access management, which SSO alone will not give you.
If it is mostly password chaos, start with a password manager and MFA. They cost a fraction of any SSO plan and fix the problem you actually have.
Still want SSO everywhere? Run your tools through the SSO tax calculator first, so you know the number before a sales call tells you.
Whatever you choose, keep a list of every tool each person has. When someone leaves, that list is the difference between a ten-minute job and an afternoon of guessing. Our employee offboarding checklist walks through the rest.