Co-Managed IT Pricing Models: How to Structure Profitable Partnerships
The most common pricing mistake MSPs make when entering their first co-managed engagement is to treat it as a discounted version of fully managed services. The logic seems intuitive: the internal IT team handles some of the work, so we charge less. The client has existing capability, so we scope down and price down accordingly. The problem with that logic is that it produces contracts that are structurally underpriced from the start — ones where the MSP discovers six months in that the co-managed relationship is generating significantly less margin than the fully managed accounts it is displacing time from.
Co-managed IT is not a cheaper version of fully managed IT. It is a different service with a different cost structure, a different risk profile, and a different value proposition — and it needs to be priced on its own terms rather than derived by subtraction from a fully managed baseline. Getting the pricing right from the first contract is what determines whether co-managed becomes a profitable growth channel or an increasingly frustrating set of relationships that look good on paper and erode margin in practice.
Why Co-Managed Pricing Logic Is Different
In a fully managed engagement, the MSP owns the entire IT function. The pricing reflects that totality — helpdesk, monitoring, patching, security, strategic advisory, after-hours coverage, vendor management. The per-user fee is an all-in number because the scope is all-in. Knowing your cost of goods sold, applying a target gross margin of 50–70% as NinjaOne's February 2026 managed services pricing strategy recommends, and arriving at a per-user price is a relatively tractable exercise because the scope is bounded.
In a co-managed engagement, the scope is not bounded by the MSP — it is bounded by the negotiated division of responsibility between the MSP and the internal IT team. That division is different for every co-managed client, because every internal IT team has different capability, different gaps, and different areas they want to retain versus offload. The co-managed pricing challenge is not calculating a per-user rate for a fixed scope — it is pricing a variable scope that is defined by what the internal team cannot or chooses not to do, which can change as the internal team evolves.
As Datapath's April 2026 co-managed IT pricing guide frames it precisely: the right pricing model needs to reflect not just monthly support fees but service architecture, security maturity requirements, and the operational burden the internal team keeps in-house. Comparing co-managed proposals on inclusions, exclusions, onboarding assumptions, and after-hours support produces stronger outcomes than picking a monthly fee number in isolation. That insight applies equally to the MSP structuring the proposal as it does to the client evaluating it.
The Four Co-Managed Pricing Structures Available to MSPs
There is no single correct pricing model for co-managed IT. The right structure depends on the nature of what the MSP is providing, the predictability of the volume, and the commercial relationship the MSP wants to build. The four models below are the ones most commonly used by MSPs with established co-managed practices, each with distinct margin implications.
Modular per-service pricing. The MSP defines a menu of specific services — after-hours coverage, patch management, security monitoring, escalation support, vCIO advisory, specific project categories — and prices each as a line item. The co-managed client selects the modules relevant to their gaps and pays for those specifically. This model is transparent, easy for the client to understand, and naturally scoped to what the internal team cannot provide. It is also the model most vulnerable to underpricing individual modules when the MSP fails to fully account for the overhead of coordinating with an internal team. The co-managed relationship requires more communication, more documentation, and more handoff management than a fully managed account of the same user count — and that overhead needs to be priced into each module, not treated as invisible.
Tiered capacity model. Rather than pricing specific services, the MSP prices access to a defined level of support capacity — a set number of escalation hours, project hours, or engineer-hours per month at a fixed monthly retainer, with defined rates for consumption above the tier ceiling. This model is simpler to administer than modular pricing and produces more predictable MRR. Its weakness is that capacity tiers require accurate estimation of how much support the internal team will actually escalate, which is difficult to assess before the relationship is established. Setting tiers too low produces a frustrated client who regularly hits the ceiling; setting them too high produces under-utilised capacity that erodes effective margin.
Tooling-plus-escalation model. Many co-managed engagements are built around the MSP providing the tool stack — RMM, PSA, endpoint security, backup, documentation platform — as a managed service, with the internal IT team operating within those tools and escalating to the MSP for issues that exceed their capability. The MSP charges a per-user fee for the tooling layer and a separate escalation rate for engineer time. This model is particularly well-suited to co-managed clients who have competent internal IT capability but lack the enterprise tooling, vendor relationships, and specialist expertise that the MSP provides. The tooling fee generates stable, low-touch MRR; the escalation rate captures value for the higher-skill work without creating fixed capacity commitments.
Outcome-based retainer. The most sophisticated co-managed pricing model prices the MSP's contribution based on defined outcomes rather than inputs — a monthly retainer that covers the MSP's responsibility for specific service outcomes, such as SLA performance thresholds, security posture benchmarks, or uptime targets. This model is increasingly relevant as DeskDay's November 2025 MSP pricing guide notes, with value-based and fixed-fee models gaining traction because clients want predictable costs and fewer surprises. Outcome-based pricing is the model that most directly aligns MSP incentives with client results, but it requires mature measurement infrastructure and a level of confidence in delivery capability that most MSPs develop only after running co-managed engagements for some time. It is not the right entry point for a first co-managed contract.
The Pricing Variables That Determine Margin in Practice
Regardless of which pricing model an MSP chooses, the margin outcome of a co-managed engagement is determined by four variables that need to be explicitly assessed before the contract is signed.
| Variable | What to Assess | Margin Risk If Misjudged | Pricing Adjustment |
|---|---|---|---|
| Internal team capability level | How competent is the internal IT person or team? What can they genuinely handle independently versus what will consistently escalate? | Overestimating internal capability produces higher escalation volume than priced for | Conduct a capability assessment before pricing; build escalation buffer into capacity models |
| Environment complexity | How complex is the client's IT environment relative to their user count? Legacy systems, multi-site, compliance requirements all increase support cost | Per-user pricing on a complex environment underrecoveres against actual engineer time | Charge environmental complexity premium; use site survey or questionnaire before quoting |
| Coordination overhead | How much management time does the internal team relationship require? Weekly calls, documentation alignment, handoff management all have cost | Co-managed coordination overhead is invisible in fully managed pricing logic and destroys margin when unpriced | Build coordination cost explicitly into the monthly retainer; minimum 2–4 hours per month of senior engineer time |
| After-hours coverage scope | Is the internal team available after hours? What is the MSP's obligation during those windows? | Undefined after-hours scope in co-managed contracts creates on-call obligations that were never priced | Define after-hours scope explicitly in the service agreement; price overnight coverage as a specific add-on |
The coordination overhead row in that table deserves particular emphasis because it is the most consistently underpriced variable in co-managed engagements. A fully managed account of fifty users generates a predictable ticket queue. A co-managed account of fifty users generates a ticket queue and a relationship with an internal IT person who has opinions, questions, and escalation patterns that require management time to align and sustain. That management time has a cost, and it needs to appear in the pricing model rather than being absorbed as invisible overhead.
Where Offshore Staffing Changes the Co-Managed Economics
One of the most underappreciated applications of offshore staffing in the MSP context is the margin improvement it enables in co-managed engagements specifically. In a co-managed model, the MSP's primary cost driver is engineer time — the hours senior local technicians spend on escalations, projects, and strategic advisory. If L1 overflow and after-hours coverage are also included in the scope, those functions are consuming expensive local engineer time on work that does not require that cost level.
An offshore L1 technician handling the after-hours and overflow component of a co-managed engagement allows the MSP's senior local team to focus entirely on the escalation and advisory work that actually justifies their cost. The gross margin on the after-hours coverage module improves dramatically — the local senior engineer cost is replaced by an offshore L1 cost, while the module pricing to the client remains the same. For a co-managed MSP charging a 30% premium for after-hours coverage and delivering it through an offshore technician rather than a local on-call engineer, the margin on that module can approach 70–80% rather than the 30–40% that local on-call arrangements typically produce.
The Konnect guide on scaling your MSP from 50 to 150 clients without hiring locally covers how offshore staffing fits into the broader growth model for MSPs managing multiple account types simultaneously. The co-managed pricing and staffing structure is one of the highest-leverage applications of that model, because the co-managed client relationship generates higher lifetime value — with churn rates under 5% compared to the 8.4% industry average — and the margin improvement from offshore delivery compounds over the duration of that longer relationship.
Building the First Co-Managed Contract Correctly
The first co-managed contract is the one that establishes the pricing precedents that are hardest to correct later. Getting it right means being explicit about three things before the contract is signed.
First, the responsibility matrix — a clear, signed document that defines what the internal team owns, what the MSP owns, and what the escalation handoff procedure looks like for items in the middle. This document is not boilerplate. It is the foundation of the commercial relationship and the reference point for any scope dispute. Solution Builders' 2026 managed IT pricing guide confirms that incentive alignment — ensuring the MSP's pricing model is aligned with the client's success rather than optimised for out-of-scope charges — is one of the most important factors in sustainable co-managed partnerships. The responsibility matrix is how that alignment is made concrete rather than conceptual.
Second, the after-hours definition — an explicit statement of what the MSP's obligations are outside business hours, how they are triggered, and how they are priced. Undefined after-hours scope is the most common source of co-managed contract disputes, because the internal IT person's unavailability during evenings and weekends creates a default expectation that the MSP will fill the gap, whether or not that gap was ever priced.
Third, the review cadence — a defined schedule for quarterly business reviews where the responsibility matrix is reviewed against actual performance, pricing is assessed against delivered scope, and any adjustments to the arrangement are discussed before they become operational friction. Co-managed engagements that include a formal QBR cadence in the contract from the start have significantly better long-term margin performance than those that treat the review as optional, because the QBR is the mechanism that prevents scope creep from silently eroding what was priced.
If you are an MSP owner building your first co-managed engagement or reviewing existing co-managed contracts that are not performing to the margin expectations you set, the pricing structure and responsibility matrix conversation is where it usually needs to start.
📅 Book a 20-minute call: https://meet.brevo.com/konnectph
✉️ Email us: hello@konnect.ph
We work with MSP owners on both the co-managed pricing structure and the offshore staffing component that improves margin on the after-hours coverage module specifically.
About the Author
Vilbert Fermin is the founder of Konnect, a remote staffing company connecting North American and Australian businesses with top Filipino talent. With deep expertise in IT support and remote team management, Vilbert helps MSPs access skilled technical professionals without the overhead of full-time domestic IT staff. His mission is to showcase Filipino excellence while helping businesses stay protected, productive, and competitive through strategic remote staffing.
Related Resources
