PSA software for MSPs: what a UK managed service provider actually needs

PSA software for MSPs is the system that runs the business side of your managed service business: it takes a request in as a ticket, ties that work to a client contract with its included hours and rates, tracks it against an SLA, captures the time, and turns it into an invoice. If your tickets, time, contracts and billing live in different places, the gaps between them are where your margin quietly disappears.

I spend my working week building business systems for firms that have outgrown the tool they started with. The pattern is consistent. Nobody goes shopping for a PSA because they like software. They go shopping because invoices are going out late, hours are missing, or the monthly fee no longer lines up with the work being done. This article covers what a UK MSP genuinely needs, how the realistic options compare, what drives cost, and when a bespoke build makes more sense than bending a packaged product. If you already know you need something built to fit, our bespoke business systems service is the route we take.

What does a UK managed service provider actually need from a PSA?

At minimum, seven things: a shared ticket queue, client and contract records, SLA clocks, time capture at the point of work, billing that follows the contract terms, documentation linked to the client, and reporting that shows which contracts are profitable. Anything beyond that is a question of scale.

The order matters. Most MSPs buy on ticketing and discover later that contracts and billing are the hard part. A PSA is not a helpdesk with a billing tab bolted on. It is the record of what you sold, what you delivered, and what you are owed, and those three things have to agree.

Tickets and the service desk

Work arrives by email, phone, portal or a monitoring alert, and each route has to become a ticket with a client, a priority and an owner. The practical test is whether a technician can work a queue without switching to another system, and whether a client can see progress without emailing you for an update. A self-service portal that turns requests into tracked work is worth having; several vendors highlight it as a core function of MSP tooling (NinjaOne).

Contracts, included hours and rates

This is where UK MSPs bleed. A flat monthly fee with a bundle of included hours, an out-of-scope hourly rate, and a handful of exceptions per client is normal. Your PSA has to hold all of that as structured data, not as a note in a spreadsheet. This is the difference between billing that takes an afternoon and billing that takes a week.

SLAs that are measured, not promised

A service level agreement sets measurable targets for response and resolution times (Teamwork). A promise in a contract that no system measures is a risk, not a feature. You want the clock to start when the ticket lands, to pause when you are waiting on the client, and to produce a report you would be comfortable sending.

Time capture and billing

The single biggest reason MSPs replace a PSA is unbilled time. Capture it at the ticket as the work happens, not from memory on Friday. In practice, a request comes in, a technician logs the work against the ticket, the contract decides whether that time is covered by the fee or becomes an extra line, and the invoice goes to your accounting package with the agreed charges (SherpaDesk). Test that last step before you buy. Do not assume your accounting sync works both ways.

Reporting that tells you where the money went

The question to ask of any candidate is simple: can it show me hours delivered against fee for each client this month? If the answer needs a spreadsheet export and an afternoon, the tool is not doing the job.

Packaged PSA versus a bespoke build: an honest comparison

The packaged market is mature and consolidating, and many MSPs run the long established platforms (Teamwork). Those products are good at the common shape of an MSP. If your business looks like the textbook, buy packaged and spend your energy elsewhere. Vendor prices and plans change, so check current details directly with each supplier rather than trusting any comparison, including this one.

Where I see bespoke builds win is when the commercial model is unusual: tiered support with a satisfaction credit, project work that draws down hours from three pots at different rates, or approvals that have to pass through a client's finance team before work starts. The same is true where the PSA has to talk to a line of business system that nothing integrates with. In those cases, bending a packaged tool means paying twice: once for the licence, and again for the workarounds.

What drives the cost of a PSA in the UK?

Four things: the number of users, the number of client contracts and their complexity, the integrations you need, and the migration of historical tickets and time. The first is visible on any vendor's price list. The rest are where projects overrun.

For a bespoke build, a PSA is a custom project and is priced by quote. It depends on the contract model, the billing rules, how many systems it must talk to and how much history you want carried across. We build those systems as part of our custom CRM and internal systems work, often alongside data integrations to your accounting and monitoring tools.

A practical rule I give clients: if you can describe your billing rules in a paragraph, a packaged tool probably handles them. If describing them takes a page and a diagram, budget for a build and treat it as a business asset rather than a subscription.

What should a UK MSP check before committing?

Run three tests on a shortlist, with your own numbers.

1. Take last month's messiest contract and ask each vendor to show it set up in their system: included hours, rate, exceptions, renewal date.
2. Submit a test ticket and watch the SLA clock behave correctly through a client wait.
3. Push a sample invoice into your accounting package and confirm it arrives as you expect, with the right tax treatment.

If any of those three falls down, so will month end. Add security to the list: your PSA holds client details, ticket content and perhaps credentials, so it sits inside your own obligations under UK GDPR. Our security monitoring and code scanning work covers the builds we run, and Varsuite is Cyber Essentials certified. That certification shows a baseline of controls is in place; it does not guarantee that any system is secure, and you should still assess each supplier properly before you hand over client data.

When a bespoke PSA is the wrong answer

Say it plainly: if you are a tidy MSP of a few technicians with a common contract shape, buying a packaged PSA is almost certainly cheaper and quicker than building one. You get a supported product that improves without your involvement. Building is the right call when your rules are the differentiator, when the volume justifies the investment, and when you have someone to own the system after launch.

What is the sensible next step?

If you have read this and recognised your own month end in it, the useful next step is not a demo. It is a short conversation about how your contracts, rates and approvals actually work, so you can see whether a packaged tool fits or a build is justified. Send us the shape of your contract model through our contact page and we will tell you honestly which it is, including when the answer is to buy something off the shelf.

Frequently asked questions

What is the difference between PSA and RMM software?

RMM, remote monitoring and management, looks after client devices and alerts you when something breaks. PSA runs the business side around that work: tickets, contracts, SLAs, time and billing. Some vendors sell them together and some separately; if you buy a standalone PSA you will also need to account for the monitoring licence and the integration between the two (Syncro).

How much does PSA software cost for an MSP?

Packaged pricing is usually per technician or per user, with the headline figure rarely telling the whole story once endpoint limits and add-ons are included. Vendors publish their own current prices, so check directly. A bespoke PSA is priced by quote, because the scope depends on your contract rules and integrations.

Can we keep our existing monitoring tool and add a PSA?

Yes, and many MSPs do. The deciding factor is how cleanly the PSA can receive alerts as tickets and how much manual reconciliation sits between the two systems. Test that integration before you commit, since it is the most common source of double entry.

How long does it take to move to a new PSA?

For a packaged platform, weeks rather than days once you include historical data, contract setup and team training. Matching your existing tickets and time records to the new system is often the longest part. A bespoke build follows the usual specification, build and test phases, so plan for longer before you see value. Either way, run the old and new systems in parallel for at least one billing cycle.