How to Sell an IT Services or MSP Business

MRR versus break-fix and project work: why the mix drives the multiple

Every IT services business is really a blend of three revenue types: monthly recurring revenue from managed services contracts, hourly or per-incident break-fix work, and one-time project work like network builds, migrations or hardware refreshes. Buyers value these very differently, and the blend is usually the first thing a buyer's advisor calculates from the financials.

MRR from managed services agreements — flat-fee monitoring, patching, help desk and support billed monthly per user or per device — is the closest thing this industry has to a subscription business. It is predictable, it renews without a new sales effort each month, and a buyer can reasonably forecast next year's revenue from this month's contract roster. That is exactly the kind of revenue that supports a premium multiple.

Break-fix revenue, where clients call only when something breaks and pay by the hour, is the opposite. It has no contractual floor, it depends on the phone ringing, and it typically ties up the owner or senior technicians in ways that don't scale. A shop that is mostly break-fix looks more like a service job than a business, and buyers price it accordingly.

Project revenue sits in between. A steady cadence of projects sourced from the existing client base is a healthy sign of account growth, but project revenue is lumpy and doesn't repeat on its own, so buyers generally don't count it toward the recurring base even when it's substantial. An MSP with 70% or more of revenue in contracted MRR, a modest project pipeline layered on top, and only a small break-fix tail is the profile that reaches the top of the range.

Contract terms, auto-renewal, per-seat pricing and assignability

Not all MRR is equal. A one- or three-year managed services agreement with automatic renewal, a defined per-seat or per-device rate, and a real notice period for cancellation gives a buyer genuine forward visibility. A stack of clients on month-to-month agreements, verbal understandings, or contracts that lapsed years ago and were never renewed is a much weaker asset even though the monthly invoice looks identical today.

Per-seat or per-device pricing matters because it's the mechanism that lets revenue grow automatically as a client's headcount grows, without a renegotiation. Flat-fee agreements that haven't been repriced in years, especially for clients that have grown substantially since signing, understate the value of the relationship and often flag an overdue price increase a buyer will want to make post-close.

Assignability is a detail sellers frequently overlook. Many MSA templates require client consent to assign the contract to a new owner, and some allow the client to terminate on a change of control. Read your actual agreements, not just your standard template, since older clients are sometimes on an outdated version. Buyers will ask for a full contract schedule during diligence, and finding assignment problems late in a deal is a common and avoidable way to lose momentum or renegotiate price.

Auto-renewal with a defined notice window (60 or 90 days is typical) also protects a buyer from a wave of clients quietly lapsing right after closing. If your contracts don't currently include auto-renewal language, updating them before you go to market is a low-cost fix that removes a diligence objection.

Client concentration, tenure and vertical specialization

Client concentration is scrutinized closely in this industry because MSP client relationships run through a small number of people — often just the owner and one or two senior technicians. If a single client accounts for more than roughly 10% to 15% of revenue, buyers worry about what happens if that relationship doesn't survive a change of ownership, and concern grows quickly above that threshold.

Average client tenure is one of the best indicators of how sticky the book really is. An MSP where the median client has been on board for four or five years demonstrates that the service holds up over time even as account managers or technicians change. A book built mostly in the last 18 months, even if revenue looks strong today, hasn't yet proven it can survive normal churn, let alone a sale.

Vertical specialization can work for or against a business depending on execution. An MSP that has built real depth in, say, dental practices, law firms or manufacturing — with compliance knowledge, referral relationships and a reputation in that niche — often commands a premium because it's harder to replicate and comes with a built-in growth channel. The same specialization becomes a risk if it means concentration in an industry facing its own headwinds, or if the specialized knowledge lives entirely in the owner's head rather than in documented processes the team can execute.

Gross margin per seat, tool stack costs and pass-through revenue

Buyers look past top-line MRR to gross margin per seat, since two MSPs billing the same per-user rate can have very different economics depending on their tool stack and staffing ratio. Core costs to model include the RMM (remote monitoring and management) platform, PSA (professional services automation) software, backup and security tools, and any outsourced NOC or help desk overlay — all of which are typically priced per seat or per device and scale with the client base.

