Guide
RMM pricing: per technician vs per device, with worked examples
The question usually arrives as a spreadsheet with two tabs and a headache. One vendor wants a fee for every person who logs into the console; another wants a fee for every machine running its agent. The totals look wildly different, and whichever one you pick will shape your margins for years, because leaving an RMM means re-deploying agents across every client you have. This guide walks through the arithmetic that answers the question of which model is cheaper, and then covers the parts of the bill that the arithmetic misses.
Every unit price below is hypothetical, chosen to make the maths easy to follow. None of them is a quote from any vendor. Real prices change, depend on tier and term, and are often negotiated; always check the vendor’s current pricing page or ask for a written quote.
The two models in plain terms
Per technician (per seat). You pay for each named user who needs access to the console, and endpoints are unlimited or very generous. Atera and Syncro have built their MSP plans around this model: your bill moves when you hire, not when a client adds ten laptops. See our Atera review and Syncro review for how each structures its tiers.
Per device (per endpoint). You pay for each managed endpoint, and you can add technicians without changing the bill much. NinjaOne works this way and does not publish a price list; pricing is quote-based and typically depends on device volume and the modules you add. Action1 also charges per endpoint but lets a limited number of endpoints run on its free tier, which matters for very small fleets. Details are in our NinjaOne review and Action1 review.
Neither model is inherently cheaper. The deciding variable is density: how many endpoints each technician looks after.
The break-even formula
Let T be technicians, D devices, Pt the monthly price per technician and Pd the monthly price per device.
Per-technician monthly cost = T × Pt
Per-device monthly cost = D × Pd
Break-even density (devices per tech) = Pt ÷ PdIf your devices-per-tech ratio is above the break-even density, per-technician pricing costs less on licensing. Below it, per-device pricing wins.
For the examples we will use two made-up list prices: $150 per technician per month and $2.50 per device per month. Break-even density is therefore 150 ÷ 2.50 = 60 devices per technician.
Worked example 1: two technicians, 400 endpoints
A two-person shop covering a dozen small offices. Density is 400 ÷ 2 = 200 devices per technician, well above 60.
| Model | Calculation | Monthly | Annual |
|---|---|---|---|
| Per technician | 2 × $150 | $300 | $3,600 |
| Per device | 400 × $2.50 | $1,000 | $12,000 |
On licensing alone, per-technician pricing saves $700 a month. That gap is big enough that a per-device vendor would need to replace several other paid tools before it came close.
Worked example 2: six technicians, 900 endpoints
A growing MSP with a helpdesk tier, two field techs and a project engineer. Density is 900 ÷ 6 = 150 devices per technician.
| Model | Calculation | Monthly | Annual |
|---|---|---|---|
| Per technician | 6 × $150 | $900 | $10,800 |
| Per device | 900 × $2.50 | $2,250 | $27,000 |
Per-technician still wins on the headline number, by $1,350 a month. Notice, though, that density dropped from 200 to 150. Staff-heavy growth (more people doing projects, onboarding and vCIO work rather than tickets) pushes you toward the break-even line.
Worked example 3: where per-device wins
An in-house IT team with three admins supporting 150 endpoints across a manufacturing site: density 50, below the break-even of 60.
| Model | Calculation | Monthly |
|---|---|---|
| Per technician | 3 × $150 | $450 |
| Per device | 150 × $2.50 | $375 |
Low-density teams, including internal IT departments where admins also run networks, telephony and facilities systems, are the natural fit for per-device pricing. So are MSPs with many part-time or contractor logins who each touch only a few clients.
What the formula leaves out
Licensing is rarely more than half the real cost. Before you trust any of the tables above, add these lines to both tabs of the spreadsheet.
- Tier gates. Per-seat plans often put third-party patching, advanced automation or network discovery in a higher tier. If the tier you actually need costs, say, $200 instead of $150, break-even density rises to 80.
- Per-device add-ons on per-seat plans. Backup, endpoint protection and some network monitoring are frequently billed per device even when the RMM seat is not. Ten dollars a month of backup on 400 endpoints dwarfs the seat price.
- Tools the platform replaces. A per-device platform that includes ticketing, documentation or MDM can retire a separate PSA or documentation subscription. Price the whole stack, not the RMM line.
- Minimum commitments. Quote-based vendors may ask for a minimum device count or an annual term. A 250-device floor changes example 3 completely.
- Seats you forget. Owners, dispatchers, part-time contractors and an auditor who needs read-only access may all need a named user under per-seat pricing.
- Switching cost. Moving 900 agents, rebuilding policies and scripts, and retraining staff easily costs a few weeks of technician time. A cheaper licence that you will outgrow in 18 months is not cheap.
Match the vendor model to how you bill clients
Most MSPs sell managed services per device or per user. If you charge clients per device, per-device tooling means your costs scale with revenue: a new client with 60 laptops brings both the income and the cost. Per-seat tooling behaves differently: your cost moves in steps when you hire, and every device you add between hires is nearly pure margin. That is great when a client grows, and uncomfortable when you hire ahead of revenue.
A quick check we like is tooling cost per managed endpoint. In example 2, per-seat licensing works out to $1.00 per endpoint per month and per-device to $2.50. Compare that with what you charge per endpoint and decide how much of the gap your other tools will eat.
Common mistakes
- Comparing a per-seat list price with a per-device quote that includes backup and MDM. Normalize the feature set first.
- Modeling today’s staff and fleet only. Run the numbers at your 12-month plan too.
- Ignoring the annual-versus-monthly difference. Discounts for annual terms are common, but so is being locked in.
- Assuming unlimited endpoints means unlimited everything. Read the fair-use terms for storage, scripts and remote sessions.
Where to go next
For product-by-product detail, the RMM software category lays out licensing models side by side. The NinjaOne vs Atera comparison is the classic per-device versus per-seat decision, and Syncro vs Atera compares two per-seat platforms. How we weigh cost against capability is explained in our methodology.