SaaSClerk Blog · Choosing a SaaS subscription tool

SaaS Subscription Tools by Team Size: Which Layer You Need at 1, 10, or 30 People

Choose by the question you cannot answer today: at one person the missing piece is a list of recurring charges, at two to ten people the next renewal date on each line, at ten to thirty a named owner per line, and past thirty the authority to create a charge, which is where approval workflows and payment control belong.

Team size works as a filter because it proxies how many people can start a charge, and that is the variable deciding the tool. Each stage below also names what stays unnecessary until the next one.

One person: the missing piece is the list

Nothing is out of control while you are the only signer, so the work is five minutes of listing. The gap is memory: an annual plan bills once and is out of mind for eleven months, and a trial converts without anyone deciding. List every recurring software charge from the last twelve months and divide each annual figure by twelve so the lines compare. A shorter window does not contain the annual charge and reports a clean result. Keep the list short and current, because one you rebuild annually drifts within a quarter. Approval flows, provisioning and a spend policy can wait.

Two to ten people: the missing piece is the renewal date

The list is still short enough to hold in your head, and the misses come from timing. Renewals land on staggered dates, so the surprise arrives mid-quarter as an old charge repeating. Add one column, the next renewal date, and set a reminder fourteen days ahead of it. A cancel decision made before that date is a decision; made after it, it is a refund request. Then widen your sources, because a teammate who buys a seat on a personal card and expenses it never appears in your mailbox.

Ten to thirty: the missing piece is a name per line

Three things change at once: several people buy software, several cards exist, and people leave. A subscription whose requester has left keeps billing, and nobody can say what it was for. The question for any line is now who asked for it, what it costs per month, when it bills next, and where the cancel page is. That needs an owner column, a status, and one stored cancel URL per line, with the owner being a named person. Check the list against each name before a login is deactivated, because that is the last moment a witness is available.

Thirty and up: the missing piece is control at purchase time

Past about thirty people the failure moves upstream. Software is bought by department heads against budgets nobody set, on cards nobody issued, and the invoice reaches accounting weeks later without a matching purchase order. The questions become who may create a charge, on which instrument, against which budget, and how a license is reclaimed when someone leaves. The category answering them is sold as a SaaS management or spend governance platform: approval intake, payment limits, license reclamation from your identity directory, invoice capture and accounting sync. Pricing there is seat-based or quote-based and varies by vendor, so verify on the vendor site. A tracker does not grow into this layer.

How the tool categories compare

Read the table by the question you cannot answer. Every stage still needs the inventory built in the stage before it, and the categories differ mainly in how much of that inventory stays current without you re-entering it.

Team size	Question you cannot answer	Layer that answers it	Where the data comes from
1	What do I pay for at all?	An inventory normalised to monthly figures	Twelve months of billing email, plus the card statement
2–10	When does each line bill next?	The inventory plus renewal dates and a reminder	Shared mailboxes, app-store receipts, expensed seats
10–30	Who owns this line, and where do I cancel it?	The inventory plus an owner, status and cancel URL	Billing email across accounts, plus offboarding checks
30+	Who may create a charge, and how does it reach accounting?	A control layer: approval intake, payment limits, invoice sync	Identity directory and procurement, with email as the cross-check

What SaaSClerk covers in the first three stages

SaaSClerk connects to a mailbox read-only (the gmail.readonly OAuth scope, or an IMAP authorization code), reads twelve months of billing email, and returns the service, amount, billing interval, next renewal date and last charged date for each subscription. Annual charges are divided by twelve before the list sorts, so an annual plan and a seat price sit on one axis. On Starter and Business it sends one reminder email fourteen days before a renewal date. Each line can hold a cancel URL and a status of CANCEL, and nothing is cancelled on your behalf. Tokens are encrypted at rest with AES-256-GCM, the site runs over TLS, and no email content is stored. Starter is $49 per month, or $39 per month billed annually ($468 per year). Business is $149 per month, or $119 per month billed annually ($1,428 per year). The twelve-month scan needs no card.

Where it stops: it reads email, so it cannot see a card statement, an app-store receipt or a purchase made outside the mailbox you connect, and it runs no approval workflow. At the fourth stage its inventory is a cross-check on a governance platform.

FAQ

Which SaaS subscription tool should a small team start with?

One that builds the full inventory first: service, amount, billing interval and next renewal date, with annual charges converted to a monthly figure. An owner per line comes next, and approval workflows come last.

How is a subscription tracker different from a governance platform?

A tracker says what is paid, how much, and when it bills next. A governance platform says who may create a charge and enforces it at the payment and provisioning layer. Verify features and pricing on the vendor site.

Is a SaaS management platform worth it under thirty people?

Rarely. That category enforces approval before a purchase, and a team under thirty has neither a purchase queue nor a written payment policy. The leak at this size is an unowned annual plan renewing quietly.

When does a small team outgrow a subscription tracker?

When a purchase needs approval before it happens, or when accounting needs invoices matched to payments. The missing piece is a control layer, and the tracker becomes a cross-check on it.