At what size should a business hire an IT company?
There is no headcount that triggers it. Most Dallas businesses hire an IT company when one of five things happens: a staff member is quietly doing IT instead of their job, a client or insurer starts asking security questions, a server or shared files appear, an office move or build-out is coming, or something breaks badly. Size matters less than what you now depend on.
Answered by Anthony Omini, Cross River Tech, Dallas
Key takeaways
- No employee number triggers this; five specific events do, and any one of them is enough on its own.
- The most expensive trigger is the accidental IT person: a capable employee doing IT badly, slowly, and instead of the job you hired them for.
- Around ten people, informal arrangements usually stop working, because onboarding, offboarding and shared logins start producing real problems.
- A Dallas startup can wait, but not on domain and email ownership, identity, and multi-factor authentication, which are cheap now and painful later.
- You can hire help in small amounts first: hourly at published rates, then a month-to-month plan once maintenance is the bigger cost.
At what size should a business hire an IT company?
There is no size. I know that is not the answer people want, but every attempt to name a number falls apart in practice. I have seen five-person offices that badly needed a provider and twenty-person offices that genuinely did not. What actually decides it is dependency: how much of your revenue stops if a system stops, and how much of what you hold would hurt you if it leaked.
If you want a rough shape rather than a rule, here it is. Under about five people, with cloud email and nothing shared, informal help is usually fine. Between five and fifteen, most businesses cross at least one of the triggers below, and the ones that have not crossed one are usually about to. Past about twenty, almost every office needs someone accountable, because the number of accounts, devices and small decisions has outgrown anybody's memory.
But headcount is a proxy, and a poor one. The five triggers in the next section are the real thing. If one of them applies, hire someone, whatever your headcount says. If none applies, you can wait, whatever a salesperson says. I run managed IT and hourly support for Dallas businesses, and I would rather tell you to wait than sell you a plan you cannot use.
What are the five triggers that actually mean it is time?
Any single one of these is enough. Most businesses that call me have two or three at once and have had them for a while.
- Somebody on staff has become the IT person by accident. Usually the office manager, the operations lead, or whoever was good with computers on their first week. This is the most expensive trigger, and it is covered in detail below.
- Someone outside is asking security questions. A cyber-insurance renewal questionnaire, a client vendor form, a lender, or in regulated work a compliance obligation. These ask for evidence of ongoing controls, and evidence takes someone whose job it is.
- Something has to be maintained. A server, a firewall, a shared file store, line-of-business software, a backup that matters. Shared systems fail silently. Nobody notices a backup stopped until the day it is needed.
- You are moving, building out or opening a second location. Cabling, internet lead times, the IT room and the cutover all have to be sequenced, and the mistakes are physical and expensive to reverse. This is the trigger with the hardest deadline.
- Something already went wrong. Email compromise, ransomware, a dead server, a laptop that walked out with a departing employee. Post-incident is a common time to hire, and the worst time to shop, so treat a near miss as the trigger rather than waiting for the real one.
What is deliberately not on that list: employee count, revenue, having an office rather than remote staff, or how many computers you own. Those correlate with the triggers, but they do not cause them.
How many employees before you need IT support?
Ten is where informal arrangements usually break, in my experience, not because ten computers are hard to manage, but because ten people generate turnover, and turnover exposes everything you never set up properly. Here is what tends to change as an office grows:
| Size | What usually works | What starts breaking |
|---|---|---|
| 1 to 4 people | Cloud email, consumer-grade router, hourly help when needed | Nothing yet, unless the data is sensitive |
| 5 to 9 people | Hourly help plus a deliberate maintenance visit each quarter | Shared logins, no offboarding, backups nobody checks |
| 10 to 24 people | A managed plan, business firewall, proper Wi-Fi, real onboarding | Consumer Wi-Fi, ad-hoc setup, undocumented everything |
| 25 to 50 people | Managed plan with documentation, standards and a device refresh cycle | One-off decisions, no standard build, license sprawl |
The middle row is where most of my Dallas clients are when they first call. If you are sitting at ten people, the concrete build I would put in is written out in what IT support a 10-person office in Dallas needs, and what changes on the way past twenty-five is in what changes when a Dallas office grows past 25 people.
What does the accidental IT person really cost you?
More than a provider, almost always, and the cost is hidden in three places at once.
The first is their real salary. Take whoever is doing it. Work out their hourly cost to the business from their salary. Now count the hours a month they spend on computer problems, and be generous, because they are not counting: the printer, the new laptop setup, the password resets, the afternoon lost to the Wi-Fi. Multiply. In most ten-person offices this lands somewhere between a few hundred and well over a thousand dollars a month of salaried time, spent by someone hired to do something else entirely.
The second is the speed difference. A capable non-specialist takes three or four times longer than someone who has done it a hundred times, and often does not finish. That multiplier means the salary number above understates the cost of the same work done properly.
The third is what they cannot do. This is the real one. The accidental IT person fixes what is visible and never touches what is not, because they do not know it exists. Patching across every machine, verified. A test restore from the backup. Admin rights reviewed. Licences reconciled. Firewall firmware. Documentation. None of that gets done, so the risk accumulates quietly while the visible problems get solved.
There is a fourth cost that is not financial. Being the accidental IT person is a miserable job. It is interruption-driven, thankless, and the person is blamed for outages they did not cause and cannot prevent. Handing it to someone else is often the retention decision, not the technology decision.
When should a startup in Dallas get an IT provider?
Later than most vendors will tell you, but earlier than nothing. A Dallas startup with three founders working from laptops in a coworking space does not need a managed plan. What it needs is about two hours of a professional's attention on the decisions that are cheap now and expensive to reverse.
The list is short:
- Own the domain yourself. Registered to the company, in an account the founders control, not in a developer's personal account or an agency's.
- Own the Microsoft 365 or Google Workspace tenant. Whoever sets it up should not be the only global admin. This is the single most common mess I get called in to untangle.
- Multi-factor authentication on everything from day one. It is far easier to start with it than to roll it out to thirty people later.
- Pick a device standard. One business-class laptop model, bought with a business warranty. Mixed consumer machines cost more to support forever.
- Write down who owns what. Domain registrar, tenant, licenses, bank of accounts. A page in a shared drive is enough at this stage.
That is an hourly engagement, not a plan, and I will happily do it at my published hourly rate and then leave you alone until you need me. A startup should hire a provider properly at the point where it hires its first non-founder employees, signs its first enterprise client with a security questionnaire, or takes an office. The onboarding routine you will need on that first day is in the IT onboarding checklist for your first employees.
What if you are not ready for a monthly plan?
Then do not buy one. There is a middle option that suits businesses sitting between "nothing" and "managed", and I use it with plenty of small Dallas offices.
Buy hourly help at published rates when things break, and separately buy a deliberate block of time once a quarter for the maintenance nobody calls about. In that block: apply and verify updates on every machine, run a real restore from the backup rather than looking at a green tick, review who has admin rights, close accounts for anyone who left, check licenses against actual people, update the firewall firmware and look at its rules. Half a day, four times a year, at a known cost.
It is genuinely weaker than continuous management, because nothing is caught between visits and there is no monitoring. But it covers most of the accumulated risk, it is predictable, and it does not commit you to anything. When the calls start coming monthly, the arithmetic will tell you to move, and the on-call versus managed comparison has the worksheet for that. If you would rather stay off a plan permanently, IT support without a contract in Dallas covers how that works.
What should you have ready before you call anyone?
Four things, and none of them are technical. Having them turns a vague first conversation into a real quote.
- Headcount, and how it will look a year from now. Including part-timers and contractors who use company email.
- A rough device count. Laptops, desktops, servers, printers, phones. Rough is fine.
- The software the business cannot run without. The practice management system, the case management system, the agency system, the design suite, the accounting package. Name them.
- What has gone wrong lately, and who fixed it. This tells a provider more than any inventory.
Anyone competent will ask for those anyway. What they should not ask for on a first call is a password, and if they do, that alone tells you enough. I set out how the first conversation actually goes, including what I never ask for, in what happens at the first meeting with an IT provider.
Where should you go from here?
Count your triggers first. If none of the five applies, do the startup list above and get on with running the business. If one applies, you do not need a full plan yet; you need a few hours of someone competent, aimed at that specific trigger. If two or three apply, you are already paying for a provider, just in salaried time and accumulated risk instead of an invoice.
When you are ready, I am in Dallas and you deal with me directly: I plan the work and stay your contact, my team handles the routine monitoring and updates behind me, remote-first because it is faster and cheaper for you, onsite across the metroplex by appointment. Hourly is $100 remote and $150 onsite in business hours, $150 and $225 after hours, with a one-hour minimum; managed IT is quoted per user or per device, month to month, cancel any time. Everything I publish is on the pricing page.
Tell me your headcount and which triggers you recognize and I will tell you honestly whether it is time, including the case where the answer is not yet.
Questions people ask
At what size should a business hire an IT company?
There is no size that triggers it. Dependency does. Under about five people with cloud email and nothing shared, informal help is usually fine. Between five and fifteen most businesses cross at least one real trigger, and past twenty almost all of them need someone accountable. The five triggers, such as a staff member doing IT by accident or an insurer asking security questions, matter far more than headcount.
How many employees before you need IT support?
Ten is where informal arrangements usually break, though not because ten computers are hard to manage. Ten people generate joiners and leavers, and turnover exposes everything that was never set up properly: shared logins, no offboarding, accounts nobody closed, backups nobody checked. Smaller offices holding sensitive records, such as legal, dental or insurance practices, need support well before they reach ten.
When should a startup in Dallas get an IT provider?
Get a couple of hours of professional attention immediately, and a full provider later. The immediate list is short: own the domain in a company account, own the Microsoft 365 or Google Workspace tenant with more than one admin, turn on multi-factor authentication, pick one business laptop standard, and write down who owns what. Hire properly when you take an office, hire non-founder staff, or face a client security review.
What does it cost to let an employee handle IT?
More than a provider, usually. Take their hourly cost to the business, multiply by the hours a month they lose to computer problems, then multiply again because a capable non-specialist takes several times longer than someone who does this daily. Then add what they never do at all: patching, tested restores, admin reviews and documentation. That last part is where the real risk accumulates, invisibly.
Can I hire IT help without committing to a monthly plan?
Yes. Pay hourly when things break, and separately buy a deliberate block of time once a quarter for maintenance: updates applied and verified, a real test restore, admin rights reviewed, leavers closed out, licenses reconciled, firewall firmware updated. Half a day, four times a year, at a known cost. It is weaker than continuous management because nothing is caught in between, but it is predictable and commits you to nothing.
What should I have ready before calling an IT company?
Four non-technical things: your headcount today and roughly a year out, an approximate count of laptops, desktops, servers, printers and phones, the names of the software the business cannot operate without, and a short account of what has gone wrong lately and who fixed it. That is enough for a real quote. No competent provider will ask you for a password on a first call.
