Flat rate RMM pricing: how it works and when it beats per-endpoint or per-tech

Flat rate RMM pricing charges one fixed monthly fee per company, banded by device count, so adding technicians or endpoints inside a band never changes the bill. It usually beats per-technician and per-endpoint billing once you pass roughly 80 endpoints or hire a second technician. It loses for a solo technician with a small, static estate, or an MSP stuck just over a band edge. This piece covers what vendors charge MSPs, not what MSPs charge clients; we have covered that side of the pricing question separately.

How flat rate RMM pricing works

The model is simple enough to describe in one sentence: your company pays a fixed monthly fee, set by which device-count band you fall into, and nothing else changes the bill. Not headcount. Not new endpoints inside the band. Not which features you turn on.

A typical published band structure looks like this: one price up to 50 devices, a second up to 250, a third for unlimited. Every feature on every band, because the bands exist to segment company size, not to ration functionality. The important properties are the ones the meter does not touch:

• Hiring is free. Adding a third technician, or giving the apprentice a login, costs nothing. You staff for service quality, not for licence arithmetic.
• Growth inside a band is free. Onboarding a 40-endpoint client when you are at 180 devices on a 250 band changes your revenue and not your costs.
• The bill is predictable. The finance owner can put next year's tooling cost in a spreadsheet without a renewal quote, which matters when you are modelling tooling as a percentage of MRR.

The obvious question is what happens at a band edge, and the honest answer is that you get a step up in cost. More on that below, because it is the model's genuine weakness.

The two meters it competes with

Per-technician pricing charges for each named or concurrent technician login, typically somewhere between £100 and £150 per technician per month at published list prices once you include the tier a working MSP actually needs. It is cheap when you are one person and expensive the moment you are not, because the meter runs on the one thing you add when service quality slips: staff.

Per-endpoint pricing charges per monitored device, usually a few pounds per endpoint per month at small volumes, often quote-only, often with add-ons for patching, backup or antivirus that sit outside the headline rate. The meter here runs on the thing you are in business to grow: managed devices. Every client win raises your software bill, and the headline figure is rarely the invoice once the add-ons and minimums land.

Per-agent PSA pricing is a variant of per-technician and behaves the same way in the arithmetic, so treat it as the same model.

Break-even: the arithmetic at four team shapes

Assume round, plausible figures you can substitute with your own quotes: £129 per technician per month for the per-tech model, £2.50 per endpoint per month for the per-endpoint model, and flat bands of £99 (up to 50 devices), £199 (up to 250) and £399 (unlimited). None of these are exotic numbers; check them against your own renewal paperwork.

Three things fall out of the table. First, per-endpoint wins at the very small end, and it is not close. Second, flat rate wins everywhere a normal MSP growth curve goes, because the two meters compound: you add endpoints, which forces you to add technicians, and one of the two meters is always running. Third, the co-managed shape, technician-heavy and endpoint-light, is where per-technician pricing is at its cruellest, because five people sharing a queue with an in-house team is five full licences.

Where flat rate is worse value

An honest comparison names the losing cases, so here they are.

• The solo technician with a small, static estate. One person managing 30 endpoints pays £75 on a per-endpoint meter against £99 flat. If that estate is not growing, the meter is the better deal and will stay the better deal. Flat rate is a bet on growth; if you are not making that bet, do not pay for it.
• The band cliff edge. Sitting at 255 devices on a 250 band means paying the unlimited price for five devices of overage. The step is visible and published, which is better than a surprise renewal quote, but it is still a step. If you live permanently just over a band edge, run the numbers for that specific position rather than assuming.
• Shrinking estates. Per-endpoint bills fall when you lose a client. Flat bands fall only when you cross a boundary downwards. A shrinking MSP gets no reward from flat pricing, though a shrinking MSP has larger problems than its tooling bill.

Work out your own break-even in ten minutes

1. Write down three numbers: technicians who need a login (including part-timers and the owner), endpoints under management today, and endpoints you plausibly expect in 18 months.
2. Get real per-unit prices, not list prices. Use your current invoice, or a dated public comparison such as our RMM pricing comparison, and include the add-ons you actually run: patching, AV, backup monitoring, the PSA tier.
3. Multiply out all three models at today's numbers and at the 18-month numbers. The second calculation matters more, because you are choosing the bill you will be paying, not the one you would have paid.
4. Apply the hiring test. The hiring test: if you added one technician next quarter, which bills change? Any model that taxes hiring will shape your hiring decisions, and that cost never appears on an invoice.
5. Check the exit terms. A cheap monthly rate inside a three-year auto-renewing contract is not cheap. Monthly billing with no notice period is worth a premium; run the numbers with that in mind.

Failure modes, side by side

Every pricing model fails somewhere. The useful question is whose failure mode you can live with.

• Per-technician fails when you succeed at staffing. The moment service quality demands a third pair of hands, your vendor gets a raise. Some MSPs share logins to avoid it, which breaks audit trails and usually breaches the licence.
• Per-endpoint fails when you succeed at selling. Your software cost scales linearly with the thing you are trying to grow, which means your vendor takes a fixed slice of every new client forever.
• Flat rate fails when you are tiny and static, and at band edges. Its failure mode is paying £24 a month more than a meter would charge. The other two fail by hundreds.

A pricing model is a bet on how you will grow. Choose the one betting on your side of the table.

Where this fits with Helios

Helios is priced exactly as this article describes: flat per MSP at £99, £199 or £399 a month, banded at 50, 250 and unlimited devices, every feature on every band, monthly billing, cancel any time. The bands in the worked examples are ours, deliberately, so you can check the arithmetic against a real published price list rather than a hypothetical. The honest caveats also apply to us: a solo technician with 30 static endpoints will find a per-endpoint meter cheaper, and we would rather you worked that out before trialling than after. If your numbers point the other way, the trial takes an afternoon, not an implementation project.

Helios is a single RMM and PSA platform for small MSPs and internal IT teams, with monitoring, patching, a service desk and an AI agent included on every plan. 14-day trial, no card to start, no feature tiers. Start free.

Related: The cheapest RMM for under 100 endpoints: real totals, not headline prices, MSP software with no long-term contract: why monthly billing changed the market, MSP margin per endpoint: the one number every owner should know

Researched and written with Helio SEO, our AI writer for business blogs.