PSA software (professional services automation) is the system a service business uses to run delivery: projects or tickets, people, time, billing and reporting. For an MSP, that means tickets, logged time and client billing in one system.
Key takeaways
PSA stands for professional services automation: software for companies that sell their people's time.
Two groups use it, and search results mix them up.
This guide follows the MSP case, where work starts with an email that says the printer is offline.
What each one runs, and where a PSA fits:
| Software | How it differs from a PSA |
|---|---|
| Project management | Plans and tracks the work: tasks, schedules, budgets and staffing. A PSA puts that work in one system with time tracking, resource planning and billing. |
| Accounting | A PSA often connects to it rather than replacing it. MSPs describe PSA invoices flowing into QuickBooks Online or Xero. |
| ERP | Runs a whole company's core processes, such as finance, HR, supply chain and inventory, on shared data. A PSA covers the narrower delivery side. For service firms it plays a role similar to the one ERP plays in manufacturing and retail. |
A small MSP usually sells two things: a monthly agreement and work outside it. Both depend on knowing who did what, for which client, and whether it was billable. When that record is split across a ticketing tool, a spreadsheet and memory, each hand-off risks a missed or misbilled hour.
One r/msp commenter described their month-end in November 2025: the PSA builds invoices from ticket time, a PowerShell script pulls the line items, and they're imported into accounting. "This takes a lot of time and manual checking," they wrote.
Say you run three technicians on flat-fee clients with a $125 out-of-scope rate, and each one leaves 20 minutes of billable, client-approved work unlogged a day. Over 20 working days that's 20 hours, or $2,500 a month that never reaches an invoice. Put in your own numbers:
Estimate time that could go unbilled
Technicians × minutes ÷ 60 × working days × rate. Your numbers stay in the browser.
Not sure about the minutes? Compare last month's calendars with the hours your team logged. The gap is usually the number to fix first, whichever tool you use.
Example
The setup. A dental practice pays its MSP a flat $1,500 a month, including 6 hours of remote support; approved work outside scope is $125 an hour. It has used 5 of the 6 hours this month.
On Monday the office manager emails: scan-to-folder has stopped, and a new hire starting Thursday needs a workstation. Email, a portal, a call or an RMM alert can all become tickets; see our MSP ticketing system guide.
The technician fixes scanning remotely and logs 0.75 hours on the ticket. That's 5.75 of 6 included hours, so nothing is added to the invoice.
The workstation is outside the agreement. The technician estimates two hours at $125; the office manager approves by email, on the ticket.
On Wednesday the technician logs 2.0 hours as workstation setup, flagged billable and out of scope. Logging at the ticket, not from memory on Friday, lowers the risk of a missed hour (see time tracking in SherpaDesk).
On the 1st, the owner checks both entries, their notes and work types, and the approval.
The invoice shows the $1,500 fee and one extra line: "Workstation setup, ticket #1042, 2.0 h × $125 = $250." The covered 0.75 hours appear on the usage report, not as a charge.
The invoice reaches your accounting package through an integration or an export. In one r/msp thread, a commenter's PSA syncs the paid status back from Xero. Don't assume yours does; test it.
On an all-inclusive agreement, the invoice is just the $1,500 fee, but the time still matters. If the practice used 14 hours this month, contract revenue per logged hour was about $107 ($1,500 ÷ 14). That isn't margin: the fee may also pay for licenses, monitoring and other obligations. Treat a falling number as a signal to review the agreement's scope and costs, not as grounds to reprice on its own.
Nothing here happens just because a ticket closes. Each step needs:
How much of this is automatic varies by product.
Subscribe to the SherpaDesk Blog.
Get Tips for Running IT With a Small Team.
The core of a PSA is project, resource, and time and expense management. Other modules include CRM, a help desk or service desk, and reporting, and for an MSP a PSA also handles billing. Our grouping for an MSP:
| Criterion | PSA | RMM | Help desk | CRM |
|---|---|---|---|---|
| Main focus | The business side of delivery: tickets, time, billing | Client devices: monitoring, patching, maintenance, remote access | Support requests: logging, routing and resolving them | Interactions with past, present and potential customers: leads, contact history, deals |
| Main question | "What did we do for this client, and was it billed?" | "Is this machine healthy?" | "Who's working on this request?" | "Who might buy, and when?" |
| Billing | A core job | Not its focus; some vendors sell it in one suite with a PSA | Varies by product | Not its focus; some PSAs include CRM |
The key link is PSA and RMM. MSPs often deploy both, and integrating them lets an RMM alert open a ticket in the PSA. In one r/msp thread, closing an alert in the RMM also closed it in the commenter's PSA.
PSA products are sold either as standalone tools or as part of an integrated suite with RMM and other software. For an IT buyer, first check the audience (see above), then two things: what the subscription includes and how it connects to the rest of your stack.
| Includes | What it means for you | Example |
|---|---|---|
| PSA only | You pick the RMM and accounting package and connect them | ConnectWise PSA, sold as "Service desk and ticketing software"; HaloPSA |
| PSA + RMM | One subscription covers both | Syncro: "RMM + PSA in every plan" |
| Wider suite | PSA sold with other business tools in one subscription | Kaseya 365 Ops: PSA with IT documentation, billing and quoting tools |
A PSA can link to the same vendor's RMM or to another vendor's, and standalone PSAs often connect to CRM and accounting tools. For an RMM from another vendor, test the integration in your pilot.
Without invoices, the chain ends in a report.
Example: a six-building district
| Item | Value |
|---|---|
| Hours on projectors, term | 38 h |
| Hours on Chromebooks, term | 140 h |
| Internal cost per hour | $45 an hour |
| Chromebook support cost, term (140 × $45) | $6,300 |
One real district shows the asset side of this. Plano ISD, a SherpaDesk customer, tracks its Chromebooks as assets with handheld barcode scanning.
PIInventory Department, Plano ISD72 campuses · 54,000+ students · from SherpaDesk's published case study“We were able to add and commission a cart of 36 Chromebooks in under 5 minutes. The physical inventory for each cart now takes 8 seconds.”
| Vendor | What's priced | Unit | Published price | Notes |
|---|---|---|---|---|
| SherpaDesk Base Camp Ours | PSA: help desk, time tracking, invoicing | Per technician | $45 per technician per month, billed monthly; $40, billed annually | Single Agent plan free; free trial, no credit card |
| SherpaDesk High Camp Ours | PSA, plus asset management | Per technician | $55 per technician per month, billed monthly; $50, billed annually | Listed as best for MSPs |
| Syncro Core | PSA + RMM bundle | Per user | $129 per user per month, billed annually; $159, billed monthly | Billing and invoicing included |
| Syncro Team | PSA + RMM bundle | Per user | $179 per user per month, billed annually; $209, billed monthly | Adds Microsoft 365 security and AI-powered ticketing |
| HaloPSA | PSA (whole Halo platform, no RMM) | Per agent | Set by region and agent count; default UK view £66 per agent per month, billed annually | "Onboarding packages are required with purchase at a bespoke cost depending on scope" |
| ConnectWise PSA | Standalone PSA | Quote | No public price; "Request a Quote" | — |
Source: vendor pricing pages. Prices as of October 2026.
What three technicians pay a month, billed monthly: $165 on SherpaDesk High Camp ($135 on Base Camp), against $477 on Syncro Core or $627 on Syncro Team, which both include an RMM. HaloPSA needs a quote for three agents plus a required onboarding package; ConnectWise PSA is quote-only.
In an October 2025 r/msp thread, one commenter said unhappy MSPs are often "trying to solve a broken process problem with a tool solution". Write down how a ticket becomes an invoice today first.
Implementation, change management and upfront cost are common PSA challenges, and HaloPSA requires paid onboarding. A small HaloPSA team in the same thread needed consultant time for setup. Once it was running, someone there still spends "35% if not more sometimes" of their time working on the PSA. Get setup hours and cost in writing, and budget for ongoing admin.
Alert tickets nobody needs to act on can bury the queue. A July 2026 commenter advised starting RMM-to-PSA ticket creation "light and slow" and widening it gradually.
Test a PSA on real work before you sign, and judge it by outcomes, not feature lists. A pilot small enough to finish:
One client, one contract, one billing period. Pick your most common agreement.
One person sets it up and trains one technician to log that client's time in it.
Keep your current process for that client and produce the invoice both ways.
Compare logged hours with invoice lines. Explain every difference.
Import that client's contract and open tickets, push the invoice to accounting, record a payment, and export time and ticket data.
Unreviewed entries at month-end, invoice corrections, hours spent preparing billing, logged hours against calendars.
Tip
If a free trial is shorter than one billing period, ask for an extension or pilot half a month.
SherpaDesk is an all-in-one PSA for small businesses, IT teams and MSPs, combining help desk ticketing, time tracking, invoicing, project and asset management, and reporting. Forward your support address to an email dropbox and incoming emails become tickets. Technicians log time with a Start/Stop timer, a calendar Timesheet or Add Time, or by replying to a ticket email with "cmd time". Time logs carry billable and non-billable hours.
A Flat + Hourly contract covers included hours, then bills overage at contract rates. Rate plans include hourly, fixed rate plus hourly, retainer, blended hourly and contract-level pricing. Uninvoiced time and expenses collect in "Ready to Invoice", organized by account contract. SherpaDesk supports QuickBooks, QuickBooks Online, Xero and FreshBooks.
Base Camp is forty-five dollars and High Camp fifty-five dollars per technician per month, billed monthly (forty and fifty billed annually). The Single Agent plan is free. K-12 and higher-ed pricing is based on student enrollment.
See how invoicing works in SherpaDesk →
Who this isn't for
When a dedicated MSP PSA may be overkill:
PSA software, short for professional services automation, runs the business side of a company that sells its people's time: work intake, staffing, time, billing and reporting. MSPs use it to turn tickets and logged time into invoices; internal IT uses it to see where support hours go.
PSA stands for professional services automation. The same acronym covers tools built for consultancies and tools built for MSPs and IT teams. Check which group a comparison is written for: a list built for agencies won't test ticketing or RMM links.
A CRM manages a company's interactions with past, present and potential customers: leads, contact history and deals. A PSA's main job is the delivery that follows the sale: tickets, time and invoices. Some PSAs include CRM features, so compare the specific products.
Examples include ConnectWise PSA, Datto Autotask PSA, Certinia, BigTime and NetSuite OpenAir, plus HaloPSA, Syncro, which bundles PSA and RMM, and SherpaDesk. If your work arrives as tickets, start with ConnectWise PSA, Datto Autotask PSA, HaloPSA, Syncro and SherpaDesk. If it arrives as projects, start with Certinia, BigTime and NetSuite OpenAir.
There isn't one best PSA. The right choice depends on team size, the RMM you run, your accounting package and your contract types. In one r/msp thread, integrations were "the whole reason" one MSP stayed with its PSA, and another wanted to leave theirs over them. Pilot two or three on the same client.
They do different jobs. An RMM monitors and manages client devices; a PSA handles tickets, time tracking and invoicing, and RMM alerts can open tickets in it. If you need contracts, billable time and invoicing tied to tickets, add a PSA.
It depends on the pricing unit and what's bundled. In October 2026, SherpaDesk listed $45 to $55 per technician per month billed monthly, or $40 to $50 billed annually. Syncro's PSA + RMM bundle started at $159 per user per month billed monthly, or $129 annually. HaloPSA priced per agent by region with required onboarding, and ConnectWise PSA was quote-only. Add setup and training time before you compare.
Patrick co-founded SherpaDesk and has led it as CEO since 2013. He has worked with IT service providers since 1998, first on network projects for schools and government offices, then on the help desk software their technicians use every day.