Can one person handle IT for our whole office?
For most Dallas offices under about fifty people, yes, in the sense that matters: you deal with me directly. I am Anthony Omini, owner of Cross River Tech, and I am the person you call, who plans the work and comes onsite. Behind me, a small team handles routine monitoring, updates and day-to-day requests, so you do not depend on me alone. The real limits are a staffed overnight desk and large same-weekend rollouts, and I will say when a larger provider fits better.
Answered by Anthony Omini, Cross River Tech, Dallas
Key takeaways
- You deal with me directly, and you do not depend on me alone: my team handles routine monitoring, updates and day-to-day requests behind me while I stay your point of contact.
- A small owner-led company with monitoring, remote tools and documentation covers a Dallas office of roughly three to fifty people well.
- The genuine limits are a staffed 24-hour desk, rollouts that need a crew in a single weekend, and deep specialists on standby; I say so rather than blur them.
- Vacations are announced in advance, monitoring and routine support keep running, I stay reachable for decisions, and planned onsite work is scheduled around it.
- Above about fifty people, several locations, or a contract requiring a named overnight desk, a larger MSP is the better answer and I will say so.
Can one person handle IT for our whole office?
For most offices under roughly fifty people, yes, and the reason is not heroics. It is that the volume of genuinely urgent work in a professional office is much smaller than it feels, and almost all of the rest is either automated or scheduled. Patching runs on a schedule. Monitoring watches drives, backups and firewalls and tells my team and me before anyone in your office notices. Remote tools mean most problems are fixed from wherever we are rather than after a drive across the metroplex. What is left, the calls where a human has to think, is a handful of hours in a normal week for a twenty-person office.
I am Anthony Omini, the owner of Cross River Tech, a small managed IT company in Dallas. You deal with me: I answer the phone, I plan the work and I come onsite. My team handles the routine monitoring, updates and day-to-day requests behind me, and there is no dispatcher, no account manager and no ticket queue between you and me. That is the product, not a compromise: when I have looked after your office for a year, I know which laptop belongs to the bookkeeper, which vendor runs your practice software and which firewall rule changed last spring. You never explain your setup twice, and you never get a fix that ignores something the previous technician did, because the work is planned and documented by the same person every time. My background is over fifteen years in IT across many industries and global organizations, with MCSA and CCNA listed on my LinkedIn.
The fair question is not whether one owner can do the work. It is what happens on the days when the owner is not enough. The honest answer is that you deal with me directly, but you do not depend on me alone, and that deserves a straight explanation rather than a slogan. The rest of this is about the limits, the coverage and the point where you should hire someone bigger. Everything I offer is month-to-month managed IT, so if the honest version does not suit you, nothing traps you.
What can one person with the right tools genuinely cover?
More than most owners expect, because the tooling does the repetitive part and my team does the routine part. Here is what is realistically inside the capacity of a small owner-led provider for a small professional office.
- Daily support. Password problems, email, printing, a computer behaving strangely, software that stopped working, a new phone that will not connect. Nearly all of it remote, most of it in minutes.
- The invisible half. Operating system and application updates, endpoint protection, email security, license clean-up, monitoring alerts and backup verification. This is the work nobody calls about, it is the work my team does behind me, and it is the work that prevents the calls.
- Backups and recovery. Configuring backups for devices and for cloud data, watching that they complete, and running restore tests instead of assuming.
- Network and infrastructure. Firewall, switches, access points, printers and the internet circuit, including dealing with the provider when the circuit is the problem.
- Microsoft 365 and Google Workspace. Accounts, licensing, multi-factor authentication, security settings, mailbox and file migrations.
- Onboarding and offboarding. A repeatable checklist so a new hire is productive on day one and a departure closes cleanly.
- Projects. Cabling a new suite, an office move over a weekend, replacing a server, standardizing laptops. I plan these myself, and they are phased rather than done all at once.
- Advice. What to buy, what not to buy, what a vendor is really selling you, and what a cyber-insurance form is asking for.
What makes it work is not speed, it is the absence of waste. There is no ticket triage, no handoff between tiers, no reading a stranger's notes. A problem that takes a help desk three exchanges to understand takes me one sentence, because I already know your environment, and my team works from the same documentation I do.
What can one person not do?
Here is what a small company cannot do, and none of it can be solved with better tools.
| Limit | What it means in practice | How I handle it |
|---|---|---|
| Two outages in the same hour | If two offices go down at once, I cannot be onsite at both in the same hour | Triage by impact, tell you honestly where you are in line, and my team works the second one remotely while I am at the first |
| A staffed 24-hour desk | No rotation of people answering overnight, every night, contractually | Remote support is available around the clock at after-hours rates, but from a small company, not a named operations center |
| Large simultaneous rollouts | Fifty laptops swapped in one weekend needs a crew | Phase it over days or weeks, or tell you to hire a crew for that project |
| Deep specialists on standby | Large virtualization clusters, in-house development environments, multi-site failover watched hourly | Say plainly that this is outside my scope and point you to a provider who staffs for it |
There is a fifth honest item that belongs here even though it is uncomfortable: a small company has less internal redundancy than a large one. A big managed service provider barely notices when a technician leaves. At Cross River Tech, the owner is also the person who knows your office best. The answer to that is not a promise, it is documentation good enough for my team to work from every day and, if it ever came to it, for a stranger to pick up. I cover exactly what that means further down.
What happens if our IT guy is unavailable?
Three situations get confused with each other, so I will separate them.
Busy. This is the common one and it is not really unavailability. I am onsite in Richardson and your office in Deep Ellum loses email. Routine requests are already with my team, so they do not wait on me. For the outage, I step out of the visit, connect remotely from my laptop and start working your problem, usually without leaving the other client stranded. If your issue needs hands on equipment, I finish what genuinely cannot be left, then drive to you. You always know which of those is happening.
Away. When I take time off, you hear about it in advance, not after you call. Support keeps running: my team covers monitoring, updates and day-to-day requests, and I stay reachable for decisions, because a laptop and an internet connection travel. What changes is planned onsite work, which is scheduled around that period unless it is an emergency, and anything that needs my judgement takes longer than it would on a normal working day. That is a real difference and I would rather you plan around it than be surprised by it.
Ill. This is the one nobody likes to talk about. If I am sick for a day, routine work continues with my team, urgent remote work still usually happens, and everything that needs me personally moves. If I were out for a longer stretch, you would hear from me directly with an honest picture, my team would keep the day-to-day running from the same documentation I use, and that documentation is what would let another competent technician step into your environment quickly if it ever came to that. What I will not do is describe a small company as if it were a staffed operations center; a business that needs one should hire a provider that has one. I explain the same distinction about overnight coverage in what 24/7 IT support really means for a small business.
How are overlapping calls actually prioritized?
By impact, and the rule is simple enough to say out loud on the phone. When you reach me I ask two questions: how many people are affected, and can they work around it.
- A whole office cannot work. Internet down, server down, email down for everyone, a suspected security incident. This reshuffles the day, including cancelling non-urgent onsite visits.
- A person or function is stopped. One user locked out before a client meeting, the front desk cannot print check-in forms, one machine will not boot. Worked immediately if nothing above it is active.
- Degraded but working. Slow computer, flaky second monitor, an application that crashes occasionally. Scheduled, usually the same week.
- Projects and improvements. New hardware, migrations, cabling, documentation. Booked in advance and protected from interruption unless something in category one happens.
Two category-one events at the same time is the honest worst case. When it happens, I tell both offices the truth: which one I am on, why, and what my team and I are doing for the other in parallel, which is usually remote work while the first is running a restore or waiting on an internet provider. What I do not do is leave you guessing, and I do not claim to be somewhere I am not. A security incident always outranks an outage, because the cost grows with every minute.
Is a one-man IT company enough for my business?
Answer these and the decision usually makes itself.
- How many people, and how fast is that changing? Roughly three to fifty in one or two locations fits well. Sixty and climbing does not.
- Is your environment mostly cloud, or heavily on-premise? Microsoft 365 or Google Workspace with managed laptops is straightforward for a small provider. Several servers, complex virtualization and a private data path between sites is not.
- Does a contract or regulator require a named 24-hour staffed desk? If yes, that decides it, regardless of how well the rest fits.
- How much simultaneous project work is coming? One office build-out is fine. Three locations opening in the same quarter is not.
- What matters more, a named owner who knows your office or a large bench? Both are legitimate answers, and honest people choose differently.
If most of your answers point toward a small owner-led provider, the practical test costs you very little: month-to-month billing, no long-term term, and documentation you own from the first month. If it is not working, you leave with your keys. That is a fairer trial than any sales pitch. The longer side-by-side comparison of the two models is in an owner-led IT company vs a big MSP.
When is a larger MSP genuinely the better choice?
I turn down work that does not fit, and these are the cases where I tell a Dallas business owner to call someone bigger.
You are past about fifty employees, or spread across several cities. The daily volume of small requests alone outgrows a small company, and onsite coverage in multiple metros is not something I can offer honestly.
Your industry contract or insurer requires a staffed operations center with named escalation tiers and formal response commitments in writing. I offer round-the-clock remote support from a small owner-led company. Those are not the same thing and I will not blur them.
You run infrastructure that needs specialists on standby. Large virtualization estates, in-house software development, or systems that must be attended every hour of the night.
Your risk tolerance is low and your board asks about continuity. Some organizations should not depend on a small company, and saying so does not hurt my feelings.
You want a vendor rather than a person. A legal department, a formal service-level document and a sales representative are a legitimate preference. A small owner-led company is not that.
For everyone else, which is most law firms, dental and medical practices, insurance agencies, design studios and professional offices around Dallas, the owner-led model gives better attention at a lower cost. If you are also weighing an in-house hire, that trade-off is in hire an internal IT person or use an MSP?
How do you protect your business from depending on one person?
By owning everything, and by insisting that the documentation is good enough for a stranger to use. This is the part that actually answers the continuity worry, and you should demand it from any provider, large or small. It is also what lets my own team work behind me without you noticing a difference.
From the first month I keep a written record of your environment: every device with serial number and warranty date, every account and license, the network diagram, firewall and Wi-Fi configuration, internet and phone account details, vendor contacts for your line-of-business software, and where backups go with the steps to restore them. Passwords live in a password manager that your business owns, not in my private vault. Your Microsoft 365 or Google tenant is registered to your business, with your own break-glass administrator account that I do not control.
The test is simple: if I disappeared tomorrow, could a competent technician you found on Monday take over your environment on Tuesday? With that documentation, yes, and in the meantime my team is already working from the same record. Without it, no provider is safe, including a large one, which is exactly how businesses end up held hostage by whoever set their systems up. The full ownership checklist is in who owns your passwords, domain and equipment, and what a provider should and should not ask for is in what access an IT company needs.
If you want the honest version applied to your own office rather than in general, get in touch or call (214) 612-7080. I will tell you on the first call whether I am the right fit, and if a bigger provider suits you better, you will have lost nothing but a conversation.
Questions people ask
Do you have any backup technicians?
Cross River Tech is a small, owner-led company. I am the person you deal with, and behind me a small team handles routine monitoring, updates and day-to-day requests, so support does not stop when I am onsite or away. What I will not claim is a staffed overnight desk or a deep bench of specialists. Alongside the team there is complete written documentation of your environment, passwords in a manager your business owns, and administrator accounts registered to you, so another competent technician could take over quickly if that were ever necessary.
What happens when you are on vacation?
You know in advance. Support keeps running: my team covers monitoring, updates and day-to-day requests, and I stay reachable for decisions and anything that cannot wait. Planned onsite visits are scheduled around that period except for emergencies, and anything that needs my judgement takes longer than on a normal working day. It is a real limitation, stated plainly so you can plan for it.
What if two clients have an emergency at the same time?
I triage by impact and tell both of you the truth. A whole office down or a suspected security incident outranks a single user, and a security incident outranks an outage. While I am working the first, my team and I make progress on the second remotely, particularly during the waiting parts of a restore or a call with an internet provider. You will always know where you stand rather than wondering.
Is one person enough for a fifty-person company?
Around fifty in one or two locations is the honest upper edge for a small owner-led company, and only if the environment is mostly cloud-based and there is no requirement for a staffed overnight desk. Past that, daily request volume and onsite geography outgrow a small provider. A business heading toward that size should plan the change deliberately rather than discover it during a difficult month.
How is a one-person company different from a freelancer with a day job?
Cross River Tech is a registered Dallas business and this is my only work, not evening moonlighting. That means business-grade tooling for monitoring, patching and remote access, a small team behind me for the routine work, written documentation for every client, proper invoicing, and availability during the hours you are open. The comparison of the three models, moonlighter, small owner-led company and multi-technician MSP, is worth making before you hire anyone.
What if I outgrow you?
I say so, and I help you leave properly. Because your documentation, passwords, tenant and equipment configurations already belong to you, moving to a larger provider is a handover rather than a rescue. I would rather hand over an environment I am proud of than hold on to a client I can no longer serve well, and month-to-month billing means you are never waiting for a term to end.
