Growth is good for business. It is less good for an IT estate that has been allowed to grow by accident.
A second site, 20 new employees or the acquisition of a smaller competitor can expose weaknesses that were previously easy to ignore: unreliable connectivity, inconsistent user accounts, duplicated software, undocumented systems and a support process based on asking “the person who knows about computers”.
That is not a support-ticket problem. It is a strategy problem.
When a business expands, its technology needs to be reshaped around its operating model. Simply adding more laptops, licences and broadband connections may keep the lights on for a while, but it rarely produces a secure, scalable or cost-effective platform for the next stage of growth.
A consultancy-first approach begins with the business plan, then defines the Cloud Solutions, Network Solutions, Helpdesk Support, Voice and Connectivity and Managed IT Services required to execute it.
The growth trigger changes the IT question
Most SME technology decisions are reactive. A user cannot access a system, so somebody fixes the account. The Wi-Fi is slow, so somebody replaces the access point. A new starter arrives, so somebody orders a laptop and forwards an old checklist.
These actions may be necessary, but they do not answer the strategic questions:
- Can the business operate consistently across multiple locations?
- Which systems are genuinely critical to revenue?
- How quickly can a new employee become productive?
- What happens if the primary site, network or cloud platform is unavailable?
- Are duplicated software licences and telecoms contracts quietly eroding margins?
- Can the business integrate an acquired company without inheriting its technical debt?
The role of the Fractal IT Director is to bring structure to these questions. The concept is simple: provide strategic IT leadership at the level the business needs, then break delivery into practical workstreams supported by trusted specialist partners.
That may include networks, telephony, cloud platforms, hardware, security or service desk operations. These are execution services supporting the strategy, not substitutes for it.
Adding 20 staff: reshape the employee technology journey
An additional 20 employees can be a significant change for a UK SME. It may mean a new department, longer opening hours, more customer-facing staff or a move from informal processes to defined operational teams.
The IT response should not be limited to buying 20 devices.
Standardise identity and access
New starters should receive the right access, equipment and guidance on day one. Existing users should not accumulate unnecessary permissions simply because the business has never reviewed them.
A practical onboarding model should define:
- Identity and authentication standards
- Role-based access to applications and data
- Device configuration and security policies
- Starter and leaver processes
- Mobile and remote-working requirements
- Ownership of approvals and exceptions
Cloud Solutions can make this easier when identity, collaboration, files and device management are centrally governed. They also make it easier to support employees who work from different locations, rather than creating separate local arrangements for every office.
Review application and licence demand
Twenty new employees can trigger a surprisingly large increase in recurring costs. Software subscriptions, mobile contracts, collaboration tools and specialist applications may all be purchased independently by different teams.
This is where Technology Expense Management becomes a strategic discipline rather than a finance exercise. The objective is to understand:
- Which licences are assigned and actively used
- Which subscriptions overlap
- Which services are still being paid for after a project has ended
- Whether contract renewals match the actual growth plan
- Whether users need full, limited or occasional access
The saving is not simply achieved by choosing the cheapest product. It comes from making informed decisions about the technology estate and matching expenditure to business value.
Adding a second site: design for consistency, not duplication
A second site is often where an SME discovers that its original office network was never designed to be a business platform. It was designed to serve one building, one broadband connection and a relatively small number of users.
The answer is not automatically a larger version of the same arrangement.
Network Solutions should reflect how work is delivered
A multi-site network should be designed around the applications employees use and the risks the business needs to manage. Depending on the organisation, this may include:
- Business-grade primary connectivity
- 4G or 5G failover for critical locations
- Secure site-to-site connectivity
- Centrally managed firewalls and wireless networks
- Separate guest, operational and sensitive traffic
- Monitoring and alerting across both sites
- Secure access to cloud and on-premise applications
A cloud-centric architecture may be more appropriate than forcing every connection through the original head office. Where legacy applications remain in place, secure VPN or software-defined networking may still be required.
The important point is that Network Solutions should be selected after the application and operating requirements are understood. Buying connectivity first and hoping the architecture will follow is an expensive way to discover that the business has two sites but one bottleneck.
Voice and Connectivity should support the customer journey
A second site also raises questions about telephony. Should calls ring at one location, both locations or a central team? Can staff answer the same business number remotely? How are calls routed when a site is closed? Is the business paying for unused lines or legacy mobile contracts?
Modern Voice and Connectivity can provide centralised call routing, cloud telephony, shared numbers, hunt groups and integrated collaboration. The goal is not to purchase fashionable features. It is to make the organisation appear as coordinated to customers as it is on the organisational chart.
Voice over IP, hardware and telecoms procurement can be delivered as bolt-on execution services. The strategic decision remains: how should customers, suppliers and employees communicate as the business expands?
Acquiring a smaller competitor: treat technology as due diligence
An acquisition can bring customers, capability and regional reach. It can also bring unsupported servers, duplicated systems, expired licences and a surprising number of passwords stored in spreadsheets.
IT due diligence should take place before completion, not after the acquired team arrives at the new office.
At a minimum, assess:
- Core business applications and data ownership
- Contracts, licences and renewal dates
- Connectivity, telephony and network equipment
- Cyber security controls and known incidents
- Backup arrangements and recovery times
- Device age, operating systems and patching
- User accounts and privileged access
- Third-party suppliers and dependencies
- Any transitional service arrangements
- Regulatory and data protection responsibilities
The integration plan should distinguish between what must be standardised immediately and what can be migrated over time. Attempting to change every system on the first weekend creates avoidable operational risk. Leaving everything untouched creates a permanent two-tier business.
Where an acquired company relies on IBM i, Power Systems or AS/400 environments, specialist assessment is essential. These platforms can be highly valuable and deeply embedded in operational processes. They should not be treated as disposable simply because they are older. IBM i Management requires an informed approach to continuity, skills, integration and modernisation.
Helpdesk Support must become part of the operating model
As staff numbers rise, informal support does not scale. The helpful colleague becomes a bottleneck, managers lose visibility of recurring issues and important requests are handled through untraceable messages.
Effective Helpdesk Support provides more than a place to report faults. It creates operational intelligence.
A mature support model should provide:
- One clear route for raising requests
- Prioritisation based on business impact
- Defined response and resolution targets
- Device and user records
- Escalation to appropriate technical specialists
- Knowledge articles for repeatable issues
- Trend reporting for recurring problems
- Support for employees regardless of site
The most valuable output is often not the ticket closure. It is the pattern behind the tickets. If new starters repeatedly cannot access a system, the onboarding process needs attention. If one site reports recurring wireless issues, the Network Solutions design may need review. If a department keeps requesting the same application, the business may have an unmanaged process that deserves strategic consideration.
Helpdesk Support is therefore both a service and a source of evidence for the technology roadmap.
Managed IT Services should execute the roadmap
Managed IT Services are most valuable when they are aligned to a defined business strategy.
The consultancy layer should establish priorities, risk tolerance, service expectations and investment principles. Execution can then be delivered through an appropriate combination of internal staff, the consultancy team and a trusted network of specialist channel partners.
This model provides flexibility without pretending that every technical capability must be built in-house. It also avoids the opposite mistake: outsourcing responsibility without retaining strategic control.
Traditional MSP functions such as hardware procurement, print management, network monitoring, software licences, hosted telephony and routine support remain useful. They are bolt-ons that help deliver the plan. They should not become the plan.
Build Disaster Recovery before the next incident
Growth increases dependency. When a business has more people, more sites and more digital processes, an outage affects more than the IT department.
Disaster Recovery planning should consider:
- Which systems are critical to trading
- How much data the business can afford to lose
- How quickly each service must be restored
- Whether recovery works if the main site is unavailable
- How staff will communicate during an outage
- Who can authorise emergency decisions
- When backups were last tested
Cloud adoption can improve resilience, but cloud is not a magic word for continuity. Recovery still requires defined responsibilities, tested procedures and an understanding of supplier dependencies.
A sensible roadmap will treat resilience as an investment decision. The question is not whether perfect continuity is affordable. It is which interruptions the business can tolerate, and what protection is proportionate to the risk.
A practical growth-readiness sequence
For a UK SME preparing for a new site, new staff or an acquisition, the sequence below provides a useful starting point:
- Clarify the business change: define the commercial objective, locations, headcount and timescales.
- Assess the current estate: document systems, suppliers, contracts, risks and operational dependencies.
- Create the target architecture: decide how Cloud Solutions, Network Solutions, Voice and Connectivity and security should work together.
- Set the support model: define Helpdesk Support, escalation routes and service expectations.
- Review costs, use Technology Expense Management to remove waste and align contracts with demand.
- Plan continuity, confirm Disaster Recovery priorities and test restoration.
- Deliver in stages, use specialist partners for technical execution while retaining strategic oversight.
- Measure outcomes: review service data, user productivity, risk reduction and total technology cost.
For broader business growth and operational support beyond IT, the Evestaff group of services provides a useful gateway to the wider organisation.
Growth is not a reason to buy more technology. It is a reason to make better decisions about the technology already shaping the business.
That is the difference between scaling an IT estate and designing one that can scale.
SEO keywords: Cloud Solutions, Disaster Recovery, Dynamics 365 Jump Start, Helpdesk Support, IBM i Management, Managed IT Services, Network Solutions, Technology Expense Management, Voice and Connectivity, UK SME IT support, multi-site IT strategy, business technology consultancy, Microsoft Dynamics 365 Business Central.
Join The Discussion