Who owns this tool? How small teams keep SaaS spend in check

The person who knows about a tool is rarely the person who pays for it. A designer signs up for a font service, a developer adds a monitoring plan, someone starts a Zoom trial for a client call, and the charges land on the founder's card with no name attached. Months later the card statement shows 30 lines, and nobody can say which ones still matter.

The fix is not a bigger process. It is one rule: every tool has one owner, and that owner hears about the renewal before it happens. Add a shared list, a seat check when people leave, a short quarterly review and a clear line for who approves new tools, and most surprise charges stop.

Below is the whole system, sized for a team of 3 to 30 people, with a responsibilities table and an offboarding checklist you can copy.

Why do small teams lose track of software spend?

It is rarely carelessness. It is how small teams buy software: fast, by whoever needs it, on whatever card is closest. Four patterns cause most of the waste.

• Unowned tools renew unseen. An annual plan bought by someone eleven months ago renews on a card nobody watches. The person who could say "we stopped using that" never sees the charge.
• Seats outlive the people. Someone leaves, their email is closed, but their Figma, Notion and Google Workspace seats keep billing. At $15 to $20 a seat across a few tools, one departed teammate can cost $45 to $60 a month.
• Duplicates creep in. Two teams pay for two video tools, or a project management app is kept alongside the one that replaced it.
• "Is anyone still using this?" threads. Someone spots a charge, asks in the team chat, gets two thumbs and no answer, and the tool renews anyway.

Each of these has the same root: no named person is responsible for the decision.

What does a tool owner actually do?

An owner is the person who can answer "do we still need this, and at this size?" Usually that is the heaviest user or the lead of the team that depends on it. It is often not the person who pays.

Owning a tool is a small job. The owner:

• Decides at renewal: keep, downgrade, or cancel, a few weeks before the charge.
• Keeps seats right: removes people who left or stopped using it, and adds people only when needed.
• Notices price changes: a plan that went from $12 to $15 a seat is a 25% rise, $36 a year per seat.
• Knows the exit: where the data lives and how to export it if the team cancels.

One owner per tool, never a group. "The design team owns Figma" means nobody does. If two people share it, pick one and let them ask the other.

Who does what: a simple responsibilities table

Most small teams have three roles around software: the owner of each tool, whoever pays the bills (a founder, an operations lead or an office manager), and a founder or lead who signs off on bigger spend. Here is a split that works:

The point of the table is not paperwork. It is that every row has one person who acts, so nothing waits for "someone".

How do you set up tool ownership in an afternoon?

You do not need a new tool to start. A shared spreadsheet works for the first version; our free subscription tracker template already has an Owner column.

The first pass usually takes two to three hours. After that, the list only needs a few minutes whenever something is added or renewed.

How should renewals reach the owner?

A reminder on the payer's calendar does not help if the payer cannot make the call. Send each renewal to the owner, with enough context to decide in one minute: what it costs a year, how many seats are in use, and whether the price changed since last time.

Timing matters more than format. Monthly tools need a nudge only when something changes. Annual plans need a reminder early enough to act: some contracts require notice 30 days or more before the renewal date, and that window is easy to miss when the reminder arrives the day before.

How do you stop paying for seats of people who left?

Offboarding is where seat costs leak. Accounts get closed in the order people remember them, and paid seats are rarely on the list. Add these steps to whatever offboarding you already do:

The last item matters. Some tools bill for removed seats until the end of the billing period, and some keep billing until an admin downgrades the plan. The statement is the only proof.

What goes into a quarterly software review?

Once a quarter, the person who pays runs a 45-minute review with each owner joining for their tools. The agenda is short:

• What renews in the next 90 days, and has each owner decided?
• Seats vs active users for the five most expensive tools.
• Price rises since last quarter.
• Duplicates: two tools doing the same job.
• Tools with no owner, which should be none.

If you want a deeper one-off pass first, the SaaS subscription audit guide covers a full cleanup. The quarterly review then keeps it clean, and it feeds straight into planning next year's numbers, as in budgeting for 2027.

Who approves new tools?

Without a rule, either everything needs the founder (and people start expensing tools quietly) or nothing does (and the list grows by three tools a month). A simple threshold works:

• Under a small monthly amount, say $50 a month: the person who needs it can buy it, as long as they add it to the shared list with themselves as owner.
• Over that amount, or annual plans: one named person approves, usually the founder or operations lead.
• Anything that holds client data, whatever the price: same named person, because it is a security and contract question as much as a cost one.

Write the threshold down where everyone can see it. The number matters less than everyone knowing it.

How Subly keeps owners in the loop

Personal covers 3 people, Business 10 and Team 20; see Subly for teams for how a typical week looks.

Whatever you use, the habit is the same: one name per tool, renewals to that name, and a short look at the whole list every quarter. That is enough to keep a small team's software spend from running itself.