IT Services and MSPs: When Recurring Revenue Hides a Profitability Problem
MSPs love to talk about their recurring revenue. MRR looks great in a pitch deck, feels like stability in a cash crunch, and makes the business sound more predictable than it often is. What the MRR number rarely reveals is whether the managed services contracts generating it are actually profitable — or whether the profitability is being quietly subsidized by one-off project work and vendor rebates that nobody is tracking consistently.
IT service businesses and managed service providers operate with a revenue mix that requires genuinely different accounting treatment for each stream. Managed services, project work, hardware resale, and vendor margin each have distinct cost structures, recognition rules, and margin profiles. Blending them into a single revenue line is how an MSP ends up with a healthy top line and a persistent mystery about why it never seems to have enough cash.
The bookkeeping issues that hurt IT services businesses and MSPs:
- MRR and project revenue are mixed into a single revenue line: Monthly recurring managed services revenue — typically booked as flat-fee contracts for monitoring, helpdesk, and infrastructure management — has completely different economics than project revenue. MRR is relatively predictable, has defined labor costs per seat, and scales with headcount management. Project revenue is episodic, requires scoping and change order discipline, and collects against a defined deliverable. When these two streams are reported together, neither can be managed: margin per seat under managed services is invisible, and project profitability is impossible to evaluate cleanly. The first step in MSP financial clarity is a clean revenue bifurcation.
- Project profitability disappears into time-and-materials invoices that never fully collect: A project scoped at 80 hours that runs 110 hours has a $15,000 cost overrun that either gets billed as a change order, absorbed as a write-off, or argued into a partial recovery. Most MSPs do not have a systematic way to identify when a project has gone over budget in real time — they discover it at invoice time, when the options for recovery are already limited. Without project-level cost tracking against scoped hours, the MSP cannot tell at any given moment which projects are profitable and which are bleeding.
- Technician utilization is not tracked against a target: Billable hours divided by total available hours is the fundamental labor efficiency metric for any time-based services business. For MSPs, a utilization target of 65 percent is typical — meaning 35 percent of technician hours are consumed by internal work, training, non-billable client calls, and administrative overhead. MSPs that do not measure utilization by technician cannot tell whether a staffing problem is a hiring issue, a scheduling issue, or a scope management issue. And an MSP running at 50 percent utilization is effectively funding a 50 percent overhead rate out of its managed services margin.
- Vendor rebates and margin stack are not tracked as revenue: Microsoft, Cisco, Datto, and other core MSP vendors pay rebates, deal registration incentives, and back-end margin to MSP partners. These payments are real revenue — often representing $30,000 to $150,000 annually for a mid-size MSP — but they are frequently deposited as miscellaneous income, credited against vendor invoices, or simply overlooked in financial reporting. An MSP that cannot tell you its annual vendor margin contribution cannot tell you its true margin per managed seat or make rational vendor consolidation decisions.
- The contract renewal cliff is invisible without a dedicated report: In a subscription-revenue business, the percentage of ARR up for renewal in the next 90 days is a leading indicator of revenue at risk. An MSP with $180,000 in monthly MRR that has 40 percent of contracts coming up for renewal in Q3 has $864,000 of annualized revenue at risk that needs proactive retention activity. Most MSP accounting systems do not surface this number automatically. Owners who discover renewal cliffs late are negotiating from a reactive position instead of an intentional one.
- Hardware resale margin is mixed with services margin and destroys gross margin clarity: Hardware resale — servers, workstations, switches, firewalls — is a low-margin, capital-intensive business that has nothing in common with managed services economics. An MSP with 65 percent gross margin on services and 12 percent gross margin on hardware resale that reports a blended gross margin of 45 percent has a number that describes neither business accurately. Separating hardware COGS from services labor cost is foundational to understanding whether the managed services practice is financially healthy or being subsidized by hardware volume.
- PSA and ticketing system data is not integrated with accounting: ConnectWise, Autotask, HaloPSA, and similar PSA platforms contain the most accurate record of actual technician time and client activity in the business. When that data is not reconciled against billing and accounting, the MSP loses the ability to verify that all billable work has been invoiced, that time-and-materials projects are being billed accurately, and that technician cost is being allocated correctly to contracts. The disconnect between PSA data and accounting is one of the most common sources of revenue leakage in MSP businesses.
What it costs: managed services contracts that look profitable at the contract level but erode margin when support overhead is fully allocated, vendor rebates that disappear into miscellaneous income, project overruns that never get billed, and an MRR number that tells you what you want to hear without telling you whether the business is actually making money.
We help IT services businesses and MSPs build the revenue segmentation, utilization tracking, and vendor margin reporting that turns MRR from a vanity metric into a profitability story.