An IT budget is easier to approve when it explains what the business is protecting, what it is improving and what it expects to get in return. A list of monthly subscriptions rarely does that. It shows the cost of technology, but not the cost of risk, delay or lost working time.
For UK SMEs planning for the new year, the case should start with business priorities, not a supplier’s service catalogue. The Fractal IT Director approach is to set the direction, test the investment against business outcomes and then use support providers and specialist partners as the execution layer.
Separate essential risk spend from improvement
Start by dividing proposed spend into two clear groups.
Essential risk and continuity spend keeps the business operating within its agreed risk tolerance. Depending on the organisation, this may include security controls, tested backups, recovery planning, supported devices, connectivity resilience and a dependable route to Helpdesk Support. The test is not whether a particular product is fashionable; it is whether the business has a credible way to prevent, detect and recover from foreseeable disruption.
The UK Government’s Cyber Security Breaches Survey 2025/2026 found that 43% of businesses reported a breach or attack in the preceding 12 months. It also reported that only 33% had a business continuity plan covering cyber security. This is useful context for a budget discussion, not a prediction of what will happen to any one company.
Discretionary improvement spend supports growth, efficiency or a better customer and staff experience. Examples might include a cloud migration, a network refresh ahead of a new site, improved call handling or a finance-system project. These investments should have a stated business owner, a measurable outcome and a reason to proceed now rather than next year.
A proposal may include both groups, but it should not blur them. Risk reduction is not the same as optional enhancement, and the finance director needs to see which is which.
Use Technology Expense Management to find funding
Before asking for more budget, establish what the business is already paying for. Technology Expense Management (TEM) brings together invoices, contracts, users, devices, licences, phone numbers, cloud subscriptions and renewal dates. The aim is to identify spend that no longer earns its place.
A practical TEM review can uncover:
- Licences assigned to former staff or people who no longer need that service.
- Overlapping tools, duplicate subscriptions or unused mobile and voice services.
- Circuits, devices or support arrangements that remain on invoices after a change of site or supplier.
- Cloud resources and storage that have grown without a clear business owner.
- Contract renewals approaching without time to assess alternatives.
Savings should be evidenced rather than assumed. Record the current cost, the proposed change, any exit or implementation fees, and the expected net saving. Then decide where released funds go: towards resilience, service improvements or back to the business.
The FinOps Foundation’s budgeting guidance recommends clear budget ownership, regular variance reviews and a defined process for handling exceptions. The same discipline is valuable for an SME: track actual spend against forecast, review it quarterly and investigate surprises early.
Present services as business outcomes
Cloud Solutions, Network Solutions, Helpdesk Support and Voice and Connectivity are service areas, not business cases. For approval, connect each to an outcome and an indicator that can be reviewed.
| Investment area | Business outcome to describe | Useful measure |
|---|---|---|
| Cloud Solutions | Staff can access approved information and applications reliably, with suitable controls and recovery arrangements. | Service availability, recovery-test results, time to onboard a user, and cloud spend against forecast. |
| Network Solutions | Staff, sites and cloud applications have dependable, appropriately secured connectivity. | Connectivity incidents, time to restore service, Wi-Fi coverage issues and performance at critical sites. |
| Helpdesk Support | Staff regain the ability to work sooner, while recurring faults are identified rather than repeatedly patched over. | Response and resolution times, repeat incidents, user feedback and time lost to avoidable IT issues. |
| Voice and Connectivity | Customers and colleagues can reach the right person, including during busy periods or disruption. | Missed calls, call-answer times, service availability and cost per user or location. |
Choose measures that matter to the business and that can be collected consistently. A target for “fewer repeat incidents”, for example, is more meaningful if the current number is known. Avoid promises of savings or productivity gains that have no baseline.
Licences also need scrutiny. Microsoft’s business plans comparison sets out differences in features, commitment terms and pricing. The right budget is based on the plan that fits users’ needs and security requirements, not simply the cheapest headline monthly amount. Check current terms and the full scope before approval; prices and included features can change.
Answer the finance director’s questions directly
A strong business case anticipates reasonable challenge. Be ready to answer:
- What happens if we defer this? Describe the operational, security, contractual or customer impact, without relying on alarm.
- What is the full cost? Separate recurring services from one-off work, hardware, licences, implementation, VAT and any exit charges.
- What is included, and excluded? Clarify service hours, response targets, backup and recovery responsibilities, onsite work, project fees and support boundaries.
- How will we know it worked? State the baseline, target, owner and date for reviewing each outcome.
- What alternatives did we consider? Compare keeping the current arrangement, making a smaller change and funding the recommended option.
- Can we phase or stop the work? Identify decision gates, dependencies and what must be true before the next stage is funded.
- What is the financial exposure if costs change? Explain contract terms, renewal dates, assumptions and how variations will be approved.
The point is not to force every technology decision into a precise return-on-investment formula. It is to make assumptions visible and show why the recommendation is proportionate.
A costed roadmap for a 25-person SME
The following is an illustrative planning model, not a supplier quotation or market benchmark. It assumes a 25-person organisation, excludes VAT and major hardware replacement, and should be replaced with costs validated against the business’s environment and service scope.
| Phase | Proposed work | Illustrative allowance |
|---|---|---|
| Quarter 1: establish the baseline | Strategy and risk review, asset and contract inventory, TEM review, service scope and prioritised roadmap. | £4,500 one-off |
| Quarter 2: protect the essentials | Address priority network and connectivity weaknesses; confirm backup arrangements and complete a recovery test. | £8,000 one-off |
| Quarter 3: improve cloud and support operations | Apply agreed cloud optimisation, tidy access and licence allocation, and improve helpdesk reporting and recurring-issue analysis. | £6,000 one-off |
| Quarter 4: improve communications and review | Assess voice configuration and call handling, complete a resilience exercise and agree the next year’s priorities. | £5,000 one-off |
For a simple annual baseline, add separately priced recurring allowances, for example, £22,500 for managed support and security, £6,000 for cloud licences, and £6,000 for network, connectivity and voice services. These figures are modelling assumptions only; validate the inclusions and price before seeking approval. On those assumptions, the model totals £58,000 before contingency. A separate £5,000 reserve would take the planning envelope to £63,000.
Show the recurring baseline and project phases separately. That gives the finance director visibility of the ongoing commitment, the timing of one-off costs and the scope to pause or re-sequence discretionary work. Include a contingency only with clear rules for who can approve it and what evidence is required.
Keep the roadmap strategy-led
The annual plan should be sequenced by dependencies and risk, not by which supplier can start first. A useful order is: understand and remove waste; address material risk; improve reliability; then fund growth and transformation projects where the business case is ready.
That could mean prioritising Disaster Recovery and connectivity resilience before a broader cloud migration. It could also mean planning a distinct specialist workstream instead of hiding it in a generic support line: for organisations that rely on legacy platforms, IBM i Management should be costed against its own operational requirements. Where finance-process change is a genuine priority, discovery for Microsoft Dynamics 365 Business Central, and a scoped Dynamics 365 Jump Start, can sit in the improvement portfolio, with defined outcomes and decision gates. It should not be presented as an automatic add-on.
David’s practitioner-led background, including Google-certified IT project management, multi-national onboarding and IBM i systems administration, supports a consultancy-first approach: establish the plan, explain the trade-offs and coordinate delivery through a trusted network of specialist partners. Managed IT Services, telephony, print, network and hardware support can then operate as the bolt-on execution layer that delivers the approved strategy.
A budget is not just a list of things to buy. It is a year-long agreement about risk, priorities, expected value and how decisions will be made when circumstances change. For a wider view of Evestaff group services, visit evestaff.co.uk; for consultancy information, see itandconsultancy.co.uk.
SEO tags: SME Managed IT & Cloud Services, Managed IT Services, Cloud Solutions, Disaster Recovery, Dynamics 365 Jump Start, Helpdesk Support, IBM i Management, Network Solutions, Technology Expense Management, Voice and Connectivity
Join The Discussion