Average MSP net margins sit at 8–12%. Most MSP owners are working 60-hour weeks and still wondering where the money went at the end of the quarter.

The difference between the MSPs printing 20–35% net margins and the ones grinding at break-even isn't effort. It's structure – the right niche, a pricing model that doesn't leak, a tool stack that doesn't eat your revenue, and a hiring strategy that doesn't get ahead of your cash flow.

This guide covers all of it.

Before You Start: The Reality Check Nobody Wants to Give You

If you've been working in IT long enough, you probably have a moment – maybe more than one – where you thought: I could just do this myself.

You might be right. But "I could do this" and "I'm ready to build a business" are two different things.

Running an MSP is running a business. Here's a nice take from one guy in r/msp.

Reddit comment from u/mobchronik on starting an MSP business

Step 1: Pick a Niche Before You Do Anything Else

The fastest path to struggling as an MSP is taking every client who calls. You end up with a dental office, a plumbing company, a law firm, and a restaurant – all with different software stacks, compliance requirements, and escalation patterns. You can't standardize. You can't automate. You're constantly firefighting instead of building.

Vertically-focused MSPs earn 30% higher profit margins and 28% more revenue growth than generalists, according to 2025 industry data. Healthcare MSPs are growing at 31% annually. Legal and financial services aren't far behind.

Picking a niche doesn't mean turning away every other client tomorrow. It means building your service delivery, tooling, documentation, and sales motion around one type of client first. You get faster at it. Your techs learn the compliance requirements cold. Your pricing reflects the actual value you deliver, not just hours and tickets.

High-value verticals for your MSP business in 2026:

  • Healthcare – Largest vertical at 28% of specialized MSP revenue. HIPAA compliance creates a natural moat. Clients can't casually switch providers mid-audit cycle.
  • Legal – Small and mid-sized law firms are underserved. High data sensitivity, predictable headcounts, steady billing.
  • Financial services – SOC 2, PCI-DSS requirements lock in longer contracts and justify premium pricing. Clients treat IT as a compliance function, not a cost center.
  • Manufacturing – OT/IT convergence is creating demand for MSPs who understand both sides of the network.

How to find your niche: look at the last 10 clients who paid on time, had reasonable expectations, and referred you to someone else. There's usually a pattern. That's your vertical.

Step 2: Choose the Right MSP Business Model

This is where most new MSPs leave money on the table – or worse, price themselves into losses before they've got traction. There are three core MSP pricing models. Each has a place, and none of them is universally right.

Per-Device Pricing

You charge a flat monthly fee for each managed device – servers, workstations, network gear. Typical range in 2026: $50–100 per device per month for full managed services.

Best for: endpoint-heavy environments like healthcare facilities, warehouses, and manufacturing, where device counts are high but headcount is relatively low.

Watch: clients add devices mid-month without telling you. Define your scope explicitly in the contract.

Per-User Pricing

You charge per user per month. The average for SMB clients (under 500 employees) is $185/user/month. Mid-market clients average $310/user/month.

Best for: office-based businesses where the user is the real unit of work – legal, finance, professional services. One user might have three devices; you still charge once.

Watch: clients with high employee turnover. Onboarding and offboarding costs are real time, not just paperwork.

Flat-Rate / All-You-Can-Eat (AYCE)

One fixed monthly fee for a defined scope of services. Clients love the predictability. You love the recurring revenue.

Best for: established MSPs who know their delivery costs cold. If you don't know your true per-client margins yet, AYCE can turn into a money pit fast. A new client opens 40 tickets in month one and you're absorbing that cost.

Which Model Fits Your MSP

78% of MSPs use a tiered service model – basic/standard/premium, or bronze/silver/gold. The mid-tier package captures 56% of client revenue. Tiers let you upsell without renegotiating the full contract.

Start with per-user or per-device. Flat-rate is a model for MSPs who've already run the numbers on their real cost of service delivery. If you haven't served 20+ clients and tracked your actual time per ticket, you don't have that data yet. Guessing on AYCE pricing is expensive.

Pricing ModelBest ForAvg Price PointWatch Out For
Per-deviceEndpoint-heavy clients$50–100/device/moDevice count creep
Per-userProfessional services$100–310/user/moHigh-turnover clients
Flat-rate (AYCE)Established MSPsCustom by scopeUnknown cost base
Tiered (Bronze/Silver/Gold)Most growing MSPsVaries by tierScope creep at lower tiers

Step 3: The Margin Math – Benchmarks That Actually Matter

