# Revenue Per Technician

In the managed service provider world, most owners obsess over total top-line growth. While hitting a new monthly recurring revenue (MRR) milestone feels great, it doesn't tell you if your business is actually getting healthier or just getting bigger and more chaotic.

In the managed service provider world, most owners obsess over total top-line growth. While hitting a new monthly recurring revenue (MRR) milestone feels great, it doesn't tell you if your business is actually getting healthier or just getting bigger and more chaotic. The metric that truly defines the efficiency, scalability, and ultimately the enterprise value of your MSP is **Revenue Per Technician**.

Revenue Per Technician (RPT) is a financial productivity KPI that measures the total gross revenue generated by the business divided by the number of full-time equivalent (FTE) technical staff. It reveals how effectively your team delivers services and how well your internal processes, automation, and standardisations are performing. High RPT indicates a lean, profitable machine; low RPT suggests you are simply "throwing bodies" at problems.

At MSP Agenda, we view this metric as the heartbeat of operational excellence. Luis Navarro, our founder, spent 15 years building Totality Services from a small startup into a highly profitable MSP serving over 150 clients. That journey, which led to a successful eight-figure acquisition, was built on the realisation that scaling isn't about hiring more people—it’s about making every person on the team more impactful through better systems and clearer client communication.

## Key Takeaways

- **Efficiency Benchmark:** A healthy MSP should aim for a minimum of $200,000 to $250,000 in Revenue Per Technician.
- **Scalability Indicator:** RPT tells you if your growth is sustainable or if you are at risk of "profitless scaling."
- **Process Over Headcount:** Improving RPT requires investment in automation, standardisation, and rigorous documentation.
- **Client Quality Matters:** High-touch, low-margin clients drag down RPT; standardised, high-value clients boost it.
- **Valuation Impact:** Buyers and investors look at RPT to determine if the business is a well-oiled machine or a chaotic labour-intensive shop.

### What is Revenue Per Technician?

Revenue Per Technician is calculated by taking your **Total Annual Revenue** and dividing it by your **Technical Headcount**. This includes everyone involved in service delivery: help desk, onsite engineers, project engineers, and centralised services. It excludes sales, admin, and pure management roles.

For example, if your MSP generates $2,000,000 in annual revenue and you have 8 technicians, your Revenue Per Technician is $250,000. This figure allows you to compare your performance against industry leaders and identifies when it’s time to hire—or when it’s time to fix your internal workflows.

| Metric Level | Annual Revenue per Tech | Operational Health Status |
| --- | --- | --- |
| **Laggard** | Under $150,000 | Inefficient. High overhead, poor automation, likely struggling with profitability. |
| **Average** | $150,000 - $200,000 | Functional. Typical MSP operations, but significant room for optimisation. |
| **High Performer** | $200,000 - $275,000 | Strong. Standardised stacks, proactive management, and good project margins. |
| **World Class** | $300,000+ | Exceptional. Heavy automation, elite technical talent, and high-value strategic services. |

## Why Revenue Per Technician is the Ultimate MSP Metric

If you only look at your profit and loss statement, you see the past. If you look at your **Revenue Per Technician**, you see the future of your capacity. This metric cuts through the noise of technical jargon and focuses on the commercial reality of running a services firm.

Most MSP owners fall into the trap of thinking that more clients automatically require more staff. In the early days of Totality Services, Luis Navarro learned that adding a technician for every $15,000 of new MRR is a recipe for stagnation. True growth happens when you can support more endpoints and more complex environments without linearly increasing your payroll expenses.

### The Trap of "Profitless Scaling"

If your revenue grows by 20% but your technical headcount also grows by 20%, your business isn't actually becoming more valuable; it's just becoming bigger and riskier. When RPT stays flat or declines during growth, it means your complexity is outstripping your efficiency. You are likely dealing with "technical debt" in your own operations—messy documentation, non-standard client stacks, or a lack of automation.

