Many UK SMEs receive a monthly managed IT services report full of numbers. Tickets closed. Calls answered. Devices monitored. Patches deployed. Licences renewed.
It can look impressive while leaving one important question unanswered:
Is the technology actually helping the business achieve its plan?
That is the difference between measuring activity and measuring outcomes.
A consultancy-first approach starts with the business objectives, then defines the technology roadmap and the measures that prove whether it is working. Helpdesk Support, Cloud Solutions, Network Solutions, and Voice and Connectivity remain important, but they are execution layers supporting a wider IT strategy.
The role of the Fractal IT Director is to hold that strategy together: connecting operational support, infrastructure, security, supplier performance and investment decisions to commercial priorities.
Start with the business outcome, not the service desk
Before reviewing metrics, define what the technology is meant to achieve.
For example:
- Enable staff to work reliably across multiple locations.
- Reduce disruption to customer-facing operations.
- Support growth without repeatedly rebuilding infrastructure.
- Improve financial control over cloud and software spending.
- Protect critical data and restore services quickly after an incident.
- Prepare the business for a planned Microsoft Dynamics 365 Business Central implementation.
- Reduce dependency on fragile legacy platforms while managing them responsibly.
Each objective should have an observable outcome.
“Improve our cloud environment” is not a useful target. “Reduce cloud-related service interruptions by 30% over six months” is measurable. “Review Microsoft 365 licences” is an activity. “Remove unused licences and reduce annual technology spend without reducing capability” is an outcome.
Good performance measurement follows the same essential principle: metrics should be tied to a service’s purpose, measured over time and used to decide what happens next. That principle applies equally to business IT.
The five measures every SME should expect
A useful managed services scorecard does not need to contain dozens of indicators. Five groups usually provide a clearer view.
1. Support quality and ticket trends
Ticket volume alone is a poor measure of performance. A supplier can close a high number of tickets while the same problems continue to return.
Ask for trends across:
- Total tickets by month.
- Incidents, service requests and problems.
- Tickets by department, location or application.
- Reopened and escalated tickets.
- Repeat incidents linked to the same root cause.
- Proactive work compared with reactive support.
- First-time fix or First Contact Resolution.
A first-time fix rate of around 70–80% can be a useful indicative benchmark, although the right figure depends on the complexity of the environment. Password resets and straightforward device issues should not be compared directly with specialist finance or clinical applications.
More important is the direction of travel. If ticket volumes are rising, is that because the business is growing, because a new system has been introduced, or because the same unresolved problem is appearing repeatedly?
A strong service review explains the reason behind the trend and identifies the corrective action. A weak one simply reports the total.
2. Response, resolution and service-level performance
Response time is not the same as resolution time.
A quick automated acknowledgement does not mean that a user’s problem is being dealt with. Your report should separate:
- Time to human response.
- Time to technical ownership.
- Time to workaround.
- Time to permanent resolution.
- Time awaiting information or approval.
- Time outside the supplier’s control.
Service levels should be defined by business impact rather than vague priority labels. A critical outage affecting every user should not be treated like an isolated printer issue.
As an indicative starting point, many SMEs work towards:
- Critical incidents acknowledged within 15–60 minutes.
- Critical incidents restored or contained within four hours where practical.
- Overall service-level compliance of at least 95%.
- Clear escalation for repeated breaches.
- A documented root-cause review after major incidents.
These are not universal contractual requirements. A logistics operation, accountancy practice and medical organisation may have very different tolerance for disruption. The important point is that the targets are agreed, relevant and reported consistently.
3. Availability, resilience and recovery
A system can be available most of the time and still expose the business to unacceptable risk.
Review availability alongside resilience:
- Core network and internet uptime.
- Cloud application availability.
- Voice and Connectivity performance.
- Major incident frequency.
- Backup completion and restore testing.
- Recovery time against agreed objectives.
- Single points of failure.
- Disaster Recovery exercise results.
A 99.9% availability target sounds strong, but it still allows approximately 8.7 hours of downtime across a year. Whether that is acceptable depends on when the downtime occurs and which service is affected.
A resilient Network Solutions design should consider more than the primary connection. It may include a secondary circuit, mobile failover, resilient firewall arrangements and tested recovery procedures. Similarly, Cloud Solutions should be assessed for identity resilience, data protection and the ability to restore access when a provider or configuration fails.
The question is not simply, “Was the service up?” It is, “Could the business continue operating when something went wrong?”
4. Cost per user and Technology Expense Management
IT costs are often spread across supplier invoices, software subscriptions, telecommunications bills, hardware purchases and project fees. That makes waste difficult to see.
Technology Expense Management brings those costs into one view.
Track:
- Total technology cost per active user.
- Cloud spend by service and department.
- Software licences assigned, unused and duplicated.
- Support cost per user.
- Voice and Connectivity cost by site.
- Hardware replacement cost over time.
- Cost per ticket or service request.
- Spend against the agreed technology roadmap.
A reduction in monthly cost is not automatically a success. Cutting a security service or reducing backup coverage may produce a short-term saving while increasing business risk.
The better question is whether the business is receiving the expected value for its level of spend. Are users more productive? Are outages less frequent? Are services easier to scale? Is the organisation paying for capability nobody uses?
Technology Expense Management should identify waste without weakening the control environment.
Measure the roadmap, not just the helpdesk
Operational metrics tell you how the service performed yesterday. The roadmap shows whether the business is becoming better prepared for tomorrow.
Every service review should include a simple status against agreed strategic objectives:
| Objective | Measure | Status | Next action |
|---|---|---|---|
| Improve remote working | Availability and user-impacting incidents | On track / at risk | Confirm next resilience change |
| Reduce licence waste | Unused licences and monthly spend | On track / at risk | Remove or reassign unused seats |
| Prepare for Business Central | Readiness actions completed | On track / at risk | Approve Dynamics 365 Jump Start |
| Improve recovery | Restore tests and recovery time | On track / at risk | Complete Disaster Recovery exercise |
| Control legacy risk | Documented dependencies and support plan | On track / at risk | Review IBM i Management requirements |
This prevents strategic work from disappearing beneath the noise of daily support.
Microsoft Dynamics 365 Business Central, for example, should not be approached as a software purchase alone. It may affect finance, operations, reporting, permissions, integrations and staff processes. A Dynamics 365 Jump Start should therefore be measured by readiness, adoption and business benefit, not simply by whether workshops took place.
Where an SME relies on IBM i, Power Systems or AS/400 platforms, the same principle applies. Specialist IBM i Management should be assessed against system resilience, skills coverage, documentation, recovery capability and the organisation’s longer-term plans.
How to read a service review properly
A useful service review answers three questions:
- What happened?
- Why did it happen?
- What will change as a result?
Look for trends rather than isolated monthly figures. One missed service level may be understandable. Six months of declining first-time fix rates is a management issue.
Ask the provider to explain:
- Why ticket volumes changed.
- Which problems generated the most disruption.
- Whether the same root causes are recurring.
- Which risks remain open.
- What roadmap actions are late and why.
- What decisions are needed from the business.
- Whether the recommended work changes cost, risk or capability.
The review should also distinguish supplier performance from user behaviour, project activity, third-party outages and business change. Context matters. An average can conceal serious problems within one department or site, so useful reports segment the data where appropriate.
Reports should inform decisions, not merely decorate a meeting.
Warning signs that your supplier is reporting activity, not outcomes
Be cautious when:
- The report celebrates ticket closure but does not show repeat incidents.
- Response times are reported without resolution times.
- There is no root-cause analysis for major incidents.
- SLA compliance is high because priorities are routinely downgraded.
- Cloud and licence costs are not visible by user, service or department.
- Project milestones are listed without business benefits.
- The roadmap changes frequently but ownership is unclear.
- The same risks appear in every meeting with no accountable action.
- The supplier cannot explain how its work supports your business plan.
- The service review is a sales presentation rather than a governance conversation.
A managed service provider should be able to show reliable execution. A consultancy-led partner should also be able to explain whether that execution is moving the business in the right direction.
The Fractal IT Director view
The Fractal IT Director does not treat IT as a collection of disconnected suppliers.
The strategy sets the priorities. The roadmap sets the sequence. Measurement tests whether the plan is working. Managed IT Services then provide the operational capability to execute it.
Helpdesk Support, Network Solutions, Cloud Solutions, Voice and Connectivity, hardware and software licensing are valuable bolt-on services, but they should not become the strategy by default. Where specialist execution is required, a trusted network of channel partners can provide scale and technical depth while strategic accountability remains clear.
For an SME owner, the practical test is simple:
Can your IT partner show what has improved, what remains exposed, what it costs and what happens next?
If the answer is yes, your reporting is probably supporting good governance. If the answer is no, it may be time to move from activity reporting to an outcome-led IT strategy.
For wider group services and business support, visit Evestaff. For consultancy-led IT support and strategic planning, explore Evestaff IT Support and Consultancy.
SEO tags: Managed IT Services, Cloud Solutions, Network Solutions, Helpdesk Support, Voice and Connectivity, Technology Expense Management, Disaster Recovery, Dynamics 365 Jump Start, IBM i Management, UK SME IT strategy, IT service metrics, managed service reporting, IT consultancy UK
Join The Discussion