# MSP Cost Per Ticket

In the world of managed services, your help desk is often the heartbeat of the business. It is where your client relationships are maintained daily, where technical expertise is demonstrated, and unfortunately, where most of your profit can be quietly eroded if you aren’t paying attention.

In the world of managed services, your help desk is often the heartbeat of the business. It is where your client relationships are maintained daily, where technical expertise is demonstrated, and unfortunately, where most of your profit can be quietly eroded if you aren’t paying attention. Understanding your **MSP cost per ticket** isn't just a mathematical exercise for the finance team; it is a fundamental pillar of operational maturity.

When I was co-founding Totality Services, we didn't start with a perfect grasp of our ticket economics. We focused on growth. But as we scaled to over 150 clients across London and Johannesburg, we realised that without a firm grip on what every interaction cost us, we couldn't accurately price our contracts or reward our high-performing engineers. We had to move from "feeling" profitable to "knowing" exactly where every dollar of labour was going.

This guide draws on those 15 years of experience building, scaling, and eventually selling an MSP in an eight-figure acquisition. We will break down how to calculate this metric, why it fluctuates, and how to use it to drive a more profitable, predictable services business.

## What is MSP Cost Per Ticket?
**MSP cost per ticket** is a financial metric that represents the total average expense an MSP incurs to resolve a single support request. It is calculated by dividing the total burdened cost of the service desk (salaries, benefits, tools, and overhead) by the total number of tickets closed within a specific period.

To be commercially useful, this metric must account for more than just the time a technician spends typing. It should include:

- **Gross Labour:** The actual wages paid for the time spent on the ticket.
- **Burdened Overhead:** Taxes, insurance, office space, and management oversight.
- **Tooling Costs:** The per-ticket or per-technician cost of your PSA, RMM, and documentation platforms.

| Component | What it Includes | Why it Matters |
| --- | --- | --- |
| Direct Labour | Technician hourly rate (based on actual worked hours). | The primary driver of service delivery expense. |
| Labour Burden | Payroll taxes, health insurance, 401k, paid time off. | Reflects the true cost of employing a human being. |
| Management Overhead | Service Manager salary, dispatcher costs. | Accounts for the "non-billable" leadership required to run the desk. |
| Operating Tools | PSA, RMM, Documentation, AI/Automation tools. | The "factory floor" costs required to process tickets. |

## Why This Metric Dictates Your Valuation
When we prepared Totality Services for acquisition, the buyers weren't just looking at our total revenue. They were looking at the quality of that revenue. An MSP with a high cost per ticket is often a business that lacks standardisation. It suggests that every problem is being solved for the first time, every time.

High ticket costs usually indicate that your team is struggling with "technical debt" or that you have taken on clients with aging infrastructure. From a commercial perspective, this makes your business less attractive because it is harder to scale. If every new client requires a linear increase in headcount, your margins will always be capped. A low, stable cost per ticket demonstrates that you have built a repeatable machine.

Luis Navarro, the founder of MSP Agenda, often emphasises that while he wasn't the "technical guy," he understood that the help desk was a cost centre that needed to be managed with the same rigor as a sales pipeline. If you don't know your cost per ticket, you don't know if your "Gold" support package is actually making you money or if you're subsidizing a difficult client's inefficiency.

## How to Calculate Your MSP Cost Per Ticket
Many MSP owners make the mistake of simply taking their total payroll and dividing it by tickets. This is too broad. To get a number you can actually act on, you need to isolate the service delivery costs. Here is a practical framework for getting to the real number.

### Step 1: Calculate the Burdened Hourly Rate
Start with your service desk team. Take their annual salaries and add the cost of benefits, taxes, and perks. Divide this by the number of workable hours in a year (usually around 2,080, though you should subtract vacation and holidays for more accuracy).

```
(Annual Salary + Benefits + Taxes) / 2080 = Burdened Hourly Rate
```

### Step 2: Factor in Indirect Service Costs
Your technicians don't work in a vacuum. You need to add the costs of the tools they use. If your PSA/RMM stack costs $5,000 a month and you have 10 technicians, that’s $500 per tech per month. Add this to their monthly burdened cost before calculating the hourly rate.

### Step 3: The Final Calculation
Once you have the total monthly cost of your service department (including managers and dispatchers), divide it by the total number of tickets resolved in that month.

```
Total Service Department Monthly Expense / Tickets Resolved = MSP Cost Per Ticket
```

**Example:** If your total service desk costs are $50,000 per month and your team resolves 1,000 tickets, your cost per ticket is $50. If a client paying you $2,000 a month generates 50 tickets, you have spent $2,500 just in support labour to service them. You are losing $500 a month before you even consider the cost of their licenses or your office rent.

## The Hidden Dangers of Low Ticket Costs
It is tempting to think that the lowest possible cost per ticket is the goal. In reality, an extremely low cost can be a warning sign. If your cost is too low, it often means one of three things is happening:

1. **Poor Resolution Quality:** Technicians are rushing through tickets, applying "band-aids" rather than root-cause fixes. This leads to "rebound tickets" where the client calls back two days later for the same issue.
2. **Underpaid Staff:** You may be paying below-market rates, which leads to high turnover. The cost of recruiting and training a new engineer is far higher than the few dollars you save on a ticket.
3. **Inaccurate Tracking:** Your team might be closing tickets without documenting the work, or grouping multiple issues into a single ticket to make their stats look better.

The goal is **efficiency**, not just **cheapness**. You want a cost that reflects a highly skilled engineer using modern tools to solve a problem correctly the first time.

