An IT budget is not a list of things the business would like to buy. It is a set of commitments: licence renewals that cannot be missed, support contracts that define response times, hardware replacement cycles, security controls that need evidence, and the internal hours required to run all of it. When those commitments are scattered across invoices and inboxes, the annual planning conversation becomes a negotiation about guesses.
Buying help with IT budget planning is therefore not the same as buying more IT. The engagement should produce a defensible baseline, a forward view and a decision calendar. This guide sets out what to require, the supplier models you will encounter, how to score them and the terms that prevent the plan from becoming a sales channel.
What the engagement should deliver
- An asset and contract register: systems, devices, servers, cloud accounts, licences and renewals, each with an owner and a renewal date.
- A cost baseline: recurring and one-off spend, split into run, change and risk categories, with pass-through charges visible.
- A forward plan: expected replacements, contract changes and capacity needs over the next planning cycle, expressed as scenarios rather than one forecast.
- A risk view: unpatched systems, unsupported software, single points of failure and unowned accounts, with a cost to address and a consequence of delay.
- A decision calendar: what must be decided, by whom and when, so renewals are not auto-approved by default.
- A reporting format: a one-page view the finance lead and managing director can use without translating technical terms.
Requirements to write into the brief
State the scope in business units, not tool names. The supplier needs to know how many legal entities, branches, staff, devices and cloud accounts are in scope. List the systems that hold money, student or customer data, and identify the person accountable for each. Provide the last twelve months of invoices if you want a baseline rather than an estimate. Say which decisions are reserved to the board and which the finance team can make.
Also define the output format. A slide deck with a single total is not a budget. Ask for a spreadsheet or database export with a line per commitment, a named owner, a renewal date, a cost basis and a confidence level. That structure is what makes the plan reviewable after the adviser leaves.
Four support models
Independent IT adviser
An adviser with no resale agreement can provide a baseline and challenge incumbent suppliers. This is useful when the current estate has grown through purchases rather than design. Ask for a written disclosure of any commission, referral fee or reseller relationship, and check whether the adviser is willing to recommend that you stop buying something.
Managed service provider
An MSP can combine planning with day-to-day support, monitoring and procurement. The advantage is accountability for delivery. The risk is that the plan expands toward the services the provider sells. Separate the planning engagement from the support contract, even if you intend to award both, so the baseline is produced before pricing is negotiated.
Accounting or business advisory firm
These firms are strong on cash-flow treatment, capital versus operating expense and board reporting. They may be weaker on architecture, security and licensing mechanics. Use them when the main problem is financial governance, and pair them with a technical reviewer for the asset and risk sections.
Internal finance lead with a framework
A capable finance lead can run the process with a standard template and a technical adviser for specific questions. This is often the cheapest sustainable model, provided the lead has authority to challenge department heads and the time to maintain the register. It fails when the register is treated as a one-off exercise and allowed to go stale.
A weighted scorecard
Score each candidate from 1 to 5 on these criteria, with evidence notes. Set the weights before proposals arrive.
- Baseline rigour (25%): can they reconcile invoices to a contract register and explain every material variance?
- Independence (20%): are commissions, resale margins and referral arrangements disclosed in writing?
- Commercial and technical range (20%): can they cover licences, cloud, support contracts, security and replacement cycles without hand-waving?
- Decision support (15%): do they present trade-offs and scenarios rather than a single recommended number?
- Transfer (10%): will your team own the register and the calendar after the engagement?
- Cost model (10%): is the fee fixed for a defined output, with change control?
Pricing questions that expose the real model
- Is the fee fixed, day-based or a percentage of IT spend? A percentage can reward higher spend, so ask how that incentive is controlled.
- Does the supplier earn commission on software, hardware, cloud or support renewals? Request a written disclosure.
- What happens if the baseline reveals that a current contract should be renegotiated or cancelled?
- Which internal hours are expected from finance, operations and technical staff?
- What is the fee for a re-run or refresh of the plan next year?
Run the first cycle as a pilot
Do not commission a multi-year transformation. Start with one planning cycle. In the first month, build the register and baseline. In the second, produce scenarios and a decision calendar. In the third, support one real decision, such as a renewal, a replacement or a consolidation. Then review whether the output was used, whether the numbers held, and whether your team can maintain the register without the adviser in the room.
A useful acceptance test is simple: give the plan to a new finance officer and ask them to explain the five largest commitments, their owners and their renewal dates. If they cannot, the deliverable is a presentation, not a budget.
Warning signs in the proposal
- A recommendation set that maps neatly to the supplier's product catalogue.
- No asset register, only a spending total.
- Benchmark claims without a described sample, date or comparison basis.
- No exit clause, no data export and no obligation to hand over the register.
Decision framework and exit
Choose an independent adviser when spend has grown without a clear architecture and you need an impartial baseline. Choose an MSP when you want one accountable party for planning and support, with the planning phase contracted separately. Choose a finance advisory firm when board reporting and cash-flow treatment are the weak points. Keep the work internal when you have the discipline and only need a template and a technical reviewer. In every case, retain ownership of the register, the contract dates and the decision calendar. Put the handover format, data export and final review session in the contract before work begins.
IT planning and managed support sit inside Managed Technology & Cybersecurity. The pricing page explains how assessment and retainer engagements are separated. For the annual planning cycle in more detail, read how SME IT budgeting changes year by year.
Sources
- NIST Cybersecurity Framework 2.0, accessed 17 November 2026.
- NIST SP 800-34 Rev. 1, Contingency Planning Guide, accessed 17 November 2026.
- Flexera, State of the Cloud Report, accessed 17 November 2026.
- ISO/IEC 27001, Information Security Management Systems, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.