Most of a small company's SaaS spend goes on per-seat subscriptions, and the waste hides in four places: seats for people who left or never log in, plans upgraded for a single feature, two tools doing one job, and monthly billing on tools you will clearly keep for years. Each has a fix you can make in an afternoon, and a check that stops it coming back.
You don't need a spend-management platform to find these at 5 to 50 people. You need your card statement, each tool's billing page, and an hour a quarter. Prices below are list prices from the vendors' own pages as we read them on 27 October 2026, used as worked examples. Your invoices are the real numbers.
Why per-seat pricing hides the waste
Almost every tool a small company uses bills per seat. That makes each tool look cheap, which is the point: $10 or $14 a person a month never gets a meeting. But the bill scales with your headcount, not with use, and nobody adds the rows up. A seat for a leaver costs the same as a seat for your busiest user. A plan upgrade costs the difference times everyone, not just the person who wanted it. Per-seat pricing explains how the model multiplies every decision.
So reducing SaaS costs is mostly not about negotiating. It is about counting seats and asking why each plan is the plan it is.
Seats nobody uses
The biggest leak is also the dullest. Someone leaves, their email is suspended, and their seat in every other tool carries on billing. Or someone was added to a tool for one project and hasn't opened it since.
How much a forgotten seat costs depends on the tool's rules, and they differ.
Google Workspace charges suspended accounts. Its help page on suspending users says "suspended accounts are still charged at the same rate as active accounts", on annual and flexible plans alike. To stop paying, you delete the account, or, if you need to keep the data, archive it, which usually needs a separate Archived User subscription.
JumpCloud bills suspended users too. It says so on its pricing page.
Slack works the other way. Its pricing page says members who take an action within a 28-day period count as active for billing, and when a paid member becomes inactive, Slack adds a prorated credit for the unused time.
So "we suspended them" can mean you're still paying full price. A worked example: Google lists Business Standard at $14 per user a month on a one-year commitment. Two leavers left suspended for six months cost $168 for two accounts nobody can use. Multiply that pattern across every per-seat tool they were in.
The fix is a rule: when someone leaves, their seat is removed or reassigned in every paid tool, the same week. SaaS license management covers how to find unused licenses and reclaim them in detail, and orphaned accounts covers the security side of the same leftover seats.
Tiers bought for one feature
The second leak is the upgrade bought for one thing. Somebody needed one feature, the feature was on the next plan up, and the whole company moved up with it, because plans are priced per seat and you can't upgrade one person.
Single sign-on is the classic case, which is why it has a name: the SSO tax. Notion's pricing page lists Plus at $10 per seat a month billed yearly and Business, where SAML SSO starts, at $20. For 20 people, that one login feature costs $2,400 a year. Notion SSO goes through that choice plan by plan.
Other common one-feature upgrades are an audit log, a higher file or history limit, admin roles, or a guest limit. For each paid upgrade, ask the owner three questions. Which feature did we upgrade for? Is anyone still using it? Is there a cheaper way to get it, or can we live without it?
Sometimes the upgrade is worth it. Write down why, so the question has an answer next year. The SSO tax calculator shows what the SSO upgrade costs across your tools.
Duplicate tools
The third leak is two tools for one job. It usually isn't a mistake: different teams chose different tools before anyone compared notes. Common pairs in small companies are video calls, note-taking or wikis, project tracking, file storage, and diagramming.
To find them, sort your inventory by what each tool is for, not by vendor name. Anywhere two rows share a job, ask which one more people use, whether the other does something the first can't, and when each renews.
Then pick one, move the data, and cancel the other at its renewal date, not after it. SaaS sprawl covers how the duplicates build up and how to consolidate.
Annual vs monthly
Annual billing is a discount for a commitment. On the pages we read:
| Product | Billed monthly | Billed annually, per month | Saving |
|---|---|---|---|
| Notion Plus | $12 per seat | $10 per seat | 17% |
| JumpCloud SSO package | $13 per user | $11 per user | 15% |
| Microsoft 365 Business Premium | $26.40 per user | $22 per user | 17% |
| Google Workspace (all Business) | Not compared on page | $7, $14, $22 per user | "Save 16%", per Google's page |
Sources: Notion, JumpCloud, Microsoft 365 Business Premium, Google Workspace.
The trade-off is flexibility. An annual plan commits you to the price and usually to a seat count for the year; check each contract for whether you can lower seats before renewal.
Is annual billing worth it? Go annual for tools everyone uses and will keep: email, chat, your main docs tool. Stay monthly for anything on trial, used by a few people, or likely to be replaced. And never go annual to fix a problem you haven't fixed yet. Clean up seats first, then commit, or you lock in a year of empty seats.
How to reduce SaaS costs, in order
The order matters, because each step makes the next one cheaper.
Remove leavers' seats first. It needs no decisions, no negotiation and no migration, and it shrinks every later number.
Then question the upgrades. With the seat count right, the cost of each plan upgrade is accurate, and the "is it worth it" question has a real answer.
Then merge duplicates. This takes the most work, because people have to move, so do it once the cheaper wins are in.
Then move keepers to annual billing. Only now are you committing to the right number of seats on the right plan.
Common mistakes
Reading the invoice total instead of the seat count. A bill that hasn't changed in a year looks fine. It may hide three leavers and three new hires who were added on top. Get the number of paid seats from each tool's billing page and compare it with people.
Removing a person without checking the seat went. In some tools, removing a member frees a seat you still pay for until you lower the seat count yourself, or until the annual term ends. Check the next bill.
Missing the expensed tools. Subscriptions on personal cards come back as expense claims, not card charges. They are often the ones nobody else knows about, and the ones that keep running after the person leaves.
Cutting the tool, keeping the accounts. Cancelling a paid plan often drops the tool to a free tier with every account and document intact. Remove the accounts, or you have swapped a cost for a risk.
Saving money by sharing logins. One seat for four people looks like a saving until someone leaves and you have to rotate the password and work out who saw what. Shared accounts covers the real cost.
What SaaS spend management means at 5 and at 50 people
SaaS spend management is keeping track of what each subscription costs, how many seats you pay for against how many you use, and when each renews, so you can act before the bill rather than after.
At five people, that is a short list and the founder's memory, plus one rule: every subscription is on a company card, not a personal one. The risk is not waste so much as a forgotten annual renewal for a tool nobody opens.
At fifty people, the list is long enough that nobody holds it in their head, and several people can put tools on cards. You need a sheet with an owner, renewal dates in a shared calendar, and a quarterly check. That is still not a reason to buy a platform; it is a reason to keep the sheet honest. The SaaS management guide has a sheet with the columns you need.
A quarterly spend check
Once a quarter, one person, about an hour. Pull three months of card and bank statements, and add any new recurring charge to the inventory with an owner. List renewals due in the next 90 days, and decide keep, downgrade or cancel for each, before the date. For each per-seat tool, compare seats paid with people who should have one, removing leavers first. Check each upgrade still has a written reason that holds. Look for two tools doing one job. And note the total monthly spend, so next quarter has something to compare against.
The software license audit is the longer version, for the first time you do this properly.
Where SmashSSO fits
SmashSSO does no spend tracking, and it has no CSV export. The money side of this post stays in your spreadsheet: it won't read invoices, track renewals or total your bill.
What it does help with is the first leak, seats held by people who shouldn't have them. It reads your people from Google Workspace and shows, for each tool you've added, who has an account and with what role, matched by email. Accounts that match nobody in the directory are flagged. When someone is suspended in Google Workspace, it shows every tool they're still in, and removes them through the tool's API where you've added a token, or through an agent in your own Chrome otherwise. Any step that would add a paid seat waits for your approval, so new seats don't appear unnoticed either. It costs a flat fee from $199 a month billed annually (pricing).