Technology Strategy
Turning a vague sense that something needs to change into a sequenced, costed plan. What to fix first, what can wait, and what the trade-offs actually are in plain language.
Independent Technology Consulting
Technology decisions that hold up.
I help organizations make sense of complex systems — choosing what to build, what to replace, and what to leave alone. Two decades of doing the work, not just advising on it.
Twenty years of building and steadying critical systems.
About
Twenty years in the room where it gets built.
- 20+
- Years in Technology
- Hands-On
- Not Slideware
- Direct
- No Handoffs
I have spent more than twenty years in technology — designing systems, leading delivery, and untangling the kind of infrastructure that a business quietly depends on. That work has spanned greenfield builds, long-overdue modernizations, and the unglamorous stretches in between where reliability is won or lost.
Consulting, done well, is not a slide deck. It is sitting with the constraints a team actually has — the budget, the deadline, the system nobody wants to touch — and finding the path that survives contact with reality. I work in the details because that is where projects succeed or quietly fail.
I take on a small number of engagements at a time, which means the person you talk to is the person doing the work. No handoff to a junior bench, no rotating cast.
What I Do
Four ways I tend to help.
Most engagements start with one of these and grow into the others as the picture gets clearer.
Architecture & Modernization
Assessing systems that have accumulated years of decisions, then charting a migration that does not require stopping the business to complete it.
Cloud & Infrastructure
Right-sizing infrastructure for the workload in front of you — with attention to cost, resilience, and the operational burden your team will carry afterward.
Delivery & Team Enablement
Helping teams ship predictably. Reviewing how work moves from idea to production and removing the friction that makes estimates meaningless.
Approach
Understand it, then change it.
A deliberately unremarkable process. The value is in doing each step honestly rather than rushing to a recommendation.
- 01
Assess
I start by listening and reading code, not prescribing. Where are the real constraints? What has already been tried? A short, focused review beats a long one built on assumptions.
- 02
Plan
A written plan with sequencing, dependencies, and the risks stated out loud. It should be clear enough that your team could execute it without me, and honest enough to name what might go wrong.
- 03
Execute
I stay involved through delivery — reviewing, unblocking, and adjusting as reality intervenes. Plans that survive first contact are the only ones worth writing.
Contact
Tell me what you are working on.
A short description of the situation is enough to start. If it is not something I can help with, I will tell you that directly and point you somewhere better where I can.