IT budgets contain more waste than the teams managing them can see, and the SaaS management tools and processes for finding that waste have not kept pace with how fast technology spending has changed. Fragmented invoices, unused licences, and unmonitored cloud consumption accumulate quietly, not because anyone decided to tolerate them, but because the tools and processes for finding them have not kept pace with how fast technology spending has changed.
IT spend optimisation is the continuous process of understanding what every technology expenditure is actually producing, and adjusting it where the return does not justify the cost. The goal is not to cut the IT budget. It is to ensure the budget reflects current usage, current needs, and current priorities rather than historical decisions that nobody has reviewed. This guide provides a detailed look at the frameworks, the necessary tools, and the best practices required to master this critical function.
Gartner forecasts worldwide IT spending will reach $6.15 trillion in 2026 - with software growing at 14.7% year-on-year and GenAI features now embedded across the majority of enterprise software products. The scale of the budget is growing. The visibility into what it is actually producing is not keeping pace.
Frameworks: Building the Blueprint for Value
Effective IT spend optimisation cannot be achieved through sporadic cost-cutting exercises; it requires a structured, cultural approach. Two frameworks give structure to what would otherwise be an ad hoc cost-cutting exercise.
1. FinOps (Cloud Financial Operations)
FinOps is arguably the most crucial modern framework, specifically designed to address the unique, variable, and often opaque nature of public cloud spending. It is a cultural practice that emphasises collaboration between Engineering, Finance, and Business teams to ensure the entire organisation owns its usage and costs.
FinOps is the practice of treating cloud spend as a shared responsibility; engineering, finance, and business teams collectively accountable for what gets provisioned and what it costs. It operates across three core phases:
- Inform: This phase focuses on visibility and allocation. Engineers need tools to see the cost implications of their architectural decisions in real-time. This includes accurately tagging every resource so costs can be precisely allocated back to the specific business unit, team, or application responsible.
- Optimise: Once costs are understood, this phase leverages techniques like rightsizing (ensuring resources aren't over-provisioned), commitment discounts (purchasing Reserved Instances or Savings Plans for predictable workloads), and usage elimination (shutting down non-production resources after hours).
- Operate: This is the continuous governance loop. It ensures cost efficiency becomes a maintained state, using automated alerts and budget monitoring to prevent "cost drift" and continuously refine best practices.
The scope of FinOps is expanding beyond cloud. The FinOps Foundation's State of FinOps 2026 report found that 90% of FinOps teams now manage SaaS spend alongside cloud infrastructure, up from 65% the previous year, reflecting the reality that software cost management and cloud cost management have become the same discipline.
2. Technology Business Management (TBM)
While FinOps is focused on the how of cloud spending, TBM is focused on the why and what of all IT spending. TBM provides a standardised model for categorizing IT costs (across people, technology, vendors, and business applications) so that IT leaders can communicate the value of technology in clear, business-centric terms.
TBM transforms IT's communication from "We spent $10M on servers" to "The cost of delivering our Customer Relationship Management service was $2 per customer, which is 15% lower than the industry average." By mapping spending to discrete business services, TBM justifies strategic investments (like AI platforms) while highlighting areas where maintenance costs are disproportionately high compared to business impact.
Essential Tools for Spend Optimisation: Taming the Sprawl
The complexity of modern IT, multi-cloud infrastructure alongside a vast portfolio of SaaS subscriptions, makes manual cost management impossible. Specialised tools are the bedrock of effective optimisation.
1. Cloud Cost Management Platforms (CCMPs)
These platforms are the central clearinghouse for multi-cloud spend. They ingest detailed billing data from hyperscalers (AWS, Azure, GCP) and provide crucial capabilities:
- Cost Allocation: Automatically applying tagging rules to attribute costs accurately to business units for true chargeback.
- Anomaly Detection: Using machine learning to flag sudden, unexplained spikes in spending - often signaling misconfigurations or runaway processes.
- Commitment Management: Dynamically analyzing usage patterns and advising on the most financially advantageous time and quantity to purchase Reserved Instances or Savings Plans.
2. SaaS Management Platforms (SMPs)
The rise of decentralised, departmental SaaS purchasing has led to rampant waste. SMPs address the SaaS visibility problem directly.
- Discovery and Audit: SMPs connect to financial systems (invoices, expense reports) and SSO logs (Okta, Azure AD) to provide a complete, verified inventory of all applications in use, even those acquired through "Shadow IT."
Usage Rightsizing: They track actual login activity and feature usage to identify underutilised or abandoned licenses (shelfware), allowing IT to safely reclaim and de-provision licenses for immediate savings.
What Montro brings to IT Spend Optimisation |
The SaaS management tool tracking licence waste cannot identify the AI features activating inside those licences. Similarly, the AI governance programme tracking regulatory exposure cannot see the licence costs attached to those tools. Both programmes are working from an incomplete picture of the same environment, and both are performing separate discovery exercises to close a gap that is, at its core, the same problem. Montro's discovery output serves both simultaneously. The inventory that identifies an unauthorised AI tool also identifies the licence attached to it, the renewal date, the consumption charges accumulating against it, and whether anyone in the organisation is actually using it. The AI governance and IT spend programme do not need two separate inventories. They need a single inventory that is complete enough to serve both and kept current continuously rather than refreshed quarterly when the audit pressure builds. |
3. IT Asset Management (ITAM) Software
While CCMPs and SMPs focus on recurring operational expenses, ITAM manages the lifecycle of physical and perpetual assets, which is crucial for hybrid IT optimisation. ITAM tracks the purchase, deployment, maintenance, and retirement of hardware and on-premises software. By maintaining an accurate software asset management record, ITAM informs critical optimisation decisions, such as calculating the true Total Cost of Ownership (TCO) for a service before deciding to keep it on-premises or migrate it to the cloud.
Best Practices: Driving Value Through Disciplined Action
Optimisation must be a continuous, systemic effort, not a panicked annual budget cut.
1. Shift Left on Cost: The Architectural Imperative
The most impactful cost savings occur during the design phase. It is dramatically cheaper to design a cost-efficient architecture on paper than to retrofit an expensive, running application. This Shift Left practice means:
- Cost Visibility in Dev: Providing cost projections before resources are provisioned.
- Training Engineers: Embedding cost-optimisation training into developer onboarding, empowering them to choose serverless functions over persistent virtual machines when appropriate.
2. Automate Non-Production Shutdowns
Non-production environments (Development, Testing, Quality Assurance) are often provisioned for the cloud's maximum 24/7 capacity but are only needed 40-50 hours a week. A simple best practice is to automate the scheduling of shutdowns for these resources during nights and weekends. This single action can eliminate 60% of compute time costs for non-critical workloads.
The scale of the opportunity is significant. The Harness FinOps in Focus 2025 report estimates that 21% of enterprise cloud infrastructure spend; approximately $44.5 billion globally in 2025, is wasted on underutilised resources, driven primarily by the disconnect between engineering teams making provisioning decisions and finance teams tracking the cost.
3. Implement Data Tiering and Deletion Policies
Data storage often becomes a massive, passive cost sink. The truth is, not all data requires instant, high-performance access (hot storage).
- Tiering: Implement policies that automatically move data to progressively colder, less expensive storage tiers (e.g., AWS Glacier, Azure Archive) after a defined period of inactivity (e.g., 90 days).
- Deletion: Strictly enforce data retention policies to ensure old, unused snapshots, logs, and backups that are no longer legally required are systematically deleted.
4. Embrace Strategic SaaS Consolidation
Address the phenomenon of SaaS Redundancy. For example, two different departments may use two different tools for internal communications or survey collection. By consolidating onto one platform, the organisation reduces the number of vendors to manage, simplifies integration architecture, and unlocks significant volume discounts and better service contracts. This strategic consolidation replaces fragmented costs with integrated value.
5. Centralise Governance, Decentralise Execution
The Cloud Center of Excellence (CCoE) or FinOps team should set the rules, define the budget allocation model, and select the tools. However, the authority and responsibility for turning resources off, rightsizing VMs, and choosing cost-effective services must be given to the engineers and product owners running those services. They have the deepest operational knowledge and are best positioned to make granular optimisation decisions in real-time.
IT spend optimisation is not a one-time project. The environment changes too fast; new cloud services, new SaaS inventory additions, AI features activating inside existing subscriptions, consumption charges scaling with usage nobody budgeted. The organisations that control their IT spend are the ones that treat visibility as infrastructure: continuous, automated, and connected to the decisions that affect cost.
Frequently Asked Questions
What is the difference between FinOps and traditional IT budgeting?
Traditional IT budgeting is a planning exercise, you allocate a fixed amount at the start of the year and track spend against it. FinOps is an operational practice built for the reality that cloud costs are variable, continuous, and tied to decisions made by engineers in real time rather than finance teams annually. The practical difference is accountability: in traditional budgeting, IT finance owns the numbers. In FinOps, the engineering teams making architectural decisions are directly accountable for the cost implications of those decisions, supported by tooling that makes those costs visible before resources are provisioned rather than after the invoice arrives.
How do you identify which SaaS licences are genuinely unused versus legitimately assigned?
Usage data is the only reliable signal, not licence assignment. A licence assigned to an active employee who has not logged in for 45 days is unused in practice even if it is not unused on paper. The standard threshold most SaaS management programmes apply is 30 days of inactivity as the trigger for a reclamation review. The review should distinguish between genuinely abandoned licences, seasonal users who will return, and employees on leave, each warrants a different response. Without that distinction, reclamation exercises cancel licences that generate a support ticket the following week when the employee returns.
At what point does a FinOps programme justify dedicated headcount?
In practice, firms start justifying dedicated FinOps ownership once cloud spend is large enough that quarterly optimisation exercises no longer keep up with usage growth. For a firm spending £10M annually on cloud infrastructure, an estimated 21% waste rate suggests approximately £2.1M in potentially recoverable spend. A FinOps programme costing £200K–£400K per year in tooling and headcount produces a return that clears most internal investment thresholds in the first year. For firms spending under £2M annually on cloud, manual review cycles are typically more cost-effective than dedicated platforms.
How does SaaS consolidation reduce costs without disrupting operations?
Consolidation reduces costs through three mechanisms, eliminating duplicate capability the organisation is paying for twice, unlocking volume discounts from vendors who price on seat count, and reducing the operational overhead of managing vendor relationships and renewal cycles across a larger portfolio. The consolidations that fail prioritise cost reduction over workflow continuity. The ones that succeed identify the tool with stronger adoption and migrate users to it with a structured transition plan rather than a hard cutover, giving teams time to adapt rather than discovering on day one that the tool they relied on no longer exists.
