How to Reduce Your IT Spend in 2027: The Complete Guide

IT budgets are not shrinking. Gartner forecasts worldwide IT spending of $7.35 trillion in 2027, up 15% from 2026, and says the next trillion dollars of growth comes from AI infrastructure and AI software. At the same time, memory prices have more than doubled in a year, software vendors keep changing how they package and price, and business units buy SaaS and AI tools without waiting for IT. Organizations that hold a flat budget in that environment must find the money somewhere.

This guide is about doing that without damaging capability. It shows where IT spend is heading, where waste hides, ten levers that work, a worked example and a 90 day plan. We name sources for every statistic and mark illustrations as illustrations.

The short answer

Start by seeing all spend in one place, then reclaim unused licenses, shut idle cloud resources, cap AI tools and renegotiate renewals early with your own usage data. Put controls and a monthly review in place so savings last. The 2027 forecasts say costs rise on their own, so a flat budget needs active management.

Where IT spend is heading in 2027

Gartner’s October 2026 forecast puts 2027 IT spending at $7.35 trillion. Data center systems, driven by AI infrastructure, are forecast to grow 55.5% to $1.37 trillion. Software is forecast to reach $1.68 trillion, up 14.6%. IaaS, listed separately, is forecast to grow 25.7% to $367 billion. Devices grow 8.1% to $916 billion. IT services grow 4.9% to $1.63 trillion and communications services 2.9%.

Worldwide IT spending forecast by segmentUS dollars in billions. Total IT spending is forecast at $6.39 trillion in 2026 and $7.35 trillion in 2027.045090013501800202620278791,366Data center systems292367IaaS1,4641,679Software1,5571,633IT services847916Devices1,3521,391CommunicationsservicesSource: Gartner IT spending forecast, October 2026. Segment figures sum to the totals shown.
Where the growth is: forecast 2027 spending growth by segmentPercent growth over 2026Data center systems55.5%IaaS25.7%Software14.6%Devices8.1%IT services4.9%Communications services2.9%Source: Gartner IT spending forecast, October 2026. Total IT spending growth is 15.0%.

Two things stand out. Growth is concentrated in AI related infrastructure and in software, which is where an enterprise has the least direct control and the most contractual complexity. And Gartner describes a market under affordability pressure: memory related price inflation, which it calls memflation, is expected to persist through 2027 and to suppress demand from end users. For most organizations the practical meaning is that costs rise on their own unless someone manages them.

Where waste hides

Savings come from finding spend that is not producing value. Four places repeat in the research.

Where waste is hidingFour numbers worth checking against your own estate29%of cloud spend isestimated as wasted,the first rise in fiveyears36%of SaaS licenses areunused on average14%of traditional IT spendsits outside the formalCIO budget81%of SaaS spend iscontrolled by businessunits, not ITSource: Flexera 2026 State of the Cloud (750+ respondents); Zylo 2026 SaaS Management Index; Gartner finance practice via CFO Magazine A/NZ(January 2026).
  • Cloud. Flexera’s 2026 State of the Cloud report, a survey of more than 750 cloud decision makers, estimates wasted cloud spend at 29%, the first increase in five years, and links the rise to AI workloads. Flexera also reports that 63% of organizations have FinOps teams, so the practice exists but the waste has not gone away.
  • SaaS. The Zylo 2026 index, covering more than 40 million licenses and $75 billion in spend, finds that 36% of licenses are unused on average, that business units control 81% of SaaS spend and that large enterprises add about 21 applications a month.
  • Spend outside IT. Gartner finance practice analysts estimate that 14% of traditional IT spend happens outside the formal CIO budget, with higher figures in federated organizations. You cannot optimize what you cannot see.
  • AI. New pricing models create new surprises.
AI spend is the newest leakFindings on AI software and AI pricing78%of IT leaders hadunexpected charges fromconsumption or AIpricing in 12 months59%say wasted AI spendrose year over year29%measure the value oftheir AI software61%were forced to cutprojects because ofthose chargesSource: Zylo 2026 SaaS Management Index (218 IT leaders surveyed); Flexera 2026 State of ITAM Report (512 respondents).