Let's talk numbers. Not aspirational – actual industry benchmarks.

Gross margin is what's left after you subtract direct service delivery costs: labor, tooling, subcontractors. Target: 50–70%. Best-in-class MSPs hit 70%+. Most new MSPs start at 30–40% gross and improve as they standardize delivery and automate repetitive work.

Net margin (EBITDA) is what's left after all operating expenses – full staff salaries, office overhead, insurance, and marketing. Industry average: 8–18%. Best-in-class MSPs consistently hit 19–22%+. The MSPs grinding at or below 8% usually have a vendor cost problem, a pricing problem, or both.

MetricLow EndIndustry AverageBest in Class
Gross margin30%52%70%+
Net margin8%12–18%20–35%
Adjusted EBITDA5%14–18%19–22%

What destroys MSP margins faster than anything else: vendor sprawl.

The average MSP runs 15+ tools. ConnectWise, Datto, Webroot, IT Glue, BrightGauge, and whatever else accumulated over the years. Add it up and you're often at $8,000–14,000+ per month in licensing – before you've paid a single technician.

That's 25–35% of revenue going to software vendors before you've touched a ticket. You can have great clients, great pricing, and still not be profitable if the tool stack is out of control.

Step 4: Build a Tool Stack That Doesn't Eat Your Revenue

Every MSP needs five core capabilities: remote monitoring and management (RMM), a PSA for ticketing and billing, security (SIEM/XDR), backup, and documentation.

Here's what most MSPs do: they buy the bundle from ConnectWise or Kaseya, get locked into a multi-year contract, and spend the next three years dealing with annual price increases at every renewal. It's not a partnership – it's a subscription with leverage.

Here's what the leaner MSPs are doing instead.

The Commercial Stack

CategoryCommercial OptionTypical Annual Cost
RMMConnectWise Automate, NinjaRMM$18,000–48,000+
PSAConnectWise Manage, Autotask$6,000–24,000+
SIEM/XDRSentinelOne, Huntress$12,000–36,000+
BackupDatto BCDR, Acronis$6,000–24,000+
DocumentationIT Glue, Hudu$3,600–7,200+

Total annual cost: $45,000–139,000+ depending on client count and tier. For a small MSP doing $180,000/year in MRR, that's a quarter of your revenue gone before margins.

The Open-Source Path

A growing segment of MSPs – especially those starting out or running lean – are building their stack on open-source tools. The cost picture changes dramatically.

CategoryOpen-Source ToolAnnual Hosting Cost
RMMTacticalRMM$240–720 (VPS)
PSAITFlow$240–720 (VPS)
SIEM/XDRWazuh$480–1,200 (VPS)
DocumentationBookStack or Outline$120–240 (VPS)

Total annual infrastructure: $1,080–2,880 vs $45,000–139,000+ for the commercial equivalent. Commercial PSA licensing alone runs $6,000–24,000+/year. Open-source hosting for the same PSA functionality: $240–720/year.

The trade-off is real. These aren't SaaS platforms with a support line. You're deploying on your own VPS, configuring integrations, and maintaining the stack. For an MSP owner comfortable with Linux, that's 20–40 hours of upfront setup and minimal ongoing effort. For someone new to self-hosted deployments, it's a steeper curve.

If you want a structured path to this – with vetted playbooks, tool comparisons, and a community of MSPs who've done the migration – OpenMSP is where that work is happening.

Real MSP Story #1: SecureTokens Cuts Licensing Costs by 27%

SecureTokens is a managed security services provider that was running a standard commercial stack. Standard costs, standard margins – and standard frustration watching the licensing bills arrive each month.

CEO Stephen Garriques said it directly: "We've been losing time and money to expensive software licenses while our technicians spend hours on repetitive tasks that should already be automated."

SecureTokens used OpenMSP to map their SOC and NOC tooling against open-source alternatives, then migrated to TacticalRMM and Wazuh. The results: 27% reduction in licensing costs, tighter stack integration, and no more annual renewal anxiety.

"OpenMSP gave us a data-backed roadmap to restructure our SOC and NOC tooling using open-source platforms like TacticalRMM and Wazuh. We cut licensing costs by 27%, eliminated vendor lock-in, and gained tighter integration across our stack." – Stephen Garriques, CEO, SecureTokens

27% isn't a rounding error. On a $10,000/month tool budget, that's $2,700/month back. $32,400/year that goes directly to margin instead of to a vendor's renewal invoice.

Step 5: Hiring Your First Technician

The biggest hiring mistake new MSP owners make: bringing someone on too early, or hiring a senior engineer when they can't yet afford the salary.