## Factors That Influence Your Ticket Economics
Several variables will shift your cost per ticket. Understanding these allows you to make strategic adjustments to your operations rather than just yelling at your team to work faster.

### Client Infrastructure Maturity
A client with standardised, modern hardware and a cloud-first approach will almost always have a lower cost per ticket. Why? Because the problems are predictable. When you are dealing with a "Frankenstein" environment of 7-year-old servers and mixed workstation brands, every ticket becomes a research project. This is why **standardisation** is the secret weapon of the most profitable MSPs.

### Tiering and Escalation Efficiency
If your Level 3 senior engineers are spending time on password resets or printer mapping, your cost per ticket will skyrocket. An efficient desk ensures that Level 1 handles the high-volume, low-complexity tasks, reserving the expensive Level 3 talent for projects and complex escalations. Effective dispatching is the traffic control that keeps your costs in check.

### Documentation and Knowledge Management
Time is the biggest component of ticket cost. Every minute a tech spends hunting for a serial number or a firewall password is profit leaking out of the business. MSPs that invest in robust documentation see a direct correlation in lower ticket resolution times. When the answer is always at the technician's fingertips, the cost per ticket drops naturally.

## Using Cost Per Ticket to Drive Commercial Decisions
This metric is most powerful when used to manage your client portfolio. At Totality Services, we used ticket data to prepare for our Quarterly Business Reviews (QBRs). If a client’s cost to support was consistently higher than their monthly recurring revenue (MRR), we had a commercial conversation.

You have three levers to pull in this situation:
 
 

1. **Increase the Price:** If the client is inherently "noisy" due to their business model (e.g., a high-turnover retail environment), they need to pay more to maintain your margin.
 

2. **Standardise the Environment:** Tell the client that their high ticket volume is caused by their aging server. If they invest in the project to replace it, their issues (and your costs) will go down.
 

3. **Offboard the Client:** Some clients are simply not a fit for a profitable MSP. If they refuse to follow your recommendations and continue to erode your margins, they are preventing you from focusing on better, more profitable accounts.

For more on how to have these difficult but necessary conversations, explore our insights on [MSP sales strategy](https://mspagenda.com/blog/msp-sales-strategy/) and how to align client needs with your business goals.

## Strategies to Reduce Your MSP Cost Per Ticket
If you find that your costs are higher than the industry average (which typically sits between $20 and $60 depending on the region and complexity), here are actionable steps to bring them down without sacrificing quality.

### 1. Implementing Shift-Left Support
The "Shift-Left" philosophy involves moving resolution as close to the end-user as possible. This means empowering users with self-service portals and automated password resets. Every ticket that never reaches a human technician has a near-zero cost. Even moving a ticket from a Level 2 tech to a Level 1 tech is a "Shift-Left" move that saves money.

### 2. The Power of "Kill the Noise"
Review your most common ticket types every month. If you see 50 tickets for "Outlook Crashing" at a specific client, don't just fix Outlook 50 times. Task a senior engineer to find the root cause—perhaps a conflicting add-in—and fix it globally via your RMM. Eliminating the *need* for a ticket is the ultimate cost-saving measure.

### 3. Automation and AI
Modern MSP tools can now handle routine tasks like disk cleanups, service restarts, and even basic user onboarding without human intervention. While there is an upfront cost to setting up these automations, the long-term impact on your cost per ticket is significant. However, ensure that your **Security Reviews** account for these automated processes to maintain a high standard of safety.

### 4. Enforce Technical Alignment
If you support ten different types of firewalls, your team has to be "ten types" of smart. If you only support one or two, they become experts. Expertise leads to speed. Speed leads to a lower cost per ticket. Luis Navarro’s experience building Totality Services proved that **standardisation** isn't just a technical preference; it’s a commercial imperative.

## The Relationship Between Ticket Cost and Security
It is a mistake to view support costs and security as separate silos. Often, a high volume of tickets is a symptom of poor security hygiene. Frequent malware infections, locked accounts due to brute-force attempts, and lost devices are both security risks and major drivers of support costs.

By conducting regular, structured **Security Reviews**, you can identify these risks before they turn into tickets. This is the core philosophy behind MSP Agenda. We believe that if you can clearly communicate risk to a client, they are more likely to approve the projects that ultimately make their environment more stable and less "noisy."

When a client invests in a recommendation from one of your reviews—such as implementing Phishing Simulation or Advanced Threat Protection—they aren't just getting safer. They are reducing the likelihood of a high-cost security incident that would swamp your help desk for days. Learn more about [effective security reviews](https://mspagenda.com/blog/msp-security-reviews/) and how they bridge the gap between technical risk and commercial reality.

## Common Pitfalls in Measuring Ticket Costs
Even seasoned MSP owners get this wrong. Avoid these common mistakes to ensure your data is clean and actionable.

- **Ignoring After-Hours Costs:** On-call pay and overtime significantly spike the cost of tickets handled outside of 9-to-5. These should be tracked separately to see if your "24/7" offering is actually profitable.
- **The "Quick Fix" Trap:** Technicians who don't log "quick" 5-minute calls are distorting your data. If it isn't in the PSA, it didn't happen. You need that data to show the client how much value you are providing.
- **Mixing Project and Support Time:** Project work is typically higher value and billed differently. If your engineers are mixing project hours into support tickets, your cost per ticket will look artificially high, and your project margins will look artificially low.
- **Forgetting About Non-Technical Time:** Time spent in internal meetings, training, or admin work is still a cost. While it shouldn't be attributed to a specific *client* ticket, it must be factored into the overall *department* cost per ticket.

---

Source: https://mspagenda.com/blog/msp-cost-per-ticket
Last updated: 2026-08-24