5 Signs Your PSA Is Quietly Bleeding You Dry

I had a conversation recently with an MSP owner who told me his ConnectWise instance was "working fine." Twenty minutes in, we'd already found $6,400 in monthly unbilled recurring charges. Not edge cases. Not weird one-offs. Just agreements that weren't configured to bill for seats that had been added over the past year.

His PSA wasn't broken. It was technically running. But "running" and "working" are two very different things when we're talking about the system that controls your entire revenue cycle.

Here are five signs your PSA is quietly costing you money — and most of them won't show up on any dashboard you currently have.

1. Your techs treat the PSA like a chore, not a tool

This one is the canary in the coal mine and almost nobody pays attention to it.

Watch how your team actually uses the PSA during the day. Not how you think they use it, or how they were trained to use it — how they actually interact with it when they're busy and tickets are piling up.

If your techs are entering time at the end of the day in bulk (or worse, Friday afternoon for the entire week), that's a configuration problem, not a discipline problem. If people are copying ticket notes into a separate spreadsheet because they can't find information in the PSA later, that's a search and workflow problem. If your dispatcher is manually assigning every ticket because auto-routing never worked right after the initial setup, that's salary dollars burning on a task a computer should handle.

I worked with an MSP where the service coordinator spent two hours every morning just triaging and routing tickets that should have been auto-assigned based on board, type, and client tier. Two hours. Every morning. That's over 500 hours a year of a skilled person doing work a properly configured workflow rule handles in milliseconds.

The tell: ask your team what they'd change about the PSA if they could change anything. If the list is long and specific, your configuration has drifted far from useful. If they just shrug and say "it's fine" — that might be worse. They've given up expecting it to help them.

2. You can't tell me which clients are profitable without pulling out a spreadsheet

This one gets me every time.

Your PSA has every data point needed to calculate client profitability in real time. Labor costs based on actual time entries. Agreement revenue. Product margins. Project fees. Even expense allocations if you're tracking them. It's all right there in the database.

But if I ask "which of your clients made you money last month and which ones cost you money," and your answer involves exporting to Excel and spending an afternoon fighting with VLOOKUP, your PSA is fundamentally failing at one of its primary jobs.

I worked with an MSP last year who discovered — after we built proper profitability reporting — that their second-largest client by revenue was actually their least profitable. The agreement had been written years earlier, the client's environment had grown significantly, and the billing never kept pace. They were subsidizing that client's IT to the tune of about $3,200 a month. Nobody knew, because nobody could see it.

That's not an unusual story. It's the norm. Most MSPs I talk to have at least two or three clients that look great on the revenue line and terrible on the margin line. They just can't see it because their reporting was never built to show it.

3. Month-end billing takes more than a day

Billing should not be an event. It should not require a dedicated person spending two or three days reconciling spreadsheets, cross-referencing license counts, and manually creating invoice line items for things that should have been captured automatically throughout the month.

If your billing process looks anything like this — be honest — you've got a configuration problem:

Pull M365 license counts from the Partner Center. Compare against what's in the PSA agreements. Manually adjust the ones that changed. Do the same thing for Azure consumption. Same for security tools. Same for backup agents. Cross-reference time entries to catch any that weren't applied to tickets. Check for project work that wasn't invoiced. Build the invoices. Review them. Send them. Then spend two more days fielding client questions about line items that don't look right.

I've seen that process take a single person three full days every month at some shops. Three days. That's 36 days a year — close to two months of somebody's time — doing work that a properly configured PSA with the right integrations handles automatically.

The M365 license count should sync. The agreement additions should update when seats change. Time entries should be validated at the ticket level before they ever reach billing. Invoices should generate with one click. If any of those steps require a human to manually intervene every single month, you're paying for automation you're not using.

4. You've stopped configuring and started compensating

This is the most common pattern I see, and it's the hardest to recognize from the inside because it happens gradually.

It starts small. A workflow rule doesn't quite work right, so someone creates a manual step to catch the edge case. A report doesn't pull the right numbers, so someone builds a parallel tracking spreadsheet. The client portal doesn't display the information clients need, so the account manager sends a weekly email summary instead.

Each individual workaround makes sense on its own. But over two or three years, you end up with an entire shadow operation running alongside your PSA — spreadsheets, email chains, manual checklists, tribal knowledge in people's heads — and the PSA becomes just the place where tickets live instead of the operational backbone it was supposed to be.

Here's how to gut-check this: count the spreadsheets your team maintains that track things the PSA should be tracking. If it's more than two, you've got significant configuration drift. I've walked into environments with fifteen supplemental spreadsheets. Fifteen. All because somebody at some point couldn't figure out how to make the PSA do what they needed, built a workaround, and that workaround became permanent infrastructure.

The cost isn't just the time maintaining those spreadsheets. It's the data fragmentation. It's the single point of failure when the person who owns the spreadsheet goes on vacation. It's every decision you're making on incomplete information because the full picture lives across six different places instead of one.

5. New hires take months to get comfortable in the PSA

Most MSP owners write this one off as "just how it is." They're wrong.

If every new technician needs three months of hand-holding before they can navigate the PSA without constant questions, that's not a training problem. That's a configuration problem. Your boards are probably too complicated, your statuses don't make intuitive sense, your custom fields are a mess of legacy data nobody uses anymore, and your documentation of how things are supposed to work either doesn't exist or hasn't been updated since 2021.

A well-configured PSA should be navigable by a competent tech within the first week. Not mastered — navigable. They should be able to find their assigned tickets, enter time, update statuses, and follow the basic ticket lifecycle without memorizing a 40-page internal wiki or shadowing somebody for a month.

If that sounds unrealistic for your environment, it shouldn't. ConnectWise and HaloPSA are both capable of being intuitive when they're configured thoughtfully. The problem is that most implementations accumulate years of cruft — abandoned custom fields, boards nobody uses, statuses that made sense for a process you dropped two years ago, workflow rules that conflict with each other — and nobody ever goes back to clean house.

So what do you actually do about it?

I'm not going to pretend any of this is easy to fix while you're simultaneously running an MSP and putting out fires for clients. That tension is actually the whole reason this problem exists — PSA configuration always gets deprioritized because there's always a more urgent ticket, a more pressing client issue, a more visible problem to deal with.

But the math is pretty straightforward. If your PSA is leaking even 5% of your billable revenue through configuration gaps — and from what I've seen, most MSPs are closer to 8–15% — and you're doing $80K a month in recurring revenue, that's four grand to twelve grand a month you're not collecting. Every month. Quietly. Before you factor in productivity losses from manual workarounds and bad decisions made on incomplete data.

If any of these five signs hit close to home, start with an honest audit. Pull up your PSA with fresh eyes — or better yet, have someone who hasn't been staring at it for years take a look — and ask one question about every configuration, every workflow rule, every custom field: does this serve how we work today, or is it a leftover from a version of this business that doesn't exist anymore?

The answer might surprise you.

---

If you want a structured second opinion on your PSA setup, that's what PaxRig is here for. Book a free discovery call and I'll tell you exactly where I'd focus first.