Solution · For MSPs
Price, staff and document every client — without guessing.
An MSP sells a promise: reliable IT service for a fixed monthly price. That promise only works if the cost of keeping it is known — per ticket, per client, per month — and if every change is documented well enough to survive a staff handover.
Every ticket priced, so no client is quietly losing money.
Staffing matched to real volume across all clients.
Changes and SLAs documented per client, not per memory.
The problem
Why MSP margins leak
MSP margins disappear in the gaps: the client whose tickets cost more than the fee, the change nobody documented, the service level agreed in a call and forgotten by Monday.
One fee, very different costs
Two clients pay the same monthly fee, but one opens three times as many tickets. Without a cost per ticket, the expensive client looks like the good client — until the numbers are finally worked out.
Staffing by feeling across clients
The desk feels busy, but nobody can say how many agents the combined volume needs. Hiring is delayed, the queue grows, and the clients who notice first are the ones who pay the most.
Client changes undocumented
An engineer changes a client’s system and records nothing. Months later another engineer inherits the client and finds a setup nobody can explain — and an outage nobody can trace.
One SLA for every client
Every client gets the same promise, whether they need it or not. The demanding client is underserved, the undemanding one is overpromised, and the agreement matches nobody’s reality.
The process
Five steps, and the itserva page for each
Five steps, per client, every month.
- 01
Price every ticket
Work out the fully loaded cost of resolving one ticket, including agent time and the tools behind it. Multiply by each client’s volume, and the clients that lose money become visible for the first time.
- 02
Staff across clients
Estimate how many agents the combined ticket volume needs at the service level you promised. Staffing across the whole book is the number that decides the next hire — and the next price review.
- 03
Document each client’s changes
Propose, assess and approve every client change in writing, with its risk and rollback plan. The record is what makes a client portable between engineers — and what protects the MSP when something goes wrong.
- 04
Agree SLAs per client
Write a separate agreement for each client: the services covered, the targets, and what is excluded. A per-client agreement is the document a price conversation can actually stand on.
- 05
Compare the PSA and RMM stack
Compare the software that runs the MSP itself — PSA, RMM and ticketing — on price, deployment and fit. The stack is a cost like any other, and it should be chosen on facts, not on a sales call.
What’s included
Tools, templates and guides for msps
Tool
Help Desk Staffing Calculator
Estimate how many agents a ticket volume needs at a given service level.
Product
Software Advisor
Honest software lists and comparisons, built from vendor pages with gaps marked.
Template
Change Request Template
Propose, assess and approve a change with its risk and rollback plan.
Measure it
The four numbers worth tracking
Four numbers, per client, every month. An MSP that does not know its cost per client is pricing on hope.
Cost per ticket, per client
What one ticket costs for each client, and what that client’s volume costs in total. Compare it with the fee, and the unprofitable clients stop hiding.
Downtime cost per client
What an hour of downtime costs each client’s business. It is the number that makes the case for the backup, the monitoring, or the higher tier.
SLA met rate, per client
The share of incidents resolved within target, for each client separately. One client’s misses should not hide inside an average that looks fine.
Tickets per agent
How many tickets each agent resolves, across the whole book. A rising count is either efficiency improving or the team approaching its limit — the staffing number tells you which.
Frequently asked questions
How do I know if a client is unprofitable?
Multiply the cost per ticket by the client’s monthly ticket volume, add the fixed costs of serving them, and compare the total with the fee. If the total is higher than the fee, the client is losing money — however pleasant the relationship is.
Should every client have the same SLA?
No. Different clients need different response times and pay different fees. One agreement for all clients either underserves the demanding ones or overpromises to the easy ones.
What should a client change record include?
What will change, why, the risk, the rollback plan, and who approved it. That is the whole record — and it is what the next engineer needs when the client calls about the change.
How do we choose PSA or RMM software?
List what the MSP needs — ticketing, remote monitoring, billing, reporting — then check each vendor’s published facts on price and deployment. Where a vendor does not publish a fact, mark it as not published instead of guessing.
Find the client that is quietly losing money.
Run the cost-per-ticket calculator on your busiest client’s volume, then compare it with the fee. A free workspace saves the calculation, so the price review starts from evidence.