Why Generic Service Exists: 25 Years to Independence

Generic Service wasn't a planned exit. I didn't write a business plan or save up runway. The company I'd worked at for six years collapsed, and I was standing in the rubble with 25 years of infrastructure stabilization experience and a clear picture of what the work should look like.

The Arc

I started in the late '90s building IT infrastructure for a family medical practice that would grow into one of Arizona's largest OB/GYN organizations. Ten years as the sole IT leader. Twenty-one sites, 80 clinicians, 250+ employees. Paper charts to VMware datacenter. No external consultants.

After that, a short stint at an MSP doing VMware vCloud Director, NSX, and Cisco UCS at scale. Then six years as Senior Cloud Architect at a cloud service provider: VMware/Azure hybrid, Veeam immutable backups, VDI overhauls, and serving as the senior escalation point for downstream MSPs.

I was the CEO's primary technical advisor. I evaluated emerging technologies before the company committed resources. I mentored junior engineers. I delivered the projects that other teams couldn't.

Then the company was sold to a finance guy who had never run a technology operation. Within months, it was over. No one works there anymore.

What I Learned

From healthcare: Infrastructure decisions have consequences that land on real people. When the network goes down at a medical practice, patients don't get seen. That's not a KPI problem. That's a 25-year-old woman in her third trimester sitting in a waiting room wondering why nobody can pull up her chart. HIPAA isn't a checkbox. It's the minimum standard for handling information that belongs to someone who trusted you with it.

From the MSP world: I saw how managed service providers actually operate, from the inside. What gets tracked. What gets skipped. The gap between what's in the contract and what's delivered is often wider than either party realizes. Most clients don't have the technical depth to audit their own provider, and most providers aren't incentivized to make that easy.

From the cloud service provider: Complex environments need someone who can hold the whole picture. I was the senior escalation point because I understood how the pieces connected. Hybrid environments, multi-tenant isolation, backup architecture, identity boundaries. When something breaks at scale, the person who fixes it isn't the one who knows one tool deeply. It's the one who knows where the tool meets the next tool.

Why Independent

I take projects that interest me. Interconnected problems. Root solutions that cascade outward. Environments with moving parts and unique topologies.

The site exists so that when someone searches my name, they find someone they can trust with their infrastructure.

Seven services cover the stability lifecycle. Fixed-scope projects. Everything goes back to your team with documentation they can actually use.

If the project is interesting and the fit is right, we start. If not, I'll tell you.