Break-fix support — calling someone when something breaks, paying for that one visit, and going back to normal until the next thing breaks — works fine for a lot of small businesses. It's how most businesses start out with technology support, and there's nothing wrong with it while it still fits.
The problem is that businesses grow past it without noticing, because break-fix support doesn't fail all at once. It fails a little at a time: a slightly longer wait here, a repeated problem there, a decision made without anyone thinking through the consequences. None of it feels urgent enough to change anything, until it adds up to real cost.
I work with businesses on both models, so I'm not writing this to talk anyone out of break-fix. I'm writing it because I see the same seven signs over and over in businesses that would genuinely benefit from a different arrangement, and most of them haven't stopped to notice the pattern.
1. The same problem keeps coming back
If you've called about the same slow computer, the same network drop, or the same printer three times this year, break-fix support is treating symptoms instead of causes. A single visit fixes what's in front of the tech that day. It rarely includes the time to ask why this keeps happening, because that's not what you're paying for in that visit.
An ongoing relationship changes the incentive. When support isn't billed visit-by-visit, there's room to actually track recurring issues and fix the root cause instead of the symptom for the fourth time.
2. Nobody has looked at your backups in longer than you'd like to admit
Break-fix support is reactive by design — you call when something's already broken. Backups are the opposite: they only matter if someone checked on them before the failure. I still see businesses running on drives whose backup status nobody has actually verified in a year or more, because no one's job includes checking.
That's not a knock on the business owner. It's just not something break-fix support is set up to catch. It takes someone with an ongoing view of your systems to notice.
3. Downtime is now expensive enough to plan around
Early on, an afternoon without email or a day without the point-of-sale system is annoying but survivable. At some point, that same downtime starts costing real money — missed appointments, delayed jobs, frustrated customers, staff standing around. When downtime has a real dollar cost attached to it, waiting in a queue for the next available appointment slot stops making sense.
4. You're buying technology decisions on your own
New computer, new router, new software subscription, a vendor's sales pitch for something you don't fully understand — when there's no one you already trust to ask "does this actually make sense for us," those decisions get made based on whatever the salesperson said or whatever seemed easiest that day. I've walked into more than one business running software they didn't need, or missing something basic they did need, because nobody was in a position to just ask.
5. You have more than a handful of devices or people relying on the same systems
One computer and one employee, break-fix is manageable. Five computers, a shared network, a couple of cloud accounts, and a small team who all depend on the same things working — that's a different level of complexity. More moving parts means more that can go wrong, and more coordination needed when it does. At that scale, having someone who already knows your setup saves real time every time something comes up.
6. You've started keeping a mental list of "small things" you haven't gotten around to
Slow logins, a printer that needs restarting twice a week, an account that should've been deactivated when someone left, a network closet nobody wants to open. None of these are emergencies, so none of them get a call. They just accumulate. An ongoing support relationship gives those small things somewhere to go instead of nowhere.
7. You're the default IT person, and you didn't sign up for that
This is the most common one. Somebody in the business — often the owner — has become the person everyone asks when something's wrong, not because they wanted the job, but because there wasn't a clear alternative. If that's costing you time you'd rather spend running the business, that's a real cost even if it never shows up on an invoice.
Why I don't publish a price list for this
Ongoing support gets shaped around what a business actually has and needs — number of devices, number of people, how critical uptime is, whether there's a network to maintain, whether backups need active monitoring. A flat number on a webpage would either overcharge a simple setup or undercharge a complex one. I'd rather have a short conversation about your actual environment and give you a number that reflects it, instead of publishing a price that's wrong for almost everyone who reads it.
What this doesn't mean
None of this means break-fix is a bad way to run things. If you've got one or two computers, low complexity, and downtime that's a genuine inconvenience rather than a real cost, staying on break-fix support is a completely reasonable decision. The point isn't that everyone needs an ongoing arrangement — it's that a specific set of signs tends to show up right around when a business has outgrown it, and it's worth noticing them instead of just absorbing the cost quietly.
If a few of these sound familiar
You don't need to hit all seven. Two or three is usually enough to make the conversation worth having. Take a look at Business IT Support for what an ongoing relationship actually covers, or just contact us and describe what's been going on — I'll tell you honestly whether break-fix is still working for you or whether it's time for something different.