MSP tooling cost per endpoint: how to calculate it, and what good looks like

To work out your MSP tooling cost per endpoint, list every tool you pay for, convert each bill to a monthly amount on what you are actually charged, divide by the number of endpoints you manage, and add the results together. Good does not mean a magic number. It means every layer of the stack is paid for once, minimums are not quietly inflating the figure, and the per-endpoint cost falls rather than rises as the estate grows. Here is the method, then a worked example.

Why per-endpoint is the right unit, even when nobody bills that way

Your stack is priced in at least three currencies: per device, per technician and per user. Some tools add a fourth, the flat monthly minimum. Added up as invoices, the total tells you what you spend but not whether it makes sense, because it moves every time you hire a technician or win a client.

Endpoints are the thing you sell, whether the machines belong to clients or to your own company. Normalising every tool to cost per endpoint per month puts the stack in the same unit as your revenue, which is what makes it comparable to the figure in MSP margin per endpoint. A per-technician PSA and a per-device EDR agent finally sit in the same column.

Step one: list every tool and its native pricing unit

Pull the last three months of card statements and supplier invoices, not the list in your head. The list in your head is the tidy version. The statements include the remote access tool a technician bought on a card two years ago and the documentation platform nobody cancelled.

For each line, record four things:

• The tool and the layer it covers. Monitoring, patching, EDR, backup, remote access, PSA, documentation, email security. Be honest about everything a tool does, not just why you bought it.
• The pricing unit. Per device, per technician, per user, per protected server, flat fee.
• The billed quantity. What you pay for, including any minimum, not what you use.
• The billing period. Monthly, annual or multi-year.

Step two: normalise each tool to a monthly per-endpoint figure

One formula does the work for every pricing model:

Three traps catch people here.

• Annual and per-year pricing. Divide by 12 before anything else. Endpoint security is often quoted per year: Guardz notes that Guardz found SentinelOne's own page lists Core at $69.99, Complete at $179.99, and Commercial at $229.99, per endpoint per year. Compare those against a monthly RMM rate without dividing and the security line looks twelve times worse than it is.
• Minimums. Use the billed quantity, then divide by real endpoints. Invenio IT reports Datto RMM pricing starts at $2.99 per endpoint, per month, with a minimum of 10 endpoints or $29.90 monthly. On six devices, that is roughly $4.98 each, not $2.99.
• Per-technician and per-user tools. These are not free per endpoint just because the invoice does not mention devices. Divide the monthly total by your endpoint count like everything else.

The shelfware test: compare billed quantity with active quantity for every per-device tool. Licences for decommissioned machines are a cost per endpoint you no longer have.

Step three: a worked example, with invented figures

Every number below is made up for illustration. It is not a benchmark and not any vendor's price. The fictional MSP manages 400 endpoints with four technicians.

The total is £15.15 per endpoint per month. On its own that number means little. The interesting part is the layer column.

Spotting overlap: where you pay twice for one layer

Sort the table by layer rather than by vendor and the duplicates surface. In the example, three stand out.

• Remote access, bought twice. The RMM already includes it. The separate tool costs £0.40 per endpoint for technician habit. Skip this check and you keep paying for a preference.
• Patching, bought twice. The add-on duplicates the RMM's third-party patching. If the RMM's catalogue covers your clients' applications, that is £0.75 per endpoint going nowhere.
• Threat detection, arguably bought twice. EDR and the SIEM both sell detection. This one is a judgement call, not an automatic cut, because a SIEM correlating identity and email signals does work an endpoint agent does not. The question is whether you can name what the SIEM catches that the EDR misses.

Removing the first two saves £1.15 per endpoint, which on 400 endpoints is £460 a month. Overlap rarely looks dramatic per line. It looks dramatic over a year.

Overlap is a cost you chose once and keep choosing every month by not looking.

What good looks like, without a fake benchmark

Published anchor prices tell you what ranges exist, not what your stack should cost. Domotz puts per-device RMM pricing typically from $1 to $5 per endpoint per month, and per-technician pricing from $79 to $209 per technician per month. RFP Wiki reports NinjaOne's published range runs from $1.50 per endpoint per month at 10,000 devices to $3.75 at 50 or fewer. At the other end, AIMultiple notes Action1 is free for up to 200 endpoints with no feature limits and no expiry. These are US dollar figures, so convert before comparing. For a fuller table, see the MSP software price index.

A healthy stack passes three tests instead:

1. The one-owner test: every layer has exactly one tool responsible for it, or a written reason for two.
2. The growth test: recalculate at 1.5 times your current endpoints. If the figure rises, a per-technician tool or a tier jump is punishing growth.
3. The minimum test: no tool's minimum pushes its real per-endpoint cost far above its headline rate.

Where this fits with Helios

Most of this exercise is discipline, not tooling: no platform will read your card statements for you. Where Helios helps is the overlap step, because monitoring, patching, remote access, the helpdesk, documentation and billing sit in one product, so several rows in a table like the one above collapse into one. It is priced by fleet size with no charge per technician and every feature on every plan, from £20 a month, which keeps the growth test simple. You can check the detail on the Helios pricing page and run it through the same formula as everything else.

Common questions about MSP tooling cost per endpoint

Should tooling cost per endpoint include the PSA and documentation tools?

Yes, tooling cost per endpoint should include every tool the business pays for, including the PSA, documentation and remote access. Those tools are priced per technician or per user, but they exist to deliver service on endpoints. Leaving them out flatters the figure and hides the cost of hiring, which is exactly when per-technician pricing starts to bite.

Do I count servers and network devices as endpoints?

Count whatever unit you bill clients on, and keep it consistent between quarters. If you charge per device including servers, count servers. If you charge per user, calculate tooling cost per user alongside the per-endpoint figure. Changing the denominator between reviews makes the trend meaningless, which defeats the point of tracking MSP tooling cost at all.

How should I handle tools I resell to clients at a markup?

Include resold tools such as EDR or backup in the tooling cost calculation, then track the markup separately. Tooling cost per endpoint measures what the stack costs you to run. Margin per endpoint measures what you keep after charging for it. Mixing resale revenue into the cost figure makes an expensive stack look cheap and hides genuine overlap.

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