What AIS takes on in a co-managed agreement
The split is yours to set. These are the pieces most co-managed clients hand to AIS first:
- Monitoring and alerting, 24/7/365, with ticket triage so your team wakes up to a summary, not a pager.
- Help desk overflow, after-hours and onsite coverage, so your people stop being the only line.
- Patching, endpoint management and server lifecycle work across Microsoft 365, Azure, AWS, Google Cloud, Cisco, Meraki and Veeam.
- Managed Cybersecurity: security awareness training, email and content filtering, dark web monitoring, and the option to add Managed Detection and Response.
- Backup and disaster recovery, tested on a schedule, with the results in writing.
- Vendor management, so your team stops being the go-between for carriers, ISPs and software vendors.
- Project engineering capacity: migrations, network refreshes, Microsoft 365 security hardening, delivered alongside your team rather than instead of it.
- vCIO access for roadmap, budget and risk conversations with leadership.
What your team keeps
Whatever you decide. Most internal teams keep line-of-business applications, the relationships with department heads, local onsite presence, and the projects that define their roles. Many keep tier 1 help desk and hand AIS tiers 2 and 3. Some do the reverse. The point of the model is that your best people spend their time on the work only they can do.
How a co-managed engagement starts
Every co-managed engagement starts with a documented environment review: what you run, who touches it, where the gaps are, and what keeps your IT lead up at night. From that we build the responsibility matrix, agree the service levels, connect your environment to our monitoring and documentation platforms, and introduce your team to the engineers they will work with. Most clients are fully onboarded in 30 to 45 days. The responsibility matrix is reviewed every quarter.