High RPT allows for higher wages for your top performers, better tools, and higher net margins. It provides the financial "breathing room" to invest in things like [Security Reviews](https://MSP Agenda.com/security-reviews/) that add immense value to the client while generating high-margin project work. Without a strong RPT, you are constantly stuck in reactive mode, putting out fires rather than building a business.

## Drivers of High Revenue Per Technician

Achieving a high RPT isn't about making your engineers work 60 hours a week. In fact, overworked technicians usually make mistakes that lead to rework, which *decreases* RPT. Instead, high RPT is driven by strategic decisions made by leadership.

### 1. Standardisation of the Technology Stack

The single greatest killer of RPT is "snowflake" clients—clients who have unique setups, varying hardware brands, and custom configurations that no one else in your portfolio uses. When every client is different, your technicians spend half their time just trying to understand how things are connected.

By enforcing a standard stack, your team becomes specialists in a specific set of tools. They can solve problems faster, automate more tasks, and move between client environments seamlessly. Standardisation is the bedrock of efficiency. It’s what allowed Totality Services to scale across two continents—London and Johannesburg—while maintaining high profitability.

### 2. Leveraging Automation and Centralised Services

Every ticket that a human has to touch is a cost to the business. Low RPT often stems from a lack of RMM (Remote Monitoring and Management) maturity. High-performing MSPs use automation for patching, disk cleanups, and user onboarding/offboarding.

Centralised services—a dedicated team or individual focused on the "behind-the-scenes" maintenance rather than reactive support—is a massive RPT booster. They ensure the tools are working so the front-line technicians don't have to manually intervene. This proactive approach keeps the "noise" down, allowing technicians to focus on higher-value tasks.

### 3. Client Selection and "Right-Sizing"

Not all revenue is created equal. A client paying you $2,000 a month who calls the help desk 50 times is significantly less profitable than a client paying the same amount who calls 5 times. If you have "noisy" clients who refuse to upgrade their legacy hardware, they are actively dragging down your Revenue Per Technician.

Part of being commercially minded is recognising when a client relationship is no longer viable. If their environment is so unstable that it requires constant manual intervention, you must either charge them more, move them to a modern stack, or part ways. Freeing up a technician's time from a low-value, high-maintenance client allows them to support two or three high-value, standardised clients.

## The Relationship Between Security and RPT

One of the most effective ways to increase RPT is to shift your service mix toward high-value security services. Traditional "plumbing" work—fixing printers or resetting passwords—is low-margin and labour-intensive. Strategic security oversight, however, commands a premium and often requires less "hands-on" time once the systems are implemented.

This is where [MSP Agenda](https://MSP Agenda.com/) fits into the equation. By standardising your Security Reviews, you aren't just protecting the client; you are streamlining the process of identifying and selling high-margin projects. Instead of an engineer spending hours manually auditing a site and writing a report from scratch, they can use a structured framework to deliver a clear, commercially focused recommendation.

### From Reactive Support to Strategic Projects

When you use a tool like MSP Agenda to facilitate a security conversation, you are moving away from the "hour-for-hour" labour model. A well-presented Security Review might lead to a $10,000 project that takes 20 hours to implement. That’s $500 per hour in revenue—a massive boost to your RPT compared to standard managed services. This shift in focus is how you move from the "Average" bracket to "World Class."

## How to Calculate and Track RPT Correctly

To get an accurate picture, you need to be consistent in your math. Here is the formula and the common pitfalls to avoid when tracking Revenue Per Technician.

#### Who to include in the denominator:

- Help Desk Technicians (Levels 1, 2, and 3)
- Onsite Engineers / Field Techs
- Project Engineers and Architects
- Service Desk Managers (if they still handle tickets)
- Centralised Services / RMM Administrators

#### Who to exclude:

- Sales and Marketing staff
- Administrative and Finance staff
- The CEO/Owner (unless they are still acting as a primary engineer)
- Third-party outsourced help desks (these should be tracked as an expense, though some MSPs include them as FTEs for a "true" efficiency check)

**Pro-tip:** Track this monthly using a trailing twelve-month (TTM) average. This smooths out seasonal spikes in project revenue and gives you a realistic view of your trend line. If the trend is going down while revenue is going up, you have an operational problem that needs immediate attention.

## Common Mistakes That Erode RPT

Even the best MSP owners can fall into habits that destroy their efficiency. If your RPT is stagnating below $180,000, look for these three common culprits.

### The "Hero" Technician Culture

Many MSPs rely on one or two "hero" technicians who know everything but document nothing. They solve problems fast, but they are a bottleneck. Because they don't document their fixes, the rest of the team stays slow. This caps your RPT because you can't scale the knowledge of a hero. You can only scale documented processes.

### Poor Project Scoping

Project work can be the biggest driver of RPT, or its biggest detractor. If you sell a 40-hour project but it takes 80 hours because of poor scoping, you’ve just slashed that technician's productivity in half for two weeks. Commercial awareness means ensuring your sales team (or the owner) is aligned with the technical team on what is actually achievable.

### Ignoring the "Cost of Noise"

Noise is anything that interrupts a technician's workflow. This includes alerts that don't require action, clients who call personal cell phones instead of the help desk, and internal meetings that lack an agenda. Reducing noise is the fastest way to increase RPT without hiring a single person.

## Practical Steps to Increase Your Revenue Per Technician

If you want to move the needle on this metric, you need an action plan. You can't just tell your team to "work faster." You have to change the environment they work in.

### Step 1: Audit Your Ticket Volume

Look at your last 90 days of tickets. Which clients are generating the most noise per seat? Which issues are recurring? If you see the same "password reset" or "VPN connection" issue 50 times, that is a prime candidate for automation or a self-service training video for the client. Every ticket eliminated is a direct contribution to your RPT.

### Step 2: Formalize the Account Management Process

Revenue grows when clients buy more of your high-value services. However, technicians shouldn't be the ones trying to "sell." Instead, use structured [QBRs (Quarterly Business Reviews)](https://MSP Agenda.com/qbr/) to identify gaps in their security or infrastructure. By making these reviews consistent and easy to understand for the client, you increase the likelihood of project approvals, which boosts revenue without needing to add more headcount to the help desk.

### Step 3: Implement a "No-Documentation, No-Ticket" Policy

You cannot have high RPT if your team is constantly re-inventing the wheel. Make documentation a core part of your culture. When a technician solves a unique problem, they must update the client's documentation. This ensures that the next time the issue arises, a lower-level (and lower-cost) technician can handle it, freeing up your senior talent for higher-revenue tasks.

## The Commercial Impact of RPT on Your MSP Exit

Luis Navarro’s experience selling Totality Services highlights why RPT is so critical for an exit. When a private equity firm or a larger MSP looks at your books, they aren't just buying your clients; they are buying your delivery engine.

If two MSPs both have $5 million in revenue, but MSP A has 20 technicians (RPT of $250k) and MSP B has 35 technicians (RPT of $142k), MSP A is significantly more valuable. Why? Because MSP A has proven they have better processes, better automation, and more room for growth before they need to hire. MSP B is "people-heavy," which means their margins are thin and their growth will be expensive.

High RPT is the ultimate proof of **Operational Maturity**. It shows that the owner has successfully transitioned from a technical "doer" to a business "architect."

## Advanced Insights: The "RPT to Seat" Ratio

For those looking to go even deeper, look at your RPT in relation to your average price per seat. If your RPT is high but your price per seat is low, you are likely over-working your team and risking burnout. If your price per seat is high but your RPT is low, you are likely vastly overstaffed or incredibly inefficient.

The "sweet spot" is a high price per seat driven by strategic value (like cybersecurity and compliance) combined with high RPT driven by automation. This combination creates a "profit engine" that allows for 20-30% bottom-line EBITDA margins—the gold standard for the industry.

## Frequently Asked Questions

### Does a high Revenue Per Technician mean my team is burnt out?

Not necessarily. In fact, the highest RPT often comes from teams that have the *least* amount of stress because their work is standardised and automated. Burnout usually comes from "noise" and chaos, not from being productive. If your RPT is high because people are working 70 hours a week, that is not sustainable or efficient; it’s a management failure.

### Should I include my project team in the RPT calculation?

Yes. Your project team is a core part of your technical delivery. While their revenue is often lumpy compared to MRR, they are usually the biggest drivers of high RPT. Excluding them gives you a skewed view of your efficiency. The goal is to see how much revenue the *entire* technical engine can produce.

### How does Revenue Per Technician differ from Gross Margin?

Gross Margin tells you how much money is left after paying the direct costs of service (technician salaries, tools, etc.). RPT tells you how *productive* those technicians are. You can have a good Gross Margin but low RPT if your technician salaries are very low, but that usually means you have a high-turnover, low-skill team, which hurts you in the long run.

### What is the fastest way to improve RPT?

The fastest way is usually a combination of two things: implementing a strict "standard stack" for all new clients and automating the most common 5 tickets in your help desk. Beyond that, increasing your project revenue through structured [Security Reviews](https://MSP Agenda.com/security-reviews/) will provide the biggest jump in the numerator of the RPT equation.

### Is $250,000 RPT realistic for a small MSP?

Absolutely. Small MSPs actually have an advantage in RPT because they have less "management bloat." A team of 3-4 highly skilled, highly automated technicians can often outperform the RPT of a 50-person firm. The key is staying disciplined and not taking on "bad" clients who demand manual, non-standard work.

### How often should I review this metric?

You should calculate your RPT monthly, but look at it as a 3-month and 12-month rolling average. Monthly spikes (like a large hardware refresh project) can make one month look incredible, but the long-term trend is what matters for business planning and valuation.

### How does RPT help with hiring decisions?

RPT is your best "hiring trigger." If your RPT is at $275,000 and your team is starting to feel the pressure, you know you have the budget and the capacity to hire a new technician while staying profitable. If your RPT is only $150,000 and the team feels overwhelmed, hiring another person is the *wrong* move—you need to fix your processes first.

Ultimately, Revenue Per Technician is about clarity. It takes the complex, often messy reality of IT services and turns it into a clear indicator of business health. By focusing on this metric, you move away from being a technical shop and start acting like the high-value, commercially minded business leader your clients need you to be.

At MSP Agenda, we’ve lived this journey. We know that the path to an eight-figure exit isn't paved with more tickets—it’s paved with better systems, clearer communication, and a relentless focus on efficiency. Whether you are just starting to scale or looking to optimise for a sale, RPT is the compass that will lead you there.

---

Source: https://mspagenda.com/glossary/revenue-per-technician
Last updated: 2026-06-09