“We could not justify hiring someone because it was not a full-time position”
That sentence, from Paul Webber, is the cleanest description we have heard of the problem this whole month is about.
Paul is the general manager and chief operating officer of a mid-sized company, and he has been a CMIT client for more than ten years. When we sat down with him earlier this year as part of a research project into why businesses like his go looking for IT support in the first place, he described a situation that will sound familiar to a lot of operations leaders.
There was enough technology work to be a real burden. There was not enough of it to be a real job.
The gap that traps growing businesses
That gap is where a lot of fifteen to forty person organizations get stuck, and it is uncomfortable in a specific way.
Below the gap, the informal arrangement is genuinely fine. Somebody handles it, it takes an hour here and there, nobody minds. Above the gap, the answer is obvious: you hire an IT person, they have plenty to do, everyone moves on.
Inside the gap, neither answer works. Hiring cannot be justified, because you would be paying a full-time salary for a part-time workload and you would struggle to keep that person interested. Doing nothing cannot be justified either, because the workload is real and it is landing on somebody who was hired to do something else. Most businesses sit in that gap for longer than they meant to, because there is no obvious moment that forces the decision. We have written before about what internal IT really costs a business stuck in that spot.
What tends to break the stalemate is not a disaster. It is an accumulation. The interruptions stop feeling occasional. The person absorbing them starts falling behind on their actual work. And at some point a leader looks at the arrangement honestly and decides it is no longer the cheapest option, just the one nobody has questioned.
What Paul was actually shopping for
Here is the part that surprises people who assume IT buying is a technical exercise.
When we asked Paul what he was looking for when he went out to find a provider, he did not describe a technology stack. He said: “my criteria was local, approachable, and knowledgeable.”
Three words, in that order. Local first.
That ordering shows up again and again in this kind of conversation. Operations leaders are not primarily buying tools. They are buying a working relationship with people they can reach, who will show up, and who will not make them feel stupid for asking. The technical competence is assumed. It is table stakes, not the differentiator. What actually gets weighed is whether these are people you want to deal with for the next several years. It is a pattern we see across IT mistakes holding East Austin businesses back regardless of industry.
What changed, in practical terms
The change in an arrangement like Paul’s is less dramatic than people expect, and that is rather the point.
The routine load moves. Monitoring, patching, backups, account setup and removal, the day to day requests that used to interrupt somebody’s afternoon. Those stop being anyone’s side job. The internal person keeps the context and the relationships, and stops being the bottleneck for everything with a plug on it. That shift is usually what managed IT services is actually for, more than any specific tool.
What leaders in this position usually report is not that technology got better in some measurable way. It is that technology stopped being a thing they thought about. It moved from the front of their attention to the back of it. That is a hard outcome to put on a slide, and it is the one they actually wanted. Reliable network management and consistent data backup routines are usually what make that quiet outcome possible, along with the kind of ongoing cybersecurity work nobody notices until it is missing.
The ten year part matters more than the story
Plenty of providers can show you a client who is happy in year one. Year one is easy. Everybody is attentive, the problems are fresh, the relationship is new.
Ten years is a different claim, because ten years means the arrangement survived staff turnover on both sides, at least one major technology shift, several budget cycles where somebody almost certainly asked whether this line item was still necessary, and every ordinary week in between. Paul is not our longest tenured client. That is the part we would like you to sit with.
Do not take our word for any of this
This is the most useful thing we can tell you, and it is slightly against our own interest to put it this plainly.
A blog post about a happy client was written by us. It is selected by us. You should weigh it accordingly, and the research we did this year confirmed what we suspected: businesses in this position do not decide based on a provider’s content. They decide based on people they already trust, and on reference calls with clients who have no reason to flatter anybody.
Our client reviews page is a starting point, and it is still us choosing what to show you. The better step is to ask for references and actually call them. Ask the uncomfortable questions. What happened the last time something went badly wrong. Whether an invoice ever arrived with something on it they did not expect. Whether they would choose us again knowing what they know now. Some of our IT support IT packages pages also link out to this same IT guidance if you want more context before you call anyone.
Frequently Asked Questions
