Utilization & Profitability Tracking for MSPs and IT Services Firms

Managed services contracts hide their real cost until a client’s ticket volume spikes. By then you’re already three months into negative margin on a contract you can’t exit for another nine.

Updated April 2026 9 min read Target: MSPs and IT services firms, 10–80 technicians, $2M–$20M revenue

MSPs and IT services firms track project profitability through four interlocking metrics: technician billable utilization (billable hours on client tickets and projects ÷ available technician hours — best-in-class MSPs hit 65–70% [ESTIMATE, ConnectWise Benchmark Survey]), recurring vs. project revenue mix (MRR as a percentage of total revenue, where 70%+ MRR commands higher valuations), contract profitability by client (technician hours consumed × loaded cost vs. monthly contract fee), and SLA cost tracking (the loaded cost of meeting contracted service levels per client). The most common MSP profitability failure is all-inclusive managed services contracts where high-ticket clients consume 3–4× more technician hours than average without a corresponding revenue premium. ERPAIStack surfaces contract profitability, utilization by technician, and client concentration from your existing PSA and billing data without a system migration.

Three Profitability Gaps in Managed Services Firms

These are the operational patterns that compress MSP margin as the client base grows and contract vintage increases. All three are invisible on the P&L until they have already cost you significant margin.

💾

Underwater Managed Services Contracts

All-inclusive MSP contracts price on average ticket volume. High-complexity clients with aging infrastructure, poor documentation, or frequent user errors consume 3–5× more technician hours than average. Without per-contract cost tracking, these clients subsidize themselves on MRR while destroying margin.

👨‍💻

Technician Utilization Gaps

Service desk technicians have significant non-billable time from internal projects, training, rework on poorly-scoped tickets, and escalations. Without visibility into what percentage of each technician’s day is billable vs. non-billable, you cannot distinguish a staffing problem from a process problem.

📈

Project Revenue Dependency

MSPs below 60% MRR are dependent on project work that is inherently lumpy. When project pipeline dries up for a quarter, revenue drops sharply while the fixed cost of technicians stays flat. Growing MRR requires visibility into which clients are candidates for managed services upsell vs. which will stay project-only indefinitely.

The Blind Spots Running on PSA + QBO + Excel

The standard MSP stack — ConnectWise or Autotask for ticketing, QuickBooks for billing, spreadsheets for reporting — generates data but not decision-quality visibility. Here is what is invisible.

  • Contract profitability by client — your $4,200/month managed services client with 14 endpoints looks identical to your $4,200/month client with 18 endpoints and a 15-year-old infrastructure. One runs at 68% gross margin; the other at 22%. You cannot see which is which without allocating technician hours to each contract at loaded cost rates.
  • Technician billable utilization breakdown — 58% average utilization across your team includes one technician at 82% and another at 44%. The 44% technician is either underloaded, spending excessive time on rework, or assigned to non-client projects. You need the breakdown to manage it.
  • SLA cost by client — your two 4-hour response SLA clients require escalations and after-hours coverage that costs $800–$1,200/month more to serve than standard-SLA clients at the same MRR. Without SLA cost attribution, you are pricing your premium SLA the same as your standard SLA.
  • Recurring vs. project revenue trend — if your MRR is growing at 8% annually while project revenue is growing at 22%, your revenue quality is declining even as total revenue increases. You need the mix tracked monthly, not in a year-end board discussion.
  • Client concentration in the recurring base — when three clients represent 45% of MRR, your monthly recurring revenue is less stable than it appears. A single client churning $6K MRR at a small MSP is a material event that warrants proactive retention management, not a reactive scramble.

Operational KPIs for MSPs and IT Services Firms

These metrics are specific to managed services firm economics. Benchmarks are estimates based on publicly available industry research [ConnectWise MSP Benchmark Survey, Datto MSP Business Survey, IT Glue MSP Landscape Report] and should be validated against your firm’s service mix and market.

Metric What to Measure Benchmark
Technician Billable Utilization Billable hours (client tickets + projects) ÷ total available technician hours, by technician and team Best-in-class: 65–70%; target floor: 55%; below 50% sustained signals staffing or process gap ESTIMATE
Contract Gross Margin Monthly contract fee − (technician hours consumed × loaded cost) ÷ contract fee, by client Target: 50–65% on managed services contracts; below 35% per contract signals repricing need or client complexity mismatch ESTIMATE
MRR as % of Total Revenue Monthly recurring revenue ÷ total revenue (MRR + project + break-fix), tracked monthly with trend Target: 70%+ MRR for valuation quality; below 50% creates revenue volatility and staffing planning challenges ESTIMATE
Client Concentration Risk MRR from top client and top 3 clients as % of total MRR Target: no single client above 20% of MRR; top 3 below 45%; above these levels creates existential churn risk ESTIMATE
Effective Hourly Rate Total client revenue (MRR + project) ÷ total billable technician hours, by client and by service type Track vs. your target rate; clients with effective rates 25%+ below standard are either over-served or underpriced ESTIMATE

What the Margin Diagnostic Reveals for MSPs

ERPAIStack’s Margin Diagnostic processes your PSA ticket data and billing exports — from ConnectWise, Autotask, HaloPSA, or any CSV-exportable PSA — and produces contract-level profitability visibility that your current reporting cannot. The output shows gross margin by managed services client, technician utilization breakdown (billable vs. non-billable by category), and the MRR concentration picture.

