In the world of Managed Service Providers (MSPs), technical proficiency is the baseline, but commercial clarity is what determines the winner. Average Revenue Per Account (ARPA) is one of the most vital financial metrics for any MSP looking to scale beyond a small team and a handful of clients. It represents the average amount of revenue generated per client over a specific period, usually monthly or annually.
Understanding your ARPA allows you to see past the noise of total top-line revenue and focus on the quality of your client base. It reveals whether you are truly growing through value or simply adding administrative burden. When Luis Navarro co-founded Totality Services, he didn't come from a technical background; he focused on the commercial levers—like ARPA—that take a business from a local startup to a highly profitable MSP with an eight-figure exit.
If your ARPA is stagnant while your seat count is rising, you aren't scaling; you’re just getting busier. High-performing MSPs use this metric to identify which clients are underserved, which services are underpriced, and where the next project opportunity lies. By the time you finish this guide, you will know how to calculate, analyse, and systematically increase your ARPA to drive enterprise value.
Key Takeaways
- Commercial Health Check: ARPA is the ultimate indicator of your MSP's ability to cross-sell, up-sell, and deliver high-value strategic services.
- Standardisation is Key: Higher ARPA is almost always linked to a standardised "all-in" seat price and consistent security stacks.
- Quality Over Quantity: A high ARPA often indicates a healthier business than a high client count with low individual spend.
- Strategic Reviews: Regular security and business reviews are the primary drivers for moving the needle on per-account revenue.
- Operational Efficiency: As ARPA increases through better service bundles, your operational overhead per dollar earned typically decreases.
- Valuation Impact: Potential acquirers look for high ARPA as a sign of client "stickiness" and a sophisticated sales process.
What is Average Revenue Per Account (ARPA)?
Average Revenue Per Account (ARPA) is a profitability metric that measures the average revenue generated per client relationship. For MSPs, it is typically calculated on a Monthly Recurring Revenue (MRR) basis, though it can also include non-recurring project revenue to provide a "Total ARPA" view. It helps leadership understand how much the average client is worth to the business and identifies the gap between your smallest and largest accounts.
Core Components of ARPA
- Monthly Recurring Revenue (MRR): The predictable, baseline fees for support, licensing, and managed security.
- Project Revenue: One-time professional services, migrations, and hardware sales (often averaged over 12 months).
- Account Count: The total number of unique legal entities or billing relationships you manage.
| Metric Focus | Low ARPA Characteristics | High ARPA Characteristics |
|---|---|---|
| Service Model | Break-fix or basic "monitoring only" services. | Fully managed, security-first, "all-in" pricing. |
| Client Relationship | Transactional; viewed as a commodity vendor. | Strategic; viewed as a Virtual CIO or partner. |
| Security Stack | Basic Antivirus and simple backups. | Advanced EDR, SOC/SIEM, Compliance, and MDR. |
| Profitability | High overhead; thin margins per account. | Scalable; high margin per account. |
How to Calculate Average Revenue Per Account (ARPA)
Calculating Average Revenue Per Account (ARPA) is straightforward, but the nuance lies in how you segment the data. The basic formula is your total revenue divided by the total number of accounts. However, most MSPs find the most value in calculating "MRR ARPA" to strip away the volatility of hardware sales.
To get a clear picture, use this formula:
ARPA = Total Monthly Recurring Revenue / Total Number of Clients
For example, if your MSP has $150,000 in MRR spread across 60 clients, your ARPA is $2,500. If you add a one-off cloud migration project for $12,000, that client’s individual revenue for that month spikes, but it doesn't represent a sustainable increase in your account value. This is why we distinguish between MRR-based ARPA and Total-Revenue ARPA.
Why ARPA Matters to Your MSP’s Bottom Line
If you want to build a business that is attractive to investors or simply one that provides a great lifestyle for the owners, you have to care about ARPA. Luis Navarro learned through building Totality Services that a client paying $500 a month often requires the same amount of administrative attention as a client paying $5,000. The difference is the $5,000 client is actually profitable.
1. Efficiency of Scale
Every account you take on has a "cost of management." There are invoices to send, QBRs to schedule, and primary contacts to manage. When you increase your Average Revenue Per Account (ARPA), you are increasing your revenue without necessarily increasing your administrative burden at the same rate. This is the definition of scaling.
2. Identifying "The Gap"
By looking at your ARPA, you can identify "laggard" clients. If your average is $3,000 but you have ten clients paying $800, those ten clients are likely a drain on your resources. They are using your helpdesk but aren't contributing enough to the growth of the firm. You either need to move them up your stack or move them out of the business.
3. Measuring Sales Performance
Is your sales team just hunting for "low-hanging fruit" by selling basic packages? A rising ARPA indicates that your team is successfully communicating the value of higher-tier services, such as advanced cybersecurity and strategic consulting. It shows that they are selling solutions, not just licenses.
Strategic Drivers to Increase ARPA
Increasing your Average Revenue Per Account (ARPA) isn't about just raising prices—it’s about delivering more value. If you simply send a letter saying costs are going up 20%, you risk churn. If you explain that the threat landscape has changed and your new standard includes advanced threat hunting and compliance management, you are justifying the increase through value.
1. Move to "All-In" Per-Seat Pricing
The most successful MSPs have moved away from a-la-carte menus. When you offer 50 different line items, the client will always try to cut the ones they don't understand. By bundling your security stack, support, and strategic planning into a single "Modern Workspace" or "Secure Seat" price, you naturally lift your ARPA because every new user added to a client’s team comes with the full margin of your entire stack.
2. Standardise Your Security Stack
Security is the biggest lever for ARPA growth today. Clients are increasingly aware of the risks, but they don't know how to solve them. By making advanced tools like Multi-Factor Authentication (MFA) management, Endpoint Detection and Response (EDR), and Security Awareness Training mandatory parts of your offering, you increase the revenue per user and the overall account value.
3. Use Strategic Security Reviews to Drive Projects
Project revenue is the "bonus" that boosts your annual ARPA. However, projects shouldn't be random. They should be the result of a structured assessment. Using tools to conduct regular [security reviews](https://MSP Agenda.com/security-reviews/) creates a roadmap for the client. When a client sees a clear gap in their defences, a project recommendation isn't a "sales pitch"—it’s a professional recommendation for their protection.
The Relationship Between ARPA and Client Retention
There is a common misconception that higher ARPA leads to higher churn. In reality, the opposite is often true. Clients who pay more for a comprehensive service are usually more deeply integrated with your MSP. They rely on you for strategy, security, and business continuity, not just fixing a broken printer.
High-Value Clients are Stickier
When you manage a client’s entire technology lifecycle, the "switching costs" for them to move to a competitor are very high. They would have to replace their entire security stack, their backup solution, and their strategic roadmap. A client paying a low ARPA for basic services can leave you over a $50 price difference because they don't see the unique value you provide.
Account Management vs. Technical Support
Increasing ARPA shifts the relationship from the basement (technical support) to the boardroom (business strategy). When you talk to a client about their business goals and how technology supports them, you become an indispensable partner. This is a core tenet of the MSP Agenda philosophy: technology is the tool, but the business outcome is the product.
Common Mistakes When Managing ARPA
While chasing a higher Average Revenue Per Account (ARPA) is good for business, there are traps that even experienced MSP owners fall into. Avoid these pitfalls to ensure your growth remains sustainable.
- The "Kitchen Sink" Trap: Bundling too many low-margin third-party tools into your seat price without accounting for the support labour. If the tool is cheap but the tickets it generates are expensive, your ARPA goes up but your profit goes down.
- Ignoring the "Cost to Serve": If your ARPA is $5,000 but the client is so demanding that they require a dedicated tech 40 hours a week, that account is a liability. Always look at ARPA alongside your "Gross Margin per Client."
- Failing to Re-price Legacy Clients: Many MSPs have "grandfathered" clients paying rates from five years ago. These accounts drag down your average and communicate to your team that it’s okay to accept sub-par revenue for the same amount of work.
- Selling Technology, Not Risk: If you try to increase ARPA by selling "faster firewalls," you’ll get pushback. If you sell "reduced downtime" or "ransomware protection," the commercial conversation becomes much easier.
Benchmarking Your MSP
What should your Average Revenue Per Account (ARPA) actually be? This varies by market (a client in Manhattan pays more than a client in a rural town) and by vertical (law firms pay more than non-profits). However, there are some general rules of thumb for the US market.
| MSP Maturity Level | Typical Monthly ARPA (per Client) | Primary Revenue Source |
|---|---|---|
| Emerging MSP | $500 - $1,200 | Reactive support, basic O365, hardware margins. |
| Growth-Phase MSP | $1,500 - $3,500 | Managed services, basic security, some project work. |
| Strategic MSP | $4,000 - $10,000+ | Advanced security, vCIO services, high-value projects. |
Leveraging Professional Assessments to Lift ARPA
You cannot increase ARPA by sitting behind a desk. It happens in the room with the client. Luis Navarro spent over 15 years in these rooms, and he realised that the biggest barrier to higher revenue was communication. If the client doesn't understand the risk, they won't pay for the solution.
This is why [Quarterly Business Reviews (QBRs)](https://MSP Agenda.com/qbr-process/) are the engine of ARPA growth. A well-structured review does three things:
It demonstrates the value you have already delivered (justifying your current ARPA). It highlights current risks in their environment (justifying a project spend). It aligns their future business goals with your technology roadmap (setting the stage for future recurring revenue increases).
Instead of a 40-page report of "green checkboxes" that the client ignores, focus on high-impact visuals. Show them where they are today, where they need to be, and exactly what it will cost to get there. When the path to safety is clear, the budget usually follows.
ARPA as a Metric for Enterprise Value
If you are building your MSP with an exit in mind, ARPA is a metric that will be scrutinized during due diligence. Acquirers aren't just buying your contracts; they are buying your ability to generate high-margin revenue from a stable client base. A business with a high Average Revenue Per Account (ARPA) and a standardised stack is far more valuable than a fragmented one.
Standardisation reduces the "technical debt" of an acquisition. If every client is on a different plan with different tools, the buyer has to spend months migrating them. If your ARPA is high because everyone is on your "Gold Standard" security plan, you are a "plug-and-play" acquisition target. This was a critical factor in the eight-figure acquisition of Totality Services.
Advanced Tactics for ARPA Optimisation
- Implement a "True-Up" Process: Ensure you are billing for every seat, every month. Revenue leakage is a silent killer of ARPA.
- Add Compliance as a Service: For clients in regulated industries (HIPAA, CMMC), compliance management can add 20-30% to your ARPA with minimal additional tool costs.
- Co-Managed IT: Don't ignore larger firms with internal IT. You can achieve high ARPA by providing the "advanced stack" (Security, Cloud, Backup) while their internal team handles the day-to-day tickets.
Frequently Asked Questions
Does a higher ARPA always mean a better business?
Not necessarily, but it is a very strong indicator. You must also look at your gross margins. If you have a high ARPA but your "cost to serve" is equally high due to inefficient processes or expensive third-party vendors, your bottom line won't reflect the revenue. However, generally speaking, higher ARPA allows for better talent acquisition and more robust service delivery.
How often should I calculate my Average Revenue Per Account (ARPA)?
You should track this monthly. It’s a "lagging indicator" of your sales and account management performance over the previous 90 days. If you see your ARPA dipping, it might mean you are taking on too many small "problem" clients or that you aren't successfully closing project work.
Can I increase ARPA without adding more services?
Yes, through price adjustments and seat growth within existing accounts. As your clients grow, their seat count increases, which naturally raises the revenue for that specific account. However, the most significant jumps in ARPA come from adding strategic value, particularly in the realm of [cybersecurity governance](https://MSP Agenda.com/cybersecurity-governance/) and compliance.
Should I include hardware sales in my ARPA calculation?
It depends on what you are trying to measure. For valuation and operational planning, use MRR-based ARPA. This gives you the "floor" of your business. For a holistic view of client profitability, use a 12-month rolling average of total revenue (including hardware and projects) per account.
How do I handle small clients that drag down my ARPA?
You have three choices: Up-sell, Price-up, or Out-sell. First, try to move them to your minimum standard stack. If they refuse, implement a "minimum monthly spend" policy. If the client is still not profitable, it may be time to transition them to a smaller provider that is better suited for their needs, freeing up your team to focus on higher-value accounts.
What is the difference between ARPA and ARPU?
ARPA (Average Revenue Per Account) looks at the entire client entity. ARPU (Average Revenue Per User) looks at the revenue generated per individual seat. Both are important. ARPU helps you check if your per-seat pricing is correct, while ARPA helps you understand the overall health and management overhead of your client base.
Is ARPA relevant for break-fix providers?
It’s even more critical for them because their revenue is so volatile. A break-fix provider will likely have a very low and unpredictable ARPA. Measuring this is often the "wake-up call" that pushes a break-fix shop to transition into a managed services model, where they can stabilize and grow their account value.
Conclusion: The Path to Commercial Excellence
Managing an MSP is a balancing act between technical excellence and commercial discipline. Average Revenue Per Account (ARPA) is the bridge between those two worlds. It forces you to look at your clients not just as technical endpoints to be managed, but as business partnerships to be developed.
When you focus on increasing your ARPA, you are inherently focusing on providing more value. You are moving away from being a "cost centre" for your clients and toward being a strategic asset. This transition is what separates the MSPs that struggle from the ones that scale and eventually command eight-figure valuations.
MSP Agenda was born from this exact reality. Luis Navarro built Totality Services by focusing on these commercial levers, ensuring that every client relationship was profitable, standardised, and secure. Whether you are just starting out or looking to prep your business for sale, your ARPA is one of the most honest reflections of your business's health. Watch it closely, grow it intentionally, and your MSP will thrive.