Skip to content

Blog

How to calculate your SSO tax

How an SSO tax calculator works, and how to do it by hand: the formula, a worked example with real list prices, and what the number leaves out.

· 9 min read

An SSO tax calculator works out one sum: for each tool, the price of the cheapest plan with SAML single sign-on minus the price of the plan you are on, times the seats you pay for, times 12. Add the tools up and you have the yearly figure. The SSO tax calculator does it for you with each vendor's published prices; this post shows the method by hand, so you can check it or adapt it.

It takes about ten minutes with your billing pages open. The worked example below uses prices we read on each vendor's pricing page on 27 October 2026. If you want the background first, what the SSO tax is and why vendors charge it covers that.

The formula

For a tool that charges per seat:

(SSO plan price − current plan price) × seats × 12

For a tool that charges a flat amount per account:

(SSO plan price − current plan price) × 12

Your SSO tax is the sum across every tool you would need to upgrade. Three rules keep the number honest.

Use the same billing term on both sides. Annual against annual, monthly against monthly. Mixing them inflates or hides the gap.

Use the cheapest plan that includes SAML, not the one the sales page pushes. That is the true price of the feature.

Count the seats you pay for, not the people at the company. Your designers may not be in GitHub; your engineers may not be in HubSpot.

"SAML" is the standard most tools use to accept a login from your identity provider, such as Google Workspace or Okta. When a vendor says "SSO" on a pricing page, that is almost always what they mean, and SAML against SSO explains the difference.

Per-seat vs flat vs "contact sales"

Vendors charge for SSO in three ways, and each goes into the sum differently.

Per-seat upgrade. The SSO plan costs more for every person. Slack, GitHub, Figma and Notion work this way. This is the version that grows when you hire, which per-seat pricing looks at over three years.

Flat add-on or flat plan. One price for the account. Vercel lists SAML SSO on its Pro plan at $300 a month; PlanetScale sells an SSO add-on at $199 a month per organization. Seats do not matter.

"Contact sales." The plan with SAML has no public price. Asana and Linear both do this. You cannot put a number in the formula, so write the tool down separately and get a quote. Do not leave it out of the conversation just because it is missing from the sum. Asana SSO is a typical case.

A fourth kind belongs on your list too: included. Some tools put SSO on free or entry plans. Their tax is zero, and they are worth knowing about; the wall of shame lists a few.

A worked example

A 20-person company. Everyone uses Slack and Notion. Eight engineers use GitHub. Four designers use Figma. The engineers deploy on Vercel. Project management is in Asana. Each tool is on the plan small companies usually pick.

Prices are per seat per month on annual billing, from each vendor's page as we read it on 27 October 2026:

ToolCurrent planCheapest plan with SAMLKindSource
SlackPro, $7.25Business+, $15Per seatslack.com/pricing
NotionPlus, $10Business, $20Per seatnotion.com/pricing
GitHubTeam, $4Enterprise, $21Per seatgithub.com/pricing
FigmaProfessional, $16 (full seat)Organization, $55Per seatfigma.com/pricing
VercelProPro + SAML SSO, $300 a monthFlatvercel.com/pricing
AsanaStarter, $10.99Enterprise, no public priceQuoteasana.com/pricing

Now the formula, tool by tool:

ToolGap a monthSeatsMonthsExtra a year
Slack$15 − $7.25 = $7.752012$1,860
Notion$20 − $10 = $102012$2,400
GitHub$21 − $4 = $17812$1,632
Figma$55 − $16 = $39412$1,872
Vercel$300 (flat)n/a12$3,600
AsanaNo public pricen/a12Quote needed

Total: $11,364 a year, plus whatever Asana quotes.

Three things the example shows. First, the flat Vercel add-on is the single biggest line, even though it is the only one that does not care about headcount. Second, GitHub and Figma have the largest per-seat gaps but cost less in total here, because only part of the team uses them. Third, if you had assumed all 20 people were in every tool, GitHub would jump to $4,080 and Figma to $9,360. Seat counts change the answer more than people expect.

One Figma detail: the example uses full-seat prices. Figma also sells cheaper Dev and Collab seats, and on Organization they are $25 and $5 a month. If some of your people only comment, price them on the seat they need.

What the number leaves out

The formula gives the upgrade cost at list price. Your real cost of SSO is usually higher, for six reasons.

The identity provider. Something has to send the login. Google Workspace does it at no extra cost if you already pay for it. Okta starts at $6 a user a month with a $1,500 yearly minimum (Okta pricing). SSO pricing adds both bills together.

One-time fees. HubSpot's pricing page says its Professional tier, where its SSO starts, needs a one-time $1,500 onboarding fee.

Provisioning. SAML handles login, not account creation and removal. That is SCIM, and some tools put it a tier higher: Notion has SAML on Business but SCIM only on Enterprise. What SCIM is explains why that matters for offboarding.

