The office is down and the IT ticket is two days old: what a small firm actually needs

The morning the front desk cannot log in

It is 8:15 and the scheduling software will not open. The receptionist has rebooted twice. Someone emails the IT company and gets an automatic reply with a ticket number. The office manager calls and reaches a help desk that asks for the ticket number. By ten, the front desk is writing appointments on paper and the owner is wondering what, exactly, the monthly invoice has been paying for.

I am Anthony Omini, owner of Cross River Tech in Dallas. We support offices of one to fifty people, mostly law firms, dental and medical practices, insurance agencies and design firms, and a large share of our clients came to us after a morning like that one. The problem is almost never one broken computer. It is a support model that was designed for someone else's business. This guide is about recognizing that, and about what the alternative looks like.

Why small offices end up with IT that does not fit them

A fifteen-person law firm has the same technology dependencies as a large company, email, documents, a practice management system, a network, phones and printers, but none of the staff to run them. So the owner picks one of three paths. They rely on the most technical employee, who has a real job to do. They call a one-person consultant who is excellent until he is on vacation. Or they sign with a large managed services provider whose help desk is built for hundreds of users and treats a dental office with eight workstations as a low-priority account.

Each path fails in a predictable way. The internal volunteer never gets to patching, backups or security because those are invisible until they are urgent. The solo consultant has no backup and no monitoring, so problems are found by staff rather than by systems. The large provider has monitoring but no familiarity, so every call starts from zero and a problem that takes a local technician twenty minutes takes the queue two days.

Underneath all three is the same gap: nobody owns the office's technology as a whole. Patches are behind. The firewall was configured once. The backup job has been reporting an error for months that nobody reads. Multi-factor authentication was never turned on for email. The network closet is a tangle of unlabeled cables from three previous vendors. None of this causes a problem on an ordinary day, which is exactly why it is still there.

• Updates and patches applied irregularly or not at all
• Backups that run but have never been test-restored
• Email without multi-factor authentication
• A firewall and Wi-Fi set up years ago and never reviewed
• Unlabeled cabling and consumer-grade switches in the closet
• No single person who knows how the office's systems fit together

Six things an office manager can check this week

You do not need to be technical to find the biggest risks. Ask whoever handles IT for the date of the last successful backup and the date anyone last restored a file from it. If the second answer is never, that backup is a hope, not a plan. Ask whether every staff email account requires a second factor to sign in. Ask when the server and the workstations last received updates, and whether anyone is notified when they fail.

Walk to the network closet and look. If the equipment is sitting on the floor, if there are consumer routers daisy-chained together, or if cables run unlabeled into a switch nobody can identify, write that down. Check who has administrator access to your systems and whether former employees or former vendors still appear in the user list. Finally, time your current provider: send a routine, non-urgent request and note how long until a human responds.

Those six answers tell you most of what you need. An office with tested backups, enforced multi-factor authentication, current patches, a tidy and documented network, a clean user list and a responsive provider is in good shape regardless of who runs it. An office missing three or more of those is carrying risk it has not priced.

When the current setup is good enough

If your office passed most of the checks above, and your current provider is responsive and knows your systems, there is no reason to change for the sake of it. A solo consultant who documents, monitors and has a coverage arrangement for absences can serve a small office well. A larger provider whose help desk actually resolves your issues quickly is doing its job.

Change becomes worth the disruption when the checks fail, when the response times are costing you billable hours or patient appointments, when you are about to move or open a new office, or when a compliance requirement in your field now asks for controls your current arrangement cannot document. Those moments are when a conversation with another provider is worth an hour.

How we take over an office's IT, in order

It begins with a short assessment. I look at the workstations, server if there is one, network, Microsoft 365 or Google Workspace, backups, phones and printers, and I ask how the office works: what software cannot go down, who needs access to what, when the busy hours are. From that we produce a written quote for a managed plan priced per user or per device, on month-to-month terms you can cancel at any time. If you prefer not to commit, we also work hourly with no contract, at published rates of $100 an hour for remote work and $150 an hour on site during business hours.

