Co-Managed IT

Backup for your IT team, without replacing it.

Your internal IT staff knows your business. We add senior engineering, security tooling, and extra hands, working inside your management tools or alongside them. Who owns what, how we get access, and how it ends are all agreed in writing before we touch anything.

What's included

How we help

Escalation support

Senior engineering help for the complex server, network, identity, and security issues your team doesn't see every day.

Security tooling & alert response

EDR, email security, and vulnerability scanning, in your stack or ours, with alert routing agreed up front so nothing lands in a mailbox nobody reads.

Patching & maintenance

Workstation and server patching on a schedule you approve, with maintenance windows and a plan for the patches that fail.

Backup oversight

Someone watching the backup jobs and running scheduled restore tests, so your backups are proven rather than assumed.

Project capacity

Migrations, upgrades, and rollouts scoped and quoted separately, with your team involved so the knowledge stays in-house.

Coverage when your admin is out

Continuity for a one- or two-person IT department during vacations, sick days, and turnover.

Knowledge transfer

We explain the why, not just the fix, and help a junior admin grow into the work.

Reporting for leadership

A monthly asset inventory, patch status, and open-issue summary your IT lead can hand to management.

Engagement models

Four ways to work together

Every co-managed engagement answers the same question for each tool: yours, ours, or one we share? Pick one model for everything, or mix them tool by tool.

1

Integrate

We work inside your tools.

You grant us a sysadmin-level role in your existing management tool. We support workstations and servers from there, but we never change the tool's own configuration. Each side keeps its own stack.

2

Parallel

Separate tools, separate access.

We deploy our own management and ticketing tools alongside yours. Neither side has access to the other's tools, and the boundary between them is written down.

3

Shared

One mutual tool, owned by you.

We agree on one platform and set it up with your organization as the account owner. Both sides work in the same queue with the same history.

4

Bootstrap

For smaller IT shops.

We set up the tools in your name from day one and run them for you, and you have full access to your own data throughout. As your team matures, admin rights hand over to you on a schedule we agree.

Tool by tool

How each tool works under each model

Computers need one central management point, and we need remote access to fix things. Beyond that, every choice is yours. Under the bootstrap model we start in the shared column and hand the admin seat to you when you're ready.

ToolIntegrateParallelShared
Endpoint management (RMM)A sysadmin-level role in your RMM to monitor, patch, and support devices. We don't change the tool's own configuration.Our RMM agent goes on the devices you assign to us. Your tool and ours never see each other.One RMM, with you as the account owner and both sides as technicians.
Remote accessWe connect through your remote-access tool, using our own named accounts, with sessions logged.Our remote-access tool, installed only on the devices in our scope. We export the access logs on request.One remote-access tool with session logs both sides can review.
TicketingTickets are assigned to us in your system, and we work and update them there.Our ticketing for the work you send us, with a shared view or a regular export so you keep the history.One queue and one history, with both sides in it.
Security toolingWe work inside your EDR, email security, and scanning tools, with alerts routed as agreed.We run our security stack on the devices in our scope and route alerts to whoever you choose.One security stack, with alert routing and response ownership agreed up front.

Documentation and passwords are never a parallel tool. We write documentation as we work, and a copy is replicated automatically to storage you own, such as your SharePoint, in a format you can open without us. Passwords live in a vault your organization owns. If we part ways, the latest copy is already yours.

Responsibilities

Who owns what

A starting point we fill in together before work starts. One accountable owner per row, so nothing falls between the two sides.

R does the workA approves and owns the outcomeC consulted firstI kept informed
ActivityYour leadershipYour IT teamDefense GridNotes
First response for your usersIA RCYour team is the first call unless we agree otherwise in writing.
After-hours urgent issuesIARYour team decides what counts as urgent. Support hours are Mon–Fri, 9am–4pm ET. Urgent issues outside them reach us by email.
Escalated technical issuesIARServer, network, identity, and security problems your team hands to us.
Patching and maintenanceIARYou approve the schedule and windows. We run it for the devices in scope.
Backups and restore testsIARWe watch the jobs and run the tests. You own the recovery targets.
Security tooling and alertsIARAlert routing and response ownership agreed up front.
Security incidentsARRYour leadership declares the incident and makes the business calls, including when to bring in your insurer and attorney. We isolate affected devices under a standing approval, preserve evidence, and work alongside your insurer's response team.
Changes to your environmentIARWe propose, carry out, and log. Someone you've named approves.
Identity and your Microsoft 365 or Google tenantIA RRYou keep global admin. We work through a delegated role.
Purchases, licensing, and vendorsARCEverything stays in your name. We recommend and coordinate.
ProjectsACRFixed scope and fixed price, with your team involved.
DocumentationIARWe write it. A copy lives in storage you own.
Handover when the engagement endsARRMethod agreed at the start. Access revoked and verified.
In practice

What a co-managed week looks like

Four ordinary situations, and who does what in each. None of them promises a response time. They show where the line sits.

The file server stops responding at 10 a.m., and your admin is in a meeting.

Your teamLogs the ticket, tells users, and hands it to us.

Defense GridGets temporary access to the server, finds the cause, brings the service back, and writes up the cause and the fix in your documentation the same day.

ResultYour admin comes out of the meeting to a fixed server and a write-up, not a mystery.

