You've outgrown your MSP agreement. You're still not an enterprise account.
Too big for one, too small for the other
Two commercial models serve Microsoft-heavy companies today, and both were sized well away from a few hundred employees. This is about scope and pricing, held apart from whether your provider is good at their job.
Your current IT agreement
Scoped for the company you were when you signed it
Ticket queues and generalist coverage got you here, and for plenty of companies that is exactly the right arrangement. The scope was written for a smaller environment, ahead of the Microsoft estate with hundreds of employees and a board that asks about security posture.
Enterprise-priced security vendors
Built for deployments in the thousands of seats
Seat minimums sized for a much larger deployment, and a quoted number that has a way of moving once the scoping call happens. The commercial model was built for a much larger footprint.
Both models are sized for a different company than yours. The rest of this page is about the space in between.
What right-sized looks like
Three things a company at your scale should expect, and rarely gets from either category above.
Named operators
A real team with names. The engineers who join your onboarding calls are still the ones running your identity, devices, and cloud tenants a year in.
See managed ITOne cross-domain platform
Identity, devices, cloud, security, and compliance, visible in one system, in place of the four or five vendors a growing company usually accumulates.
Explore the platformTransparent, published commercial terms
A plan structure you can read before a call ever happens, sized for a few hundred seats and published the same way for every company at your scale.
See plansSecurity and compliance, from the same operators
The people running your identity, devices, and cloud tenants also handle managed detection and response across endpoint, identity, cloud, and email, correlated and triaged by operators against the coverage tier you choose. It is one team's work, priced as a hand-off to a separate security vendor.
Where your framework work depends on how we operate your environment, inherited controls maps which control families move onto our side of the line, and security and compliance covers the frameworks themselves, from SOC 2 to HIPAA.
Reading this as the provider?
A client outgrowing the scope you signed is a normal part of their growth, and it does not have to end with them leaving. We run security and compliance underneath MSPs as a named subcontractor, and we take referrals when the whole function needs one operator. See how we work with MSPs.
One estate, one system
Identity, devices, cloud, security, and compliance, on one system.
The platform is the front door for everything we run: access requests, tickets, evidence, and the incidents our operators are working, in a system built for a few hundred employees from the start.
See the terms, or meet the team.
A published plan structure sized for your estate, or the full operated partnership end to end.
Published structure with a written annual escalator cap, sized for a few hundred seats.
Named operators and one accountable lead, with the scope of what we take on stated plainly.