One tech. Up to 6× the endpoints.
Every MSP's growth is capped by one ratio: endpoints per technician. Add clients and you must add techs, the hardest, most expensive thing to scale. Scylos changes the ratio itself, because the per-endpoint workload largely disappears.
Up from ~200 on Windows, a 6× lever, because patching, drift, reimaging, malware, and truck rolls fall away.
Growth decouples from headcount.
Industry benchmarks put endpoints-per-tech at ~123 median, 200–250 as a typical MSP target, and ~350 as the well-automated gold standard. The #1 constraint on MSP growth is hiring and training technicians. Remove the per-endpoint work and revenue can grow without the payroll, the holy grail of services scaling.
What one technician can carry
Identity, password, and access is the biggest ticket category, and Scylos doesn't touch it. That puts a floor under per-endpoint time. Pair Scylos with self-service password reset and the ratio climbs further. The calculator lets you set the multiplier to your own ticket mix.
Two ways to spend the same lever
Or grow without hiring: the same 10 techs carry ~12,000 endpoints. Most MSPs do a blend, grow the base several-fold while cutting labor cost per endpoint.
Pricing power and margin at once
Labor at ~$5/endpoint and the tool stack collapsed to ~$13 lets you undercut competitors AND expand margin. You rarely get to do both.
Revenue per employee jumps
Industry average is ~$142k/employee. When each tech carries 6× the endpoints, revenue per technician moves toward a different tier entirely.
The weekends come back
No 2 a.m. patch windows, no mass reimaging, no CrowdStrike-style fire drills. Lower burnout means lower tech turnover, a large hidden cost in the MSP model.
About the scaling lever
Where does the 6× come from?+
From the handle-time engine: tech time per endpoint falls from ~60 min to ~10 min a month as OS, malware, drift, reimage, and hardware-swap work collapses to a remote reset. Identity and network tickets don't shrink, which bounds the multiplier.
Is 6× guaranteed?+
No. It's a representative model bounded by your identity/access ticket share, which Scylos doesn't reduce. The calculator lets you set the multiplier to your own numbers rather than taking ours.
Do I have to cut headcount to benefit?+
No. You can keep the team and grow the book several-fold, cut cost on today's book, or blend the two. The lever is the same either way.
See the stateless endpoint on your own hardware.
Flash an idle machine into a live endpoint and run your real workloads. You buy no hardware and sign nothing.