The system of record for how the service business actually runs.
Early accessPSA Software
Professional services automation for MSPs - clients, contracts, tickets, time, projects and billing data on one model.
- Part of CubeMSP
- Serving businesses across the UK
- 01234 672 617
Professional services automation is a grand name for a simple ambition: stop running the service business out of six disconnected tools. A PSA holds the client, the contract, the ticket, the time booked against it, the project it belongs to and the figures that come out of the far end. CubeMSP does that with one data model and one set of permissions, so a question about any of them has a single answer. Most PSAs list the same features, so the distinction that matters is whether the parts share one record, or whether they are separate modules that synchronise overnight and disagree by Wednesday.
- One model
Shared by clients, contracts, tickets and time
- Per period
Cost and margin per client, computed not estimated
- Fixed
Implementation quoted before it starts
What it does
Inside PSA software
The parts of CubeMSP that make up PSA. Everything here shares one database, so nothing needs re-keying between them.
Contracts and recurring services
Support agreements, licence counts, hosted services and circuits held as structured records with term, cost, sell and renewal date - not as a PDF in a folder and a line in a spreadsheet.
Time against the work it was spent on
Time booked to the incident or task it belongs to, billable or not, at the applicable rate. What a client costs to support stops being a feeling and becomes a figure.
Work you can see across the firm
Every open incident, project and task on one board, filtered by client, engineer or status, so the Monday meeting is a review rather than an investigation.
Approvals with limits
Out-of-contract work, write-offs, discounts and purchases routed by value to whoever is allowed to sign them, with the decision and the reason recorded against the record.
Alerts instead of chasing
Renewals approaching, incidents breaching target, projects overrunning and unbilled time all raise themselves rather than waiting for somebody to notice them.
Reporting without exports
Dashboards by role and scheduled reports delivered by email. If somebody is still exporting to a spreadsheet to answer a routine question, that is a report we have not built yet.
In practice
Problems this actually solves
Anonymised, but not invented. These are the situations businesses describe to us before they change anything.
A firm paying for four tools that disagreed
The situation
A CRM held the clients, a ticketing tool held the incidents, a project tool held the migrations and a spreadsheet held the contracts. All four had a different idea of which clients were active and none of them knew about the others.
What changed
One record per client with services, tickets and projects attached to it. Three subscriptions cancelled, and the weekly argument about which list was correct stopped entirely.
A managed service that had never been costed
The situation
A fixed monthly fee covered "reasonable support". Nobody had ever measured what reasonable meant, and two clients were quietly consuming more engineering hours than the three largest accounts combined.
What changed
Time booked against incidents made the true cost of each contract visible within a quarter. Two agreements were renegotiated at renewal on the strength of the actual figures, not an impression.
Unbilled work discovered a quarter late
The situation
Out-of-contract work was agreed on the phone, done, and then remembered at invoicing time - or not. The write-off line was significant enough to matter and nobody could explain where it came from.
What changed
Billable time is flagged at the point it is booked and appears on a monthly unbilled report. The write-off is now a decision somebody makes on purpose rather than an accident discovered afterwards.
How it happens
What implementation actually involves
No mystery, no discovery phase that quietly becomes the project. Five stages, and you will know what each one costs before it starts.
Discovery
A structured session mapping how you run now - the PSA you have outgrown, the spreadsheet of renewals, the shared mailbox that is really your ticket queue, and the review deck somebody rebuilds by hand every six months. We come back with what the platform covers as standard and what needs building.
Configuration
Your service catalogue, ticket taxonomy, boards, roles, approval limits and review templates set up to match how you actually work - not a demo tenant with your logo dropped on it. Your categories, not ours.
Data migration
Clients, contacts, sites, services, renewal dates and enough ticket history to make the knowledgebase and similar-incident retrieval useful on day one. An empty AI is a useless AI, so the history matters more here than in most migrations.
Training & rollout
Role-based training - the service desk learns logging and resolution, account managers learn reviews and renewals, directors learn the reporting. We usually pilot with one technician and one client before opening it up.
Ongoing support
UK support from the people who built the platform and use it themselves, with a named contact, agreed response times, and a roadmap you can influence. Being a small vendor is an advantage here and we intend to keep it.
You might call it something else
PSA goes by a lot of names - if you searched for any of these, this is the page you wanted.
- Professional services automation
- PSA platform
- PSA tool
- MSP PSA
- Service automation software
- IT services business software
Questions
The things people ask first
It is the system that runs the commercial side of a services business: who the clients are, what you have agreed to do for them, what work has been done, how long it took, and what should be billed. For an MSP it sits alongside the RMM, which handles the technical side.
Almost every MSP ends up with both, because they answer different questions. The RMM tells you a server is down; the PSA tells you whose server it is, what you have agreed about it, who fixed it last time and whether the work is chargeable. CubeMSP is the second of those and integrates with the first.
Services are held per client with quantity, unit cost, sell price, billing frequency, term and renewal date. That produces a recurring revenue and margin view, and feeds billing data out through the API to whichever finance system you use.
Yes. Clients, contacts, sites, contracts, service lines and ticket history are all migrated as part of implementation. You reconcile against the old system and we only cut over once the numbers agree.
Pricing is per named technician per month with a one-off implementation fee covering configuration, migration and training. Client users invited to shared boards are not charged for, and the API is not licensed per connection.
Related
Other things we can put right
MSP Software
One system for clients, services, renewals, incidents, projects and reviews - built in the UK by a managed service provider.
Read moreIT Service Management Software
Incidents, requests, problems and knowledge handled consistently, with the service catalogue and the client record in the same system.
Read moreSubscription Management Software
Every licence, circuit, backup and contract you resell - with quantity, cost, sell price, term and renewal date, and the margin visible on all of it.
Read moreIT Project Management Software
Shared kanban boards for migrations, rollouts and onboardings - with the client invited in, and internal-only tasks filtered on the server.
Read more
Part of a bigger system
PSA is one part of CubeMSP. You can start here and switch the rest on later - it is the same system, not a separate purchase bolted on.
Talk to us
Is PSA your actual problem?
Sometimes it is not. Tell us what is going wrong and we will tell you whether this is the right thing to fix first.