Worried a Tech Problem Could Put Your Clients' Confidential Files at Risk?

Nearly thirty years ago, I was the person people found in a college computer lab when something had to work and no one else knew how to fix it.

Not because it was my career plan. But when someone couldn't get their work to print at 9pm the night before finals, I was the one who could figure it out. Why? Because I liked figuring things out.

Here's what I didn't know then: I was actually studying criminal justice. I wanted to be an attorney. But nobody in my life told me that I should have majored in Political Science until it was too late. So, I went to where the paying work was — IT. But the fascination with the law never left. To this day, I'll drop everything for a good legal procedural. What draws me in is the same thing that draws me to I.T. and security work: watching someone build a case piece by piece, until nothing is left to guesswork.

For nearly three decades, I kept ending up as the go-to person. Different companies, different industries, different job titles. Same story: someone would show me a broken process, and I'd fix it — usually with tools we already had, in ways nobody had thought to try. Along the way I became an Information Security Analyst at a national organization, working in the discipline that matters most when the stakes are highest.

I started The Halo Technology Group because I got tired of watching tickets die in queues, weeks past the SLA due date. Support requests that everyone forgot about. The client who really needed help, getting lost and buried in the ticketing queue. I knew technology could be better than that. I knew the person on the other end deserved better than that.

So because of my unique background, I built HTG for solo and small-firm attorneys 50 and over specifically because your work sits at the exact intersection of everything that fascinates me — the discipline of building a case, the weight of client confidentiality, the reality that a single technology failure can undo years of trust with a client. That's not an abstract problem to me. It's the kind of problem I've spent my whole career learning to solve.

When you work with me, you're not calling a help desk. You're calling the person who's going to answer the phone, take your problem seriously, and treat your practice like it's worth something. Because it is.

That's why I do this work.