The rule of thumb: hire when you're consistently at 80%+ utilization and you're deferring or turning away real work. Not when you feel stretched. Not when you land two big clients in the same month. When you're at 80%+ and the pipeline is solid.

Who to hire first: a Level 1/2 technician, not another senior. Your job as the MSP owner isn't to close tickets – it's to manage client relationships, build the pipeline, and run the operation. A mid-level tech handles the queue while you handle growth.

In 2026, AI handles 70%+ of routine tier-1 work for MSPs running modern stacks. That changes the math on who your first hire needs to be. Your Level 1/2 tech can tackle more complex issues because the simple stuff is automated away.

Budget reality: plan for $55,000–75,000/year for a solid Level 1/2 technician, plus benefits and tooling allocation. Factor that into your pricing from the start. If your pricing model doesn't cover one tech at 80% utilization, your margins will compress the moment you're ready to scale.

How Much Does It Cost to Start an MSP Business?

Startup costs vary significantly based on your tooling decisions.

Commercial stack route: $10,000–20,000 in first-year tooling before you've signed a single client, plus mandatory business costs (E&O insurance runs $1,500–3,000/year, general liability, business registration).

Open-source route: $2,000–5,000 in total first-year costs is realistic. Your VPS hosting for the tool stack is $100–300/month. The mandatory business insurance and registration costs are the same regardless.

Most MSPs serving small businesses start with 5–10 clients and build from there. At $185/user/month and an average of 20 users per SMB client, five clients = $18,500/month in MRR. That covers one tech salary and a lean tool stack with room for margin – if you've built the stack to cost under $2,000/month.

Frequently Asked Questions

How much does it cost to start an MSP business?

Budget $2,000–5,000 for year one with an open-source tool stack, or $10,000–20,000 with a commercial stack. Mandatory costs regardless of route: E&O insurance ($1,500–3,000/year), general liability coverage, and business registration. Don't skip the E&O – one missed backup claim will cost more than a decade of premiums.

What's a realistic MSP profit margin for a new business?

New MSPs typically run gross margins of 30–40% in year one. By year two, target 50%+ gross and 15%+ net. Industry best-in-class MSPs hit 70% gross and 20–35% net. If you're below 10% net after two years of operation, something in the business model – pricing, vendor costs, or client mix – needs to change.

Per-device vs per-user pricing – which is better?

Per-user is cleaner for most MSPs serving office-based clients. One user, one price, regardless of how many devices they have. Per-device works better for endpoint-heavy environments like warehouses, retail, or healthcare facilities where devices outnumber users. Many MSPs use a hybrid: per-user for desktops and laptops, per-device for servers and network hardware.

How do I get my first MSP clients?

Start local. Chamber of commerce memberships, vertical-specific networking (bar associations for legal MSPs, MGMA for healthcare MSPs), and referrals from existing contacts. Cold outbound works at scale but not in month one. Your first five clients come from relationships, not ad campaigns.

Can you run a profitable MSP with open-source tools?

Yes. SecureTokens did it. Hundreds of MSPs in the OpenMSP community are doing it. TacticalRMM, Wazuh, and ITFlow are production-ready in 2026. The upfront setup time is real, but the ongoing cost advantage is significant. The question isn't whether open-source works for MSPs – it's whether you have the technical baseline to deploy and maintain it. If you do, the margin impact is immediate.

How many clients does an MSP need to be profitable?

With a lean tool stack and per-user pricing at $185/user/month, five clients averaging 20 users each = $18,500/month in MRR. That covers one tech salary, tooling, and leaves margin. With a commercial stack, you need eight to twelve clients to hit the same number after licensing costs. The tool stack choice directly affects how many clients you need before the business actually makes money.

Build the Foundation Right – Then Scale It

The MSP businesses struggling in 2026 aren't struggling because the market is bad. The market is growing. They're struggling because they said yes to every client, bought every tool in the vendor catalog, and priced on gut instinct instead of actual delivery costs.

The ones winning are narrower. They serve one type of client well. They know exactly what it costs to deliver a ticket, onboard a new client, and run the stack each month. They price accordingly – and they don't let vendor fees quietly consume 30% of revenue.

You don't need a 20-person team or a $500K funding round to build a profitable MSP business. You need a niche, a pricing model that reflects your real costs, and a tool stack that doesn't eat your margin before you've invoiced anyone.

See how the stack looks in practice →

Kristina Shkriabina

Kristina Shkriabina

Leading the flock content flare!