The AI figures show why governance has to start now. In the Zylo data, 78% of IT leaders reported unexpected charges from consumption or AI pricing in the past 12 months and 61% were forced to cut projects as a result. Flexera found only 29% of organizations measure the value of AI software, so most cannot tell whether the spend is earning its cost.

A framework that works: visibility, control, utilization, optimization

Gartner’s finance practice describes four tactics for regaining control of IT spending: visibility, control, utilization and optimization. The order matters. Without visibility you act on guesses. Without control, savings leak back through new purchases. Without utilization data, you cannot tell what to cut. Optimization is the action that follows.

Four tactics to regain control of IT spendGartner finance practice guidance, with the Desqcon view of what each means in practice1VisibilityOne view of what isbought, by whom, fromwhom, for what and untilwhen. Tags, vendor listsand contract data.2ControlApproval paths anddelegation limits thatmatch risk, so new spendpasses a check beforecommitment.3UtilizationMeasure real use oflicenses, cloudresources, devices andservices against what ispaid for.4OptimizationAct on the findings:reclaim, rightsize,consolidate andrenegotiate, then keepthe savings.Source: Gartner (Vaughan D Archer), Four Tactics to Regain Control Over IT Spending in 2026, CFO Magazine A/NZ, January 16, 2026. Descriptionsparaphrased.

Gartner suggests concrete first steps over 20 to 60 days: define software tags and vendor lists, review delegation frameworks and renegotiate license pricing. It cites example delegation approval thresholds of $10,000, $100,000 and $1 million for small, midsize and large enterprises. Those figures are examples, so set limits that reflect your own risk and size.

Ten levers to reduce IT spend

Ten levers compared: effort against impactA Desqcon judgment for a typical mid size or large enterprise. Your own numbers should replace it.Effort and time to deliverLowHighSavings impactHighLowDo firstReclaim unused licensesRenegotiate renewalsCloud rightsizing and commitmentsAI spend controlsConsolidate overlapping toolsHardware lifecycleSupplier and services rebidProcess automationSource: Desqcon Consulting. Single view of spend and ITSM problem management are enablers and are not plotted.

1. Build a single view of spend

Combine contract data, purchase orders, card and expense data, cloud billing, single sign on logs and HR records into one list of what you pay for, who owns it and when it renews. This is the base for every other lever. It is the same discipline as IT asset management, and our guides to ITAM and software asset management cover how to build it.

2. Reclaim unused licenses and subscriptions

With 36% of SaaS licenses unused on average, reclaiming is usually the fastest saving. Pull usage data, set an inactivity rule such as no login in 60 or 90 days, notify owners, reclaim and reassign. In the Flexera ITAM survey, 43% say license reuse produces significant savings. The saving is real only if you reduce the quantity at renewal, so link reclaim to the renewal calendar.

3. Rightsize editions and tiers

Many users hold the most expensive edition because it was the default. Compare feature use to edition and move users who do not need premium features to lower tiers. Check contract terms first, since mid term downgrades are often restricted.

4. Consolidate overlapping tools

Large enterprises add about 21 applications a month on average, so overlap is normal: several collaboration tools, several project tools, several note taking tools. Choose a standard for each category, set a retirement date for the others and offer migration help. Consolidation also improves your negotiating position with the remaining vendor.

5. Renegotiate and time renewals

Review every contract above a set value six to nine months before renewal. Use your own usage data to reduce quantity, change terms, reset price increases and remove auto renewal. Flexera reports that negotiating SaaS contract terms rose 14 percentage points as a SAM activity year over year, which shows more teams are doing this. Cases like VMware show why preparation matters: in a January 2026 survey of 302 IT decision makers commissioned by CloudBolt, 59% saw price increases above 25% and 14% saw prices double, and 86% are reducing their use. See our SAM guide for the full picture.

6. Rightsize cloud and manage commitments

