Most MSPs hit a revenue wall and immediately ask the same question: how many people do we need to hire? It's the wrong question. The right one is “How much does it cost to deliver one unit of service capacity, and can we compress that number without adding headcount?”
Almost nobody has the answer. Not because the math is complicated, but because the inputs are scattered across tools that don't talk to each other, buried in a profit and loss (P&L) statement that shows monthly recurring revenue (MRR) but hides technician utilization. That gap is a margin problem and it's getting more expensive to ignore.
The numbers most MSPs never look at
It's not that MSP leaders don't care about the math. It's that three structural problems make it genuinely hard to run.
1. Cost inputs are dispersed
Labor, licensing, endpoint management and administrative overhead live in different systems. Nobody aggregates them into a cost-per-ticket figure because no one owns that number across the business.
2. Sprawl hides overhead
When technicians switch between four platforms to close a single ticket, the time cost disappears into productivity rather than showing up as an operational liability. The Kaseya IT Service Delivery Solution Study researched by Omdia found that organizations running fragmented tool stacks consistently cited context-switching and documentation gaps as drags on throughput — costs that never appear in a service agreement but erode margin on every ticket worked.
3. P&L tells the wrong story
MMR is visible. Cost-to-serve is not. An MSP can grow MRR 12% year over year and still lose ground if delivery costs grow faster. According to the 2026 Kaseya State of the MSP Report, the share of MSPs reporting unprofitable operations doubled year over year as rising delivery costs (labor, tools and infrastructure) quietly eroded margins as deal sizes compressed.
The model: capacity as a measurable line item
The first step toward fixing any of it isn't a new tool. It's knowing which numbers to track. Four variables turn capacity from an abstract understanding into a line item:
- Fully loaded labor cost per ticket: This is what it costs your business to close one ticket — not just the hourly rate, but the real number when you fold in salary, benefits, training and management overhead. Most MSPs only account for base salary, which means they’re working with a figure that understates the true cost. When your cost figure is wrong, your pricing is wrong too, and a contract that looks profitable on paper may just be keeping people occupied.
- Tool-switching overhead: Every time a technician moves between platforms mid-ticket — from the RMM to the PSA to a documentation system to a chat thread — they lose context and time. That friction doesn't show up anywhere in your reporting, but it accumulates across every ticket worked every day. Tracking this shows how much labor your team spends on administration instead of resolving issues.
- First-response time as a throughput multiplier: Slow first response doesn't just frustrate clients. It keeps tickets open longer, so more tickets remain in the queue at once, limiting how many tickets technicians can handle. A technician working five open tickets handles them differently than one working fifteen. Faster first response keeps queues tighter, which compresses the overhead attached to each resolution.
- Endpoint-to-technician ratio as the growth ceiling: This is the most direct measure of whether your operations can scale without a proportionate increase in cost. It tells you how many endpoints each technician currently supports, and whether your team can absorb new accounts without adding headcount. If your sales team signs contracts that push a technician from 150 endpoints to 250, you have two options: hire or get more efficient.
Where automation moves the numbers, and where it doesn't
Knowing the variables is step one. Step two is understanding which parts of the workload can be compressed without compromising quality, and which parts can't. Automation changes the math on specific, repeatable work. But it only does that reliably when the operational foundation underneath it is solid. Here's where it moves the numbers:
Proactive alert triage
When monitoring tools surface and classify issues before a ticket is created, technicians skip the diagnostic step. It’s one of the more time-consuming parts of routine work that rarely gets measured on its own. A study by Kaseya/Omdia found that MSPs using integrated endpoint management and service desk platforms reported a 32% reduction in ticket resolution times, with automation accounting for a significant share of that compression. Datto RMM goes after this step directly. Smart Insights lets a technician ask a plain-English question about live device data and see the cause of an alert in one place, with no hopping between screens to check patches and performance.
Documented runbook execution
When resolution steps are codified and accessible inside the ticketing workflow, junior technicians can close issues that previously escalated. Escalations are expensive. Every tier-2 ticket that gets resolved at tier-1 is a cost reduction.
Scheduled maintenance automation
Patching, backup verification and health checks run without technician involvement. That's not just time saved but time that can go toward billable work or client-facing activity instead of infrastructure upkeep. Datto RMM's ComStore gives your team hundreds of free, prebuilt scripts and automation policies, so they deploy proven automation on day one instead of writing scripts from scratch. Dynamic grouping policies add to that. Filters assign the right policy to new and changed devices automatically, which ends the habit of assigning policies device by device.
Intelligent alert routing
Not every alert needs a human response. When teams tune alerting logic and integrate it with ticket creation rules, fewer alerts become tickets, filtering noise before it reaches the queue. Technicians spend time on issues that need them, rather than working through alerts that could have been handled automatically or dismissed entirely. Datto RMM applies the same idea. Its AI and automation quiet the alert noise and run jobs in the background, so your technicians see fewer low-value alerts and spend their day on work that needs a human.
Billing reconciliation
Time-to-invoice and billing accuracy are underrated margin drivers. Automated time capture tied to ticket activity reduces billing leakage, which is money already earned that never gets invoiced.
Client onboarding standardization
The first 60 days of a new client relationship carry disproportionate support load. Automated onboarding workflows — provisioning, documentation setup, access configuration — reduce that spike and free technicians for work that requires human judgment.
Where automation doesn't help: complex multi-system incidents, client relationship management, non-standardized environments and anything requiring nuanced judgment about risk. These don't automate. An MSP with fragmented documentation and inconsistent runbooks won't get much from automation because the inputs aren't there.
What it looks like at scale
The variables and the examples above are useful in isolation. But the real question for most MSP leaders is what this looks like when you run the numbers across a whole team.
The Kaseya/Omdia study interviewed MSPs that had moved from fragmented tool stacks to a unified IT service delivery platform. Their results offer a useful external reference point to test against your own numbers.
Take a 10-technician MSP as a baseline. The results are:
- Endpoint capacity: MSPs in the study managed approximately 217 endpoints per technician. After consolidating platforms, they reported a 27% increase in endpoints managed per technician. On a 10-person team, that's roughly equivalent to gaining the capacity of two to three additional technicians without adding to headcount.
- Ticket throughput: Respondents handled 23% more tickets per technician per week, equivalent to approximately 136 additional tickets weekly for a 10-person team.
- First-response time: Response times dropped 36%, tightening queue management and reducing the coordination overhead attached to open tickets.
- Cost per technician: The study reported average total monthly savings of approximately $2,600 per technician, or roughly $312,000 annually for a 10-technician MSP across labor, tooling and endpoint management costs. One MSP described reducing costs by $53,000 annually while adding $23,000 per month in new services without new clients.
The takeaway: consolidating and automating to compress cost-per-endpoint and cost-per-ticket creates capacity that's otherwise only available by hiring.
Datto RMM customers add their own data point. After implementation, they tell us they see an average 40% efficiency improvement. Datto RMM also tackles the tool switching we covered earlier. Technicians manage Microsoft 365 users and Intune devices right inside the platform and check MFA and Conditional Access status without logging into separate Microsoft admin portals. Better yet, if you make the switch and don't see a similar improvement, you get free Kaseya expert-led sessions to help you optimize your environment.
The strategic payoff
When capacity becomes a line item, three business decisions change:
- Hiring becomes math driven: Instead of making staffing decisions based on how the team feels, you make them based on what the numbers show. When you know your endpoint ceiling, your ticket volume trends and how much of your routine workload automation is already handling, the question of whether to hire, automate or reprice has a clear answer rather than a gut feeling behind it. If the numbers show you have room, your next hire can be a salesperson instead of another technician. Datto RMM is built to make that happen.
- Contract pricing ties to true cost-to-serve: Most MSPs price on competitive market rates, not on what it costs them to deliver. When you know your fully loaded cost per ticket and your current resolution time distribution, you can price contracts that protect margin at scale rather than hoping volume absorbs the gap.
- Vendor consolidation becomes a ROI question: The 2026 State of the MSP Report found that 60% of MSPs cited reducing vendor fatigue as a priority, and the operational math explains why. Every additional tool in the stack adds licensing cost, integration overhead and context-switching time. Consolidation isn't a simplicity preference — it's a cost-per-unit-of-service calculation.
High-margin MSPs aren't working harder. They've compressed their cost-per-endpoint while keeping or improving service quality.
Start here this week
None of this requires a platform change or a budget conversation to get started. The data you need is already sitting in your systems. Four concrete steps you can take without a new platform, a consultant or a board meeting:
Step 1: Pull your cost-per-ticket
Divide total technician cost for a month by total tickets closed. If you don't have that number in under an hour, your systems aren't giving you what you need to manage the business.
Step 2: Map your tool-switching surface
Ask a technician to narrate the platforms they touch on an average ticket. Count the switches. Multiply by average daily ticket volume. That's your switching overhead, and it's probably larger than you expect.
Step 3: Calculate your endpoint ceiling
Take your current endpoint count and divide by technician headcount. Then estimate what your pipeline would push that number to in six months. If it's climbing without any corresponding change to how work gets done, you have a decision in front of you sooner than you think.
Step 4: Split your ticket volume into proactive versus reactive
Proactive tickets, surfaced by monitoring before the client ever notices an issue, are where automation has the most leverage. If the majority of your tickets are still reactive, your monitoring and alerting setup is functioning as a notification system rather than a capacity multiplier.
Where to go deeper
The Kaseya/Omdia IT Service Delivery Solution Study is the most granular independent benchmarking available on what unified service delivery moves across financial performance, technician productivity and SLA compliance. It's worth reading as a set of benchmarks to test against your own numbers.
The MSPs gaining ground in 2026 aren't doing so because they hired faster. They're doing it because they figured out the math and built operations around it. That math is available to anyone willing to run it.
Ready to see what a 40% efficiency gain looks like in your own environment? Datto RMM pairs AI-powered automation with Kaseya experts who work with you until you see the gains.
Victoria Boryaeva — Senior Director, Product Marketing & Business Development at Kaseya https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgE72pmULNi62PgJZwtZ748TVMrTpNdqjgv2N5SZhsDIn3vA7NwYnczZcl-CZ2wOX9so6jVJwVwHp_i4fMK_SqSEaO8Y7ZDibSb0ML4Vf7fjb7THy-0sCq4snPSkzu-vcaWxrdmj1-pTu3MFYxbEQwhyphenhyphen_UmkDd2JCF8R6RMVyrI2Ib8yfHrdiwIRB4R-N4/s1600/vic.png
