RMM pricing and licensing: what actually drives the bill

The three counting models

Everything else in a quote is detail. Establish the counting model first, because it determines how the bill behaves as the organisation changes.

• Per managed endpoint: you pay for each device with an agent. Predictable if your estate is stable, punishing if you have many low-value machines such as classroom PCs or shop-floor terminals.
• Per named operator: you pay for each person with a login. Simple, but it taxes flexibility — the after-hours helper and the occasional second-line engineer each cost money, which pushes teams towards shared logins.
• Per concurrent session: you pay for how many sessions can run at once. Cheap on quiet mornings, awkward on busy afternoons and during incidents, when everyone needs access simultaneously.
• Hybrids exist: an operator price with a concurrency cap, or an endpoint price with operator tiers. Read the cap, not the marketing.

Model your own shape, not an average

Take two real examples. A four-person team supporting 400 devices pays heavily under per-endpoint pricing and lightly under per-operator. A twenty-person team supporting 200 devices experiences exactly the reverse. Same category, same shortlist, opposite conclusions.

So build a small three-year model before you look at any quote: current devices and people, expected devices and people in year three, peak simultaneous operators during an incident, and the number of occasional or out-of-hours users who need access. Then price each candidate against that grid. The exercise takes an hour and routinely changes the answer.

Where the real figure hides

The advertised number is usually the entry tier. What moves the real figure is tiering and add-ons, and specifically whether the capabilities you marked as daily are included at the level you were quoted.

• Remote control quality or session limits gated to a higher tier.
• Patch management, scripting or reporting sold as separate modules.
• Two-factor authentication, role-based access or extended audit-log retention charged as security or compliance add-ons.
• Onboarding, configuration or alert tuning delivered as billable professional services.
• Minimum seat or endpoint counts that price you above your actual usage.
• Annual commitment only, with monthly pricing unavailable or materially higher.

Renewal is part of the price

In this category the second and third years are where budgets break. Ask directly: is pricing published, what has the uplift been for existing customers over the last few renewals, and is the current figure contingent on a multi-year commitment. Get the answer in writing before signing, because the switching cost after agents are deployed across an estate is precisely why uplifts happen.

Published, fixed pricing has a value beyond the number itself. It removes an annual negotiation, makes forecasting straightforward, and means a small customer is not quoted differently from a large one.

The costs that never appear on a quote

Two hidden costs dominate. The first is time-to-session friction: thirty seconds of extra friction per session, across a desk running dozens of sessions a day, is hours of paid time a week. Price that in and cheap tools sometimes stop being cheap.

The second is unused breadth. Paying suite prices while using a device list and a remote control button is a common and quiet waste. Reviewing which modules were actually opened in the last ninety days is the cheapest saving available in most IT budgets.