Skip to main content
Free assessment Map your profit, tax, and enterprise-value gaps. See what you get
IT & Tech Services

Endpoints are up. EBITDA isn’t.

Your client base is growing. Your tech stack is more mature than ever. Recurring revenue looks solid on paper. And after technician payroll, software stack, and overhead — you’re netting 8–12 cents on every dollar instead of 25–30 like the legal and financial firms you sit alongside in your clients’ vendor list. That’s not a sales problem. It’s the same financial pattern I see in every MSP that scales without an operating system underneath it — labor cost outrunning revenue per technician, product margin masking the real picture, and 20–30% of clients running at negative service margin.

Book My Leak Check

For US‑based MSPs and IT services firms doing $1M–$20M in revenue.

MSP Diagnostic
Leak Map Preview
Live
Service GM Gap +$400K
Endpoint Ratio Gap +$600K
Client Profitability +$200K
Total recoverable
$200K – $700K
per year
conservative
$4M MSP example · 60‑15‑15 framework · Yours to keep

Trusted by growing service businesses

01Industry P&L
02Margin visibility
03Tax exposure
04Enterprise value
Before You Read Further

Most MSPs measure blended gross margin. I measure service gross margin separately. Here’s why it matters.

Most MSP financial guidance lumps product revenue and service revenue together into one blended gross margin. Industry sources put the target at 65–75% blended, 25% on products, 50%+ on services. The blended number is misleading because it masks the real diagnostic. A $4M MSP doing $1.5M in product reselling at 25% GM and $2.5M in services at 50% GM looks “healthy” at 41% blended GM. But the service business — which is what determines whether you scale or stall — is sitting at 50%, ten points below where it needs to be. The blended number hides the leak. I separate the two and run 60‑15‑15 on the service business specifically: 60% service gross margin, 15% S&M, 15% G&A. That leaves 30% operating margin on services — the same number the best‑performing MSPs hit.

Service gross margin: 60%

Industry typically lands at 50% — that’s the gap.

Product gross margin: 25–35%

Separate diagnostic, separate decisions.

S&M: 15% or less of total revenue

Sales and marketing spend held inside the standard.

G&A: 15% or less of total revenue

Overhead capped so service profit actually lands.

Net margin: 20–25% blended

If you’re cross‑referencing this against Service Leadership Index, ConnectWise, or Kaseya benchmarks, the language is different but the destination is the same — only 25% of MSPs are best‑in‑class, and the gap is closeable.

Illustrative example
MSP Net Margin vs PeersIndustry comparison
Legal/Financial MSP Average
$1M$2M$4M$8M$12M$20M
Peer margin30–35%
MSP margin8–12%
Take‑home gap−3x
The Problem

The average MSP makes a third of what its peers in legal or financial services do.

I’ll show you the math. This isn’t an opinion — it’s straight from Fred Voccola at Kaseya and corroborated by Service Leadership Index data. Average MSP net margin: 8–12%. Average net margin for the legal and financial firms your clients pay every month: 30–35%. Same client. Same SMB market. Three to four times the take‑home for the lawyer or CPA. The gap isn’t because IT is somehow harder to monetize. It’s because three structural problems compound in MSPs and almost nobody fixes them in the right order.

01
Technician Labor

Labor outruns revenue per technician

When tech salaries exceed 33% of service revenue, profitability collapses fast. Most MSPs cross that line and don’t notice because revenue is still growing.

02
Endpoint Ratio

Endpoint‑to‑tech ratio runs 15–20% low

Industry gold standard is 350 fully managed endpoints per technician. Most MSPs are at 280–300 because automation hasn’t caught up to client growth.

03
Utilization

Service utilization stuck at 50%

It should be 60–75%. Half your tech payroll is funding non‑billable activity — internal projects, undocumented client work, idle capacity, and rework.

