Most IT budgets do not fail because executives are unwilling to invest.
They fail because the spend is framed as technical cost instead of business value.
Mid-sized companies will approve sales investments. They will approve expansion. They will approve marketing. In fact, one survey found that 53% of SMBs allocate 10% or more of revenue to marketing. Why? Because leaders can see the growth story.
Then the IT budget lands on the table, and suddenly every line item feels suspect.
That tells you something important. Executives are not resisting investment. They are resisting unclear investment logic.
Most IT budgets fail because they are presented as technical spending instead of business investment.
At Narrative Group, we use a Financials First approach to help leadership teams evaluate technology the same way they evaluate any other investment: based on growth, efficiency, risk reduction, and EBITDA protection. The goal is not to spend more on IT. It is to make better decisions about where technology investment should create measurable business return.
I have spent more than 20 years leading technology and transformation in large enterprises like Shoppers Drug Mart and Loblaw. I founded Narrative Group because I wanted mid-sized companies to benefit from the same level of executive thinking, without enterprise-sized waste. The pattern is remarkably consistent.
The budget usually fails before anyone starts debating the number.
The Budget Goes Wrong at the Beginning
The first question I ask is simple.
How does the business actually make money?
If that is not clear, the IT budget has no real foundation.
Every business exists to create value. So if you want to talk about technology investment, start there. Start with the value chain. Start with where revenue is created, where friction is slowing performance, where labor is absorbing cost, and where process or systems are limiting scale.
This is why I use a Financials First approach. I want to understand how the business creates value. I want to know where the money comes from, where the costs are building up, and where the operation is losing leverage. Then I want to map how people, process, and technology work together across that chain.
When you do that, patterns show up quickly. You see where the technical architecture is working against the value chain. You see where manual effort is hiding. You see where the company is spending money without getting enough operational return.
At Loblaw, I helped introduce an IT strategy, roadmap, and governance model that aligned millions in capital spend to the overall enterprise strategy. That was a much larger business, but the principle is exactly the same in the mid-sized. Follow the money first. Then decide what technology deserves investment.
When a budget starts with tools, renewals, and vendor pitches, it is already in trouble. A CFO is not buying switches. A COO is not buying licenses. A CEO is not buying cloud for the sake of cloud. They are evaluating whether the spend will improve productivity, reduce operational drag, lower risk, or support growth.
That is the real budgeting conversation.
Mid-Sized Companies Feel This Pain Faster
Mid-sized companies often face the hardest version of this problem.
They are large enough to have real complexity, growing cybersecurity exposure, and operational dependencies across multiple systems. But they are often not large enough to have deep strategic IT leadership shaping investment decisions across the business.
That creates a familiar pattern. The owner or CEO is close to the business. The CFO has real skin in the game. The COO needs the operation to keep moving. Meanwhile, the head of IT is often buried in tickets, vendor calls, cyber concerns, and tactical firefighting.
That is not a strong setup for strategic budgeting.
Many of these businesses are also only half modern. A Flint Global report shows that 40% of SMEs in the EU report a low level of digitalization, and another 27% say their level is very low. The data is European, but the pattern is familiar in North America too. You see a few cloud tools, a few spreadsheets, a few manual workarounds, and a lot of hope.
Tool sprawl makes it worse. ZipDo data suggests that 64% of mid-sized companies use at least some cloud-based software and 40% use five or more cloud tools. So the spend is already there. The architecture often is not. The governance often is not. The budgeting logic usually is not.
Security shows the same problem. Some mid-sized company data suggests the average small business spends only $1,200 per year on cybersecurity software. That may buy a tool. It does not buy resilience. Resilience comes from controls, process, testing, recovery, and accountability.
This is why mid-sized IT budgets often feel chaotic. The business already has complexity. It just has not named it properly.
Where the Budget Goes Off the Rails
IT talks in technical language
This is one of the biggest reasons budgets fail.
IT walks into the room talking about infrastructure refreshes, backups, endpoint protection, licenses, architecture, and integrations. The executive team hears overhead.
They are thinking about a different set of questions.
What risk does this remove?
What labor does this reduce?
What customer pain does this fix?
What growth does this unlock?
If you want budget approval, you need to speak their language.
When I go into a business, I spend a lot of time listening. I want people to show me the day in the life. Where does the process break? Where does the workaround start? Where is the frustration?
Usually it comes back to the same things. Role definition is fuzzy. Or the technology is not doing what the company is asking it to do.
One client gave us a very simple example. They had six offices. When people moved from one office to another, they could not reliably connect to the network. Their meeting rooms barely worked. Every request for help seemed to get blocked by security.
Now we have a real business issue. Lost time. Frustration. Lower productivity. Declining confidence in IT.
That is a business case.
At Narrative Group, we assessed the environment, replaced core switches and network gear, refreshed outdated servers, improved the meeting room experience, and made it clear how those rooms were supposed to work. Over time, the environment stabilized.
That may sound basic. It matters.
Talk is cheap. Actions speak volumes. Credibility matters. IT should be an enabler, not a blocker.
Cost cutting moves the expense into labor
A lot of bad budgeting starts with a false saving.
A company cuts enterprise software licenses because the number looks large on a spreadsheet. For a quarter or two, it feels smart. Then the manual work starts piling up. People compensate with spreadsheets, email chains, duplicate entry, and side systems.
The work still has to happen. It just happens more slowly and more expensively.
If you favor labor over the cost of enablement, the most expensive line in your P&L will eventually become labor.
Early-stage companies can sometimes get away with minimal enablement because a few strong people hold everything together. But as the business grows, quality and consistency begin to break. If you want to scale cleanly, you need standardization. You need automation. You need people who are empowered, not buried.
I have seen companies avoid licensing cost by hanging onto older tools that looked cheaper in the moment. Later, when broader upgrades were required, those earlier decisions returned as complexity, rework, and hidden cost.
That is what weak budgeting often misses.
The right technology investment changes the labor curve in a positive way. The business grows, but headcount does not have to grow at the same pace.
We helped Canada’s largest provider of equipment for people with physical disabilities move to a predictable evergreen IT model. Service quality improved. Spend became more predictable. IT cost moved from 3.5% of revenue to 2% of revenue.
That is what happens when the budget is built around business outcomes instead of short-term cuts.
Custom complexity creates drag
Another budget killer is the belief that custom software automatically creates advantage.
Usually it creates complexity.
Leaders need to ask a harder question: what actually makes the business distinctive?
If the answer is service, expertise, relationships, execution, or delivery model, then that uniqueness probably does not live inside a fragile custom workflow no one else can support.
I am a big believer in vanilla software. I want companies current. Mainstream, not leading edge and certainly not bleeding edge. Standard software comes with security, scale, robustness, and performance built in.
That matters in a growing business. Industry estimates suggest 50% to 70% of custom software projects miss objectives or run dramatically over budget. Mid-sized companies do not need more technical debt. They need reliable platforms that can scale.
Look at each process honestly. Is it a true competitive advantage, an operational necessity, or a commodity?
For commodity processes, treat them like commodities.
Focus your investment on what actually drives enterprise value.
Shiny projects jump the queue
Right now, the shiny object is AI.
I am optimistic about AI, but a lot of organizations are still talking in ambiguity. Industry analysis shows that roughly 68% of AI projects miss their ROI targets within two years and deliver about 47% less return than projected.
That should not surprise anyone.
A lot of companies are trying to automate work they never properly defined in the first place.
You cannot codify broken business processes and expect elegant economics on the other side.
When AI is used in the right places, the value can be real. Long-running workflows are a good example. Data quality is another. In one case, an e-commerce product setup cycle that had been taking one person three weeks was reduced to four hours through automation. That worked because the process was defined, the rules were clear, and the data was structured well enough to support the automation.
I learned the same lesson in retail. At Shoppers Drug Mart, we designed a very simple self-checkout experience. It was easy to use. Intervention levels stayed low. After the pilot, the business approved rollout across hundreds of stores. At Loblaw, the early self-checkout experience had so many intervention problems that we had to rebuild the front end.
Same concept. Very different return.
The budget assumption only works when the user experience works and the underlying data works. If either one is weak, labor comes back into the process and the economics fall apart.
So the sequence matters. Clean up the data. Standardize the process. Document the workflow. Then bring in AI or automation where it can actually create leverage.
Weak governance kills trust
A lot of budgets fail because the organization has not built trust in how decisions are made.
Every major rollout carries risk. Anyone telling you it will be flawless is selling hope, not leadership.
You need pilots. You need testing. You need leaders to own decisions. You need enough information in the room for executives to make sound calls, even when the options are imperfect.
That is governance.
I was involved in a loyalty rollout where the technology worked in a small setting, but scale introduced a different problem. Ten users are easy. Ten million users hitting the same endpoint in a short period is something else entirely. Performance testing delayed the launch by several months.
That delay was the right decision.
At Shoppers Drug Mart, we re-engineered the IT operating model through Project Symphony and moved to a portfolio-based structure. Productivity improved by 40% year over year as measured by total invested capital. That happened because the organization became more disciplined about structure, prioritization, and execution.
I also coach IT leaders to stop living as firefighters. Hero Syndrome may look impressive in the hallway. It is terrible for budgeting.
If the IT leader spends the year rescuing poor decisions, they miss the strategic discussions where capital gets shaped.
In one case, I coached a Head of IT to let an unmanaged production change fail instead of stepping in and saving it. The disruption forced the business to adopt proper change management and risk assessment. Sometimes people need to see the consequence before they will govern the process properly.
The Wrong Work Stays In-House
One more issue sits underneath a lot of failed budgets.
IT is effectively two departments.
One side is commodity operations: desktop support, network support, and core infrastructure. Important work, yes. Strategic differentiator, usually no.
The other side is strategic enablement. That is the part that should understand the business, improve workflows, and drive productivity.
Too many mid-sized companies keep all the commodity work inside. Then the budget gets consumed by maintenance, while internal talent spends time closing tickets instead of improving the business.
My view is straightforward. Take the pieces that do not represent competitive advantage and outsource them. Let a third party industrialize those functions. Keep your internal talent focused on the work that creates leverage, intellectual property, and enterprise value.
That is one reason Narrative Group can act as the IT department for smaller mid-sized organizations. We can stabilize infrastructure, protect the environment, and then move up into business process work.
What gets measured gets managed.
What a Budget That Works Actually Looks Like
So what does a good IT budget look like?
It starts with Financials First.
When I sit down with a CFO, I want to know what the business is trying to transform and how that connects to value creation. Then I split the analysis into two lenses.
First, the primary value chain. Where is productivity weak? Where is cost-to-serve too high? Where can technology make delivery faster, simpler, or more reliable?
Second, the supporting functions. Where can technology help the company do more work without labor growing at the same rate?
Then I want the baseline.
What did last year’s downtime cost?
How much manual effort is buried inside key processes?
Which systems are fragmented?
Which vendors are operating in silos?
Draw it out. The picture usually tells the story.
From there, the budget becomes much easier to defend. You organize the work into three, four, maybe five strategic themes. You balance quick wins with longer-term ROI work. You phase the transformation. You avoid the big bang.
I have seen this work at every scale. At Loblaw, a structured strategy and governance model aligned millions of capital to enterprise priorities. In another case, we helped a start-up insurance distributor identify and communicate the use of funds within IT and put enterprise investment governance in place. That contributed to a considerable raise and an IT organization prepared to scale.
The size changes. The discipline does not.
Boards do not need a tour of your toolset. They need a clear view of business impact.
They need to know what the money will do to productivity, service levels, risk, growth capacity, and enterprise value.
Final Thought
Mid-sized companies matter enormously. That same Flint Global research shows that SMEs make up more than 99% of EU businesses and about two-thirds of employment.
The lesson is simple. When mid-market companies budget technology poorly, growth slows and risk rises.
I do not want companies to spend more on IT for the sake of spending more. I want them to budget better. I want them to follow the money. I want them to ask how they actually make money, where productivity is stuck, where labor is absorbing cost, and where technology can make the business model operate more elegantly.
That is how you build a budget that survives scrutiny.
That is how you turn IT from a cost center into a growth engine.
And in my view, that is what innovation really is. Innovation is making the operation of a business model elegant.
If your IT budget keeps getting challenged, the problem is rarely just the number. It is usually the lack of a clear business case. Explore our IT Strategy Consulting services or start with an IT Value Alignment Assessment.
Frequently Asked Questions
How can CFOs identify redundant SaaS expenses during annual IT budgeting?
Start by auditing tool sprawl. Data shows 40% of SMBs use five or more cloud tools. Consolidate overlapping platforms and tie every remaining license directly to a measurable business outcome. If a cloud tool doesn’t actively reduce labor, cut it.
Why do mid-market cybersecurity budgets frequently fail to mitigate actual enterprise risk?
They buy tools instead of resilience. Average small businesses spend $1,200 annually on cyber software. That buys a single solution, not an operating model. Defensible security budgets must fund recovery testing and threat governance, not just isolated licenses.
How should executive teams measure the true ROI of technology investments post-approval?
Stop tracking IT metrics and start tracking business leverage. A successful IT budget should positively alter your labor curve. Look at the ratio of IT spend to revenue and measure whether technology investments are actively slowing your rate of hiring while the business scales.
What is the most fiscally responsible way to fund AI initiatives in the mid-market?
Fund the foundational data cleanup first. Roughly 68% of AI projects miss their ROI targets because companies automate broken workflows. Approve AI spend only after the business has standardized key processes, improved data quality, and defined where automation will actually create operational leverage.
When should a mid-sized company halt a custom software project to protect EBITDA?
When it stops creating unique competitive advantage. Industry data shows 50% to 70% of custom software projects fail or exceed budget. If the software merely replicates commodity workflows, kill the project immediately and migrate that budget to a vanilla, scalable platform.