What is co-managed IT, and how does it work beside an in-house IT team?
Co-managed IT means an outside provider works beside your own IT person or team instead of replacing them. Your team keeps the work it knows best, such as the helpdesk, hands-on support and projects; the provider adds what one person or a small team cannot cover alone, starting with security monitoring around the clock. At Strata Modus, co-managed IT is priced on the same published per-seat tiers: Business Basics $127, Cyber-Insured Core $179, Zero-Trust Compliance $258, Managed Cloud & AI for Business $335 a seat a month.
What your IT team keeps
- The first-line helpdesk: everyday tickets, answered by people your staff already know, with harder problems escalated to us.
- Onsite hands-on work: desks, printers and hardware in the building.
- Their own admin rights, under their own named accounts.
- Projects and the vendors of your line-of-business software.
What we add
- Huntress managed EDR and identity threat detection, watched by a 24/7 human security operations centre. One person cannot watch alerts every night.
- NinjaOne monitoring with automated operating system and third-party patching
- Dropsuite immutable backup for Microsoft 365 or Google Workspace
- DNSFilter DNS blocking
- Escalations from your team, within your tier's response times.
- Our own admin access granted just in time, behind hardware multi-factor keys, with no standing admin accounts on our side.
Priced on the same tiers
Co-managed IT uses the same per-seat prices as every other agreement, with the same 5-seat monthly minimum and Microsoft 365 or Google Workspace billed at cost on its own line. Cyber-Insured Core is where the 24/7 security operations centre starts.
Not sure which tier fits beside your team? The 360 Cyber, Cloud & Cost Diagnostic at $4,312.50 reviews your accounts, devices, backups and cloud costs, credited in full to an onboarding sprint on Cyber-Insured Core or above signed within 30 days.
Settle these before you start
- Which tickets your team answers, which come to us, and how a ticket moves between you.
- Which named accounts hold admin rights, and how often that list is reviewed.
- Who approves a production change. Ours ship with written rollback steps and an architect's sign-off.
- Where the documentation lives, so both teams work from the same record.
- Who calls which vendor when something breaks.