I didn’t start my career thinking, “I want to run a technology consulting company.” What I did know—pretty early on—is that I’m wired to solve complex problems, and I’m happiest when the solution makes life easier for the people who have to live with it.
That “make it easier” part matters. Technology has a reputation for being about systems, wires, and software. In real life, it’s about people trying to do their jobs—often under pressure, often with limited time, and usually with a dozen competing priorities. The best technology doesn’t feel flashy; it feels reliable, clear, and quietly empowering.
Over the last two decades, I’ve designed, procured, and deployed hundreds of solutions across hardware, software, infrastructure, and cybersecurity—most of it in local government environments, where budgets are real, scrutiny is high, and “downtime” isn’t just an inconvenience. It can impact public safety, service delivery, and community trust.
My formal background is a blend of business and problem-solving: I graduated in 2010 with a double major in Management and Finance, which gave me a practical lens for understanding how decisions get made, how value is measured, and why “total cost of ownership” matters more than buzzwords.
In 2011, I joined local government as a Database Administrator—work rooted in data quality, systems reliability, and the details other people don’t want to think about until something breaks. Over time, I expanded into broader technology leadership, and in 2014 I stepped into the role of Technology Director, where I became responsible for the full scope of IT operations and strategy across a complex public sector organization.
That transition forced me to learn fast, lead decisively, and balance the competing realities of:
What leadership wants (cost control, stability, risk reduction)
What staff need (tools that actually work, responsive support, training that sticks)
What the organization requires (security, compliance, continuity, scalability)
It also taught me something that has become central to my consulting philosophy:
✔ 15+ years delivering real-world IT solutions
✔ Experience across infrastructure, cloud, security, and operations
✔ Designed for organizations without in-house IT leadership who need a strategic partner
You don’t build great IT by chasing technology. You build it by building trust.
When I took over technology leadership, the department was not viewed as a strategic partner. That’s not unusual—many organizations have lived through a history of “IT as a gatekeeper” or “IT as a last resort.” My goal was to rebuild the relationship between IT and the organization by delivering visible improvements, measurable service, and a consistent message: our job is to help you do your job better.
That transformation wasn’t theoretical. It showed up in outcomes:
A major modernization of infrastructure and standardization across the environment
A shift toward centralized management and scalable operations
Better service delivery expectations and accountability
Faster response and resolution times through disciplined support processes
In the public sector, the wins that matter are the ones that hold up over time. The goal is not a one-time “project victory.”
The goal is to create a well-oiled machine—a set of systems, processes, and relationships that keep performing long after the excitement of go-live has faded.
Over the years I’ve led and delivered a wide range of initiatives—often with constrained budgets and minimal outsourcing, which forces you to be both strategic and hands-on.
A few examples of the types of projects I’ve executed include:
Virtualization, server, and SAN infrastructure modernization
Backup and recovery improvements (with retention and operational resilience in mind)
Email migration from on-prem to cloud
VoIP/SIP modernization and multi-site communications upgrades
Website modernization with API and integration considerations
Surveillance and physical security expansions and standardization
Network modernization and multi-site connectivity improvements
Cybersecurity defenses: monitoring, vulnerability scanning, awareness training, phishing campaigns, and layered controls
And, like many leaders who’ve been in the seat long enough, I’ve also been through the kind of incident that tests everything you believe about preparedness. I’ve led teams through ransomware recovery under pressure—triaging, containing, rebuilding, prioritizing business services, and restoring operations without paying ransom.
Experiences like mine don’t just shape your résumé; they permanently change how you design systems, policies, and response plans.
My leadership philosophy is simple: Start with WHY?
Before we talk tools, platforms, or architectures, we should understand purpose:
Why does this matter to the organization?
Why now?
Why this approach vs. alternatives?
What problem are we actually solving?
From there, we get practical:
HOW we’ll deliver it (people, process, milestones, risk controls)
WHAT we’ll implement (the actual technology and the operating model behind it)
This keeps stakeholders aligned—because a shared “why” is the difference between “IT did a thing” and “the organization improved.”
This mindset keeps projects from turning into expensive experiments.
After years of delivering results inside large organizations, I reached a point where I wanted to bring the same level of clarity, discipline, and forward-thinking execution to a broader set of clients—especially organizations who don’t have a deep bench of technical leadership but still need enterprise-grade decision-making.
Some teams need a full transformation. Others need targeted support:
A security maturity lift
A network refresh with real operational monitoring
A cloud migration done with minimal disruption
A systems integration that doesn’t become a permanent burden
A roadmap that leadership can understand and fund confidently
That’s where I thrive: turning complexity into an actionable plan, and then executing it with discipline.
If you hire me (and my team/partners, as needed), you can expect:
Clear communication, plain-language explanations, and no smoke screens
Decisions grounded in business value, risk reduction, and operational reality
A bias toward standardization, sustainability, and documentation
A structured approach to projects: milestones, accountability, measurable progress
A partner who cares as much about what happens after go-live as before it
At the end of the day, I’m building this business on the same principle that defined my public-sector career:
Technology should earn trust—by working, by protecting what matters, and by making people’s work easier.