Here is what I know after 30 years in IT
I have lived this problem. Not read about it. Not consulted on it. Lived it — managing techs, chasing customers, staring at reports that told me nothing useful while the real answers were buried somewhere I could not easily get to.
Customer Contracts and Ticket Overload
Every MSP has that one customer who pays on time but racks up tickets like it’s a hobby. You look at their contract, and it covers a certain number of hours or incidents. But every month, they’re consuming three times that. The PSA has the data — tickets, time logs, invoices — but it doesn’t connect them. You need to know which customers are costing you more than they’re worth. If you don’t see it, you can’t make the call to adjust the contract or let them go.
Techs and Late Notes
Techs are busy, and sometimes notes get entered late. But when notes are consistently late or backdated, it skews your data. You can’t see the real time spent on tasks, which means payroll and billing may be off. The PSA logs the time when the note is entered, not when the work was done. This isn’t about catching techs out; it’s about visibility. Late entries could be a coaching problem or a process issue. Without clear data, you can’t address it.
Flat Contracts and Unbilled Time
Flat-rate contracts are supposed to simplify billing. But if unbilled time keeps slipping through, you’re losing money. The PSA tracks time, but it doesn’t flag when labor exceeds what’s covered. You might have a tech spending extra hours on a flat-rate client, and those hours aren’t accounted for. It’s not about accusing anyone; it’s about protecting revenue. You need to see these patterns to adjust staffing, renegotiate terms, or rethink contract structures.