The Definition, and the Word That Matters
An MSP, short for managed service provider, is a company that takes ongoing responsibility for a client's IT under a contract and bills a recurring fee for it. The word that matters is ongoing. A break-fix shop is paid when something goes wrong, so its revenue rises when the client's environment gets worse. An MSP is paid the same whether the month is quiet or chaotic, which reverses the incentive: every problem prevented is margin kept.
That reversal explains almost every other feature of the business. It is why an MSP invests in monitoring, patching, standards and documentation that a break-fix shop could never justify. It is why the MSP cares about which firewall and which backup product a client runs. And it is why the health of an MSP is measured in monthly recurring revenue rather than in hours sold.
If you are an MSP owner, the definition is also a test of your own contracts. Any agreement where you still earn more when the client has a bad month is partly break-fix, whatever the proposal calls it.
What an MSP Usually Takes Responsibility For
The scope is set by contract rather than by any industry definition, but most MSP agreements cover a recognizable core. Where the boundary sits is worth reading closely, because it is where disputes happen and where unpaid work hides.
- Endpoints and servers: patching, antivirus or EDR, configuration standards and lifecycle replacement advice.
- Networks: firewalls, switches, wireless and the internet connection, including vendor escalation when a carrier is at fault.
- Identity and email: user accounts, MFA coverage, mailbox administration and licensing.
- Backup and recovery: running the jobs, watching the backup success rate and proving restores actually work.
- A service desk for the client's users, with response and resolution targets written into an SLA.
- Planning: roadmaps, budgets and business reviews, often delivered by a vCIO through a regular QBR.
Items that commonly sit outside the recurring fee include projects such as migrations and office moves, line-of-business application support, hardware, and third-party software licenses. Each exclusion should be written down, because a client will assume anything unwritten is included.
Taking responsibility starts before the first invoice. A new client's environment is rarely documented, rarely standardized and often carries accounts and devices nobody can explain. A structured onboarding, such as the 30-day client onboarding checklist, is where the MSP finds that risk, prices it, and brings the environment up to the standard the recurring fee assumes. Skipping it means inheriting problems you have already agreed to own.
How an MSP Differs From the Alternatives
Clients compare an MSP against other ways of getting IT done, and each comparison changes the sales conversation. The table below is the version to have in your head when a prospect says they already have someone.
| Model | How It Is Paid | Who Carries the Risk | What It Means for the MSP |
|---|---|---|---|
| Break-fix | Per hour or per incident | The client pays more when things break | Competes on hourly rate; no incentive to prevent problems |
| Fully managed MSP | Recurring fee per user, device or site | The MSP absorbs the cost of problems | Profit depends on standards, tooling and efficiency |
| Co-managed IT | Recurring fee for a defined share of the work | Split by written agreement | Needs clear boundaries and more coordination time |
| Internal IT staff | Salary and benefits | The client, entirely | A partner for co-managed work, or a future prospect |
| Staff augmentation | Per hour or per placed person | The client directs the work | Sells capacity, not outcomes; not an MSP relationship |
The middle row is the one most often misunderstood. Co-managed IT is a real service with its own pricing and contract terms, not a discounted version of fully managed support.
How MSPs Charge
Most MSPs bill a flat monthly fee tied to something countable: users, devices, sites, or a bundle of all three. The details are covered in how MSPs price their services, but the principle is simple. The fee should cover the labor, tools and overhead needed to deliver the promised outcome, plus margin, and it should not depend on how many tickets the client opens.
Two numbers keep the pricing honest. The all-in seat price tells you what a client actually pays per user once every line item is counted, and the managed services gross margin tells you whether that price covers delivery. The managed services pricing calculator is a quick way to test a quote before it goes out.
Unlimited support plans, sometimes called AYCE, are common, but they only work when the MSP controls the standards of the environment. Offering unlimited support on an environment you are not allowed to standardize is how a contract turns into a loss.
The Tools Behind the Service
Recurring delivery at scale depends on software. Two platforms sit at the center of most MSPs: RMM to monitor and manage client machines, and PSA to run tickets, time, contracts and billing. The difference is covered in PSA vs RMM. Kaseya's 2025 benchmark survey found that 95% of MSPs say connecting their RMM, PSA and IT documentation tools is essential.
Around those two sit a documentation platform, a password vault, backup software, a security stack, and often an outsourced NOC or security operations service. The tool bill is one of the largest costs an MSP controls directly, so every product should earn its place on the stack by saving labor or reducing risk.
How to Tell Whether an MSP Is Healthy
Because revenue is recurring, an MSP can look busy and still be unprofitable. A small set of measures separates the two, and they are worth tracking monthly from the first client onward.
- Gross margin on managed services, which shows whether delivery costs are under control.
- Gross revenue retention and logo churn, which show whether clients stay.
- Endpoints per technician, which shows whether standards and automation are doing their job.
- Tickets per endpoint, which falls when the environment is well managed and rises when it is not.
- Recurring revenue as a share of total, which shows how much of the business is truly managed rather than project or break-fix work.
If you want a structured view of where your own business stands, the MSP maturity assessment scores the areas above and more.
Healthy numbers also depend on people. An MSP sells the judgment and availability of its technicians, so employee turnover and technician billable utilization belong on the same report as margin. When a senior technician leaves, the knowledge that was never written down leaves too, and the clients notice before the owner does.
Where the MSP Model Is Heading
Security has moved from an add-on to the center of the offer. In the same Kaseya 2025 survey, 76% of MSPs said their clients are most concerned about security, and 67% named security among their five fastest-growing revenue categories. For an MSP owner, that means decisions about MDR, zero trust and whether you need a SOC are now core service decisions, not side projects.
The same survey found that 64% of MSPs said clients want guidance on best practices, not just tools. That is the argument for building advisory work into every agreement: the MSPs that can explain risk in business terms are the ones clients keep. If you are earlier in the journey, the Starting an MSP section covers the first decisions in order.
Common Questions
Is an MSP the same as an MSSP?
No. An MSSP focuses on security operations such as monitoring for threats and responding to incidents, while an MSP runs the whole IT environment. Many MSPs now resell or partner with an MSSP rather than building that capability themselves.
Do you need a license or certification to operate as an MSP?
There is generally no license required to call yourself an MSP. Certifications and audits such as SOC 2 matter because clients and their insurers ask for them, not because the law requires them to operate.
Can a one-person business be an MSP?
Yes, if it bills recurring fees for ongoing responsibility. The risk is coverage: a sole operator needs a written plan for holidays, sickness and after-hours incidents before promising response times.
What is the difference between an MSP and a VAR?
A value-added reseller earns mainly from selling hardware and software with some services attached. An MSP earns mainly from recurring service fees, and product sales are secondary.
Do MSPs only serve small businesses?
Most MSPs focus on small and mid-sized organizations, but many serve larger clients through co-managed agreements that support an internal IT team rather than replacing it.
Is a cloud provider an MSP?
Not by itself. A cloud provider supplies infrastructure, while an MSP takes responsibility for how a client's systems are configured, secured and supported, which may include cloud services from several providers.