A Precision Manufacturer, Wired Like a House

The situation walking in

A shop whose reputation is exact parts on exact dates, standing on technology chosen by accident. Email lived on one computer and nowhere else. The network ran on home-grade gear, daisy-chained port to port as needs came up. Speed tests looked fine, but under real working load traffic was quietly getting lost. And the system that runs orders and inventory sat on an aging machine in the building, with everything about it living in one person's head.

What we did

Core · Foundation first

Email, calendars, and files moved onto managed cloud accounts first, because there was nothing worth protecting yet. Then the locks: a second step on every sign-in, threats screened before they load, every computer watched around the clock. It has caught real incidents since.

System · Proven, then built

Proved the network problem instead of asserting it: a load test in their own building, results in plain English, and leadership approved the rebuild as a planned budget item on their timeline. Business-grade equipment, a clean line to every desk, the daisy chains gone.

Logic · Keep what works

Kept the decades-old core system and the person who knows it, and moved it off the aging machine into managed hosting, with him leading the kickoff. The migration to a modern system is now underway on their timeline. The standing rule now: nothing gets built that only lives in one person's head.

Month one, as it ran

D+1 · The walkthrough. Two days under one roof: front office, warehouse, and the wiring closet nobody opened. The notes from that walkthrough became the working document; nothing observed went unrecorded.

D+9 · The verdicts. Every line of the inventory got one of four verdicts: keep, fix, kill, defer. Email couldn't wait. The core system could. The daisy chains made the kill list without debate.

D+14 · The map. One page. What connects to what, who owns it, what it costs, what happens if it fails. The first time anyone had seen the whole operation at once.

D+30 · The seat. The plan moved to a standing rhythm: the urgent work underway, the network rebuild scheduled like any other capital decision, and one number to call instead of guessing who to ask.

Asked at the start

"What happens to the person who's handled this for years?"
Nothing to apologize for. We worked alongside him. He pulled us into vendor calls, we carried the layers no one person can, and when the core system moved to managed hosting, he led the kickoff. The transition ran at the pace of trust rather than the pace of a contract.

"What is this going to cost us, really?"
One flat monthly number for the whole company, no contract, no hourly surprises. Projects get quoted before they start and approved before a dollar moves. They budget technology the way they budget the rest of the operation.

"Do we actually need all this security?"
A fair question from a company that had never been hit. But they ship to major manufacturers, and their customers' security requirements only move in one direction. The protections have flagged real incidents since. The question answered itself.

"What about our core system?"
It's decades old, it runs the business, and they weren't ready to replace it. The truth: we didn't need to rip it out to fix everything around it. It moved to managed hosting on their timeline, it still runs the company every day, and the migration to its modern replacement is underway.