A rising tool stack cost per seat without a corresponding increase in client pricing is a margin problem that shows up clearly once someone builds a seat-level model, even if the income statement still looks fine in aggregate. Buyers will ask for the vendor contract list and current per-seat costs, and will often re-underwrite margins assuming their own tool stack pricing, which can be better or worse than yours depending on scale.

Hardware and software license resale — reselling firewalls, servers, Microsoft 365 licenses and similar — is usually necessary to serve clients well, but it's low-margin, pass-through revenue that inflates top-line numbers without adding much profit. Buyers generally strip this out or heavily discount it when calculating the revenue base a multiple gets applied to, so a business that reports revenue heavily padded by hardware resale looks smaller, and often more valuable per dollar of real service revenue, once that's separated out clearly in the financials.

Technician team, certifications, documentation and key-person risk

The technician team is the delivery engine of an MSP, and buyers evaluate it almost as closely as the client contracts. A team with a mix of tiers — a help desk layer for routine tickets and senior engineers for escalations and projects — that isn't entirely dependent on one irreplaceable person is worth materially more than the same headcount concentrated around a single star technician who holds all the institutional knowledge.

Certifications (Microsoft, CompTIA, vendor-specific credentials for the security and networking tools you deploy) matter both for client-facing credibility and because some client contracts, particularly in regulated industries, require a minimum level of certified staff on the account. A team with current, relevant certifications is easier for an acquirer to keep in place and easier to grow.

Documentation is where many MSPs lose value without realizing it. If client network diagrams, passwords, configurations and standard operating procedures live in one senior technician's head or personal notes rather than in the PSA and a shared knowledge base, the business carries serious key-person risk that has nothing to do with the owner. Buyers will ask how documentation is maintained and may sample a few client accounts to check it against reality. Getting documentation genuinely current, not just claimed to be current, is one of the highest-leverage things to do in the year before a sale.

Cybersecurity posture, insurance and past incidents

MSPs occupy a uniquely sensitive position: a breach at the MSP itself, or a preventable breach at a client that traces back to an MSP's negligence, can be catastrophic, and buyers diligence this closely given several well-publicized supply-chain incidents in the industry. Expect detailed questions about your own security stack, multi-factor authentication enforcement across client environments, patch management discipline, and whether you follow a recognized framework such as CIS Controls or NIST.

Errors and omissions (E&O) insurance and cyber liability coverage are close to mandatory in this industry, both for your own protection and because buyers will want them assumed or replaced at close. Gaps in coverage, or coverage limits that look thin relative to the size of clients you serve, are a red flag a buyer will price in or insist you fix before closing.

Past incidents don't automatically kill a deal, but they must be disclosed and explained. A buyer wants to know what happened, what changed afterward, and whether any client relationships or legal exposure remain outstanding. An MSP that can show a clean incident history, or a well-handled past incident with documented remediation and no lingering liability, is in a far stronger position than one where a serious incident surfaces for the first time during diligence.

Owner dependence, growth engine, and who buys MSPs

As in most owner-operated service businesses, the biggest single factor separating the bottom of the range from the top is how dependent the business is on the owner personally. If you are the lead salesperson, the escalation point for every unhappy client, and the person who ultimately signs off on every quote, the business is a well-paid job wrapped in a corporate structure, and buyers discount for that. An MSP with a service delivery manager running day-to-day operations, a defined sales process that doesn't require the owner in every meeting, and client relationships that are institutional rather than personal is a fundamentally more transferable asset.

Buyers also want to see a growth engine, not just a stable book. That means a repeatable way new clients are found — referral partnerships with CPAs, insurance brokers or industry associations, a functioning outbound or marketing motion, or a track record of expanding wallet share within existing accounts through security add-ons and projects — rather than growth that has historically come entirely from the owner's personal network.

The buyer pool for MSPs has become considerably more sophisticated over the past several years. Private equity-backed platform roll-ups actively acquire MSPs to consolidate tool stacks, cross-sell services and build scale, and they tend to pay the highest multiples for businesses with strong MRR, low concentration and clean documentation, because those businesses integrate easily. Local and regional buyers — often other MSP owners looking to add a book of business or enter a new geography — are more common for smaller deals and may value technician retention and local reputation more heavily than a platform buyer would. Understanding which type of buyer is realistic for your size and profile shapes both the achievable multiple and how you should prepare the business for sale.