The report identifies the specific contracts running at negative margin after full technician allocation, the technicians with the widest utilization variance from the team average, and the effective hourly rate by client that reveals where your managed services pricing has drifted below sustainable levels. You get specific numbers: “Client X contract: $4,200 MRR, 68 technician hours consumed last quarter × $45 loaded rate = $3,060 direct cost — 27% gross margin vs. your 55% target.”

The Industry Benchmarking Report ($99) adds external comparison against similarly-sized MSPs — so you can tell whether your 61% technician utilization rate is strong for your revenue tier or whether you have a process efficiency opportunity relative to peer firms.

Is This the Right Tool for Your MSP?

This is for you if…

  • You run an MSP or IT services firm with $2M–$20M revenue and 10–80 technicians
  • You have 10+ managed services clients on all-inclusive contracts
  • You suspect some contracts are underwater but cannot quantify which ones
  • Your MRR is below 65% of total revenue and you want to track the mix monthly
  • You are preparing for a PE investment, acquisition, or owner exit and need documented revenue quality metrics
  • You want to know which clients to reprice at next renewal without guessing

Not for you if…

  • You are a solo consultant or break-fix shop without managed services contracts
  • You run exclusively project and T&M work with no recurring revenue base
  • You are already on a PSA with full contract profitability dashboards (e.g., ConnectWise Manage with Profit module)
  • You have fewer than 5 managed services clients

MSP Operations: Common Questions

What is a good technician utilization rate for an MSP?
[ESTIMATE, ConnectWise MSP Benchmark Survey, Datto MSP Business Survey] Best-in-class MSPs achieve 65–70% utilization on billable technicians. Mid-market MSPs typically run 55–65%. Below 50% sustained technician utilization signals either overstaffing relative to current contract volume, excessive time on non-billable internal projects, or service desk processes that generate too much rework. The benchmark that matters most is billable utilization — hours logged to client tickets and projects divided by available technician hours — not just scheduled hours. Time spent on internal IT, training, team meetings, and administrative tasks should be tracked separately to understand the true composition of your labor cost. The goal is not to maximize utilization at the expense of quality, but to understand where non-billable time is concentrated so you can improve it systematically.
How do MSPs track profitability on managed services contracts?
Contract profitability for MSPs requires allocating actual technician hours against each managed services agreement at loaded cost rates (salary + benefits + overhead) and comparing against the monthly recurring revenue. The challenge is that all-inclusive MSP contracts mean high-ticket clients consume disproportionate technician time without a corresponding revenue increase. Contracts where technician hours consumed consistently exceed the revenue/loaded-rate breakeven point are underwater. Best-in-class MSPs review contract profitability quarterly and build automatic repricing triggers: when a client’s ticket volume exceeds a threshold for two consecutive months, the contract is flagged for renewal repricing. The conversation with the client shifts from “your price is going up” to “your environment has grown beyond the scope of your current contract — here is the data.”
What is the right recurring vs. project revenue mix for an MSP?
[ESTIMATE, SEEK EXPERT ADVICE on your specific valuation] MSPs that derive 70%+ of revenue from recurring managed services contracts (MRR) command significantly higher valuations than project-heavy MSPs — typically 6–10x EBITDA vs. 3–5x for project-dependent firms. The reason is revenue quality: recurring revenue is predictable, contracted, and scalable. Project revenue is lumpy, non-recurring, and cannot be staffed predictably. From an operational standpoint, a healthy MRR base provides the utilization floor that allows you to staff predictably and maintain margins in slow quarters. Sub-$2M MSPs often run 50–60% MRR as they build their recurring base. Above $5M, the strategic target should be 70%+ MRR with project work serving as incremental margin on top of a stable recurring foundation, not as a baseline revenue source.
How should MSPs measure SLA cost and what does it reveal?
SLA cost measures the loaded technician time required to meet your contracted service level agreements — response times, resolution times, uptime guarantees — as a percentage of contract revenue. High SLA cost per client signals one of three problems: your contracts are underpriced for the complexity of the client environment, your technicians are spending excessive time on rework caused by poor documentation or process gaps, or the client’s infrastructure generates too many tickets relative to contract value. Tracking SLA cost by client identifies which clients require the most after-hours coverage, the most senior-technician escalations, and the most non-standard work — all of which should be reflected in premium SLA pricing at next renewal. Without this data, you are offering the same price to a straightforward 20-user client and a complex multi-site client with legacy systems.
What is the biggest operational risk for MSPs between $2M and $20M?
Client concentration combined with key technician dependency are the twin operational risks at this revenue level. A single client representing 25%+ of MRR is a binary revenue event if they churn — and MSP client concentration is often higher than realized because enterprise clients with multiple sites count as single revenue relationships. When one client churns at $6,000–$8,000 MRR from a $400K MRR base, that is a 1.5–2% annual revenue event that requires immediate pipeline replacement. The second risk is key technician dependency: when two or three senior technicians hold all client institutional knowledge and cannot be effectively replaced without service degradation. Documentation processes (IT Glue, Hudu) partially address this, but the knowledge transfer risk needs to be audited and quantified. Both risks are quantifiable from ticket and billing data. [SEEK EXPERT ADVICE] on the specific valuation impact for your buyer profile.

Continue Your Research

See Which Contracts Are Actually Profitable

Start with the free ProServ Health Assessment, or go straight to the Margin Diagnostic for contract-level profitability and technician utilization analysis.

See how your firm compares → Industry Benchmarking ($99)