For many UK SMEs, technology grows by accumulation.
A new cloud application is added because the old system cannot cope. A separate provider supplies business broadband. A different supplier installs hosted phones. An IT company handles laptops and passwords. Backups are purchased after a near miss. Cybersecurity arrives as an urgent extra.
Each decision may be reasonable in isolation. Together, they create the bolt-on trap: an IT estate assembled around immediate problems rather than business strategy.
The result is familiar. More suppliers, more contracts, more overlapping tools and less certainty about who owns the outcome when something fails.
The answer is not necessarily to replace every system or buy a larger managed service package. It is to put senior strategy and risk ownership first, then use Managed IT Services as the execution layer.
What is the bolt-on trap?
The bolt-on trap happens when an SME buys operational services before deciding what its technology must achieve.
Typical symptoms include:
- A helpdesk that resolves tickets but has no influence over the technology roadmap
- Cloud services purchased without clear ownership, security or exit planning
- Separate Network Solutions with no relationship to application performance
- Voice and Connectivity contracts managed independently from business continuity
- Several suppliers claiming that an incident belongs to somebody else
- Licences renewed automatically, even when nobody knows whether they are still needed
- Disaster Recovery treated as a backup purchase rather than a tested business capability
- Projects approved because they are urgent, not because they deliver measurable value
The monthly bill may still look manageable. The hidden cost appears elsewhere: duplicated licences, lost staff time, avoidable downtime, weak security controls and projects that need to be redone because the original design was incomplete.
A consultancy-led model reverses the order. First define the business requirement. Then design the operating model. Only then select the tools, suppliers and support services required to deliver it.
The Fractal IT Director model
The Fractal IT Director is a useful way to think about strategic technology leadership for an SME.
The principle is simple: the same strategic discipline should apply at every level of the estate, from a single application to a multi-site operating environment.
Each decision should connect four things:
- Business purpose: what the technology enables
- Risk ownership: what could go wrong and who is accountable
- Commercial control: what the service costs and how it scales
- Execution: how it is implemented, supported and measured
This creates a clear distinction between strategy and delivery.
The strategic layer sets priorities, architecture, risk tolerance and investment decisions. The execution layer provides monitoring, patching, Helpdesk Support, hardware, software licences, voice provisioning and technical administration.
Those execution services remain important. They are simply no longer allowed to define the strategy by default.
Four questions to ask before adding another service
Before signing a new technology contract, ask four practical questions.
1. What business outcome does this support?
“Moving to the cloud” is not an outcome. Reducing month-end processing time, enabling secure hybrid working or improving resilience may be.
The answer should be specific enough to measure. If the proposed service cannot be connected to a business objective, it may be a convenience rather than an investment.
2. What risk does it reduce?
Technology decisions should reduce risk, not simply move it between suppliers.
For example, a hosted voice service may improve resilience, but only if call routing, broadband redundancy, user access and emergency calling arrangements have been considered. A backup service may create copies of data, but it is not a complete Disaster Recovery capability until restoration has been tested.
3. Who owns the result?
A supplier may manage a firewall, a cloud tenant or a telephone system. That does not mean it owns the business outcome.
The SME should retain clear accountability for priorities, risk acceptance and commercial decisions. A consultant or outsourced IT director can provide that ownership without pretending to be the engineer for every platform.
4. How will we know it is working?
Every service should have a small number of meaningful measures.
Useful examples include:
- Critical incident response within 15–60 minutes, depending on trading requirements
- At least 99.9% availability for genuinely business-critical services, where appropriate
- Verified backup and restore performance
- Reduction in repeat incidents
- Licence utilisation and supplier spend
- Time saved in key operational processes
- Delivery against agreed technology projects
Metrics should support decisions, not create a monthly paperwork ritual.
A practical framework for this quarter
This is not another technology transformation programme. It is a focused review designed to stop further fragmentation.
Step one: Draw the dependency map
List the systems your organisation needs to trade, deliver services and meet its obligations.
Include:
- Core applications and databases
- Microsoft 365 and other Cloud Solutions
- Internet circuits, Wi-Fi and firewalls
- Telephony and collaboration tools
- End-user devices
- Backup and recovery arrangements
- Specialist or legacy platforms
- External suppliers and contract renewal dates
Then identify the dependencies. If the internet connection fails, which systems stop working? If a key administrator leaves, who can access the platforms? If a supplier disappears, can the business operate?
This exercise often reveals that the most important systems are not the most expensive ones.
Step two: Separate strategic services from bolt-ons
Classify each service as one of three things:
- Strategic core: essential to the operating model or risk position
- Execution service: required to deliver the strategy reliably
- Optional bolt-on: useful, but not essential or not yet justified
Managed monitoring, patching, endpoint administration, Helpdesk Support, hardware sourcing and software licensing will usually sit in the execution layer.
They should support a defined architecture rather than expand it accidentally.
Step three: Rationalise suppliers and spend
Do not consolidate suppliers simply for the sake of having fewer invoices. Consolidate where it improves accountability, service quality or commercial control.
A UK SME may see indicative managed support pricing in the region of £45–£85 per user per month for a broad core service, with more comprehensive or higher-risk arrangements reaching approximately £75–£125 per user per month. These are market reference points, not universal prices. The scope, security requirements, support hours and complexity of the environment matter.
Industry pricing guidance from Connection Technologies and contract guidance from CloudSwitched both illustrate why headline price is a poor comparison unless inclusions, exclusions and service levels are normalised.
This is where Technology Expense Management becomes practical. Review:
- Unused or duplicate software licences
- Mobile and connectivity contracts
- Cloud consumption
- Hardware warranties and replacement cycles
- Support contracts that overlap
- Charges for work that should be included
- Renewal dates and automatic price increases
The goal is not to buy the cheapest service. It is to remove spend that produces no operational value.
Where the main services fit
Cloud Solutions
Cloud adoption should follow an architecture and information-management decision, not a supplier promotion.
Define where data belongs, how identity is controlled, what integrations are required and what happens if the organisation changes provider. Cloud costs should be reviewed against usage, business value and security requirements.
Network Solutions
The network is the operating foundation for cloud applications, voice, remote working and site-to-site access.
A consultancy-led review considers availability, segmentation, wireless coverage, security, circuit resilience and monitoring together. It avoids the common mistake of treating a firewall, broadband line and Wi-Fi installation as unrelated purchases.
Helpdesk Support
Helpdesk Support is the visible face of IT for most employees, but it should not become the whole IT strategy.
A strong service desk identifies recurring problems, tracks user-impacting trends and feeds evidence into the technology roadmap. The objective is not merely to close more tickets. It is to reduce avoidable demand and improve the way people work.
Voice and Connectivity
Voice and Connectivity should be designed around how the organisation trades.
Consider call flows, customer contact, remote users, site resilience, mobile working and failure procedures. Voice provisioning is an execution service; the strategic question is how communication supports service quality and continuity.
Dynamics 365 Business Central
For finance-led, distribution and operational businesses, Dynamics 365 Business Central may become a central business platform. Its implementation should begin with process design, data ownership, reporting requirements and integration priorities.
A structured Dynamics 365 Jump Start can be useful when the business needs to clarify its starting position before committing to a larger programme. The objective should be a sound business case and delivery sequence, not simply another application added to the estate.
Specialist systems are not ordinary bolt-ons
Some SMEs depend on platforms that require specialist knowledge and careful stewardship. An old system is not automatically an obsolete system.
For organisations running IBM i, Power Systems or AS/400 environments, IBM i Management should be treated as a high-value consultancy discipline. The right approach may include infrastructure review, hosting decisions, security, resilience, skills planning and integration with newer services.
The strategic question is not “How quickly can we remove this platform?” It is “What business value does it provide, what risk does it carry and what is the economically sensible future state?”
That may mean modernisation, controlled retention or staged replacement. It should not mean an unplanned migration driven by fashion.
Build a simple scorecard
At the end of the review, produce a one-page scorecard with five sections:
| Area | Question |
|---|---|
| Business value | Which business outcomes does the service support? |
| Risk | What happens if it fails, is compromised or becomes unavailable? |
| Cost | What is the total annual cost, including licences and support? |
| Ownership | Who makes decisions and who resolves incidents? |
| Next action | Keep, improve, consolidate, replace or retire? |
Review the scorecard quarterly, but do not turn it into a bureaucratic exercise. Its value is in forcing clear decisions before the next supplier renewal or urgent technology purchase.
The bolt-on trap is rarely solved by one dramatic project. It is solved by consistently asking whether each new service strengthens the operating model or merely adds another layer to it.
A consultancy-first approach gives SMEs the senior direction they need, while trusted specialist partners deliver the technical execution at the appropriate scale. That is how Cloud Solutions, Network Solutions, Helpdesk Support, Voice and Connectivity, Disaster Recovery and cost control become parts of one strategy rather than a collection of disconnected purchases.
For organisations that also need support across wider Evestaff group services, evestaff.co.uk provides a discreet gateway to the wider group.
Join The Discussion