A small shop with a long bench. Owner-operated since 1992, 200-plus DFW businesses, real ownership of the work, not just the tickets.
Most of us cross categories on a given week. The shape of a role shifts with what you're better at and what's coming up next.
Help-desk work: the calls, the tickets, the remote sessions. Your job is to actually fix the issue and write down what you did.
90s median pickup
Field work: server racks, switch swaps, office moves, new-hire desks, the calls that need hands in the room.
35-mi radius across DFW
The deeper stack: firewalls, EDR, M365 tenants, backup design, security posture. The stuff a help-desk ticket can't see.
Stack ownership
We're not for everyone, and that's fine. Here's the honest version.
The fit. You read the dashboard, notice the thing nobody asked about, and either fix it or write the ticket yourself. The win condition isn't closing the queue. It's the network being healthier on Friday than it was Monday.
The fit. You don't close a ticket "user education" when something keeps recurring. You trace it to root cause and write that down. You email the engineer who handed something to you yesterday and ask what they actually did, because the answer is going to matter Tuesday.
The not-fit. If your default is to bounce something off your queue when the cause sits on someone else's machine, this isn't going to be your week. We work the problem, not the boundary.
The not-fit. If you'd rather write a deck about the outage than find out why it happened, you'll be miserable here. We document, but the document follows the fix, not the other way around.
No application portal, no five-stage pipeline. A note, a résumé if you've got one, a short answer to "what are you good at." We read all of them.
Send a note →Or call us at (972) 509-0585 · Mon‑Fri 8:30 a.m. – 5:30 p.m. CT