The choice is simpler than the industry makes it sound: if you have no internal IT staff, you need fully managed IT support, where the provider becomes your IT department. If you have an internal IT person or team you want to keep, you need co-managed IT support, where the provider works alongside them. Everything else is detail, and this guide walks through the detail honestly: what each model includes, what each costs, and the situations where the obvious answer is wrong.
What is fully managed IT support?
Fully managed means end-to-end ownership: the provider runs your helpdesk, devices, network, servers and security as a single service, and your team has one number to call for anything IT-shaped.
A proper fully managed service for a Norfolk SME should include unlimited helpdesk and on-site support, device, server and network management, layered cyber security built in, backup management, vendor liaison (so you never sit on hold to a broadband supplier again) and regular strategic reviews. Delivered right, it means a 30-person firm in Norwich gets the IT department of a much bigger company, without the salaries.
What is co-managed IT support?
Co-managed means your internal IT person or team stays in charge, and the provider adds what they're missing: capacity, specialist skills, enterprise tooling and cover.
Typical co-managed arrangements include overflow helpdesk (the provider absorbs ticket spikes), holiday and sickness cover (your one-person IT department can finally take two weeks off), project and migration support, security uplift and posture reviews, and access to specialist tooling and vendor relationships an individual could never justify buying alone. The internal person keeps the context and the keys; the provider brings depth and resilience.
How do the two models compare?
| Fully managed | Co-managed | |
|---|---|---|
| Who's it for | No internal IT staff | An internal IT person or team |
| Who owns day-to-day IT | The provider | Your internal team, with the provider behind them |
| Your team calls | The provider's helpdesk | Your IT person, or the helpdesk for overflow |
| Security | Provider-run, built into the package | Shared: provider tooling and review, internal operation |
| Typical pricing | Per user per month, all-in | Lower per-user fee, or a tailored scope |
| Main risk | Picking a provider who oversubscribes technicians | Blurred responsibilities nobody wrote down |
On cost: co-managed is usually cheaper per user than fully managed because your internal team carries part of the load, but the total cost (their salary plus the contract) is of course higher than either alone. The comparison that matters is against the alternative: a second IT hire, or the risk of one person carrying everything. Our guide to what IT support costs for a Norfolk business covers the pricing models both arrangements use.
When is fully managed the right call?
When IT is nobody's job, or has become somebody's second job. That second pattern is the one to catch early.
In businesses between 10 and 150 people across Norfolk, IT very often lives with "whoever's good with computers": an operations manager, a finance director, an accounts assistant with admin rights. It works until it doesn't, and the cost is invisible: their actual job suffers, nothing is documented, security is whatever got set up in 2019, and when they leave, the passwords leave with them. If any of that sounds familiar, fully managed support isn't an upgrade to your IT so much as the first time your IT has existed as a managed thing at all. It's also the model where the provider-choosing questions matter most, because you're handing over everything; our guide to choosing an IT support company in Norwich and Norfolk covers how to pick well.
When is co-managed the right call?
When you have good internal IT that's stretched thin, out of depth in one area, or a single point of failure.
The classic cases we see across Norfolk and Suffolk:
- The one-person IT department. Capable, trusted, and unable to be ill, on holiday and at a conference. Co-managed gives them cover and a colleague.
- The stretched team at a growing firm. Headcount grew 40 percent; the IT team didn't. Overflow helpdesk absorbs the spike without a new hire.
- The security gap. The internal team runs operations well but security has moved faster than any generalist can track. The provider brings the tooling, monitoring and certifications; a guide like ours to Cyber Essentials for Norfolk businesses is often where that conversation starts.
- The project mountain. A migration, an office move, an ERP rollout. The provider supplies the project muscle; the internal team keeps the lights on.
One thing to watch: some providers quietly treat co-managed as a sales route to replacing your internal person. That's not what it's for. A good co-managed provider makes your IT person better at their job and more able to take a holiday, and says so out loud. (For transparency: we offer both models, we name them exactly as this article does, and we think a good internal IT person is something to keep, not compete with. This page is Snap IT's, so weigh that as you read.)
Can you switch between the models later?
Yes, and planning for it is a sign of a healthy relationship. Businesses grow into internal IT hires, and internal teams sometimes shrink.
A 25-person firm on fully managed support might hire its first IT manager at 60 people and shift to co-managed. A firm whose long-serving IT person retires might go the other way. The contractual questions are the same ones as any provider relationship: what does the transition cost, who owns the documentation, and how cleanly are responsibilities redrawn. If you're changing model and provider at the same time, read our guide to switching IT provider in Norfolk without the disruption first.
Frequently asked questions
What's the difference between fully managed and co-managed IT?
Fully managed: the provider is your entire IT department. Co-managed: the provider works alongside your existing internal IT staff, adding capacity, specialist skills and cover. The deciding factor is simply whether you have internal IT people you want to keep.
Is co-managed IT cheaper than fully managed?
Per user, usually yes, because your internal team does part of the work. Including the internal salary, the total is higher, but the honest comparison is co-managed support versus a second IT hire, and there co-managed usually wins on both cost and breadth.
At what size does a business need an internal IT person?
There's no fixed threshold; it's driven more by complexity than headcount. Plenty of 100-person cloud-based firms run happily on fully managed support, while a 50-person manufacturer with production systems might justify an internal hire plus co-managed backup.
Will a co-managed provider try to replace our IT manager?
A good one won't, and will say so explicitly. Ask the provider to define the split of responsibilities in writing; vagueness there is where both bad intentions and honest misunderstandings live.
Does co-managed IT work for a one-person IT department?
It's arguably the model's best use case: holiday and sickness cover, a second pair of eyes, escalation for the weird problems, and an end to the single point of failure.
Which model is better for security?
Either, done properly. Fully managed puts one accountable party behind everything; co-managed pairs internal knowledge with specialist tooling. What matters is that responsibilities (patching, monitoring, backup testing, incident response) are explicitly assigned, never assumed.
