Your network needs to stay up. Your data needs to stay safe. Your software needs to work. You need someone you can call who knows what they're doing — and who treats your business like it matters. That's me.
We live in the information age. Power is all around us. Learning to harness that power and make the world better is what I've been doing all my life. That is what drives me to help others use technology.
That drive is not a cliché. It means I keep myself current on where technology is headed, and genuinely care whether your system is elegant or just functional. There's a difference, and it matters.
For my entire career, my clients and coworkers have come to understand that when Toby is on it, it will get done: on time, on budget, on spec. I own my work. I don't leave clients hanging. When I run into problems I can't solve myself, I say so immediately — because we are partners in the project, and we will work together to solve those problems.
My academic focus is blue-team systems architecture — designing environments that are secure, resilient, and built to last. But I'm equally comfortable writing the software that runs on them, training the people who use them, or crawling under a desk to plug in the thing someone tripped over.
My clients don't just get a technician — they get a thinking partner.
When the town of Stockton, Utah needed a proper IT infrastructure, they came with a real constraint: a budget befitting a municipality of 200 people. What they had was an ad hoc system cobbled together over time that had long since outgrown its original design. What they needed was a server-client architecture that could handle their website, utility billing, and domain management reliably and professionally.
Working within their budget, I designed the solution from scratch — selecting equipment that balanced capability with cost, purchasing and building the server myself, configuring it for their specific operational needs, and installing it on-site. I stayed through the transition to train staff on managing and updating their own website, because a system nobody knows how to use isn't really a solution.
For a small municipality with limited resources, the result was a stable, professional infrastructure they could maintain and grow on their own terms.
Collections law is state-specific by nature, and over several years a firm had addressed that reality the straightforward way: a new form for every state variation. By the time we looked at the problem together, they had 128 forms in circulation.
The real issue wasn't the number of states — it was that nobody had stopped to ask which states were genuinely different and which were duplicates in everything but name. By mapping the actual variable elements across state requirements and implementing trigger-based logic to handle the differences, we reduced 128 forms to approximately 4 variable-data forms that could handle the full range of requirements automatically.
The simplification was significant enough that the firm was able to bring their document production in-house — a meaningful cost and time saving. When they eventually returned for their printing needs, I developed a barcode-driven document management system to ensure every page reached its intended recipient with no room for error. In collections law, a document going to the wrong person isn't just an inconvenience — it's a liability.
In 25 years of operation, that system has never failed due to an automated process error.
Some problems don't announce themselves until someone looks closely. A health insurance company was running on a billing system that was nearly 50 years old and no longer supported by any vendor. The system was functional — but it was sending outbound data files bloated with far more information than any invoice needed, creating unnecessary privacy exposure with every transmission.
The engagement started with understanding what they actually wanted their invoices to look like and working backward from there. I assessed the existing data structure, identified what was present, what was redundant, and what was creating unnecessary exposure, then designed and built a new XML data structure that streamlined their outbound files to contain only what was necessary.
The result was cleaner, faster, easier-to-process invoices and a meaningfully reduced privacy footprint. The project ultimately didn't reach full deployment — the client had additional invoice requirements that their legacy data stream wasn't capable of generating, a limitation we identified clearly rather than work around. The company was subsequently acquired and brought their operations in-house.
What the engagement demonstrated was what honest assessment of a legacy system looks like in practice — and the value of knowing what's possible before committing to what isn't.
I've done my job well if, at the end of the day, nobody even notices that I was there.— Toby Dillon, on network reliability
Outside IT vendors and MSPs will quote you a price and show up eventually. But to them, your business is a line item. They won't lose sleep if your database goes down. They won't feel the urgency when a missed mouse click means a missed deadline.
I do. I've handed colleagues my own keyboard, my own monitor, my own workstation — because I understood what was at stake and I had the means to fix it right now. That's not in any MSP's contract. It's just how I work.
I'm here to help. Give me your info and I'll get back to you by end of business day.