A $4M MSP at 50% service GM with 50% utilization keeps about $400K of EBITDA. Same firm at 60% service GM and 70% utilization keeps $1.1M. Same revenue. Same client roster. $700K difference. The framework that closes the gap has three steps in a fixed order: COGS first, S&M second, G&A third. Never reordered. For MSPs, COGS is where 80% of the leak lives.

The Numbers In Three Lines

Three numbers tell you where MSP margin is hiding.

Every MSP and IT services firm we look at in the $1M–$20M band sits somewhere on this same map. The leaks aren’t hidden — they’re just not measured against the right benchmark.

8–12%
Average MSP net margin — vs 30–35% for legal/financial peers
280
Endpoints/tech at average MSP — gold standard is 350
$700K
Yearly margin gap on a $4M MSP at 50% vs 60% service GM
The 60‑15‑15 Standard

For MSPs, the math runs through four numbers.

Service gross margin first, S&M second, G&A third — never reordered. Industry typically lands at 50% service GM and 8–12% net. Best‑in‑class MSPs hit 60% service GM and clear 20–25% net. Same revenue band. Same client roster. Different operating system underneath.

60%
Service Gross Margin
What you keep after technician labor, PSA/RMM, and direct delivery cost
15%
Sales & Marketing
Net‑new MRR acquisition cost capped inside the standard
15%
G&A
Overhead, admin, and back‑office held to a hard ceiling
20–25%
Net Margin
Top quartile MSPs hit this. Industry sits at 8–12%.
60% Service GM
−
15% S&M
−
15% G&A
=
20–25% Net
The Three Levers

In MSPs, COGS is where you bleed first. And it’s where you fix it first.

Most MSP owners think their cost problem is overhead — too much office, too many PSA/RMM licenses, too much admin. It usually isn’t. It’s service gross margin. The healthy service GM for an MSP at $1M–$20M is 60%. Most MSPs I look at are running 40–50%. The 10–20 point gap shows up in three places.

1
Lever 1 — Technician Labor

Technician labor outpacing revenue per technician

The benchmark from Profitwise Accounting and Service Leadership Index is consistent: technician salaries should not exceed 33% of service revenue. When they do, the business may look healthy on the surface — high ticket volume, full pipeline — but margin compresses fast. One slow month, one difficult onboarding, one underutilized senior hire and the math breaks. Most MSPs hire experienced technicians at competitive market rates and assume revenue per technician will follow. It usually doesn’t. Tech payroll grows on a calendar schedule (annual raises, market adjustments, new hires for capacity). Revenue per technician grows only when automation, tiered staffing, and standardized processes catch up. The fix is structural: tier the team (senior handles complex work, mid‑level handles most service requests, junior handles routine tasks and monitoring), and invest in automation before the next hire. The benchmark to track monthly: revenue per fully‑loaded technician. Target is 3–4x their fully‑loaded comp. Below 2.5x and you’re subsidizing them.

33% salary ceiling Tiered staffing Rev per tech 3–4x
Current: 2.5x compTarget: 3–4x comp
2
Lever 2 — Endpoint Ratio

Endpoint‑to‑technician ratios that nobody benchmarks

The industry gold standard from Acronis and ConnectWise: 350 fully managed endpoints per technician. Most MSPs run 280–300, meaning each technician is 15–20% less productive than they could be. On a $4M MSP that’s $600K–$800K of revenue capacity left on the table — without hiring anyone, without raising prices. The reason isn’t laziness or lack of skill. It’s that automation tools (PSA, RMM, scripting, AI ticket triage) get bolted on instead of redesigned around. Each tool reduces some friction but the workflow underneath stays the same. The fix is operational: rebuild the ticket workflow around the automation, not the other way around. MSPs that do this typically lift endpoints‑per‑tech 20–30% in two quarters.

350 endpoints/tech Workflow redesign PSA/RMM leverage
Current: 280–300Target: 350
3
Lever 3 — Client Profitability

Clients running at negative service margin