Shut idle resources, rightsize oversized instances, schedule non production environments to switch off, move storage to the right tier and match commitments to stable demand. Flexera’s State of the Cloud found 49% of organizations use unit economics, up from 40%, and that value to business units has risen as a FinOps measure. Tie cloud cost to the product or service that causes it, so teams see their own numbers.

7. Put guardrails around AI spend

Require approval for new AI tools and agents, set spend caps and alerts for consumption pricing, review terms for overage and data use, and measure value against a stated use case. Record each AI tool as an asset with an owner. This is the cheapest moment to control cost: before the first invoice.

8. Run hardware by lifecycle evidence

With memory prices up sharply and device spend forecast to rise 8.1% in 2027, a fixed refresh cycle is more expensive than it used to be. Use age, warranty, failure rate and utilization data to extend the life of devices that still meet the need, replace only where the evidence says so and reuse or repair where possible. This follows from the forecasts and is our recommendation, not a Gartner conclusion.

9. Rebid services and suppliers

IT services remain the second largest segment at $1.63 trillion forecast for 2027. Review scope, service levels and rate cards for managed services, consulting and support contracts. Check that you are paying for services you actually receive, consolidate suppliers where overlap is high and use competitive tension at renewal. This lever takes longer but can be large.

10. Remove operational waste through better service management

Repeat incidents, manual handoffs and low quality knowledge cost time and money. Problem management that removes recurring causes, knowledge that resolves issues once and measured automation of routine requests reduce effort without cutting service. See our ITSM guide for 2027 for how to sequence the work. Be careful with savings claims from automation: measure results in your own environment before you bank them.

The ten levers at a glance

LeverFirst actionMain ownerTypical timing
Single view of spendMerge contract, card, cloud and identity data into one listITAM and financeWeeks
Reclaim unused licensesApply an inactivity rule and notify ownersSAM and business ownersWeeks, savings at renewal
Rightsize editionsCompare feature use to edition heldSAM and procurementMonths, at renewal
Consolidate toolsPick a standard per category and set retirement datesEnterprise architecture and ITMonths
Renegotiate renewalsReview contracts six to nine months ahead with usage dataProcurement and SAMMonths, on renewal dates
Cloud rightsizing and commitmentsRemove idle resources, rightsize, align commitments to steady demandFinOps and engineeringWeeks to months
AI spend guardrailsApproval, caps, alerts and owner for every AI toolIT, security and financeWeeks
Hardware lifecycleUse age, warranty and failure data to set refresh by evidenceHAM and endpoint teamsMonths
Services and supplier rebidReview scope, service levels and rate cards, then test the marketProcurement and IT leadershipMonths
Operational wasteRemove repeat incidents and automate routine requests with measurementService managementMonths

A worked example

Suppose an organization spends $2 million a year on seat based SaaS. The Zylo average suggests that 36% of licenses may be unused, which would mean about $720,000 of spend on unused seats. Not all of that can be recovered. Some seats are needed for seasonal work, some contracts have minimums and some savings only arrive at renewal. If half is recoverable at renewal, the saving is about $360,000 a year.

A worked example: from seat spend to recoverable savingsIllustrative arithmetic with stated assumptions. Not a benchmark for your organization.Annual spend on seat based SaaS (assumption)$2.00MUnused share at 36% (Zylo average)$0.72MRecoverable at renewal, half of unused(assumption)$0.36MSource: Illustrative. The 36% is the Zylo 2026 average. The spend and the recoverable share are assumptions that your data should replace.

The method is the point. Savings equal spend, multiplied by the unused share, multiplied by the share you can actually recover. Replace each number with your own data, and report both identified and realized savings, because they are different things.

A 90 day plan

