A managed service provider (MSP) is a company that runs part or all of another organization's IT for a recurring fee. A contract sets what is covered and how fast the MSP responds. MSPs do most of the work remotely: they monitor systems, fix problems, and answer users' tickets.
In staffing, MSP can also mean a managed services program for contract workers. This page is about IT.
Professional services automation (PSA) software manages projects, billing, assets, and inventory. We build SherpaDesk, a helpdesk and PSA a small IT team can run alone. Two founders who ran their own MSP have built it since 2001.
So this guide covers both sides: what an MSP is for the client, and what running one takes for the owner.
What Is An MSP?
An MSP is an outside company that manages a client's IT infrastructure and end-user systems, mostly from off site. The client keeps the business; the MSP keeps the servers, laptops, network, and accounts working.
The word that matters is "managed." A break-fix technician shows up when something breaks and bills for that job.
An MSP is paid on a schedule, often monthly, to keep systems running in the first place. What the MSP owes in return is written down in a service level agreement, or SLA.
Definition
A service level agreement (SLA) is a commitment between a service provider and its customers. It covers responsibilities, the type of service, expected performance such as response times, and the terms for reporting, resolution, and termination.
Small and mid-sized businesses, nonprofits, and government agencies hire MSPs for a defined set of day-to-day services. Some MSPs specialize in one segment of IT, such as data storage. Others serve one industry, such as legal, financial services, healthcare, or manufacturing.
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) describes MSPs a little more broadly. They deliver, operate, or manage information and communications technology services for customers "via a contractual arrangement". The contract is what separates an MSP from the technician you call once a year.
Where The Term Comes From
The MSP model grew out of the application service providers (ASPs) of the 1990s, which hosted software for clients remotely. Early MSPs focused on remote monitoring and management of servers and networks, then widened what they covered. Today an MSP's offerings can include infrastructure, software, business process support, and cybersecurity.
That history explains why the term is so wide. A two-person shop looking after 15 dental offices and a global outsourcer running a bank's data centers both call themselves MSPs. The rest of this guide is written for the first one.
Why MSPs Matter
Take a 20-person business whose IT work fills a few hours a week. A full-time systems administrator would sit idle most days. Someone still has to patch the server, reset passwords, set up the new hire's laptop, and answer the call when email stops.
An MSP fills that gap. TechTarget's list of benefits includes filling staff shortages, providing expertise, constant network monitoring, and cost efficiency.
The in-house alternative has a clear price: salaries, shown as US medians in the comparison table below. Those are wages only, before benefits, tools, training, and cover for vacations.
An MSP spreads one team's skills across many clients, so each client pays for a share of that team rather than a whole salary.
The fee structure matters as much as the skills. Managed services usually run on a monthly subscription, which helps clients budget. IT becomes a planned monthly cost instead of a surprise invoice after an outage.
Why It Matters To The People Who Run Them
For IT people, an MSP is also a business you can start with the skills you already have. Someone planning a new MSP wrote in r/msp in January 2025: "It'll basically be a two man show for the first year or so."
That small team is who this guide is for. With two people, nobody is free to administer tools or chase timesheets, so the work after the fix has to run inside the day. We come back to that in what running a small MSP takes.
How An MSP Works
There is no single setup for every client, so an MSP offers different service options for different environments. One common sequence runs in five steps.
-
Assess the client's environment
Work typically begins with an assessment of the client's current environment. The MSP lists devices, users, software, and the gap the client wants filled, whether that's a missing role or a missing skill.
Example: a 25-person accounting office has one server, 30 laptops, Microsoft 365, and an office manager who resets passwords between other jobs.
-
Agree the contract and the SLA
The agreement names the services, the response times, and the reporting the client gets. It also says what happens when the contract ends.
Common mistake: leaving "out of scope" undefined. The first project request then turns into an argument about who pays.
-
Onboard the tools and the access
The MSP installs its remote monitoring and management (RMM) tool, which lets off-site technicians maintain networks, servers, desktops, and mobile devices. It also gets administrator accounts on client systems, which CISA calls privileged access.
Common mistake: shared admin passwords. CISA tells MSPs to enforce multifactor authentication on every account that reaches customer environments and to treat those accounts as privileged.
-
Run the day-to-day work
Monitoring, remote support, proactive support, and scheduled maintenance are core service types. Every request should become a ticket, and every hour spent on it a time entry. Without that record, the monthly review has nothing to stand on.
Example: Monday brings a printer that's offline, a new hire who needs a laptop, and a backup alert from Saturday. That's three tickets and three time entries for the same client.
-
Report and bill each month
The client pays the agreed fee on schedule, often monthly, and gets a report on what the MSP did against the SLA. Services can sit in one bundled price or be listed line by line, and the contract should say how out-of-scope work is billed. One r/msp owner summed up the choice: "you can either bundle everything or line item them."
Common mistake: billing from memory at month end. Hourly extras nobody logged never reach the invoice.
The steps look tidy on paper. Clients don't see the admin work behind steps 4 and 5, and in a two-person shop it falls to the same people who work the tickets.
What Services Do MSPs Offer?
The service list varies by provider, but the same groups appear in neutral definitions again and again.
- Infrastructure management: servers, networks, and the systems users depend on.
- Technical support: the helpdesk users call or email when something stops working.
- Monitoring and alerting: constant monitoring of client systems and action on alerts.
- Scheduled maintenance: updates and checks done on a calendar, not after a failure.
- Cybersecurity: security software, plus control over who gets admin access.
- Compliance and risk support.
- Contract management.
- Business process and support functions beyond IT itself.
TechTarget's list even includes payroll services. That breadth is why one word covers such different businesses.
For a small MSP, the useful question is what not to sell. Each service you add needs a tool, a skill, and a line in the contract. Start with what clients already call you about, and price those well before adding a new line.
Subscribe to the SherpaDesk Blog.
Get Tips for Running IT With a Small Team.
Loading form…
The form couldn’t load. Please try again.
Or start your free trial →SHERPADESK · FREE TRIAL
Resolve tickets.
Turn time into revenue.
Bring support tickets, billable time, and invoicing into one place. Built for small IT teams and MSPs.
- 14 days free
- No credit card required
After your trial, keep your first agent free forever.
SHERPADESK · LIVE DEMO
See tickets, time,
and billing work together.
Walk through ticketing, time tracking, and billing with a product specialist. See how SherpaDesk fits the way your team works.
- 15 minutes
- Your workflow, your questions
A live walkthrough tailored to your team.
Types Of MSPs
MSPs differ by how much of the client's IT they take on and by what they focus on. TechTarget groups them into three tiers by scope and names focus areas such as one IT segment, one industry, or security.
We add co-managed IT as its own row. It's our classification, based on TechTarget's note that an MSP often fills a gap or role in a client's IT staff.
| Type | What it takes on | Who it fits |
|---|---|---|
| Pure-play MSP | Monitoring and alerting on client systems; usually a smaller provider | Clients with someone on site who fixes what the alerts find |
| Staffing legacy MSP | Broad IT services for mid-level and enterprise organizations | Larger organizations adding capacity |
| High-level MSP | Extensive outsourcing of IT processes | Organizations handing over most of their IT |
| Segment specialist | One area of IT, such as data storage | Clients with one hard problem |
| Vertical MSP | One industry, such as legal, financial services, healthcare, or manufacturing | Clients with industry software and rules |
| Co-managed IT (our classification) | Fills a gap or role alongside the client's own IT staff | Internal IT teams short on hours or skills |
| MSSP | Specialized security services, such as remote firewall administration and other security-as-a-service offerings | Clients who want security run by a specialist |
In practice the labels blur. A three-person MSP can run monitoring only for one client and act as the whole IT department for the next. What matters for the business is that each client's contract says which role you're playing.
MSP Vs MSSP Vs Break-Fix Vs In-House IT
These four ways to get IT support differ on who pays for what, how long the relationship runs, which hours are covered, and what each side is rewarded for.
| Model | What it is | How it's paid | Relationship | Hours of coverage | What it's rewarded for | Fits |
|---|---|---|---|---|---|---|
| MSP | Outside company with ongoing responsibility for IT | Flat fee per device, user, or bundle, often monthly | Ongoing, under an SLA | Whatever the SLA sets; after-hours only if contracted | Fewer problems, since the fee doesn't grow with them | Small and mid-sized organizations without a full IT team |
| MSSP | Provider of specialized security services | Recurring service contract, like other managed services | Ongoing | Whatever the contract sets | Catching and stopping threats | Organizations that want security run by a specialist |
| Break-fix | Support only when needed, after something breaks | Hourly or a flat rate per job | Per job | On the contractor's terms, per job | Fixing problems; "little incentive to prevent them" | Rare, one-off needs |
| In-house IT | Your own employees | Salaries; US medians, all industries: $61,860 for computer user support specialists, $99,130 for network and computer systems administrators | Employment | Working hours, plus any on-call you staff | Whatever the employer measures | Organizations with enough work for full-time staff |
US median annual wages, all industries, May 2025.
MSP vs MSSP. Managed security service providers offer specialized security services, such as remote firewall administration and other security-as-a-service offerings. Some general MSPs provide security software and awareness training, but many have no major focus on cybersecurity. Check the contract rather than the name.
MSP vs break-fix. The difference is the incentive. Break-fix providers profit from problems, so there's "little incentive to prevent them". An MSP offers continuous monitoring, maintenance, and support under an SLA.
An MSP can still take hourly jobs from clients who won't sign a contract. Keep those hours out of your fixed-fee numbers so each model shows its own margin.
MSP vs in-house IT. The two often work together. In a co-managed setup, the MSP fills a specific gap or role in the client's IT staff. A school district or a 200-person company might keep its own helpdesk and contract after-hours monitoring to an MSP.
How To Choose An MSP
Choosing an MSP comes down to five things: scope, the SLA, security, access and exit, and cost. Check each one in the contract, not in the sales deck.
The exit item matters more than it looks. CISA notes that disabling MSP accounts can be overlooked when a contract ends.
How Do MSPs Make Money?
Under a managed contract, the client pays a flat fee on a regular schedule, often monthly. What changes from one MSP to the next is the unit the fee is counted in.
| Model | How the fee is counted | Works when |
|---|---|---|
| Per device | A flat fee for each device the MSP manages | Clients have a stable count of desktops, servers, and printers |
| Per user | A flat fee for each user, covering everyone with several devices | People carry a laptop, a phone, and a tablet |
| All-inclusive | One flat fee for support and management of the client's IT | You know the client's environment well enough to price the risk |
| Tiered | Bundles of services the client picks from | Clients want a choice between basic and full coverage |
| Monitoring only | Monitoring and alerting, nothing else | The client has its own staff to act on alerts |
| Break-fix or project work | Hourly, or a flat rate per job | Work falls outside the contract, or the client won't sign one |
The fee is fixed, so profit depends on how many hours each client actually takes. Example: a client who calls twice a week on a per-user plan can cost more to serve than they pay.
Owners disagree about how much to bundle. "We find it easier to include everything in one price," one r/msp owner wrote in January 2025. The other option the same owner named is to line-item each service.
Either works if the contract says which is which.
Time entries do two jobs here. Inside the fixed fee, they show what each client costs to serve and whether the price still leaves a margin. Outside it, hourly extras and overages reach the invoice only if someone logs them.
A Saturday server move or an extra user setup that nobody logged is work done for free. The billable hours you never captured are the margin you never made.
What Running A Small MSP Takes
The real question for a small MSP is whether the people already working tickets can also run the business side, without a dedicated admin. In a two-person shop there is no spare person to hire for that.
The business side is four objects, every week:
- Ticket: every request in one queue, whether it came by email, phone, or a monitoring alert.
- Time entry: every hour logged against a client and a ticket, billable or not.
- Contract: what each client pays, which hours are included, and what counts as extra.
- Invoice: the monthly fee plus the extras, sent on time and matched in accounting.
Take a two-person MSP: the owner and one technician, both working tickets all day. Nobody owns these four objects full time, so the owner works through them after the last ticket closes. For a team like that, the tools have to be simple enough to run in the gaps between tickets.
Practitioners name two tools as the base. "Your best tools start with your RMM and PSA," one r/msp veteran told someone planning a new MSP, calling them "the operational foundation of your business".
Our Guide To PSA Software covers how that works ticket by ticket, and Best MSP Software compares the tools with prices.
Month end shows whether the setup runs without a spare person. One r/msp owner described their PSA-to-accounting routine in November 2025.
"End of month a powershell pulls line items from Syncro API - This works well sometimes." Then: "This takes a lot of time and manual checking."
Another replied that their PSA connects to QuickBooks Online or Xero and "just creates the invoices automatically". The difference is the extra step.
The first owner maintains a separate script to pull the lines out, and its output still needs manual checking. The second reports a PSA that connects to accounting directly.
What month-end admin time costs at your rate
hours × rate
How this works in SherpaDesk
Run by the people who already work the tickets
A helpdesk and PSA a small IT team can run alone: that's what we build. You don't need a dedicated admin, because the business side lives where your technicians already work.
You forward your support inbox to a dropbox address, and emails become tickets. Technicians log time on the ticket by timer, timesheet, email, or the mobile app. Each client gets its own rate plan, and a contract can include prepaid hours.
The proof is at month end: uninvoiced time collects in "Ready to Invoice", grouped by contract. Supported accounting packages include QuickBooks Online, Xero, and FreshBooks.
No contract. No implementation project. No dedicated admin.
Base Camp is $45 per agent per month ($40 billed annually), and your first agent is free, forever. 14 days free, no card, and setup takes less than 2 minutes.
Limits Of The MSP Model
An MSP isn't the right answer for every organization, and the model carries risk on both sides of the contract.
For the client, the main costs are dependence and distance. TechTarget's list of challenges includes depending on a third party, waiting on a response, and information the client can't reach directly.
Not all MSPs offer security measures, either. A client that assumes "managed" includes security can find out otherwise after an incident.
Watch out
An MSP holds trusted network connections and privileged access to the clients it serves. That makes it a target: compromising one MSP can open many customer networks. CISA tells clients to disable MSP accounts when a contract ends and to keep backups separate and offline.
For the MSP, the risk is the fixed fee. Every unplanned hour on an all-inclusive client comes out of margin, which is why every contract needs clear limits.
Who this isn't for
Full outsourcing is a poor fit when your own staff already covers the daily queue and you need help with one piece. Co-managed support or contracted after-hours cover fits that case better. If you need one fix a year, break-fix covers it.
On the provider side, a shop that sells only hourly projects is closer to break-fix, and its routine is lighter. You get a helpdesk and PSA, not an RMM.
We don't build RMM. We integrate with yours, and the stack stays yours. The NinjaOne integration needs High Camp, $55 per agent per month.
What Is An MSP Job?
An MSP job is any role inside a managed service provider. The common ones are helpdesk technician, systems or network administrator, engineer, account manager, and owner.
US government data shows where two of those occupations work. The industry "computer systems design and related services" employs 21% of computer user support specialists, the largest share of any industry. It also employs 16% of network and computer systems administrators, again the largest share.
Computer user support specialist jobs require some computer knowledge but not necessarily a college degree. Median wages for both occupations are in the comparison table.
In a two-person MSP, those roles land on the same people. The person who answers the phone at 8 a.m. may configure a firewall at noon and send invoices on Friday. If you're hiring your first technician, write down which of those jobs you're handing over and which you're keeping.
Terms Used On This Page
- Break/fix
- IT support delivered only when needed, typically after something breaks, billed hourly or per job.
- MSP managed service provider
- A company that manages a client's IT infrastructure and end-user systems, mostly remotely, for a recurring fee.
- MSSP managed security service provider
- A provider of specialized security services, such as remote firewall administration and other security-as-a-service offerings.
- PSA professional services automation
- Software an MSP uses to manage projects, billing, assets, and inventory.
- RMM remote monitoring and management
- Software that lets off-site technicians maintain networks, servers, desktops, and mobile devices.
- SLA service level agreement
- The commitment that sets responsibilities, service type, expected performance, and terms for reporting, resolution, and termination.
Frequently Asked Questions
What does MSP stand for in IT?
In IT, MSP stands for managed service provider: a company that manages a client's IT infrastructure and end-user systems, mostly remotely, for a recurring fee. The client pays on a schedule, often monthly, and an SLA sets what's covered.
In staffing, the same letters can mean a managed services program for contract workers. See the Full Definition.
What are the different types of MSP?
By scope, MSPs are often grouped as pure-play (mostly monitoring), staffing legacy (broad services for mid-level and enterprise clients), and high-level (extensive outsourcing). By focus, some specialize in one segment of IT or one industry, and MSSPs specialize in security.
Some also work alongside internal IT teams, which we list as co-managed IT. The Types Table sets them side by side.
What is the difference between an MSP and an MSSP?
An MSSP offers specialized security services, such as remote firewall administration and other security-as-a-service offerings. A general MSP covers infrastructure, support, monitoring, and maintenance, and may or may not include security.
Many MSPs have no major focus on cybersecurity, so check the contract. See the Comparison Table.
What is an MSP job?
An MSP job is any role inside a managed service provider: helpdesk technician, systems or network administrator, engineer, account manager, or owner. In the US, computer systems design and related services employs 21% of computer user support specialists, the largest share of any industry.
Their median wage across all industries was $61,860 in May 2025. At a small MSP, one person may cover several of these jobs. More in MSP Jobs.
What software does an MSP use?
Practitioners name two core tools. An RMM tool lets technicians maintain client devices from off site, and a PSA tool manages projects, billing, assets, and inventory.
One r/msp veteran called them "the operational foundation of your business". Our Best MSP Software guide compares the options with prices.
How do I choose an MSP?
Check five things in the contract: scope, the SLA, security, access and exit, and cost. The SLA should state responsibilities, response times, reporting, and termination terms.
Ask whether security is included, since not all MSPs offer it. The Checklist covers the rest.
Patrick co-founded SherpaDesk and has led it as CEO since 2013. He has worked with IT service providers since 1998, first on network projects for schools and government offices, then on the helpdesk software their technicians use every day.