Your only admin is on vacation and a new hire starts Monday.

Your teamTells us the week before and approves the standard setup.

Defense GridCreates the account in your tenant through our delegated role, enrolls the laptop in your management tool, turns on MFA, and sends the welcome instructions.

ResultThe new hire works on day one. Your admin comes back to a documented setup, not a backlog.

A user reports a phishing email they clicked.

Your teamHandles first response: resets the password and tells us.

Defense GridChecks the sign-in logs, revokes sessions and tokens, looks for mailbox rules and forwarding, checks whether anyone else got the same message, and recommends tenant changes.

ResultThe thing most small incidents miss, the hidden mailbox rule, gets found.

You decide to leave us.

Your teamGives notice and names who receives the handover.

Defense GridRuns the handover agreed at the start: data export, a meeting with your IT leadership, and third-party contacts. Then our access is removed and you get written confirmation.

ResultNothing to migrate, because it was always yours.

Getting started

Your first 90 days

Co-managed IT fails when both sides assume the other owns a task. The first three months are about removing that assumption, then proving the setup works, including the part where you could leave.

Days 1 to 30

Agree and connect

  • Kickoff with your IT lead: what you have, what hurts, which tools exist.
  • A model chosen per tool. If you don't have a management tool, the handover method is agreed now.
  • Responsibilities filled in and the not-included list written down. One page, signed by both sides.
  • Named accounts with MFA, a delegated role, and just-in-time access set up. Agents on in-scope devices, or roles granted in your tools.
  • Inventory and documentation baseline, with replication to your storage running.
  • Week 3: a simulated incident. About 45 minutes with your IT lead and one leader, walking the responsibilities through a ransomware alert at 2 a.m., plus a live isolation of a test device. Whatever the walk-through exposes gets fixed.
Days 31 to 60

Stabilize

  • Patching on schedule, the first maintenance window, failed patches handled.
  • Alert noise tuned down and routing confirmed.
  • The first backup restore test.
  • Security baseline gaps, such as MFA coverage and local admin rights, closed or scheduled.
  • The first monthly report, and a check that tickets are flowing to the right side.
Days 61 to 90

Run and prove

  • The exit test. We confirm the documentation replica and the data export actually work. A restore test for the relationship.
  • Responsibilities adjusted from real experience.
  • A monthly 30-minute review agreed.
  • A project roadmap with fixed quotes.
Access and changes

How we get access, and how it ends

Letting an outside engineer into your systems should make you safer, not more exposed. These rules apply under every model.

Named accounts, never shared logins

We get our own named admin accounts in your directory and your tools, so every action traces back to a person.

MFA on everything

Every account we hold with you has multi-factor authentication turned on, including the emergency ones.

Least privilege

Only the roles the work needs. You keep the global administrator and emergency access accounts in your tenant, and we work through a delegated role. A sysadmin role on devices doesn't mean a global administrator role.

Just-in-time access to support platforms

Standing admin rights are the exception. For device-level work, our elevated access is time-boxed, expires on its own, and your team is notified when it's used. For tenant-level roles, someone you've named approves each elevation. Where a platform can't do either, our admin account stays disabled until your team enables it for the work.

Logged sessions

Remote sessions and admin actions are logged. In your tools, your team can review them directly. In ours, we export the access logs on request.

Change control

No configuration change without approval from someone you've named, and a change log both sides can see.

Handover agreed at the start

If you don't have your own management tool when we begin, we agree then how everything will be handed over, not at the end. The handover is a short fixed-price engagement, listed as a line item on the agreement you sign, covering data export, a handoff meeting with your IT leadership, and any third parties.

A clean exit

When the engagement ends, our access is revoked, the revocation is verified, and you get written confirmation.

Pricing

How co-managed IT is priced

Per user per month is the standard, for the people whose devices are in our scope. Your team stays the first call for those users.

Per device per month when our scope is servers and network equipment and we never touch users' devices. Per-user would be the wrong unit there.

Projects are fixed scope and fixed price, quoted before work starts, as on every engagement.

The handover is a short fixed-price engagement, listed as a line item on the agreement you sign at the start. Under the integrate model it's included, because it's mostly removing our access and a meeting.

A monthly minimum applies for small teams, and the quote says exactly what it is. Nothing is hourly.

How pricing works
Ownership

What stays yours

Everything. Co-managed IT only works if your team can walk away from us without losing anything.

  • Your Microsoft 365 or Google Workspace tenant, in your name, with you holding the global administrator and emergency access accounts
  • Documentation of your environment, replicated automatically to storage you own, in a format you can read without us
  • Passwords, in a vault owned by your organization
  • Backups, licenses, and vendor contracts, all in your name
  • Tools set up under the shared or bootstrap models, with your organization as the account owner
  • If you leave, you keep all of it. There is nothing to migrate away from us.
Scope

What's not included

A short list, so there are no surprises later.

  • Round-the-clock on-call. Urgent issues outside support hours reach us, but we don't promise 24/7 response.
  • Being your users' first call, unless that's agreed in writing.
  • Changing the configuration of your management tools under the integrate model.
  • Work outside the agreed scope. Anything extra is quoted and approved first.

Let's make IT simple.

Request a free, no-pressure consultation. We'll talk through your environment, your concerns, and where to start.