How to reduce SaaS costs without cutting the tools people need
When finance asks for a cut in software spend, the instinct is to draw up a list of tools and start cancelling. That usually backfires. You save a little, break a workflow someone quietly depended on, and spend the next month fielding requests to buy it back. The good news is that most SaaS savings sit in waste, not in tools people use: duplicate platforms, seats nobody logs into, and contracts that renewed at last year's price because nobody looked in time.
This guide is a playbook for finding that waste and removing it, in an order that saves money without disrupting the people doing the work. The numbers below are illustrative, not figures from any particular company.
Start with what you actually pay for
You cannot cut what you cannot see. Before any decision, build one register that lists every tool you pay for - not just the obvious platforms, but the small monthly utilities that never cross a finance review. Pull the last few months of card statements and invoices and record, for each tool, the vendor, the owner, the renewal date, the notice period, the annual cost and how many seats you actually use.
One register in one place is what turns a vague sense that "we spend too much on software" into a list you can act on. If you are starting from scratch, our guide to the register fields that matter covers exactly what to capture, and StackTrackr's spend view gives you the total and the per-tool breakdown once the data is in.
Remove duplicate and overlapping tools
Estates grow team by team, so overlap is normal. Two departments buy two different project trackers. Marketing and sales each pay for a separate mailing tool. A design licence lingers after the team standardised on something else. Sort your register by category and the overlaps become obvious.
Overlap is not the same as duplication. Two tools may share a label but do genuinely different jobs. Before consolidating, ask the owners what each is used for. Where two tools truly do the same work, pick the one people prefer, migrate, and cancel the other at its next deadline. Some of the biggest overlaps are tools nobody will even claim - our guide to finding software nobody owns covers how to surface those.
Right-size your seats
Seat counts drift upward and almost never come back down. You add licences for a project, people leave, roles change, and the bill keeps charging for all of them. This is the least disruptive saving available, because reclaiming an unused seat takes nothing away from anyone who is working.
For each tool, compare seats paid for against active users in the last 60 to 90 days. A team paying for 50 seats at £15 a month while 32 are active is spending over £3,000 a year on empty licences on that one tool. Reclaim the inactive seats, and at renewal drop the contracted count to match reality plus a little headroom.
Match the plan to the usage
Right-sizing is not only about seat count. Teams are often on a higher tier than they use, paying for an enterprise plan to get one feature that a mid-tier plan also includes. Check the tier against what people actually touch before you renew.
Catch silent auto-renewals in time
The date that costs money is not the renewal date. It is the cancellation deadline - the last day you can give notice before the contract rolls over. That deadline is the renewal date minus the notice period, and it is often months earlier than people expect. A tool that renews on 1 October with a 90-day notice period must be cancelled by early July.
Miss that window and the decision is made for you: another year, at the new price, whether you wanted it or not. Record the notice period alongside the renewal date for every tool, and set alerts against the deadline so the owner hears about it while there is still time to act. Our guide to tracking software renewals sets out the process, and the hidden cost of auto-renewing SaaS explains why these rollovers are the quietest line on the bill.
Consolidate onto annual only where it genuinely saves
Annual billing is usually cheaper per seat than monthly, and switching stable, well-used tools to annual can be a real saving. But annual terms cut both ways. They lock you in, they often carry longer notice periods, and they make it harder to walk away from a tool you are still deciding on.
- Move to annual when the tool is settled, the team is stable, and the discount is real
- Stay monthly for anything new, contested, or likely to be replaced within the year
- Whatever the term, record the notice period - a longer commitment means a longer window to watch
Use the renewal deadline as leverage
Renewal is the one moment you hold real negotiating power, and it is wasted if you notice it late. When you know a deadline is coming, you can approach it prepared: your actual usage in hand, a sense of what you would pay, and enough time to consider alternatives without panic.
- Start 60 to 90 days out, before the notice window closes and while you still have the option to leave
- Bring your usage data - seats used, features touched - so the conversation is grounded in fact, not the vendor's assumptions
- Ask directly about right-sizing the seat count and the tier to what you use
- Be willing to name your walk-away point; a credible alternative is what moves a price
A vendor is far more likely to hold or reduce a price for a customer who clearly knows their own usage and has time to leave than for one emailing in a hurry the week before renewal.
Make it a habit, not a one-off
A single spring clean feels good and then quietly undoes itself. Seats creep back up, new tools arrive, contracts roll over. The saving holds only if the register stays current and each renewal gets a short review before it lands. Keep one live register, watch the deadlines, and the waste stops rebuilding.
StackTrackr keeps the register, the spend view and the renewal alerts in one place so this becomes routine rather than a project. See how it fits together on the features overview, or start tracking your own estate and find the waste before the next renewal does.