The other things the new plan bundles. Sometimes you get features you would have bought anyway, which lowers the true tax. Sometimes you get nothing you need.

Discounts and price changes. List price is the starting point for a negotiation, and vendors change prices without notice. GitHub, for example, shows its prices "for the first 12 months".

Your time. Setting up SAML on each tool and renewing certificates when they expire. Not on any invoice.

The same company at 5 people and at 50

Team size changes not just the total but which line matters. Keep the same mix as the example (everyone in Slack and Notion, two in five in GitHub, one in five in Figma, Vercel and Asana as before) and run the formula at both ends.

At 5 people, with 2 GitHub seats and 1 Figma seat, the per-seat lines come to $465 for Slack, $600 for Notion, $408 for GitHub and $468 for Figma. Vercel's flat $3,600 makes the total $5,541, and Vercel alone is about two thirds of it. For a very small team, the flat add-ons are the SSO tax.

At 50 people, with 20 GitHub seats and 10 Figma seats, the per-seat lines grow to $4,650, $6,000, $4,080 and $4,680. Vercel is still $3,600, and the total is $23,010. Now Vercel is about a sixth of the bill, and the per-seat tools are the problem.

That is the practical reason to calculate rather than guess. The tool you resent most at 5 people is often not the one that costs most at 50.

Edge cases: contractors, guests and shared logins

Real seat counts are messier than a headcount.

Contractors count if they hold a paid seat in the tool. They often do, and they are often the seats nobody remembers to remove. If a contractor's work is over, remove the seat before you count, not after.

Guests and external collaborators are billed differently from tool to tool. Some tools let them in free or on cheaper seats, some charge them as full members. Check each tool's billing page for how it counts them before you multiply.

Shared logins are one seat used by several people. They lower the seat count, but they do not survive an SSO rollout well, because SSO identifies one person per account. If you upgrade a tool for SSO, expect shared logins to become individual seats, and count them that way.

Leavers still holding seats inflate the figure and the bill alike. Clean them up first; SaaS license management covers how.

Use the calculator

The SSO tax calculator does the arithmetic above for the tools in its list. Pick your tools, set your team size, and it shows the yearly extra for each, with a link to every vendor's pricing page. Tools that only quote on request are listed separately, so they do not quietly fall out of the total, and tools that include SSO on cheap plans are listed too.

Two things to know when you use it. It applies one team size to every per-seat tool, so it assumes everyone has a seat everywhere; if your seat counts differ by tool, as in the example above, do those lines by hand. And its prices carry the date they were checked. Before you take the number to a budget meeting, open each vendor's page and confirm.

What to do with your number

A total on its own decides nothing. Split it first.

Put a mark next to every tool where something outside the company requires SSO: a customer contract, an auditor's control, an insurer's question. Those lines are the cost of doing business, and the useful question for them is whether you can negotiate the price down.

Every other line is optional. For those, ask what you wanted SSO to do. If the answer is "remove people when they leave", the number you calculated is the price of the expensive route to that, and it is worth comparing with the cheap ones before you sign. If the answer is "fewer passwords", Google sign-in on your current plans may already cover most of it.

Where SmashSSO fits

SmashSSO is not SSO, and it does not lower the tax for any tool where an auditor, insurer or customer contract requires login through your identity provider. For those, the formula above is your budget.

It does the job most small companies wanted 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 every tool and with what role, invites new hires through role-based access bundles, and removes leavers, through a tool's member API where you have added a token or through an agent in your own Chrome where you are already signed in as an admin. Any step that would add a paid seat waits for your approval, and every change is logged. The agent needs Chrome open and can fail when a tool redesigns its screens.

Its price is the comparison to make against your number: a flat fee from $199 a month billed annually, however many people and tools (pricing). If your SSO tax came out at $11,364, see how it works and decide which half of that you actually need.

FAQ

How is the SSO tax calculated?
For each tool, take the price of the cheapest plan with SAML SSO, subtract the price of your current plan, multiply by the seats you pay for and by 12. For tools that charge a flat amount per account, leave out the seats. Add the tools together for the yearly total.
Where do the prices come from?
From each vendor's own public pricing page, using the same billing term on both sides. The SSO tax calculator links every source and shows the date its prices were checked. Vendors change prices without notice, so confirm each one before you rely on it.
Does it include the identity provider?
No. The SSO tax is only the extra the tools charge. The identity provider is a separate bill, from $0 if you use Google Workspace or Entra ID Free to $6 a user a month or more for Okta, so add it if you need one.
What if a tool says "contact sales"?
Then there is no number to put in the formula. List the tool separately and get a quote before you decide, rather than leaving it out. The calculator shows these tools apart from the priced ones for that reason.
Does team size change which tool matters most?
Yes. Flat add-ons such as Vercel's $300 a month for SAML dominate the total for a very small team, while per-seat upgrades take over as headcount grows. Run the formula at the size you expect to be in two years, not just today.

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