A Desktop Under a Desk Was Their Whole Server

What we found on day one

We came in, took one look, and realized what we were actually dealing with. Their order system was running on a seven-year-old desktop acting as a "server" under someone's desk. No backups - zero. If that machine died, they'd lose everything. WiFi coverage was patchy enough that half the warehouse had to walk over to the front office just to print. One workstation had been infected with malware for two months, and nobody had noticed.

What "pretty good with computers" actually covers

None of this was anyone's fault in a dramatic sense. It's what happens when a business grows past the point where one internally-designated tech-savvy person can keep up, and nobody ever officially took ownership of the environment. Things get patched together as problems come up, and eventually the patches become the system.

The first two weeks

We set up a real server with redundancy and backups. Deployed endpoint protection across every device. Cleaned up the network and fixed the WiFi dead zones. Sat down with their team, one by one, to fix the nagging computer issues they'd assumed they just had to live with. Built a basic IT playbook - who to call, what's covered, and how to get support without guesswork.

Why this pattern shows up so often

This is one of the more extreme versions of a pattern we see constantly in new-client onboarding: a business that outgrew its ad hoc IT setup years before anyone noticed, because everything technically still worked - until the day it didn't. The fix isn't usually exotic. It's backups, endpoint protection, a real network, and someone who actually owns the environment.

If your team's been winging it with IT, or putting off getting real support, the earlier that gets looked at, the smaller the cleanup.