There is a particular kind of invoice that every office manager learns to dread. It arrives a week after the server hiccup, itemized down to the quarter hour, and it reads like a receipt for a fire you did not know you were paying someone to let start. Pay-per-ticket IT feels thrifty right up until you notice who benefits when the printer, the firewall and the shared drive all fall over in the same month.
I want to be fair to break/fix support, because for a three-person shop it can be perfectly sensible. But somewhere around thirty people, the math quietly flips, and most businesses only notice after a bad quarter. That is the point to get a flat-rate quote for managed IT services in Calgary, or wherever you operate, and lay it next to last year’s break/fix invoices before you renew anything. The way a provider structures its pricing tells you more than the sales pitch ever will.
The incentive problem nobody puts in the contract
Here is the uncomfortable part. Under break/fix, your provider earns money when your technology fails. Not because anyone is crooked, but because that is simply how the business model is wired. A technician paid by the hour has no financial reason to spend a quiet Tuesday tightening your backups, cleaning up stale user accounts or replacing the switch that has been flickering since spring. None of that generates a ticket. All of it prevents one.
So the preventive work does not happen, or it happens only when you ask, and you will not ask, because you do not know it needs doing. It is a failure of design, not character.
Contrast that with a flat monthly fee. The moment a provider is paid the same amount whether your month is calm or chaotic, every outage becomes their cost, not their revenue. Suddenly the dull work is the profitable work. Patching on schedule, monitoring drives before they die, catching the expired certificate early: all of it protects the provider’s margin as much as your uptime. The incentives finally point in the same direction.
The costs that never show up on the invoice
The hourly invoice is the cost you can see. It is rarely the expensive one.
The expensive one is the afternoon your sales team spent unable to reach the CRM. It is the bookkeeper who now restarts her machine every morning as a ritual because nobody ever found out why it freezes. It is the hesitation before calling for help, because everyone in the office knows each call starts a meter running. That hesitation is poison. Small problems get tolerated until they become large problems, and large problems arrive at the worst possible moment.
At thirty people, these losses compound. You have enough staff that someone is always stuck on something, and enough systems that the stuck points multiply. Yet you are still small enough that leadership tends to treat IT as a utility bill to minimize rather than an operation to run. That combination is exactly where pay-per-ticket support does the most damage while looking the cheapest on paper.
What to actually compare
When you weigh the two models, do not compare last year’s break/fix invoices against a monthly quote. That compares the tip of one iceberg against the whole of another.
Ask what the provider does in a month when nothing goes wrong. If the honest answer is “nothing, until you call,” you are buying a fire department that only exists after the flames are visible. Ask whether the price changes when you need more help. If it does, you are back to a meter, just with a nicer name. Ask about contract length and exit terms, because a flat fee locked behind a punishing multi-year agreement is its own kind of trap. And ask who on their side is accountable for your setup being documented, so that knowledge does not live in one technician’s head.
None of this means flat-rate is automatically better, or that every provider charging monthly is doing the preventive work they promise. Plenty of them simply collect the fee and wait for calls. The model only fixes the incentive; you still have to check that someone is acting on it.
So before your next renewal or your next surprise invoice, pull up the last six months of tickets and read them as a story. Count how many were genuinely unforeseeable. If the answer is “very few,” you have been paying for repairs to problems someone could have prevented, and you already know which pricing model would have made preventing them worth their while.
Afiya Jafar is a technology and digital trends writer at TechWebin. She creates reader-focused content covering technology, software, apps, digital tools, web technologies, gadgets and emerging digital trends.
View Profile →
Sameena Begum is a technology and digital content reviewer at TechWebin. She reviews selected content for clarity, organisation, consistency, readability and overall editorial quality.
View Profile →