Managed IT and security with a clear owner.

Choose the responsibility that fits.

Monitor — $49–$79 per user per month; site minimum $499. Visibility and routine review for an organization that retains its own IT operating owner. This is not outsourced help desk or incident response.

Protect — $119–$159 per user per month; site minimum $750. Business-hours support and the named endpoint, email and backup responsibilities in the service schedule.

Operate — $159–$219 per user per month; site minimum $1,250. Protect with a defined allocation of vendor coordination and executive technology work.

These are planning ranges, not all-inclusive quotes. Covered users, devices, licenses, onboarding, remediation, storage, sites and additional work are identified in the proposal.

Compare Plan Responsibilities

Support is only part of the operating relationship.

Maintenance, access, backup review, exceptions, documentation and escalation need owners too. Before service begins, we identify the covered environment, support channels, service windows, permissions and the work retained by your team or other providers.

Start service with evidence.

Confirm inventory and access. Enroll the agreed controls. Record backup status and perform the restore tests in scope. Verify the support path. Review outstanding exceptions and acceptance before treating onboarding as complete.

See Onboarding and Acceptance

Keep decisions visible.

The operating review records completed work, open risks, client decisions, upcoming changes and the next priorities. Support-response targets concern initial engagement; resolution depends on the issue, access and relevant dependencies.

Keep projects and specialist work clear.

Server administration, major migrations, on-site work, incident forensics, MDR and after-hours response are not silently included in every per-user plan. Each is identified when part of the engagement.

Need engineering beside an existing team? Explore Co-Managed IT.

An example of the operating review

Illustrative example: a covered system has no agreed maintenance window. The client owner selects a window, the delivery lead records the change plan, and the completed maintenance is reviewed against the acceptance criteria. This is an example of the process—not a client result or automatic service commitment.

Start with your environment.

Tell us the approximate number of users, locations, current provider arrangements and the issue that needs attention. We will identify the appropriate assessment and service model.

Compare the existing plan responsibilities.

The assessment establishes the environment, then the written service schedule identifies the actual responsibilities. The planning bands and minimums below are unchanged.

The executed agreement governs scope. Existing planning bands remain available for comparison. Covered systems, support hours, response targets, device allowances, backup testing, and reserved leadership capacity are confirmed in the applicable service schedule.

Useful checklists for the next decision.

These public resources are available to review before an assessment. They do not replace a scoped engagement or written agreement.

• Technology Roadmap & Decision Brief
• Microsoft 365 Migration Readiness Checklist
• Recovery Validation Checklist
• Lead-to-Revenue Workflow Checklist