Most MSPs have 15–25% of clients running at negative or marginal service margin once you load in technician hours, account management, project work, and “small favors” correctly. These aren’t always the smallest clients. They’re often the biggest revenue clients with the most ticket volume, the most scope expansion, and the most senior tech time tied up in reactive work. The number you need is effective hourly rate per client — monthly revenue from a client divided by total technician hours spent on them. Most MSPs don’t have it because time entry is loose, scope creep isn’t tracked, and “all‑you‑can‑eat” agreements were signed without unit economics. Once you see effective rate per client, the action is obvious — re‑price the bottom 20%, narrow scope, or transition them out. The COGS leak is rarely just one of these three. It’s all three, compounding. That’s why service GM sits at 50% instead of 60.

Effective hourly rate Re‑price bottom 20% Unit economics
15–25% clients negativeTarget: zero
The Owner Trap

Most MSP owners are the senior tech, the closer, and the relationship manager all at once.

If you took 90 days off — no calls, no emails, no decisions — what happens? In most MSPs I look at, three things break: the hardest tickets escalate to nobody because you’re the senior tech everyone defers to. New business stalls because you’re the one who closes deals over $5K MRR. The biggest clients call asking for you specifically because the relationship is with you, not the firm.

That’s not an MSP. It’s a senior tech with a payroll. Practices like this sell at 2–3x EBITDA — buying a job. MSPs that run independently with documented workflows, tiered tech teams, and delegated client relationships sell at 5–7x. Same earnings, different multiple. On an MSP doing $500K in EBITDA, that’s the difference between a $1.4M sale and a $3.5M sale.

The fix is what I call “firing yourself” — building the firm so it doesn’t need you in three places at once: senior tech judgment, sales, and relationship management. It’s a 12–18 month process and it’s the single biggest enterprise value lever any service business has. For MSPs specifically, it’s also what unlocks the endpoint ratio improvement — when you stop being the bottleneck, the senior techs start being the bottleneck, and the senior techs can delegate down because their incentives are aligned with margin, not heroics.

This is also why “we just need more MRR” is the wrong answer. Bigger numbers in a more dependent MSP don’t move the multiple. They make the on‑call rotation worse.

See Your Numbers

Want to see where your MSP sits against 60‑15‑15?

Book the Leak Check. I’ll work through your rough numbers — service revenue, blended GM, technician count, endpoint count, owner comp — and show you the top 3–5 leaks with dollar ranges. No documents, no prep. You keep the Leak Map either way. 15 spots per month.

Book My Leak Check
Proof

What this looks like in real businesses.

Eden Data

“$0 to $300K MRR with embedded CFO from day one.”

Taylor Hersom Founder, Eden Data
Read case study
Motiv Marketing

“$402K tax bill eliminated — refunded at federal and state level.”

Motiv Marketing Service Margin Restructure
Read case study
Optmyzr

“$402K tax liability turned into $80K refund. $185K+ total savings.”

Optmyzr SaaS & Ad Tech
Read case study
Enterprise Value

Same earnings. Different multiple.

Most MSPs sell at 5–8x adjusted EBITDA. The multiple is driven by recurring revenue percentage, customer concentration, and how dependent the business is on the owner. On an MSP doing $500K in EBITDA, the difference between top quartile and bottom quartile is the difference between a $3.5M exit and a $1.4M exit.

70%+ recurring, delegated
7–8x
EBITDA multiple
VS
Owner‑dependent, project‑heavy
3–5x
EBITDA multiple

MSPs above 70% recurring revenue with no customer over 15% of MRR and a delegated owner sell at 7–8x. Owner‑dependent MSPs with heavy project work and concentrated customers sell at 3–5x. The single biggest lever to move the multiple is reducing dependence on the owner — the same lever that unlocks the endpoint ratio improvement.

Both are 12–18 month projects, and they compound. The 60‑15‑15 framework drives EBITDA up. The operational maturity that comes from firing yourself drives the multiple up. The end state isn’t just a higher exit number — it’s a business that gives you two choices: sell at a premium, or keep it running with minimal input and collect cash. The work is the same either way.

Get Started

