A PSA is where the tickets, the time, the contracts and the invoices live, and it is priced on a completely different axis from the RMM beside it. RMM charges by the endpoint, which grows with your clients. PSA charges by the technician, which grows with your payroll. Getting the two confused is the commonest reason an MSP's platform bill surprises it in year two, and it is why the two numbers on this site are kept apart.
Ask vendors to quote against your actual endpoint count
What is published for PSA RMM plans, and why HaloPSA's is not
SuperOps is the only vendor in this record publishing a figure that covers a PSA: its calculator prices 100 endpoints at $1.50 each, $150 a month, on a plan that carries both RMM and PSA. HaloPSA and ConnectWise, the two names that come up in almost every PSA shortlist, both answer a Cloudflare block to every reader available here, so what they publish is unknown to this record rather than absent from their sites. That leaves the PSA category thinner than the RMM one, and the honest thing is to say so rather than to fill it with third-party estimates. What can be said with evidence is that the one vendor publishing a combined figure prices it on the endpoint axis rather than the technician axis, which is unusual in this trade and is the thing to check when comparing it against a per-seat quote.
PSA for MSPs: per technician against per endpoint, worked through
The two axes cross at a ratio that decides which model favours you. An MSP with 2,000 endpoints and six technicians is dense: a per-endpoint platform costs it more than a per-seat one. An MSP with 400 endpoints and six technicians is thin: the per-seat bill dominates. Neither model is generous or mean in itself; they simply reward different shapes of business. This matters at renewal more than at purchase, because the shape changes. An MSP that wins a large low-touch client gets denser and its per-endpoint costs rise faster than its revenue if it priced the client per seat. Work out your own ratio before the conversation, and ask each vendor to quote against the ratio you expect in two years rather than the one you have today.
What the best MSP PSA has to do before price matters
Time entry that technicians will actually use, contracts that bill without a person rebuilding them each month, and a ticket flow that matches how your team dispatches. A PSA that fails any of those is expensive at any price, because the cost lands as unbilled hours rather than as a line on an invoice. This site does not score those things and will not pretend to. It records what each vendor publishes about price. The functional shortlist is yours to make, and the right order is to make it first and bring price to the two or three that survive, rather than the other way round.
MSP quoting software and MSP billing software are PSA modules, not separate purchases
Quoting and billing are the two places a PSA earns its licence, because they are where a ticket becomes money. A quote that turns into a project and then into an invoice without anyone retyping it is the join the category exists for, and it is also the join most often demonstrated with a tidy example that never happens. Take one awkward month to the demo instead: a fixed agreement, an out of scope job, a hardware resale and a credit, and see what leaves the system. Buying a separate quoting tool or a separate billing tool is usually a sign the PSA's version was never configured rather than that it was inadequate.
Questions people ask about psa software for MSP
How much does a PSA tool cost?
Only one vendor in this record publishes a figure covering a PSA: SuperOps, at $1.50 an endpoint a month at its 100-endpoint minimum, on a plan carrying both RMM and PSA. HaloPSA's and ConnectWise's pricing pages could not be read from here.
Is PSA priced per technician or per endpoint?
Usually per technician, which is what separates it from RMM. SuperOps is the exception in this record and prices its combined plan per endpoint.
PSA vs RMM: which is more expensive?
It depends on your ratio of endpoints to technicians. A dense MSP pays more for per-endpoint pricing; a thin one pays more for per-seat. Work out your own ratio before you ask for quotes.
Should I buy an RMM PSA bundle from one vendor?
Vendors that sell both usually discount the pair, so the bundle is where the negotiation is. Against that, a single vendor is a single point of failure and a harder migration later.