PHXTEKS
PHXTEKS is me, Brad Carson.
I'm an infrastructure-focused engineer with 20+ years across manufacturing, laboratory, and multi-site enterprise environments — including current work inside a GMP-regulated pharmaceutical operation where access governance, documentation discipline, and controlled change aren't preferences, they're requirements. PHXTEKS brings that same practice down to a scale that fits small operators, field environments, and places that need systems to hold up without a dedicated IT team.
How I work
The same principles apply whether it's a single workstation or a building's worth of infrastructure. The work isn't done until somebody else can run it.
Build for recovery, not just deployment.
The system isn't finished when it boots. It's finished when someone else can own it from documentation.
Prefer clarity over cleverness.
A boring, defensible design beats a clever one nobody understands six months later.
Keep access intentional and boundaries explicit.
Least-privilege isn't paranoia; it's the cheapest insurance against a bad day.
Document the work so it can be understood and repeated.
The handoff is the deliverable. If it can't be picked up by a successor, it isn't done.
Design systems that stay maintainable as they grow.
The right answer at 5 users should still hold at 50. Most "rebuild from scratch" projects are paying for the absence of this.
Got something that needs to hold up?
Request Engagement →