A 90 day plan to start reducing IT spendGartner suggests first steps can land in 20 to 60 days1Days 1 to 30: see itBuild one list of vendors,contracts, subscriptionsand owners. Tag spend.Find unowned items.2Days 31 to 60: quickwinsReclaim unused licenses,shut idle cloud resources,stop duplicatesubscriptions and cap AItools.3Days 61 to 90:contractsRank renewals by date andvalue. Open negotiationsearly and set approvallimits.4Then: keep itMonthly review, savingsledger, renewal calendarand a front door for newpurchases.Source: Desqcon Consulting, informed by Gartner guidance published in CFO Magazine, January 2026.

Days 1 to 30: see it

Create one list of vendors, contracts, subscriptions and owners from finance, procurement, cloud billing and identity data. Tag spend by service, owner and cost center. Mark anything without an owner. Rank the top 20 vendors by spend and by renewal date.

Days 31 to 60: quick wins

Reclaim unused licenses, shut idle cloud resources, cancel duplicate subscriptions and put caps on AI tools. These actions rarely need negotiation and show results quickly. Record each saving in a ledger with the date it takes effect.

Days 61 to 90: contracts and control

Open renewal discussions for the largest contracts using your usage data. Set approval thresholds and a front door for new software, SaaS, cloud and AI purchases. Agree who reviews savings monthly.

Then: keep the savings

Savings fade without a process. Run a monthly spend review, a quarterly reconciliation of licenses and a rolling six month renewal calendar. Track savings as realized, avoided and identified, and do not count the same saving twice.

Governance that keeps savings in place

ControlWhat it does
Single list of vendors and contractsShows what exists and when it renews
Spend tags and ownersLinks cost to services and people who can decide
Approval thresholdsStops large commitments passing without review
Front door for new software, SaaS and AIChecks existing entitlements, security and cost before purchase
Renewal calendar six to nine months aheadGives time to reduce, renegotiate or replace
Savings ledgerSeparates identified, realized and avoided savings
Monthly review with financeKeeps ownership and momentum

What not to cut

Cost programs fail when they cut capability that protects the business. Be cautious with security tooling, backup and recovery, monitoring, patching and the skills that run critical services. Cutting support or monitoring to hit a number often increases incident cost later. Ask of every proposed cut: what does this protect, and what does failure cost?

Common mistakes to avoid

  • Cutting before seeing. Without a single view, savings are guesses.
  • Counting identified savings as realized. A saving only exists once the invoice or the commitment changes.
  • Reclaiming licenses and renewing at the old quantity. Link every reclaim to the renewal.
  • Ignoring AI and consumption pricing. The next surprise bill is more likely there than in a seat license.
  • Running one time projects. Waste returns when buying is uncontrolled.
  • Treating it as only an IT task. Finance, procurement, legal and business owners all hold part of the answer.

Frequently asked questions

Where can we save the most on IT spend?

It varies by organization, but the usual order is unused SaaS and software licenses, idle or oversized cloud resources, overlapping tools, large contract renewals and AI tool sprawl. A single view of spend shows where yours is.

How much can we realistically save?

We avoid quoting a percentage because results depend on your starting point. Use the formula in the worked example: spend, multiplied by the unused share, multiplied by the share you can recover. Replace each number with your own data.

What is the fastest saving?

Reclaiming unused licenses and shutting idle cloud resources. Both need little negotiation, but the saving is only real if you reduce the quantity at renewal or the resource cost stops.

How do we control AI costs?

Require approval for AI tools, set caps and alerts for usage pricing, record each tool with an owner and a use case and measure value. Only 29% of organizations measure AI software value today.

Who should own IT cost reduction?

Share it. IT or ITAM provides the data, procurement owns contracts, finance tracks savings and business owners approve changes. A single accountable leader keeps the work moving.

How do we stop costs from creeping back?

Keep the controls: approval thresholds, a front door for purchases, a renewal calendar and a monthly review with finance.

Turn the plan into numbers for your organization

Use our toolkits to build the baseline, and our assessments to find where your process and tools hold you back. We help teams find savings and keep them.

Browse the toolkitsSoftware license position workbookSAM tool assessment

Sources and notes

Leave Comment

Your email address will not be published. Required fields are marked *

Are you human? Please solve:Captcha