Onboarding fixes the invisible items first. We install monitoring and patch management on every device, verify or rebuild the backup and run a real restore test, turn on multi-factor authentication across email and critical systems, deploy endpoint protection and email security, and document the network. If the closet is a mess, we clean it up; we also run Cat6 cabling and set up racks, patch panels, switches, firewalls and Wi-Fi for new builds, renovations and office moves. We are a Microsoft Cloud Solution Provider and work with Dell, Lenovo and Pax8 for hardware and licensing.

After that, the day-to-day is simple. Staff call or email and reach me or my team; there is no queue to navigate first. Most issues are resolved remotely, and we often start on them immediately. Remote support is available around the clock, every day of the year, with on-site visits across Dallas–Fort Worth by appointment and same-day when needed. Urgent calls during business hours are typically answered or returned within the hour, though we do not sell a written guarantee on that; we would rather earn it monthly.

• Short on-site or remote assessment of every system and how the office uses it
• Written per-user or per-device quote, month to month, cancel anytime
• Monitoring, patching and a tested backup installed first
• Multi-factor authentication, endpoint and email security enabled
• Network documented, labeled and cleaned up, with cabling as needed
• Direct line to the owner, remote fixes started immediately

What managed IT costs, and what moves the number

Managed plans are priced per user or per device each month, and the figure depends on how many people and machines you have, whether there is an on-site server, what security and backup coverage you need, and whether phones and printers are included. For context, a common range cited for the Dallas market is roughly $100 to $175 per user per month, and the right number for your office comes out of the assessment rather than a brochure. Quotes are written and invoices list the work performed, so you can see what you paid for.

Work outside Monday through Friday, 8 to 5 Central, is billed at after-hours rates, which are published on our pricing page. Hardware, licensing and cabling projects are quoted separately. Against those costs, weigh what an outage costs your firm in billable hours or canceled appointments, and what a ransomware incident with an untested backup would cost. Managed IT is cheaper than either, which is the only reason it exists as a service.

Picking a provider for a one-to-fifty-person office

Ask who will actually answer when you call, and whether that person will know your office. Ask how they handle the provider's own absence, vacations and illness, because a solo operator with no plan for that is a single point of failure; our clients are told in advance when I am out and a team covers routine requests. Ask for their certifications and years in the field. Mine are MCSA and CCNA, with more than fifteen years of IT work.

Ask what the contract terms are and how you leave. Ask whether backups are tested and how often you will see proof. Ask about the specific needs of your field: a law firm's confidentiality, a medical practice's regulatory requirements, an agency's carrier portals. And ask them to tell you, after an assessment, what they would fix first. The answer reveals whether they are thinking about your risk or their invoice.

• A named point of contact who knows your systems
• A coverage plan for the provider's absences
• Certifications and verifiable experience
• Month-to-month terms or a clear exit
• Regular evidence of tested backups
• Familiarity with your industry's requirements

The failures I see most often

Treating the backup as done because the software says it ran. Leaving multi-factor authentication off because staff found it inconvenient, then losing an email account to a phishing message. Buying consumer-grade network gear for a professional office. Letting a former employee's account stay active for months. Moving offices and discovering on day one that nobody ordered internet or ran the cabling, which is why office moves are one of our standard services.

The business mistake is subtler: waiting for the outage to decide. The office that calls after the server fails pays for emergency hours, data recovery and lost days. The office that calls before pays a monthly fee and mostly never notices its IT again, which is the entire point.

From your first call to an office that forgets about IT

You call or fill in the short form on our site, and you hear back the same business day. For a single problem, I give you an hourly estimate and we fix it, remotely or on site. For ongoing support, we schedule the assessment, and within a few days you have a written quote and a list of what we would address first, in order of risk.

If you go ahead, onboarding runs over the following days without interrupting the office, and from then on your staff have one number to call. We serve offices across Dallas–Fort Worth on site and support clients remotely across Texas, including Houston, Austin and San Antonio. The outcome we are working toward is an office where the technology is simply not something the owner thinks about.

Questions people ask me