Start with a full inventory, then harvest unused licences, then consolidate overlapping tools and tune technical consumption. That sequence returns the largest savings fastest. VendorBenchmark finds the average organisation wastes 34% of its SaaS budget, so the opportunity is large. Governance in the style of FinOps keeps the savings from creeping back.
TL;DR:
- Combine SSO logs, card feeds, procurement records, and team interviews; tag each subscription with an owner, cost center, renewal date, seat count, and purpose.
- VendorBenchmark reports 23% of purchased seats are inactive or underused; verify activity before reclaiming seats, and secure written true down rights before signing.
- VendorBenchmark’s consolidation sample showed median reductions of 31% in vendor count and 24% in SaaS spending; compare total ownership costs and pilot migrations before retiring tools.
- For AI workloads, provider level prompt caching can cut cached input token costs by 80–90%, while model routing can reduce average query costs by 60–80%.
- Measure usage for 30 to 60 days, then review costs monthly and assess renewals 90 days ahead to decide whether to keep, shrink, or retire.
Table of Contents
- How do you find every SaaS tool and hidden subscription you pay for?
- How do you reclaim unused seats and rightsize licence tiers?
- How do you choose which tools to merge or retire?
- What technical levers cut usage costs, including AI workloads?
- How does FinOps governance keep savings from creeping back?
- Which metrics prove your software cost reduction is working?
- What tools and integrations make optimisation repeatable?
- What does a 90-day sprint look like, and how do you sustain it?
- Why we see consolidation as the practical path to savings
- How we help you consolidate and pay only for what you use
- FAQ
- Sources
How do you find every SaaS tool and hidden subscription you pay for?
You cannot cut what you cannot see. Discovery comes before every other step, because licence audits, consolidation and renewal negotiations all depend on an accurate list of what the business buys and who uses it. The FinOps guidance for SaaS builds the inventory from several sources at once, then tags each item so costs can be allocated.
Automated sources give you breadth quickly:
- SSO logs show which applications people actually sign in to.
- Billing and expense card feeds reveal subscriptions bought outside procurement.
- CASB tooling flags cloud applications used on company networks.
- SaaS management platform connectors pull licence counts and renewal dates directly.
- API inventories expose integrations and keys that quietly generate usage charges.
Manual sources fill the gaps. Procurement records catch contracts that never touched a card. Short interviews with team leads uncover the tools people rely on but never registered. A one-page shadow IT survey sent to department heads often surfaces a handful of surprises in a week.
Then add metadata to every entry: owner, cost centre, renewal date, number of paid seats and business purpose. That tagging is what makes showback and chargeback possible later, since each team can see its own share of the bill.
Rank the output by three lenses: highest-spend vendors, areas where several tools do the same job, and products nobody clearly owns. Those three lists become your work queue for the rest of the programme.
Pro Tip: Start with card and expense data. It is the fastest feed to obtain and usually exposes the subscriptions that nobody in IT has ever heard of.
How do you reclaim unused seats and rightsize licence tiers?
Most organisations pay for seats that nobody uses. VendorBenchmark reports that 23% of purchased SaaS seats are inactive or below usage thresholds at any given time. That gap between purchased seats and active users is the cheapest saving available, because nobody loses a capability when an idle seat disappears.
Judge activity with evidence rather than opinion. Useful signals include SSO sign-ins, last-activity dates inside the application, feature usage telemetry, active API keys and shared licence pools. A person who has not logged in for a long time may not need a premium seat, and a team using only basic features rarely needs the top tier.
Run the harvest as a short sprint:
- Pull seat counts and last-activity data for your largest vendors.
- Define "inactive" with finance and IT, for example, no meaningful activity over a sustained period.
- Notify owners of flagged seats and give them a short window to object.
- Remove or downgrade the seats nobody defends.
- Cancel unused add-ons, modules and extra environments.
- Calendar every renewal date well ahead so you can act before auto-renewal.
Renewal timing is your leverage. Vendors listen when you arrive with usage data and a firm intention to true down. Useful talking points are your actual active-user count, the cost per active user you are paying today, a request to move low-use staff to a cheaper tier, and a request to align the term to your next review rather than a multi-year lock.
If you want a structured way to show finance what these changes return, our guide on how to calculate ROI on SaaS subscriptions walks through the arithmetic.
Pro Tip: Ask for the true-down right in writing before you sign, not at the next renewal. A contract that only allows seat increases turns every harvest into a negotiation.
How do you choose which tools to merge or retire?
Consolidation works when you decide by capability, not by brand. Map every tool to the business function it supports, such as project management, collaboration, monitoring or CRM, and look for categories where several products do overlapping work. TechTarget describes the cost of leaving this alone: higher spend and reduced efficiency, with regular audits and consolidation aligned to business goals as the remedy.
A simple decision rule keeps debates short:
- Retain a tool when it is specialised and nothing else does the job.
- Integrate tools that are complementary and share data cleanly.
- Replace a tool when it is redundant and a lower total cost of ownership exists.
Total cost means more than the licence fee. Count integration work, admin time, training and the hours people lose switching between systems. A cheap tool that needs regular manual exports is rarely cheap.
Migration is where consolidation succeeds or fails. A practitioner guide to reducing tool sprawl recommends mapping real workflows first, tackling the biggest pain points, and migrating in stages with parallel runs. In practice that means a pilot with one team, a parallel run, written cutover criteria and a rollback plan you have actually tested.
The payoff is measurable. In VendorBenchmark's consolidation sample, organisations reduced vendor count by a median 31% and total SaaS spend by a median 24%. Fewer vendors also means fewer renewals to manage and more negotiating weight with the ones you keep. If you are weighing suppliers during this process, our note on checking tenant isolation before buying white label SaaS covers selection criteria worth applying.
Pro Tip: Never retire a tool on a cost argument alone. Ask the daily users what they would lose first, and write their answers into the cutover criteria.
What technical levers cut usage costs, including AI workloads?
Aggregate spend hides where money leaks. Unit economics shows it: cost per query, cost per user and cost per workflow. A monthly total tells you nothing about whether a feature is getting cheaper to run, while a cost per workflow tells you exactly where to engineer savings.
For AI-powered features, start with model right-sizing. Route simple requests to cheaper models and reserve high-capability models for hard problems. Then apply the engineering levers that the FinOps Tokenomics guidance describes:
- Batch processing for work that does not need a real-time answer, which the guidance puts at about 50% savings for batch-eligible workloads.
- Provider-side prompt caching, which can cut the cost of the cached portion of input tokens by 80–90%.
- Model routing, which can reduce average cost per query by 60–80%.
- Semantic or application-level caching, so repeated questions never reach the model twice.
- Retrieval-augmented generation, which sends only relevant passages instead of whole documents, reducing context tokens.
- API key governance and tagging, so every dollar of usage maps to a team and a feature.
According to the FinOps Tokenomics guidance, provider-side prompt caching can cut cached input token costs by 80–90%. That makes caching one of the first levers worth testing on any workload with repeated prompts.
Before buying reserved or committed capacity, model your break-even point. Commitments only save money if your usage stays above the committed level, so base the number on measured baselines rather than forecasts. If you want help applying these levers to real workloads, Sentient Concepts publishes a practical write-up on cutting generative AI inference costs.
BCG's analysis of enterprise software costs frames the same idea at board level: combine commercial measures, demand management and technical optimisation rather than relying on any single lever.
How does FinOps governance keep savings from creeping back?
Savings fade when nobody owns them. The FinOps framework adapted for SaaS offers four domains you can reuse directly: understand cost and usage, quantify business value, optimise cost, and manage the practice. Treat them as a loop, not a one-off project.
Ownership is the heart of it. Under showback, each team sees the software costs attributed to it, without being billed. Under chargeback, those costs move into the team's own budget. Showback is easier to start with, and chargeback works well once your tagging is reliable. Both rely on the owner and cost centre tags you built during discovery.
BCG stresses centralised oversight, transparency and governance to stop costs creeping back. A workable cadence looks like this:
- Instrument spend and usage long enough to establish a true baseline.
- Set each budget above that baseline, with alerts at appropriate thresholds. FinOps Tokenomics guidance describes a more specific approach.
- Hold a monthly review with finance, IT and business owners.
- Flag every renewal 90 days out and decide: keep, shrink or retire.
- Report realised savings to your executive sponsor each quarter.
Executive sponsorship matters because renewals are where discipline breaks. A CFO who expects a usage review before any renewal signature protects the savings you worked to find. Share results in money terms the finance team already uses, and tie each saving to a named owner.
Pro Tip: Make "no renewal without a usage report" a standing finance rule. It costs nothing and quietly prevents most re-sprawl.
Which metrics prove your software cost reduction is working?
Pick a small set of indicators, baseline them, then track them monthly. The core set is discovered spend, waste rate, licence utilisation, vendor count, unit costs, renewal exposure and forecast savings.
| KPI | What it tells you |
|---|---|
| Discovered spend | How much of total software spend is now inventoried |
| Waste rate | Share of budget paid for unused or duplicate capability |
| Licence utilisation | Active seats as a share of purchased seats |
| Vendor count | Progress on consolidation |
| Cost per request, user or workflow | Whether technical levers are working |
| Renewal exposure | Spend coming up for renewal soon |
Instrument long enough before setting targets so your numbers reflect normal behaviour. The FinOps Tokenomics guidance recommends measuring for 30 to 60 days. Then use external benchmarks to keep targets realistic rather than heroic.
VendorBenchmark data shows a median waste rate of 34%, and that effective programmes bring waste down to 8–15%. That range is a sensible ceiling for your own target, and a useful anchor when you present the business case to finance.
For help turning those figures into a case your CFO will accept, our guide on maximising SaaS ROI through subscription strategy is a practical companion.
What tools and integrations make optimisation repeatable?
Spreadsheets get you through the first audit. They do not survive the second. Repeatability needs a small stack: a SaaS management platform for discovery and contract data, SSO and CASB for usage telemetry, billing and expense ingestion for the financial side, and observability for technical consumption.
When you evaluate a platform, test it against these criteria:
- Depth of automatic discovery, including shadow IT.
- API access, so data flows into your own reporting.
- Capture of contract metadata: renewal dates, notice periods and price terms.
- Allocation and reporting by team, cost centre and project.
- Alerting on budget thresholds and upcoming renewals.
- Integration with your finance and identity systems.
Do not forget the fees wrapped around the software itself. Payment processing is one example: PaySec's guide to reducing SaaS payment processing costs covers how interchange and pricing structure affect what you pay.
Validate any tool with a short operational check. Can it show your largest vendors with owner, renewal date and active-seat count in one view? Can it alert an owner well before renewal? If both answers are yes, it will support the monthly discipline described above.
What does a 90-day sprint look like, and how do you sustain it?
A time-boxed programme beats an open-ended initiative because everyone knows when it ends and what done looks like.
- Discovery and baseline. Pull SSO, card and billing feeds, tag every vendor and instrument usage. Acceptance: you can account for the large majority of software spend by vendor and owner.
- Harvest and pilot. Reclaim idle seats, cancel unused add-ons and run one consolidation pilot with parallel running. Acceptance: seats reclaimed are counted, and the pilot shows a measured saving.
- Governance and rollout. Set budgets and alerts, start monthly reviews and write the renewal playbook. Acceptance: a documented governance process with named owners.
Keep roles light. Procurement owns contracts and renewal dates. IT owns discovery, usage data and migrations. Finance owns baselines, budgets and savings reporting. Business owners own the decision to keep or retire what their teams use. A one-page RACI chart is enough.
After the sprint, the monthly review becomes the engine that prevents re-sprawl.
Pro Tip: Publish a short savings scoreboard at the end of each phase. Visible wins keep sponsors engaged and make the next budget conversation easier.
Why we see consolidation as the practical path to savings
Having built a unified platform, we have seen how much time disappears into switching between disconnected tools, re-entering the same data and chasing information that lives in the wrong place. Our experience is that consolidating work into one place can save time, and that is why we favour consolidation over endless line-item haggling. Negotiation trims a price, but consolidation removes the duplicate work as well as the duplicate invoice. Our view is that pay-per-action billing fits this approach best, because cost then follows real usage instead of shelfware.
— Paolo
How we help you consolidate and pay only for what you use
If your audit shows several tools doing the same job, we offer a unified platform covering CRM, project management, sales, marketing, finance and billing. Instead of stacking fixed licences, you pay per action, so costs follow what your team actually does.
- A unified platform in place of several overlapping subscriptions.
- Usage-based billing: for example, an invoice costs 0.03 EUR to create and a campaign send costs 1 EUR per 1,000 sends.
- Hourly support from our team when you need it.
Review the full list of fees on our pricing page and see what a consolidated, pay-per-action setup would cost you.
FAQ
What is a cost reduction program?
A cost reduction program is a structured effort to lower spending without removing the capability the business needs. For software, it usually combines discovery, licence clean-up, consolidation and ongoing governance, as described in the FinOps guidance for SaaS.
What does cost reduction mean in practice for SaaS?
It means paying less for the same or better outcomes. A typical example is removing inactive seats and retiring a duplicate tool. VendorBenchmark reports that organisations in its consolidation sample cut total SaaS spend by a median 24%.
How much SaaS spend is typically wasted?
Waste is common and often unnoticed. VendorBenchmark's data puts the average waste rate at 34% of SaaS budget, with effective programmes bringing it down to 8–15%.
Where should you start to reduce software costs fastest?
Start with a full inventory, then reclaim idle licences, then consolidate overlapping tools. BCG also recommends pairing commercial measures with demand management and technical optimisation, plus central oversight to stop costs creeping back.
Sources
- Taking Control of Enterprise Software Costs | BCG
- SaaS Sprawl Benchmark Data | VendorBenchmark
- Introduction to FinOps for SaaS