MSP Tooling Costs as a Percentage of MRR: How to Model It

MSP tooling cost as a percentage of revenue varies widely: community threads and peer surveys put it anywhere from mid single digits to around a fifth of MRR, depending on your stack, your pricing and your endpoint density per client. That spread is why your own figure matters more than any benchmark. Most MSP owners can quote their MRR to the pound and their tooling cost not at all, so here is a spreadsheet method that produces the number, column by column, for client machines and your own.

Start with a tooling ledger, not a feeling

Open a sheet with five columns: tool, monthly cost, billing unit, quantity, and what it actually covers. Then list everything that touches service delivery: RMM, PSA, endpoint protection, backup, email security, documentation platform, remote access, password manager, phone system, the reporting add-on you bought in a weak moment.

Two disciplines matter here. First, normalise everything to a monthly figure: annual invoices divided by twelve, three-year commitments divided by thirty-six. Second, record the billing unit honestly, because it drives everything downstream. Most tools bill one of four ways: per endpoint, per technician, per client or tenant, or flat. If you are not sure which model you are on, that is itself a finding. Different vendors chose different units for reasons that suit them, not you, a point we have made at length when comparing per-device, per-user and flat-fee pricing models.

Allocate every cost to a client

The ledger tells you what you spend. The allocation tells you who you spend it on. Three rules cover almost everything:

• Per-endpoint tools allocate directly. If the EDR is £1.80 per endpoint and Client A has 60 endpoints, Client A carries £108. No judgement required.
• Per-technician and flat tools allocate by endpoint share. A PSA at £70 per technician for three technicians is £210 a month. Divide by your total endpoint count and multiply by each client's endpoints. It is imperfect, but it is consistent, and consistency is what makes the comparison between clients meaningful.
• Per-client tools allocate directly. A backup subscription tied to one client's server belongs on that client's row and nowhere else.

The output is one row per client with a single figure: tooling cost per endpoint per month. Across a typical small MSP stack this lands somewhere in single-digit pounds, but the exact figure matters less than the spread. If one client costs twice the average, you want to know why before their renewal, not after.

Gross margin per endpoint: the arithmetic

Tooling is only half the cost of serving a client. The other half is labour, and your PSA already holds it: logged time per client per month. Take each technician's fully loaded monthly cost, work out a cost per logged hour, and multiply by the hours each client consumed. Then:

Gross margin per endpoint = revenue per endpoint, minus tooling per endpoint, minus labour per endpoint.

Client B is paying you to lose money. Nothing on the invoice would tell you this, because the invoice shows revenue and revenue looks fine. Only the allocation shows it, and it usually shows it for a reason: legacy pricing that never rose, an estate full of ageing hardware, or a contact who treats the service desk as a colleague. Each has a different fix, and one of them is losing the client well.

MSP tooling cost as a percentage of revenue: the honest answer

You will find people online claiming a correct benchmark for tooling as a percentage of MRR. Treat these numbers with suspicion. Community threads and peer surveys put the figure anywhere from mid single digits to around a fifth of revenue, and that spread is the real information: it depends entirely on your stack, your pricing and your endpoint density per client. An industry average applied to your business is a guess wearing a spreadsheet's clothes.

The percentages that are worth tracking are your own. Two of them: the whole-business figure, tracked quarter on quarter so you see drift when a vendor raises prices or a tool creeps in; and the per-client figure, because the variance between clients is where the unprofitable contracts hide.

Model a price rise and a new hire before you commit

Once the sheet exists, the interesting questions cost you nothing to answer.

A price rise is simple: revenue per endpoint moves, tooling and labour do not, so the margin change drops straight through. A £2 per endpoint increase across 400 endpoints is £800 a month of pure margin, which is a useful number to hold in mind when you are nervous about the conversation.

A new hire is where billing units bite. Every per-technician tool steps up on day one, before the hire has touched a ticket or brought in an endpoint. On a per-technician RMM and PSA, hiring your fourth technician can add a few hundred pounds a month of tooling cost with zero new revenue, which means your tooling cost per endpoint rises across every client simultaneously. Per-endpoint tools do the mirror image: they punish growth instead, taxing every new device you win. Run both scenarios in the sheet and you will see which billing units your business can afford to grow into. This is also why choosing an RMM by feature checklist misses the point: the pricing model shapes your margins for years.

Three ways this model lies to you

• Forgotten annual renewals. The tool billed once a year in March is invisible for eleven months. Skip the normalisation step and your percentage looks better than it is until the renewal lands.
• Averaged labour. Spreading labour evenly across clients instead of using logged time hides exactly the clients you built the sheet to find. If time logging is patchy, fixing that comes first.
• Treating the percentage as a target to minimise. The cheapest stack is rarely the cheapest service. A tool that saves each technician an hour a week is worth far more than its line in the ledger, and a bargain tool that generates noise costs you in labour instead. Minimise cost per endpoint served properly, not cost per endpoint on paper.

Where this fits with Helios

Most of this exercise is discipline and a spreadsheet, not tooling. Where Helios changes the model is the billing unit: RMM, PSA, patching, remote access, service desk and client portal are one flat monthly line at £79, £159 or £319, banded by device count rather than priced per technician or per endpoint. That makes the allocation trivial and, more usefully, it means hiring a technician or winning fifty endpoints does not move your tooling cost at all. We should be plain about the limits: Helios does not yet do recurring contract billing or rate cards, so the revenue side of your sheet still comes from your accounting system, with time tracking exported to QuickBooks for invoicing.

Helios is a single RMM and PSA platform for small MSPs and internal IT teams, with flat monthly pricing and every feature on every plan. There is a 14-day trial with no card and no feature gating. Start free at heliosmsp.io.

Related: Do you still need an MSP? An honest answer from someone who runs one, MSP margin per endpoint: the one number every owner should know, MSP tooling cost per endpoint: how to calculate it, and what good looks like

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