Find out where your MSP’s margin is leaking.

Most MSPs and IT services firms in the $1M–$20M band have $50K–$300K of profit and tax leaks hiding in technician utilization, endpoint ratios, client profitability, and entity setup. The Leak Check finds them. We work through your rough numbers and produce a 1‑page Leak Map: top 3–5 leaks with dollar ranges, ranked by 12‑month impact. 15 spots per month.

Book My Leak Check

For US‑based MSPs and IT services firms doing $1M–$20M in revenue.

Book My Leak Check
FAQ

Questions about Fractional CFO for MSPs & IT Services.

Clear answers to the questions owners ask before deciding what to do next.

Two numbers, tracked separately. Service gross margin should be 60%+ (industry sits at 50%, top quartile hits 65–70%). Net margin should be 20–30% (industry sits at 8–12%, top quartile hits 25%+). The blended gross margin number that lumps services and product reselling together is misleading — it can look healthy at 65–75% while the service business underneath is actually under‑performing. Track service GM separately or you’ll miss the leak.

Three places to check, in order. First, technician labor — when tech salaries exceed 33% of service revenue, profitability collapses fast. Second, technician utilization and endpoint ratio — most MSPs run 50% utilization and 280 endpoints per tech when targets are 60–75% utilization and 350 endpoints. That’s 15–25% of capacity left on the table. Third, client profitability — 15–25% of MSP clients run at negative service margin once you load in technician time, account management, and “small favors” correctly. The leak is almost never just one. It’s the three compounding.

Industry gold standard is 350 fully managed endpoints per technician. Most MSPs run 280–300 because automation hasn’t caught up to client growth. The fix isn’t more tools — most MSPs already have a PSA, an RMM, scripting, and AI ticket triage. The fix is rebuilding the ticket workflow around the automation rather than bolting it onto the old workflow. MSPs that do this lift endpoints‑per‑tech 20–30% in two quarters without hiring or losing service quality.

Industry benchmark for all‑you‑can‑eat (AYCE) MSP pricing is $125–150 per seat. Below $100 per seat almost always indicates underpricing relative to delivery cost. The bigger lever isn’t seat price — it’s the effective hourly rate per client (monthly revenue ÷ total technician hours spent). If a client is paying $100/seat for 50 seats but consuming 80 hours of tech time monthly, your effective rate is $62.50/hour. That’s below most MSPs’ fully‑loaded technician cost. The fix is either narrowing scope, raising the seat price, or transitioning them out.

Two angles. First, optimize the recurring‑to‑project ratio toward 80/20 (recurring/project). MSPs heavy on project work look profitable on paper but carry scope creep, billing disputes, and unpredictable cash. Second, expand within existing accounts before chasing net‑new logos — security‑as‑a‑service, compliance, cloud backup, and identity management are the highest‑margin add‑ons most MSPs underdeploy. Net‑new acquisition is the most expensive way to grow MRR. Expansion within healthy accounts is the cheapest.

EBITDA × multiple. Most MSPs sell at 5–8x adjusted EBITDA in the current market, with the multiple driven by recurring revenue percentage, customer concentration, and how dependent the business is on the owner. MSPs above 70% recurring revenue with no customer over 15% of MRR and a delegated owner sell at 7–8x. Owner‑dependent MSPs with heavy project work and concentrated customers sell at 3–5x. The single biggest lever to move the multiple is reducing dependence on the owner — same lever that unlocks the endpoint ratio improvement. Both are 12–18 month projects.

A fractional CFO turns the operating data that matters in a MSP or IT-services firm business into a regular decision process: a reliable close, a forward cash view, a small KPI set, and working sessions on the choices those numbers support. The work should complement day-to-day accounting rather than replace the people responsible for transactions.

Start with technician utilization, recurring-service margin, project margin, ticket volume, and contract profitability. The useful scorecard also connects those measures to gross margin, overhead, collections, and the cash available for the next operating decision; the exact mix should match the firm's model and reporting data.