IT Cost Cutting in a Downturn: A Technology Cost Playbook for Tough Trading Conditions
In a downturn, cut technology costs in waves: stop waste and discretionary spend immediately, restructure contracts and infrastructure over the following months, and protect the security and core systems the business depends on. The goal is a leaner cost base that can scale back up, not a hollowed-out IT function.
Written and reviewed by The Technology Office ยท Independent technology advisory
Key takeaways
- Sequence the cuts: immediate waste removal first, then contract and infrastructure restructuring, then structural changes to systems and operating model.
- Protect the non-negotiables: cyber security, backups, core operational systems and anything that generates or collects revenue.
- Every project should be re-tested. Pause or stop those without a near-term return, but finish ones that are close to delivering savings.
- Aim for variable rather than fixed costs where possible, so technology spend can flex with revenue as conditions change.
The short answer
In tough trading conditions, cut technology costs in deliberate waves: remove waste and freeze discretionary spend immediately, restructure contracts and infrastructure over the following months, and protect cyber security, backups and revenue-critical systems throughout. The aim is a leaner, more flexible cost base that can scale back up when conditions improve. Indiscriminate cuts to maintenance and security tend to create larger costs later.
Why technology needs its own downturn plan
When revenue falls, technology is a tempting target because its costs are visible and many look discretionary. But technology also runs payroll, invoicing, customer service and the systems that collect cash. Cut the wrong thing and the business loses the very capability it needs to trade through difficulty.
A good downturn plan separates spend into three groups: waste that can go now, spend that can be restructured, and capability that must be protected. Then it sequences action so savings arrive early without creating new risks.
The three-wave playbook
| Wave | Timeframe | Focus | Typical actions |
|---|---|---|---|
| 1. Stop the bleeding | First 30 days | Waste and discretionary spend | Remove unused licences, switch off idle cloud, freeze new purchases, pause non-critical projects |
| 2. Restructure | 1 to 6 months | Contracts and infrastructure | Renegotiate renewals, consolidate tools, right-size cloud and managed services, review telco |
| 3. Reshape | 6 to 18 months | Systems and operating model | Retire duplicate systems, automate manual work, shift fixed costs to variable, revisit sourcing |
Wave 1: Stop the bleeding
The first month is about quick, low-risk savings and control.
- Freeze new technology purchases above a modest threshold without executive approval, including department-bought SaaS.
- Reclaim unused licences from leavers, inactive users and over-specified plans. Usage reports in each admin console make this quick.
- Switch off idle cloud resources and schedule non-production environments to run only during business hours.
- Cancel forgotten services, such as old phone lines, data SIMs and duplicate internet connections.
- Pause discretionary projects that have not yet started or have no near-term return.
- Tighten approval of out-of-scope managed service work.
None of these should affect day-to-day operations, which is why they come first.
Wave 2: Restructure contracts and infrastructure
The next layer of savings depends on contract dates and some technical work.
- Build a renewal calendar for every material contract and prepare for each renewal with usage evidence and alternatives.
- Approach key suppliers early. Many vendors would rather adjust terms, extend payment arrangements or reduce volumes than lose a customer. Ask before you are forced to.
- Consolidate overlapping tools so you pay for one platform instead of three.
- Right-size cloud and only then consider commitment discounts for workloads that will remain stable.
- Review managed services scope, removing duplicated security tools and services you no longer need.
- Re-examine hardware refresh cycles. Extending the life of devices that are still supported and secure can defer capital spend, but do not keep running unsupported operating systems.
Wave 3: Reshape for a leaner future
Structural savings take longer but last.
- Retire duplicate or legacy systems, particularly after acquisitions or restructures.
- Automate repetitive work to reduce overtime and contractor reliance; our guide to cutting costs without cutting staff covers how.
- Shift fixed to variable costs so spend flexes with activity, such as per-user services that scale down with headcount.
- Rebuild the budget from zero to remove legacy spend permanently, using zero-based IT budgeting.
- Revisit the sourcing model, deciding which capabilities to keep in-house, outsource or share.
What you must protect
Some spending looks optional until it is needed. Protect these:
- Cyber security controls, including multi-factor authentication, endpoint protection, patching and monitoring. Criminal activity does not pause during downturns, and the Australian Cyber Security Centre's Essential Eight remains a sensible baseline.
- Backups and recovery, tested regularly. Losing data when cash is tight can be fatal.
- Revenue and cash systems, such as e-commerce, billing, payment and customer platforms.
- Compliance obligations, including privacy, record retention and any regulator-specific requirements.
- Key technical knowledge. Losing the one person who understands a critical system creates risk that is expensive to fix.
False economies to avoid
| Tempting cut | Why it backfires |
|---|---|
| Cancelling security tools across the board | Increases the likelihood and cost of an incident when the business can least afford it |
| Stopping all maintenance and patching | Builds technical debt and vulnerabilities that cost more to fix later |
| Abandoning a project that is nearly finished | Writes off the investment just before benefits arrive |
| Cutting the only senior technology role | Leaves suppliers unmanaged and decisions unmade |
| Locking into long contracts for a discount | Removes flexibility if conditions worsen further |
Governance during a downturn
Set up a short weekly or fortnightly cost review with finance and technology leadership. Track savings against a target by cost line, distinguish one-off from recurring savings, and record risks accepted. Boards and lenders will want to see that cuts are controlled and that critical risks are understood. If the situation is acute, interim leadership or IT crisis management support can stabilise things quickly.
How The Technology Office handles downturn cost reduction
The Technology Office has the executive technology experience to move quickly when trading conditions turn. We identify waste in the first weeks, negotiate with suppliers on your behalf, and build a sequenced plan where every saving is tied to a specific cost line and every risk is visible. Because we are independent and vendor-neutral, with no resale margins, our recommendations are driven solely by what keeps your business lean and resilient.
We protect security, backups and revenue-critical systems as a matter of principle, and we work with businesses of any size and industry across Australia, through IT cost optimisation engagements or interim CIO leadership when a firm hand is needed.
Frequently asked questions
What IT costs should be cut first in a downturn?
Start with waste that has no business impact: unused licences, idle cloud resources, forgotten telecommunications services and duplicate tools. Then pause discretionary projects and new purchases before considering anything that affects service levels.
Should we cut cyber security spending to save money?
Generally no. Cyber criminals do not ease off during downturns, and an incident is far more expensive when cash is tight. Review security tools for duplication and right-size them, but keep the controls that protect your critical systems and data.
Should IT projects be cancelled during a downturn?
Re-test every project rather than cancelling all of them. Stop projects with no near-term return, pause those that can safely wait, and accelerate those that will reduce costs or protect revenue soon.
How quickly can IT costs be reduced?
Some savings, such as removing unused licences and switching off idle resources, can be made within weeks. Contract-related savings depend on renewal and notice dates, and structural changes such as system consolidation take longer.
Is it worth bringing in outside help to cut IT costs?
It can be, particularly if there is no senior technology leader in-house or the internal team is stretched. An independent adviser can identify savings quickly and negotiate with suppliers without the conflicts that come with resale arrangements.
Mentioned services
These service and regional NSW pages expand on the topics covered in this article.
Need help applying this?
Bring in senior technology leadership without the full-time overhead.
The Technology Office works with Sydney and regional NSW businesses on embedded CIO support, Head of IT leadership, governance, vendor management, cost optimisation, crisis stabilisation, and no-cost technology reviews as a lighter first step.