Hi, I'm Owen.

Why solo

I spent years on enterprise helpdesks, and the pattern was always the same: the tools and processes were good, but the person answering your call had never seen your setup before and would never see it again. Every ticket started from zero.

Working solo flips that. I know every client's environment because I built or documented it myself. When you call, there's no triage queue and no "let me escalate that": you're already talking to the escalation.

The trade-off is honest scale: I keep my client list small enough that everyone gets real attention. When I'm near capacity, I say so rather than letting service slip.

How I work

• Everything gets documented. Your environment lives in a proper documentation system, not in my head. If I'm hit by a bus, your next IT person inherits a map, not a mystery.
• Boring, proven tools. Monitoring agents, managed endpoint security, encrypted backups that get restore-tested quarterly. Nothing experimental on client machines.
• Straight answers. If something isn't worth fixing, I'll say so. If a cheaper option does the job, that's what I'll recommend, since I don't resell hardware or take vendor commissions.
• You own everything. Accounts, licences, and domains stay in your name. Leaving me should be easy; that's what keeps me sharp.

Security, practised not preached

I hold client credentials in a dedicated password manager with two-factor authentication on every account, work from encrypted devices, and follow a written internal security policy covering credential handling, client data, and incident response. If your insurer or a customer's due-diligence questionnaire asks how your IT provider handles access, I can answer in writing.