EOS® for IT & MSPs
EOS® for IT & Managed Service Providers
You sell your clients proactive, documented, monitored IT — then run your own company reactive, undocumented, and on the founder's heroics. EOS® closes that gap.
Managed service providers sell a specific promise: proactive beats reactive. Monitoring beats firefighting. Documentation beats tribal knowledge. Then look inside the typical MSP itself and you find the mirror image — the founder is the final escalation tier for every gnarly ticket, the closer on every deal, and the only person who knows how half the client environments really work. The company preaches managed services and lives break-fix.
The economics punish that gap precisely. Service Leadership's data shows best-in-class solution providers sustaining 19%+ adjusted EBITDA while the median MSP earns a fraction of that — and the difference isn't technical talent. It's operational maturity: recurring-revenue discipline, standardized stacks, priced-right agreements, and a leadership team that manages by numbers instead of by whoever is loudest in the queue.
The Entrepreneurial Operating System® is how founder-led MSPs build that maturity on purpose. Jon Kludt is a Certified EOS Implementer® with 300+ sessions facilitated with founder-led leadership teams across a wide range of industries; for an MSP, EOS® means one owner on every function — service delivery, sales, centralized services, finance — and a business managed by a weekly Scorecard built from numbers the PSA already collects but nobody reviews with consequences.
Sound familiar?
- The founder is Tier 3 escalation, lead sales engineer, and CEO — and the queue always wins.
- MRR percentage is stuck because project and break-fix work keeps 'paying the bills' while diluting the managed model.
- Your best engineers are heroes — which feels great and means nothing is documented and everything depends on them.
- Agreements signed years ago are underpriced for today's labor and security stack, and nobody owns repricing them.
- Sales is the founder plus referrals; there's no owned number for new MRR added per month.
- The PSA is full of data and the leadership team still argues from anecdotes.
An example IT / MSP Accountability Chart
A typical chart for a $2–15M MSP splits Operations into reactive service delivery and proactive/centralized services — the split that makes 'proactive' a real accountability instead of a leftover. Seats, not people; the founder often holds two seats at first, deliberately and temporarily.
Visionary
- Company vision and target market strategy
- Key client and vendor/channel relationships
- New offering ideas (security, cloud, AI services)
- Culture and core values
Integrator
- Lead, manage, hold accountable (LMA)
- P&L and business plan execution
- Priority arbitration between sales, service, and projects
- Vendor stack and cost discipline
Sales & Marketing
- New MRR target and pipeline
- Agreement pricing and repricing discipline
- Marketing engine and referral program
- QBR-driven expansion revenue
- Ideal client profile enforcement
Service Delivery Manager
- LMA for the service desk and field techs
- SLA performance and ticket flow
- Escalation management (so the founder isn't Tier 3)
- Client satisfaction (CSAT) on reactive work
- Tech utilization and scheduling
Centralized Services / Projects
- Standard stack definition and enforcement
- Patching, backup, and security hygiene compliance
- Documentation standards in the ITG/Hudu
- Project delivery on time and on margin
- Onboarding new clients to standard
Finance & Admin
- Accurate financials with service-line margins
- Agreement invoicing accuracy and collections
- Gross margin reporting by agreement
- Licensing/seat reconciliation (billing what you deliver)
- HR administration
Seats, not people — one person can hold more than one seat in a growing company. The chart defines the structure the business needs, then you put the right people in the right seats.
Setting your V/TO™ numbers: what healthy looks like
The MSP industry is unusually well benchmarked — Service Leadership has published the operational math of best-in-class for years. Your V/TO™ targets should be set against that data, not against how last year felt.
Adjusted EBITDA
19%+ best-in-class; median MSPs far below
Service Leadership reports best-in-class solution providers have held 19%+ adjusted EBITDA for six consecutive years. The gap to median is operational maturity, not technical skill — which makes it a fixable gap. (ConnectWise / Service Leadership — Annual Profitability Report findings)
Recurring revenue (MRR) % of total
65–78% target; best-in-class 78–90%
Below ~60%, project and break-fix work is diluting the managed model — and your valuation multiple with it. This is the single clearest 3-year-picture number for an MSP. (Pharallax — MSP Revenue Benchmarks 2026)
All-in seat price (AISP)
$125–$150+/user/month for full-stack AYCE
With delivery costs commonly $80–$120 per user per month, legacy agreements priced years ago are often underwater today. Repricing is uncomfortable once and profitable forever.
Service revenue per technician
$150K–$200K+/year
The leverage check for your 3-year picture. If revenue per tech is falling as you grow, standardization and documentation — not hiring — are the real Rocks.
A weekly IT / MSP Scorecard that actually predicts
The beautiful thing about an MSP Scorecard: the PSA and RMM already collect every number on it. The discipline EOS® adds is a weekly review where each number has one owner and an off-track number becomes an issue — not an anecdote.
| Measurable | Example target | Why it's on the Scorecard |
|---|---|---|
| New MRR added ($) | Set from annual target / 52 | The growth engine number. MSPs that only track total revenue discover too late that projects masked flat managed-services growth. |
| MRR churned / at risk ($) | ≤ 0.5% of MRR monthly | Recurring revenue compounds in both directions. A weekly at-risk review turns QBRs and CSAT into retention tools instead of rituals. |
| Service gross margin % | ≥ 50% blended | The health of the core business. Underpriced agreements and unmanaged labor both show up here first — months before EBITDA confirms it. |
| Reactive tickets per endpoint | Trending down | The proof-of-proactive number. If centralized services is doing its job, reactive volume per endpoint falls — and margin rises without a single price change. |
| SLA response/resolution compliance | ≥ 95% | The promise you sell. Weekly visibility catches the drowning-service-desk spiral while it's still a staffing conversation, not a churn event. |
| Escalations reaching the founder | Trending to ~0 | The de-heroing metric. Every founder escalation is a documentation gap, a training gap, or a seat gap — and the count makes the pattern undeniable. |
| Patch / backup success compliance | ≥ 98% | The number that prevents the 2 a.m. phone call. Security hygiene is also now the first thing cyber insurers and enterprise clients audit. |
| Utilization (billable+covered hours per tech) | ≥ 75% | Labor is the MSP's COGS. Utilization tells you whether to hire, before the team burns out or the bench burns cash. |
Example quarterly Rocks
Rocks are the 3–7 must-do priorities for the quarter, each with one owner. Typical examples for MSP leadership teams:
- 1Reprice or exit the 10 lowest-margin agreements — every agreement above 50% gross margin or on a exit plan by week 12
- 2Stand up a true escalation path: documented tiers, named owners, founder out of Tier 3 by quarter end
- 3Define the standard stack and get 80% of clients onto it (or on a written migration plan)
- 4Launch the security offering as a packaged, priced SKU and sell it to 15 existing clients
- 5Hire and onboard a Service Delivery Manager by week 10
- 6Document the top 20 client environments to standard in the documentation platform
Free download
Get the IT / MSP EOS® one-pager
The example Accountability Chart, benchmarks, Scorecard measurables, and Rocks from this page — on one branded PDF you can share with your leadership team.
From Jon's desk
Your MSP sells proactive. It runs reactive. That's the whole problem.
Every MSP pitch deck says the same thing: stop firefighting, get proactive, let monitoring and process replace heroics. It's a great pitch. Then ask the MSP's own leadership team who owns service margin, who owns new MRR, and what the founder's week looks like — and the answers are almost always 'sort of everyone,' 'the founder, when there's time,' and 'mostly escalations.' The company is selling a discipline it doesn't practice on itself.
The industry data shows exactly what that costs. Service Leadership has tracked it for years: best-in-class providers run 19%+ adjusted EBITDA, sustained, while the median MSP scrapes by on a fraction of that. Same tools, same vendors, same labor market. The difference is operational maturity — which is a polite way of saying the best-in-class firms stopped running on adrenaline.
The pattern I see in founder-led companies everywhere shows up with extra force in MSPs: the founder built the company on being the smartest engineer in the room, and the company never stopped depending on it. They're the final escalation tier, so documentation never becomes urgent. They're the best closer, so sales never becomes a system. The hero culture that got the company to $2M is exactly what caps it there.
EOS® is how you institutionalize what the founder does by instinct. The Accountability Chart splits operations into reactive service delivery and centralized services — because until 'proactive' is a seat with an owner, it's a slide in your own pitch deck. It puts one name on new MRR, so growth stops being the founder's fourth job. The Scorecard is almost unfair for MSPs: the PSA already collects every number — tickets per endpoint, SLA compliance, margin by agreement, patch success. What's missing isn't data. It's a weekly 90 minutes where each number has an owner and an off-track number becomes an issue that gets solved.
And the quarterly Rocks handle what MSPs perpetually defer: repricing the legacy agreements everyone knows are underwater, standardizing the stack, getting the founder out of Tier 3. None of that is technically hard. It just never survives contact with the ticket queue — until it's a Rock with a name and a deadline reviewed every single week.
The endgame matters too: MSP valuations reward exactly what EOS® builds — high MRR percentage, margin discipline, and a business that runs without its founder. Run your company the way you tell clients to run their IT. Proactive beats reactive. You already believe it; you sell it every day.
Frequently asked questions
We're a small MSP — 12 people. Is EOS® overkill?
Twelve people with a leadership team of three or four is squarely in the sweet spot. Small MSPs actually see the fastest payback, because one repriced agreement book or one founder pulled out of the ticket queue changes the economics immediately. Below roughly 10 people, self-implementing from the book Traction® may be enough — Jon will tell you honestly in a free 90-minute meeting.
We already track everything in ConnectWise / Autotask and run TruMethods-style metrics. What does EOS® add?
The PSA gives you data; frameworks like TruMethods give you MSP-specific targets. EOS® adds the operating system that makes anyone accountable to them: seats with single owners, a weekly Level 10 Meeting™ where off-track numbers become solved issues, and quarterly Rocks that survive the ticket queue. MSPs with good metrics discipline implement fastest — the Scorecard practically builds itself.
Our founder really is the best engineer. Doesn't pulling them out of escalations hurt clients?
Short-term, the second-best engineer handles some escalations the founder would have handled faster. Long-term, the founder builds the documentation, escalation tiers, and hiring plan that make the whole bench stronger — which no one else can do, and which never happens while they're in the queue. The Scorecard tracks the transition (escalations reaching the founder, trending to zero) so it's managed, not abrupt.
Does EOS® help if we want to sell the MSP in 3–5 years?
It's one of the strongest exit-prep moves available. Buyers price MSPs on MRR quality, margin, and founder-independence — precisely what the Accountability Chart, Scorecard, and documented processes build. An MSP that demonstrably runs without its founder, with two years of clean weekly numbers, commands a meaningfully better multiple and survives diligence without drama.
A business coach for it / msp leadership teams
If you've been searching for a business coach for your it / mspcompany, here's the honest difference with EOS®: instead of generic advice, you get a complete operating system — installed by a world-class business coach and Certified EOS Implementer® — that starts from your numbers, your seats, and your 90-day priorities.
Jon Kludt has facilitated 300+ sessions with founder-led leadership teams across a wide range of industries. The system is industry-agnostic by design; pages like this one exist so you can see it translated into your world before you ever book a call.
Ready to run your it / msp business on EOS®?
Book a free 90-minute meeting for your leadership team. You'll leave with practical tools you can use right away — whether or not we work together.
Related industries