Responsibility map
Assign service desk, endpoint, identity, network, vendors, security, and projects.
MSP service economics
Price co-managed IT around the operating boundary
Co-managed IT becomes unprofitable when both teams assume the other owns triage, tooling, change, escalation, or user communication. Build price from the division of responsibility, shared systems, ticket flow, governance cadence, and coverage rather than discounting a full-service package.
What the decision depends on
FactorWhat to check
Workflow
Define intake, triage, escalation, change approval, documentation, and closure.
Coverage
Users, devices, sites, hours, after-hours, and internal-team capability.
Governance
Reporting, service reviews, roadmap, tooling administration, and improvement work.
A package the buyer can understand
Which team owns the first response, the final fix, the tool administration, and the user update for each service?
How to package it
Use a monthly platform and governance fee, then price the MSP-owned service lanes by user, device, or site. Add a ticket or engineering band for shared queues and document which team holds change authority.
Margin stress case
Test a month when the internal team forwards twice the expected ticket volume and escalation quality falls. The shared-workflow band should expose the labor consequence before the relationship becomes a discounted full-service plan.
Worked example
Illustration: a $12,000 monthly co-managed agreement carries $8,000 of expected platform, governance, and delivery cost, leaving about 33% gross margin. A poorly controlled shared queue adds $2,600 of engineer time, reducing margin to about 12%. The agreement needs a ticket band and a responsibility review trigger.
Questions owners ask
Should co-managed IT cost less than fully managed IT?
Only when the retained customer responsibilities reliably remove MSP workload. Shared queues and governance can add work even when the internal team keeps technical duties.
How should ticket volume affect co-managed pricing?
Set an expected band, define what enters the MSP queue, and establish the review or overage action when volume or escalation complexity moves outside it.
What belongs in the responsibility map?
Cover intake, triage, tools, changes, escalation, closure, user communication, reporting, and after-hours ownership for every service lane.
Get a second opinion on this decision
Send your website and the decision you are weighing. We will confirm the price, then send the payment link and a short intake.