🇮🇩 Baca artikel ini dalam Bahasa Indonesia
Executive Summary: The instinct to slash IT budgets during a crisis is understandable — and often wrong. This article lays out a framework for how CFOs should evaluate IT investment during crisis periods, drawing on real patterns from the current pandemic and previous downturns. The companies that emerge strongest from disruption are almost always those that invested strategically in technology while competitors were retreating.
The Budget Meeting That Reveals Everything
Five months into a global pandemic, every CFO I speak with is having the same internal debate. Revenue is uncertain. Cash reserves are under pressure. And the IT department just submitted a request for emergency spending on cloud infrastructure, collaboration tools, and security upgrades they say cannot wait.
The question of IT investment during crisis is not new. I watched the same tension play out in 2008, and before that in the dot-com collapse. What is new is the speed and totality of the disruption. COVID-19 did not give anyone a quarter to plan. It gave them a weekend. And the organizations that had already modernized their technology stack — even partially — found themselves able to pivot. Those that had not were left scrambling to keep basic operations running.
This is the moment that separates strategic CFOs from purely tactical ones. Not because cutting costs is wrong, but because how you cut — and where you choose to invest — defines what your company looks like on the other side.
Why the Default Response Is Dangerous
The typical playbook during a downturn is straightforward: freeze discretionary spending, delay capital projects, reduce headcount. IT budgets, because they are large and often poorly understood by the finance team, tend to be early targets.
I understand the logic. When revenue drops 20-40% in a matter of weeks, as many businesses experienced in March and April, preservation mode is rational. But there is a critical distinction between cutting waste and cutting capability.
A June 2020 report from McKinsey found that companies which invested in technology through the 2008 recession outperformed their peers by 10% in operating profit margins in the years that followed. Gartner’s early pandemic research shows a similar pattern forming — organizations accelerating digital initiatives are already reporting faster recovery trajectories than those in full retreat. [Source: McKinsey Digital, Gartner CIO Survey 2020]
The pattern is consistent: crises compress timelines. What would have been a three-year digital transformation roadmap is now a three-month imperative. The CFO who treats this moment as purely a cost problem is solving the wrong equation.
How to Evaluate IT Investment During Crisis: A Decision Framework
Saying “invest in technology” is not useful advice. The question is where, how much, and with what expected return. Here is the framework I use when advising executive teams on IT investment during crisis periods. It is built around four categories, each requiring a different financial lens.
1. Survival Investments (Non-Negotiable)
These are expenditures required to keep the business operating. Right now, that means:
- Remote work infrastructure — VPN capacity, endpoint security, collaboration platforms. If your employees cannot work, you have no business.
- Cybersecurity hardening — The FBI reported a 300% increase in cyberattacks since the pandemic began. A ransomware incident on top of a revenue crisis is an existential event for many mid-market companies.
- Business continuity systems — Backup, disaster recovery, and failover capabilities that were “nice to have” six months ago are now mission-critical.
Financial lens: These are not optional. Fund them. If you cannot fund them from operating budget, reclassify them as risk mitigation and pull from reserves. The cost of not spending here is measured in business interruption, data loss, and regulatory exposure.
2. Efficiency Investments (High ROI, Short Payback)
These are projects that reduce operating costs or free up capacity within 6-12 months. Examples from engagements I have been involved with this year:
- ERP process automation — Automating manual financial close processes, AP/AR workflows, and reporting. One client reduced their month-end close from 12 days to 5 by implementing automation modules within their existing ERP system, freeing finance staff to focus on cash flow analysis when it mattered most.
- Cloud migration of specific workloads — Not a wholesale “move everything to the cloud” initiative, but targeted migration of workloads where on-premise infrastructure is creating maintenance cost and fragility.
- Integration projects — Connecting disconnected systems to eliminate manual data entry and reconciliation. The number of companies still running critical financial processes on spreadsheets passed between departments via email is staggering.
Financial lens: Build a business case with a 12-month payback threshold. If the project pays for itself within a year through headcount reallocation, error reduction, or cycle time improvement, approve it. These investments actually improve your cost position during the downturn.
3. Strategic Investments (Competitive Positioning)
These are the bets that position you for the recovery. They require more capital, carry more uncertainty, and demand a longer time horizon:
- E-commerce and digital channel buildout — Companies that had digital sales channels in place before March are capturing market share from those that did not. This gap will only widen.
- Data and analytics capabilities — The ability to model scenarios, forecast demand, and make data-driven decisions quickly is worth more during a crisis than during stable times.
- ERP modernization — If you are running an aging, heavily customized ERP system that cannot scale or adapt, the question is not whether to modernize, but whether you can afford to wait another cycle.
Financial lens: Evaluate these on a 24-36 month horizon. Use scenario modeling — what does the competitive landscape look like if you invest versus if you do not? Factor in the cost of delay, which is almost always underestimated.
4. Deferrable Investments (Cut or Delay)
Not everything passes the test. Be honest about what can wait:
- Cosmetic system upgrades with no functional improvement
- “Innovation” projects without a clear business sponsor or measurable outcome
- Large-scale implementations that require extensive on-site activity during a period when your workforce is distributed
- Hardware refresh cycles that can be safely extended 6-12 months
Financial lens: Defer, but do not eliminate from the roadmap. Document what was deferred and why. Set a trigger for re-evaluation — a revenue milestone, a date, or a market condition.
What This Looks Like in Practice
Let me share a scenario drawn from a real engagement, details anonymized. A mid-market manufacturing company — roughly $200M in revenue — entered 2020 with an aging ERP system, minimal cloud adoption, and an IT budget that had been flat for three years. When the pandemic hit, their sales team could not access CRM data from home. Their finance team could not run reports without connecting to an on-premise server. Purchase orders were being routed via fax machines in an office that nobody could enter.
The CFO’s initial response was to freeze all IT spending. Every dollar was to be preserved for payroll and debt service. Reasonable at first glance.
Within six weeks, they were spending more on manual workarounds, emergency vendor contracts, and overtime than the deferred projects would have cost. Their competitors — two of whom had implemented cloud ERP within the past two years — were quoting faster, shipping faster, and winning contracts that had historically been split across the industry.
We worked with their leadership team to reclassify their IT budget into the four categories above. Roughly 30% of the originally frozen budget was redirected into survival and efficiency categories. A targeted cloud ERP migration for their finance and supply chain modules was approved as a strategic investment with an 18-month payback projection. The rest was legitimately deferred.
The result: they stabilized operations within a month and are now on track to have a more capable technology platform than they had before the crisis — at a total cost lower than their original pre-pandemic IT roadmap, because they were forced to prioritize ruthlessly.
The CFO-CIO Conversation That Needs to Happen
Much of the dysfunction I see around IT spending decisions stems from a structural communication gap between the finance and technology functions. The CFO sees line items. The CIO sees capabilities. Neither is wrong, but they are often speaking different languages.
Here is what I recommend for any organization navigating IT investment during crisis conditions:
- Establish a shared taxonomy. Both the CFO and CIO should categorize every IT initiative using a common framework — the four categories above, or something similar. This eliminates the debate about whether something is “strategic” or “discretionary” and forces specificity.
- Require business cases for everything above a threshold. That threshold might be $25K for a mid-market company or $250K for a large enterprise. The business case should include expected cost reduction or revenue impact, payback period, and risk of deferral.
- Conduct a monthly joint review. During a crisis, annual budgeting is fiction. Move to a monthly review cycle where the CFO and CIO jointly assess what is working, what is not, and what needs to be reprioritized. Quarterly is too slow right now.
- Quantify the cost of inaction. For every project you defer, document what it costs to keep operating without it. Manual labor, error rates, customer impact, compliance risk. This is the number that almost never appears in budget discussions, and it is often larger than the investment itself.
Frequently Asked Questions
Should companies increase IT spending during a recession?
Not blindly, no. The answer depends on where you were before the crisis hit. If your technology infrastructure was already modern and well-maintained, you may be in a position to hold steady and make targeted investments. If you were already behind — running outdated systems, relying on manual processes, lacking remote work capability — then selective increases in IT spending are not optional. They are the cost of remaining operational. The key word is selective. Increase spending where the business case is clear and the payback is measurable.
How do you justify IT spending when revenue is declining?
Frame it in terms the board and investors already understand: risk, cost avoidance, and competitive positioning. A cybersecurity investment is risk mitigation — calculate the expected loss from a breach multiplied by the probability. An automation project is cost avoidance — calculate the labor hours and error costs it eliminates. A digital channel investment is revenue protection — model the market share you lose by not having it. Stop presenting IT projects as technology initiatives. Present them as business investments with technology components.
What is the biggest mistake CFOs make with IT budgets during downturns?
Treating IT as a single line item that gets cut by a uniform percentage. A 15% across-the-board IT budget reduction sounds disciplined. In practice, it often means you underfund critical security and infrastructure while still spending on low-priority projects that survived only because they were already in flight. The smarter approach is to zero-base the IT budget during a crisis — evaluate every initiative from scratch, categorize it, and fund based on business impact rather than historical allocation.
How should ERP modernization decisions change during a crisis?
A crisis actually clarifies the ERP decision. If your current system held up — if your finance team could close the books remotely, your supply chain team could reroute orders, your sales team could access what they needed — then a major ERP overhaul can wait. If the system broke down or required extensive manual intervention, you now have a concrete, experience-based case for modernization that did not exist six months ago. Use this moment to document every failure point and every workaround. That documentation becomes the foundation of your business case, and it will be far more compelling to the board than any vendor slide deck.
Looking Past the Crisis
Every downturn ends. The question is what position you will be in when it does.
The data from previous recessions is unambiguous: companies that invest strategically in technology during downturns outperform those that do not. This is not about spending recklessly. It is about recognizing that a crisis reshuffles competitive positions, and technology is one of the primary mechanisms through which that reshuffling happens.
If you are a CFO reading this, the conversation you need to have with your CIO this week is not “how much can we cut?” It is “what must we fund to survive, what should we fund to come out ahead, and what can we honestly defer?” That distinction — applied rigorously and revisited frequently — is the difference between emerging from this crisis stronger or simply emerging from it.
The companies that delayed digital transformation before 2020 are paying for that decision right now. The ones that delay it through 2020 will be paying for it well into the next decade.
