By Dan Stark
Before you approve another IT salary or sign a support agreement, identify the work your current setup can’t reliably cover.
Daily requests may need more hands. A migration may need a specialist. Vacation weeks may need backup. A problem bouncing between vendors may need someone with the authority to keep it moving.
If you’re considering outsourced IT support for small business, compare it with what an internal hire or shared arrangement could cover.
Consider an internal hire when sustained work justifies a dedicated role. Company knowledge or regular on-site work can strengthen the case. Outsource when a provider can cover defined responsibilities you’d otherwise need to build internally. Combine both when your internal team needs capacity, specialist skills or dependable backup.
If the real gap is that nobody has the authority to own a problem, fix that first. It may not need a hire or a contract.
Identify the gap before choosing the model
Use four questions to identify where the current arrangement falls short.
Capacity: Is there more work than the team can finish?
Look at what gets postponed. Are routine requests eating the time set aside for maintenance, onboarding or projects?
Separate recurring demand from temporary work. A sustained workload may support another internal role. A one-time migration may only call for a scoped project. Assigning some day-to-day help desk support externally can free internal IT to concentrate on business-specific systems.
Expertise: Does the work need a skill you don’t maintain internally?
An employee who knows your business applications may still need specialist help with identity, networking or a cloud change. Decide how often you need that expertise and whether it’s worth developing internally.
One specialized project is a different hiring case from work the business needs every week.
Coverage: What happens when the usual person is unavailable?
Check vacations, illness, multiple locations and the hours your people actually work. Another employee or an outside team can fill the gap, provided the coverage is assigned and funded.
A provider contract alone doesn’t establish after-hours or on-site availability. Confirm both for the locations and work involved.
Ownership: Who keeps an issue moving across teams?
When the application vendor blames the network and the network provider points back, someone needs the authority to decide the next step and update the business.
Clarifying responsibilities in the arrangement you already have can close this gap. Adding a person or a provider without that authority leaves the same problem in place.
Compare in-house, outsourced and co-managed IT
In-house IT puts the primary support work with employees. Outsourced IT assigns defined work to an outside provider. Co-managed IT divides that work between internal IT and a provider.
These arrangements can change as the business grows. An internal team can bring in specialists, and a fully outsourced arrangement still needs someone inside the business who can make or obtain decisions.
| Model | Conditions that favor it | What to plan for |
|---|---|---|
| In-house | Sustained work can justify a dedicated role. Business-specific knowledge or regular on-site needs can strengthen the case. | Recruiting, management time, tools, documentation, specialist help and coverage when that person is out. |
| Outsourced | You need a defined support function and access to skills you don’t want to build entirely inside the business. | Provider onboarding, assigned internal roles for coordination and approval, exclusions, project charges, location-specific coverage and handover terms if you leave. |
| Co-managed | Your internal team has valuable context but needs more capacity, specialist skills or dependable backup. | Clear responsibility boundaries, shared records, escalation paths and the time it takes to coordinate two teams. |
Documentation, specialist skills and dependable coverage aren’t features of one model. They’re work you assign and fund under any of them.
CTMS offers managed and co-managed IT support, including support alongside an existing IT employee or team. CTMS’s Ohio-based engineers staff its help desk. Exact services and responsibilities depend on the agreed scope.
For a service breakdown, see what managed IT services can include.
Make the handoffs work before changing the team
Consider a business with one IT employee who understands its applications but is struggling to get new employees ready while handling daily requests. Co-managed support could divide that workload while keeping the employee involved in business-specific decisions.
Map responsibilities for one routine workflow: getting a new employee ready to work.
The table below is an illustrative allocation to agree on, not a CTMS case study or standard contract. Business approval stays with the business. Technical execution goes to whoever holds that responsibility.
| Step | Business approval | Internal IT | Outside provider |
|---|---|---|---|
| Define the request | Manager confirms the role, start date and equipment needs. Authorized owners approve access. | Checks local requirements and flags exceptions. | Confirms the assigned work and asks for any missing information. |
| Prepare access and equipment | Designated approver resolves exceptions under company policy. | Handles assigned local setup and application dependencies. | Configures assigned accounts and devices using approved instructions. |
| Confirm readiness | Manager confirms the employee can do the required work. | Coordinates final checks and follows up on anything missing. | Records completed work and lists unresolved tasks. |
Name one coordinator to track the request, follow up on unfinished work and report completion. Assign vendor contact and approval authority explicitly. Those responsibilities can sit with different people. A finished device task should not hide unfinished application access.
Use the same discipline for projects and multi-vendor issues: one shared work record, a named coordinator, clear approvals and a way to escalate work outside the agreed scope.
The roles shift with the model. In a fully outsourced arrangement, an internal business contact supplies the context. With an internal team, employees handle assigned technical work and can bring in specialists for defined tasks. The approver and the completion check stay either way.
Keep business decisions assigned
Leadership still sets priorities, approves budgets and decides which risks the organization will accept. Access approvals can be delegated to authorized managers or system owners under company policy. Document who can approve what so the technical team has clear instructions.
NIST’s Cybersecurity Framework 2.0 places responsibility for cybersecurity risk with organizational leadership and calls for clear roles, responsibilities and authority. It doesn’t prescribe a staffing model.
Technical teams can recommend and implement changes. They still need business direction on priorities and acceptable disruption. Where that direction is missing, IT planning and leadership support may belong alongside day-to-day support.
Compare the same work and coverage
A salary and a monthly provider fee are different starting points. Build the comparison around the work each option actually covers.
- Internal staffing: Compensation, benefits, recruiting, training, management time, tools, specialist contractors and leave coverage.
- Outside support: Recurring fees, transition work, separate projects, licensing, on-site work, after-hours terms, exclusions and your own coordination time.
- Co-managed support: Both sets of costs, with clear responsibility for tools and licenses. Don’t count the same charge twice, but do count overlapping products you’ll keep paying for.
Match the supported users, systems, locations, service hours and project responsibilities before comparing totals. Separate recurring operations from one-time transition costs and planned projects. Include exit and handover requirements when evaluating a provider agreement.
For provider fee structures, see how managed IT pricing is organized. Compare equivalent scope rather than assuming either option is cheaper.
Prepare these six things before requesting a quote or opening a role
The same inventory improves a provider conversation and an internal job description:
- Demand: Recent requests by type, recurring problems and work currently handled by employees whose main job isn’t IT.
- Environment: Users, devices, locations, critical applications, vendors and the people who own each system.
- Internal capacity: Current responsibilities, specialist skills, unfinished work and dependable backup during absences.
- Coverage: Work schedules, remote and on-site needs, and the urgent situations the business must be able to handle.
- Upcoming work: Projects, deadlines, dependencies and the internal participation each will require.
- Costs and authority: Existing contracts, tools, licenses, budgets and the people authorized to approve access, spending and changes.
Use it to name the gap. If clearer ownership closes it, make that change. If it needs more people or different skills, choose the model that provides them with explicit responsibilities.
Discuss the support model with CTMS
Bring your current arrangement, internal roles, locations, critical systems and the work that keeps slipping. CTMS can talk through managed or co-managed support around those needs, with services and coverage defined in scope.
