The same evidence, translated four different ways.
A hardware proposal usually passes through several people before it’s approved, and each one is weighing a different question. The CFO is assessing unbudgeted exposure, the managing director is assessing what the business can commit to, the operations lead is assessing disruption, and your own manager is assessing whether they can defend it upward. One set of facts, four translations.
Most refresh cases are written once and sent to everyone. That’s efficient, and it’s why they often stall.
The information itself is rarely the problem. A list of ageing devices, a replacement cost and a risk summary is a reasonable piece of work. But a CFO reading it is answering a different question from the one the managing director is answering, and a document written for neither tends to satisfy neither.
This isn’t about tone or presentation. It’s that the same evidence genuinely means different things depending on what the reader is accountable for.
The CFO or Financial Controller
At most mid-market businesses, this is the person who decides, and often the person who holds the IT budget in the first place.
What lands: exposure that isn’t currently on the books. An ageing fleet is a liability the business is carrying without having priced it, and that framing is familiar territory. Replacement cost against the cost of continuing, including support hours, downtime and emergency procurement when something fails unexpectedly. Phasing, because it converts a single large number into something that can be planned around. Anything that improves predictability.
What doesn’t: technical specification. Efficiency gains you can’t substantiate. Anything implying the finance team has previously underfunded IT, which closes the conversation faster than any other misstep. And vague risk language. “We’re exposed” means nothing without a number or a probability attached.
The most useful thing you can bring is a total cost of ownership comparison rather than a purchase price. A CFO is rarely resisting the spend. They’re resisting a number with no context around it.
The CEO or Managing Director
The MD is usually assessing something broader: what this does to the organisation’s capacity to do things.
What lands: constraints. What the business currently can’t do, or can’t do safely, because of the infrastructure it’s running. Connection to something already underway, whether that’s growth, a new system, a client requirement or an office move. Continuity, framed as what happens to the business rather than to the IT environment. External pressure from clients, insurers or auditors carries real weight here, because it’s someone else’s assessment rather than IT’s.
What doesn’t: detail. An MD who wanted the detail would have asked the CFO for it. Also, anything that sounds like maintenance. Replacing things because they’re old is a category of spend an MD delegates, and delegating it usually means deferring it.
The reframe that works is moving from “we need to replace this” to “here’s what we can’t currently commit to”. The second is a business question. The first is a shopping list.
The Operations Lead, COO or General Manager
This is the most underused relationship in the whole conversation, and often the most valuable.
Operations feels the cost of ageing infrastructure directly, in a way finance and the MD only hear about secondhand. They know which team loses half a morning when a system is slow. They’ve absorbed the workarounds. What they typically don’t have is the connection between those daily frustrations and the equipment causing them.
What lands: specifics tied to actual processes. Not “staff report slow machines,” but which function, how often, and what it costs in hours. The phased plan, because disruption during rollout is their concern more than anyone’s. Anything that reduces unplanned interruption.
What doesn’t: abstraction. Fleet-wide averages don’t help someone who thinks in terms of teams and processes. Neither does security risk framing, which they’ll reasonably treat as someone else’s remit.
Worth noting this person is usually an advocate rather than an approver. That’s still valuable. A proposal that arrives at the CFO with operations already behind it is a different proposition from one arriving alone.
Whoever You Report To
If you report to a Head of IT, IT Director or CTO, this one works differently from the rest, because they almost certainly agree with you already.
The task isn’t convincing them. It’s that they have to carry it into a room you’re not in, and answer questions you won’t hear. A case that’s persuasive to someone technical can fall apart the moment it meets a finance question nobody prepared for.
What lands: pre-empted objections. What happens if this is deferred twelve months. Why this scope and not a smaller one. What can be cut if the full number isn’t available. Which parts are genuinely urgent against which are simply due. Giving them the answer to “can we do half of it” before they’re asked is worth more than another page of justification.
What doesn’t: a case that only works if they understand the technical reasoning. If they have to explain why the hardware matters before they can explain why it’s needed, you’ve handed them a harder job than necessary.
Ask them directly what gets asked in those meetings. Most will tell you, and it’s better information than any assumption about what finance cares about.
A note on boards
If your organisation has a board, and plenty at this size don’t, it’s a different audience again. Boards engage with risk, obligation and governance rather than operational need. An infrastructure item reaches them when it’s material enough to affect the organisation’s risk position, usually through a security, compliance or continuity lens rather than a replacement cycle.
In practice, you’ll rarely present to a board directly. You’ll be supplying the material someone else presents, which makes it closer to the “whoever you report to” situation than a separate case.
Who not to lead with
Sequence matters as much as content, and a few common missteps are hard to recover from.
- The MD, before finance has seen it. An MD’s first move is almost always to ask the CFO what they think. If that’s the first the CFO has heard of it, you’ve created an awkward moment for someone whose support you need, and the answer is likely to be “let me look into it”.
- A department head who’ll relay it upward. Enthusiasm is useful, but a secondhand version arriving before yours does tends to arrive incomplete, and you lose control of the framing.
- Anyone, before you can answer the cost question. This applies universally. The first follow-up to any refresh proposal is what it costs and whether it can be staged. Opening the conversation without that turns a live discussion into a deferred one.
- Everyone at once, in a group setting. A proposal presented to several stakeholders simultaneously has to satisfy all of their questions in one document, which usually means it satisfies none of them properly. Individual conversations first, group decision second.
The underlying point
None of this is about adjusting tone for different audiences. It’s that an infrastructure decision genuinely has four different meanings inside one organisation, and a case that acknowledges only one of them is incomplete rather than badly written.
Practically, that means the same underlying work supports all of these conversations. The fleet’s condition, the cost of keeping it versus replacing it, the risks attached, and a plan with stages. Once you have those, the translation into each conversation is straightforward. Without them, no amount of framing helps.
Which is also why the preparation matters more than the pitch, a point we made in more detail in when’s the best time to talk about new hardware.
Getting the material together
Our free hardware refresh business case produces exactly the four components these conversations draw on: an assessment of your environment, a total cost of ownership analysis, an infrastructure risk analysis, and a phased plan.
Those aren’t four documents for four people. They’re one piece of work you can draw from differently depending on who’s across the table. No obligation attached.
If you’d rather start with a number of your own, the cost of delay calculator gives you an indicative figure in a couple of minutes.
FAQs
How do you convince a CFO to approve IT hardware spending?
Frame it as exposure the business is already carrying rather than new spending. A total cost of ownership comparison, including support costs and downtime, is more persuasive than a purchase price. Phasing helps, because it makes the cost predictable.
What does a CEO want to know about an IT refresh?
What the business can’t currently do, or can’t do safely, and what the plan is. Constraints and continuity matter more than specification. Connecting it to something already underway, such as growth or a system rollout, is usually more effective than presenting it alone.
Should you involve operations in a hardware refresh proposal?
Usually yes. Operations feels the cost of ageing equipment directly and can speak to specific processes and hours lost. They’re generally an advocate rather than an approver, but a proposal with operational backing lands differently.
Who should you approach first about replacing IT hardware?
Typically whoever controls the budget, usually the CFO or financial controller, before anyone more senior. Going to the managing director first tends to generate a request for the CFO’s view, which is a weaker starting position than having it already.
What’s the most common reason hardware proposals get rejected?
Not being able to answer the immediate follow-up about cost and phasing. The information gap turns a live conversation into a deferral, which is harder to reopen than it is to prevent.
