What IT support does a 25 person office need?
A 25-person Dallas office needs managed accounts in Microsoft 365 or Google Workspace with multi-factor authentication, business-grade firewall and Wi-Fi instead of a consumer router, standardized laptops, backups of both devices and cloud data that someone tests, a written onboarding and offboarding process, and one accountable provider handling all of it. Most offices this size do not need a server. They need the basics done properly and documented.
Answered by Anthony Omini, Cross River Tech, Dallas
Key takeaways
- At 25 people the problem is rarely one broken thing; it is that nothing was ever standardized, documented or tested.
- Fix the foundations first: proper accounts with multi-factor authentication, a business firewall, real Wi-Fi coverage and tested backups.
- Most 25-person Dallas offices belong entirely in the cloud; a server is justified by specific software or huge files, not by headcount.
- Onboarding and offboarding stop being casual favors at this size and need a written, repeatable checklist.
- One accountable provider still fits comfortably at 25 people, and I will tell you honestly when your office has outgrown that.
What IT support does a 25-person office need?
A 25-person office needs six things, and they are less exciting than most people expect. Managed identity: every person with their own named account in Microsoft 365 or Google Workspace, multi-factor authentication turned on everywhere, and no shared logins. Business-grade network equipment: a real firewall, a managed switch and enough access points to cover the whole suite. Standardized computers, bought on purpose rather than one at a time from whichever store had stock. Backups of both the devices and the cloud data, with restores actually tested. A written onboarding and offboarding process. And one accountable provider who owns all of it, with a person you can actually call.
What you probably have instead, if you grew from five people to twenty-five without planning it, is a mixture. Some laptops are managed, some are personal. Two departments share a login for a vendor portal. The router came from the internet provider. Wi-Fi is strong at the front and unusable in the back conference room. Backups exist for the file server but not for email or SharePoint. And the person who knows where everything is bought is the office manager, who never asked for the job.
None of that is a crisis on any given day. That is exactly why it survives to twenty-five people. The work at this size is turning an accumulation of decisions into a system, and doing it in an order that fixes risk first and comfort second. My managed IT service for a Dallas office this size is mostly that: standardize, document, monitor, then keep it boring.
What actually breaks between 20 and 30 people?
Five things fail almost universally in this range, and they fail quietly rather than loudly.
- Consumer Wi-Fi and the ISP router. A single all-in-one box that handled eight people cannot handle twenty-five people with a laptop and a phone each, plus a printer, a couple of tablets and video calls all day. Symptoms are not "the internet is down" but "Teams keeps freezing" and "the back office drops out."
- Shared logins. One password for the bank portal, one for the practice software, one for the shipping account. It felt efficient at six people. At twenty-five it means you cannot tell who did what, you cannot cut off a departing employee's access, and you cannot pass a cyber-insurance questionnaire honestly.
- Ad-hoc onboarding. A new hire's setup depends on who happened to do it. Somebody has full access to the accounting folder because it was easier that afternoon. Nobody ever removes anything.
- No documentation. Nobody can name the internet account number, the firewall password, who registered the domain or where the backup goes. All of it lives in one head, or in a former employee's head.
- Backups nobody checks. A backup that has been failing for months looks identical to a working one until the day you need it. Cloud data in Microsoft 365 or Google Workspace usually is not backed up at all, because people assume the provider does it.
The common thread is that every one of these is invisible until it is expensive. That is what an IT provider is really for at this size: the invisible half of the work. I wrote about the split between the visible and invisible halves in what an IT guy actually does for a small business.
When do we need a server or a better network?
You need a better network almost certainly; you probably do not need a server. Those two questions get asked together and they have opposite answers at this size.
The network is not optional. Twenty-five people means roughly sixty connected devices once you count phones, printers and anything on the wall. That needs a business firewall doing real filtering and remote access, a managed switch with enough ports and power for the access points and phones, and access points placed for the floor plan rather than dropped on a shelf. In a leased Dallas suite it also means enough cabled drops, because Wi-Fi at the back of a build-out with metal studs and glass offices is only as good as the cable feeding the access point above the ceiling tile. If your suite was wired for a previous tenant with a different layout, that is usually where the problem is, and it is the one thing you cannot fix remotely. Cat6 cabling and IT room setup is the fix, and it is a one-time cost.
A server is a different question. Ask it this way: is there software that requires one, or data that is genuinely painful in the cloud? A dental practice with imaging software, a design firm with multi-gigabyte project files, a law office with an on-premise document management system, an accounting practice with hosted tax software that performs better locally: those justify a server or a dedicated line-of-business machine. General office work, email, documents and shared folders do not. A file server bought for twenty-five people doing normal office work usually adds cost, patching, backup complexity and a single point of failure in a closet that gets warm in August.
If you already have a server that has been there for years, the question is not whether to keep it but what it is still doing. Frequently the answer is "hosting a shared drive and an old application nobody has looked at," which is a migration project rather than a hardware purchase.
What should a growing Dallas business add, and in what order?
Order matters more than the list, because budget and patience run out. This is the sequence I use, worst risk first.
| Order | What to fix | Why it comes here |
|---|---|---|
| 1 | Named accounts and multi-factor authentication everywhere | Stops the most common way small businesses actually get hurt: a stolen password reused on email |
| 2 | Backups of devices and cloud data, with a tested restore | The only control that turns a disaster into an inconvenience; untested backups do not count |
| 3 | Business firewall and endpoint protection | Removes the ISP box as your only defense and gives you visibility |
| 4 | Wi-Fi coverage and cabling that matches the floor plan | The daily productivity complaint, and the one everyone notices being fixed |
| 5 | Documentation and an asset inventory | Every future decision gets faster and cheaper; also what protects you if a provider leaves |
| 6 | Written onboarding and offboarding | Turns access control into a process instead of a memory |
| 7 | A device replacement plan | Spreads hardware cost over years instead of surprising you with eight laptops at once |
| 8 | Server, VPN or specialist infrastructure, if the software demands it | Only worth doing after the foundation is solid, or you are automating a mess |
Items one through three can usually be done in a couple of weeks without disrupting anybody. Items four and eight involve scheduled work and possibly evening or weekend hours. Item seven is a budgeting conversation more than a technical one; what a small business should budget for IT each year walks through the numbers.
How do onboarding and offboarding change at this size?
They stop being favors and become a checklist, because at twenty-five people you will hire and lose several people a year and the odds of forgetting something climb fast.
A good day-one process covers the account and license, the device with encryption and endpoint protection installed, multi-factor authentication enrolled on the person's own phone, membership in the right access groups rather than individually granted folder permissions, the phone extension, and a one-page welcome sheet telling them how to get help. Done properly it takes under an hour and the new hire is productive on their first morning instead of their third day.
Offboarding is the same list in reverse and it is the one that matters legally. Disable the account and revoke active sessions first, because changing a password alone leaves a signed-in phone working. Remove multi-factor devices. Convert or forward the mailbox. Collect the laptop, or wipe it remotely if it is not coming back. Reclaim the license so you stop paying for it. Change any shared credential the person knew, which is the argument against shared credentials in the first place.
This is where access groups pay off. If someone's access is defined by which groups they belong to, removing them is one action. If access was granted folder by folder over three years, nobody can be sure it is all gone. When the departure is unfriendly, the difference is significant, and the emergency version of this is covered in an employee left with the company laptop and accounts.
What does IT support cost for an office this size in Dallas?
Managed IT for a small business in the Dallas market is commonly quoted somewhere around $100 to $175 per user per month, which is a market range and not my price. I quote per user or per device after a short conversation about what you actually run, and billing is month-to-month with no long-term contract, so the number has to keep earning itself.
Two things move the figure at twenty-five people. The first is whether you have servers or specialist software that needs vendor coordination. The second is how much cleanup the first quarter needs, which is a project cost rather than a monthly one. An office that has never been standardized has real one-time work in front of it: inventory, account cleanup, firewall replacement, sometimes cabling.
If you prefer to stay hourly, my published break/fix rates are $100 per hour remote and $150 per hour onsite during business hours, and $150 remote or $225 onsite after hours, weekends and holidays, with a one-hour minimum. That is honest but it usually stops making sense somewhere in the teens of headcount, because monthly work like patching and backup checks never gets called in and therefore never gets done. The break-even math is in hourly vs monthly IT support.
Whatever you compare, compare like with like. Two quotes for a growing Dallas business can differ by half simply because one includes backups, license management and after-hours remote work and the other bills all three separately.
Is a small, owner-led IT provider still enough at 25 people?
Yes, comfortably, for most offices in this range, and I will tell you plainly when that stops being true. Twenty-five people in one or two Dallas locations, mostly cloud-based, without a contractual requirement for a staffed overnight desk, is squarely inside what a small, owner-led company with proper tools and monitoring handles well. You deal with me directly: I plan the work, I come onsite, and my team handles the routine monitoring and updates behind me. Nobody has to explain your setup twice, and there is no ticket queue between you and the fix.
The honest limits are those of a small company. When two clients need me onsite in the same hour, I say which building I am driving to first and why, while remote work carries on behind me, rather than pretending otherwise. Rolling out fifty laptops in a single weekend is a scheduled project, not a phone call. A regulator or a large client contract that demands a named 24-hour staffed operations center is a requirement I do not meet. I have written the full version of that in whether a small IT company can handle IT for your whole office
The thing to watch is the direction of travel. If twenty-five is heading for sixty within a year or two, plan the transition deliberately instead of discovering it during a bad month. Growth that fast changes the answer, and pretending otherwise would cost you more than it costs me.
How do I find out where my office actually stands?
Start with a walkthrough. I come to your Dallas office, look at the equipment, ask who has admin rights, check how backups are configured and whether they restore, look at the firewall and the Wi-Fi coverage, and list the software that runs the business. It takes a couple of hours and you get a written summary of what is solid, what is risky and what it would cost to fix, in the order above.
You do not need to prepare much. Roughly how many people and devices, who currently helps with IT, what breaks most often, and any compliance obligation you carry. If you have an inventory or an old network diagram, bring it; if you do not, that is normal and part of the first month's work is producing one.
If you are earlier in the journey and closer to ten people, the shorter version of this build is in what IT support a 10-person office needs. If you are ready to talk about twenty-five, get in touch or call (214) 612-7080 and we can walk through it.
Questions people ask
Does a 25-person office need its own server?
Usually not. Headcount does not justify a server; specific software does. Dental imaging, on-premise document management, multi-gigabyte design files or a line-of-business application that requires local hosting are real reasons. General office work, email and shared documents run better and cheaper in Microsoft 365 or Google Workspace, with no hardware to patch, cool, back up or eventually replace.
How many Wi-Fi access points does an office of this size need?
It depends on the floor plan and construction far more than on headcount. A single open suite may be fine with two well-placed access points, while the same square footage split into glass offices and a hard-walled conference room can need four. The determining factor is usually whether there is cable in the ceiling where the access point should go, which is why coverage problems often turn into a small cabling job.
What is the first thing to fix in a growing Dallas business?
Identity. Named accounts for every person, multi-factor authentication turned on everywhere, and shared logins eliminated. It is the cheapest control available, it addresses the way small businesses most commonly get hurt, and it makes everything after it easier: offboarding, cyber-insurance questionnaires and knowing who did what. Backups with a tested restore come immediately after.
How long does it take to clean up an office that grew without a plan?
The urgent risk items, accounts, multi-factor authentication, backups and endpoint protection, usually take two to three weeks alongside normal support. Documentation and inventory take the first month. Physical work such as a firewall swap, additional cabling or access points is scheduled separately, often on an evening or weekend so nobody loses working time. After roughly a quarter, the environment is standardized and support calls drop noticeably.
Do we need to replace all our computers at once?
No, and you should not. Buying twenty-five machines in one purchase means replacing twenty-five machines in one purchase four or five years later. A replacement plan spreads it: identify age and warranty status for every device, retire the oldest each year, and standardize on one or two business models so parts, images and support are consistent. That turns hardware into a predictable line rather than a shock.
Can you support a Dallas office of this size remotely, or do you come in?
Both. Most day-to-day work is remote because it is faster for you and cheaper than a drive, and remote support is available around the clock with after-hours rates applying outside business hours. Onsite visits happen by appointment across the Dallas–Fort Worth metroplex for anything physical: hardware, cabling, a new hire's desk setup or a scheduled project. Same-day onsite visits are often possible when a whole office is affected.
