I was speaking to an IT Director at a university recently. At one point he said something that was delivered almost casually, but stayed with me afterwards.
“We still talk about our IT budget like we can shape it. In reality, most of it is already gone before the year starts.”
If you’ve spent any time in Higher Education IT, you’ll recognise that sentiment. Nothing has broken. Systems are running. But the nature of the budget has changed in a way that’s easy to miss until you try to do something new.
When IT Spend Was Something You Could Influence
There was a time when most IT spend was tied to decisions you could actively shape. Infrastructure was something you owned, systems were deployed deliberately, and teams were built around what you chose to run. If you needed more capacity, you invested in it. If you needed new capability, you hired for it.
That model came with its own pressures, but it had one advantage. You could change it.
What has gradually replaced that is a model where a significant proportion of spend is tied to access rather than ownership. Platforms are no longer something you run; they are something you subscribe to. That shift in itself isn’t the issue. The issue is what it does to your ability to respond once those commitments are in place.
The University IT Budget That’s Already Spoken For
In most universities today, a large part of the IT estate is built on a set of core platforms that are essential to how the organisation operates. Typically, that includes:
- collaboration and productivity tooling
- identity and access management
- cloud infrastructure and storage
- security and compliance services
Individually, each of these makes sense. Collectively, they form a baseline that you can’t realistically step away from. By the time the financial year begins, a significant proportion of the budget is already committed to maintaining access to these systems.
Over time, this changes how the budget behaves. It still exists as a line in a spreadsheet, but in practice it functions more like a series of standing charges. You’re not choosing whether to spend that money. You’re ensuring continuity of service.
Why This Lands Differently in Universities
Every sector has seen software costs increase, but universities experience the impact in a more constrained way. Unlike commercial organisations, they can’t adjust pricing to absorb those increases. Tuition fees in England have remained capped at £9,250 since 2017, and their real value has declined significantly with inflation, something the Office for Students has highlighted in its financial sustainability reports.
That creates a simple but uncomfortable reality. When costs rise, they have to be absorbed internally. There is no offset.
In practical terms, that means every increase in IT spend reduces what is available elsewhere. It might show up in reduced investment in facilities, delays to projects, or pressure on staffing. The effect is rarely dramatic, but it is cumulative.
The Scale Problem That Doesn’t Quite Resolve
It’s often assumed that scale should bring efficiency, but licensing models don’t always align neatly with how universities operate.
Smaller institutions tend to feel the weight of fixed costs more acutely. They require the same core systems as larger universities, but those costs represent a much higher proportion of their income.
Larger institutions face a different challenge. Per-user licensing means that costs increase with every additional student and member of staff. In universities with significant Transnational Education activity, that tension becomes more visible. Income per student may be lower, but expectations around access to systems remain the same, and the cost structure does not adjust to reflect that.
Different pressures, but the same outcome. Less room to manoeuvre.
What emerges from all of this isn’t a sudden problem, but a gradual constraint. Systems continue to run, services remain stable, and from the outside everything appears under control. The challenge shows up elsewhere.
As more of the budget becomes committed, it becomes harder to invest in anything new. Decisions are shaped by what cannot be changed rather than what could be improved. Over time, that begins to slow progress. Not because there is a lack of ambition, but because there is less flexibility to act on it.
Where Linux Re-Enters the Conversation
Most universities already rely on Linux, particularly in areas that are critical to research and data processing. It is widely trusted, well understood, and often central to the most demanding workloads in the institution.
What is less common is for Linux to be considered as part of broader financial or strategic discussions. It tends to sit slightly outside the main IT conversation, used where it is needed rather than where it could be most effective.
As cost pressures increase, that distinction starts to matter more.
Reclaiming Room, Not Replacing Everything
This is not about replacing core platforms or undoing years of investment. That is neither realistic nor necessary. The more practical approach is to look at where pressure can be reduced.
In many environments, there are specific workloads that carry a disproportionately high licensing cost. When those workloads can be moved onto Linux, the effect is not just technical. It changes the structure of the budget.
Instead of spend being tied to recurring licensing, it becomes something that can be shaped and controlled. That creates room, and in a university context, that room has real value.
It allows institutions to redirect spend towards priorities that are often under strain, whether that is research capability, infrastructure, or simply giving internal teams the capacity to improve what is already in place.
The Role of Linux Support in Making It Work
It’s important to be clear that Linux is not a way of removing cost altogether. Running Linux environments well requires expertise, ongoing management, and the right level of operational support.
The difference is in how those costs behave. They are not tied to user counts, they do not scale automatically, and they can be aligned more closely with the needs of the organisation. With the right support in place, Linux becomes a stable and predictable part of the environment rather than something that introduces risk.
For many universities, the challenge is no longer deciding what to invest in. It is understanding where there is still room to make meaningful decisions.
A useful place to start is with a simple question: How much of your IT budget is genuinely flexible in practice?
Answering that tends to reveal where the real constraints sit, and where there may be opportunities to reduce pressure without large-scale disruption.
If you would like to discuss any of the topics covered in this article, please get in touch. Either contact the Tiger team here or send me a message on LinkedIn.
