Do I need an IT guy on call or a managed IT plan?
If your Dallas office has fewer than about five people, simple cloud email and no server, an IT guy on call at an hourly rate is usually cheaper. Once you have shared files, a real network, ten or more people, or rules you have to follow, a managed plan wins, because it pays for the patching, backups and account clean-up nobody thinks to call about.
Answered by Anthony Omini, Cross River Tech, Dallas
Key takeaways
- On-call hourly support pays for problems you notice; a managed plan pays for the work nobody notices, which is where most of the real risk sits.
- My published hourly rates are $100 remote and $150 onsite in business hours, $150 remote and $225 onsite after hours, with a one-hour minimum.
- Do the count in two parts: hours you called for last year, plus the hours nobody called for. The second number is the one that decides it.
- Under about five people with cloud email and no shared server, hourly is usually the honest answer, and I will say so.
- Hourly has stopped making sense when calls are monthly, a server or shared files exist, or you cannot say when a backup was last tested.
Do you need an IT guy on call or a managed IT plan?
You need an IT guy on call if your office is small, mostly cloud-based, and the phone only rings for IT a few times a year. You need a managed plan once something in the business has to be looked after between problems: a server, shared files, a network with more than a router, ten or more people, or an obligation to a client, a regulator or a cyber-insurance carrier.
That is the whole distinction, and it has very little to do with how much you like paying invoices. Hourly support is a way to buy fixes. A managed plan is a way to buy maintenance, and fixes come with it. If nothing in your office needs maintaining, you are paying for something you would not use. If plenty needs maintaining and you are on hourly, you are not paying for it, which feels cheaper right up until the month it is extremely expensive.
I sell both, from Dallas, and I do not steer people. My hourly break/fix support has published rates and no agreement. My managed IT plan is quoted per user or per device, month to month. What follows is the arithmetic I use to tell an owner which one will cost them less, so you can run it yourself before you talk to anybody.
What is the actual difference between on-call and managed IT?
On call means you have someone's number and you use it when something breaks. Managed means someone is responsible for your systems continuously, whether or not anything has broken. Here is the difference laid out on the things that matter to a small office:
| Question | IT guy on call (hourly) | Managed IT plan (monthly) |
|---|---|---|
| What triggers work? | You notice something and call | A schedule, an alert, or you call |
| Who applies Windows and application updates? | Nobody, unless you pay for the hours | Included and checked afterwards |
| Who confirms the backup ran? | Nobody | Included, with test restores |
| Who closes a departed employee's accounts? | You remember, or you do not | Part of the offboarding routine |
| Antivirus and email security | Whatever came with the computers | Managed and monitored centrally |
| Cost shape | Nothing in quiet months, a lot in bad ones | The same number every month |
| Documentation of your setup | Usually in somebody's head | Written down and kept current |
| Commitment | None at all | Month to month with me; often a year elsewhere |
Notice that the top half of that table is not about speed or friendliness. It is about who owns the boring work. That is the honest core of the decision. Everything else, including price, follows from it. If you want the day-to-day version of what that boring work looks like, I broke it down in what an IT guy actually does for a small business.
What does each one cost in Dallas?
My hourly rates are published, so I can be exact. Break/fix work, no agreement, billed by the hour with a one-hour minimum:
| When | Remote | Onsite |
|---|---|---|
| Business hours, Monday to Friday, 8 AM to 5 PM Central | $100 per hour | $150 per hour |
| After hours, weekends and holidays | $150 per hour | $225 per hour |
Remote means I connect over the internet and fix it from my desk. It is faster for you and cheaper, and it is how most problems get solved. Onsite means I come to your office in Dallas or elsewhere in the metroplex by appointment, for hardware, cabling, network equipment and anything that needs hands.
Managed IT is different in kind, not just in price. I quote it per user per month or per device per month after a short conversation, because the number depends on whether there is a server, how many devices each person carries and what the business runs on. As a typical market range, small-business managed IT around Dallas is commonly quoted somewhere around $100 to $175 per user per month. That is the market, not my price, and I include it only so the worksheet below has a number to work with. The longer version is in how much managed IT services cost in Dallas.
One more thing to ask any hourly provider before you compare rates: the minimum. A lower hourly rate with a two-hour onsite minimum costs more for a 30-minute fix than a higher rate with a one-hour minimum.
How do you work out your own break-even?
Sit down with last year's invoices and a notepad. This takes about fifteen minutes and it settles the argument better than any sales conversation.
- Count the hours you were billed for last year. Old invoices, or an honest estimate if the help was informal. Include the times your office manager lost a morning to a printer.
- Add the hours nobody called for. These are the ones that decide the outcome. Patching every computer and confirming it took: call it two to three hours a month. Checking backups and doing one real test restore: one to two. Account clean-up, license review, security alerts: one to two. New starter or leaver: one to two each time.
- Price the total at hourly rates. Use my published rates, or anyone's. Remember the one-hour minimum: five ten-minute problems in a month is five hours, not fifty minutes.
- Get a real managed quote for your real headcount. Not a market range, a quote, with the inclusion list in writing.
- Compare, then weigh the risk. If the two numbers are close, the plan is better value, because it also removes the bad-month spike and puts someone else on the hook for the maintenance.
- Check the lock-in. If the plan is month to month, trying it costs you one month. If it runs a year with automatic renewal, be far more careful. I cover that in month-to-month vs annual IT contracts.
For most Dallas offices I look at, step two is where the surprise lives. Owners are usually close to correct on step one and wildly low on step two, because that work is invisible when it is happening and only becomes visible when it has not been happening.
When does hourly IT support stop making sense?
Hourly stops making sense at the point where you start deciding not to call. That is the signal, and it comes before the maths does. Here are the five triggers I actually see:
- You are calling every month. Two or three calls a month at business-hours rates is already in the same territory as a plan, and you are getting none of the maintenance.
- Somebody hesitates before calling. When the clock is running, small problems get lived with. Lived-with problems compound, and the office quietly gets slower.
- There is something that has to be looked after. A server, a firewall, a shared file store, line-of-business software, a backup. These fail silently. Hourly support has no mechanism to notice.
- You cannot answer a basic security question. When was the last successful backup restore? Who still has admin? Is multi-factor authentication on for everyone? If those answers are not to hand, no one is doing the job.
- Somebody outside is asking. A cyber-insurance questionnaire, a client security review, a regulator, or a lender. These ask for evidence of ongoing controls, and evidence is exactly what hourly support does not produce.
None of these is a headcount. I have seen a four-person law office that genuinely needed a plan because of what it held, and a fifteen-person sales floor that was fine on hourly because every single thing it used was a browser tab. If you want the growth-stage version of this question, see at what size a small business should hire an IT company.
Is managed IT worth it for a small office?
For a small office, managed IT is worth it when the plan is buying maintenance you would otherwise skip, and it is not worth it when it is only buying support you rarely use. That sounds obvious, and it still gets decided the wrong way in both directions.
The honest case against a plan for a very small office: if there are four of you, everyone works in Microsoft 365 or Google Workspace, the laptops are new, there is no server, no shared drive, no line-of-business application and no compliance obligation, then a monthly fee is buying availability you will not consume. Pay hourly. Spend an hour a year with someone to turn on multi-factor authentication, check the backup of your cloud data, and write down who owns the domain. That is a defensible IT strategy for that business, and I will tell you so rather than sell you a plan.
The honest case for a plan at the same headcount: four people in a dental practice, a law office or an insurance agency is a different animal entirely, because of what is stored and who is asking about it. So is any office with a server in a closet. So is any office where the "IT person" is the office manager doing it between real work.
The other thing a plan buys, which does not show up on a spreadsheet, is that costs stop being a decision. Nobody weighs whether a problem is worth an hour. People report things early, which is when things are cheap. That behavioural change is a bigger deal in a ten-person office than most of the technical inclusions.
Can you have both, or start with one and switch?
Yes, and it is the most common path I see. Start hourly, see how the work goes and how often your office really needs help, and move to a plan when the arithmetic catches up. Going the other way is fine too, if an office shrinks or moves everything to the cloud.
A useful middle position for offices that are not ready to commit: buy a small block of hourly time once a quarter and spend it deliberately on the maintenance list rather than on incidents. Patch everything, verify a restore, review admin accounts and licenses, check the firewall firmware. It is not as good as continuous management, because nothing gets caught between visits, but it is dramatically better than nothing and it costs a predictable amount. If you would rather stay off a plan permanently, I wrote about that in IT support without a contract in Dallas.
What I would avoid is the arrangement where you have a plan and still pay hourly for most of what happens, because the scope was written narrowly. Read the exclusion list before the inclusion list. What a managed IT services agreement usually includes walks through the clauses worth arguing about.
How do I work this out with you?
Tell me three things and I can usually give you the answer on the first call: how many people, what runs the business day to day, and whether there is a server or shared storage anywhere. From that I can tell whether the maintenance column is big enough to justify a plan.
If it is not, I will quote you hourly and say plainly that a plan would be poor value for you today. That is not modesty, it is that an office paying for something it does not use tends to cancel and tell people it was a waste, and I would rather have the hourly work and your good opinion. If it is, I will quote per user or per device, month to month, with the inclusion list in writing so you can hold it against anyone else's.
Either way you deal with me directly, and my team works from the same documentation, so you never explain your office twice. Get in touch with your headcount and what tends to go wrong, and I will run the comparison with you. If you want to see the raw cost comparison first, hourly vs monthly IT support has the same maths from the price side, and the pricing page lists every rate I publish.
Questions people ask
Do I need an IT guy on call or a managed IT plan?
On call is right for a small, mostly cloud-based office where nothing needs looking after between problems: no server, no shared drive, few people, no compliance pressure. A managed plan is right once something has to be maintained continuously, or once you have around ten people, because the plan covers patching, backups, security and account clean-up that hourly support never gets asked to do.
Is managed IT worth it for a small office?
It is worth it when the plan buys maintenance you would otherwise skip, and poor value when it only buys support you rarely use. Four people working entirely in Microsoft 365 with new laptops and no server can reasonably stay hourly. Four people in a dental, legal or insurance office holding sensitive records usually should not, because of what is stored and who will eventually ask how it is protected.
When does hourly IT support stop making sense?
When you start deciding not to call. Other reliable signals: calls happening every month, a server or shared files that nobody is checking, no clear answer to when a backup was last restored, or an outside party such as a cyber-insurance carrier asking for evidence of ongoing controls. At that point hourly is not cheaper, it is just billing less while leaving more undone.
What do you charge hourly, and what does a managed plan cost?
Hourly is $100 remote and $150 onsite during business hours, Monday to Friday, 8 AM to 5 PM Central, and $150 remote and $225 onsite after hours, weekends and holidays, with a one-hour minimum. Managed IT is quoted per user per month or per device per month after a short conversation. Across the wider Dallas market, managed IT is commonly quoted somewhere around $100 to $175 per user per month.
Can I start hourly and move to a managed plan later?
Yes, and most people do it in that order. Start hourly, watch how often your office actually needs help and how the work goes, then move to a plan when the hours and the unmaintained items add up. My plan is month to month, so trying it costs one month rather than a year. Moving back to hourly later is fine too if the office gets smaller or simpler.
What is the cheapest sensible option for a very small office?
Pay hourly, and once a quarter buy a deliberate block of time for maintenance instead of waiting for incidents: apply updates everywhere, test a real restore, review who has admin rights, check licenses and the firewall. That gives a tiny office most of the protective value of a plan at a predictable cost. It is weaker than continuous management, because nothing is caught in between, but it beats doing nothing.
