I work with you from first conversation through last deployment. No handoff, no translation layer. I write the code myself.
Thirty years of engineering judgment plus AI-assisted development. I can see the whole system and still be the one at the keyboard.
I'm not here to write a report and leave. I'm here to ship the thing that solves your problem.
The discovery work, the architecture, the code, the rollout. Same person, one conversation, all the way through.
Developer, architect, CTO, VP. The titles kept changing. The code kept calling me back.
That reaction is what every project is for. Everything else is engineering in service of it.
I listen harder than most developers. I ship faster than most consultants. The overlap is where the interesting work happens.
I understand the business problem. I know what's actually buildable. I start building on day one.
Client engagements and open source projects. I build both, and they feed each other.
Built the scoring engine, financial model, and contract-to-application mapping for a 600-application portfolio spanning 47 departments. Automated the analysis and handed the team the tools to keep the program running after the engagement.
Joined a seed-stage startup as Interim CTO. The product was a Joomla proof of concept; I rebuilt it from scratch as the sole developer on PHP, hired an onshore/offshore engineering team, and migrated the platform to Java as the product matured. Stayed to close the Series A, then exited.
Designed and stood up a new service offering from concept to recurring revenue. Built the practice, the delivery model, the client relationships, and the team around it. Zero to $500K ARR in three years. Still running.
Walked into a $250K operating loss and built the systems, processes, and tools that reversed it. Not a report. The actual infrastructure that made the turnaround stick.
A voice-first Microsoft 365 check-in app. Ask about your calendar, your email, or anything across Teams and hear the summary. Built so the morning briefing happens while the coffee is still pouring. Free. Open source. Anyone can try it.
Most engagements start with a conversation about a problem. I listen for a while, ask a lot of questions, and start building. Not a prototype to demonstrate a concept; the thing itself, rough but working, that we can change on the spot while the person who will use it watches.
I stay in the room from that first conversation through the last deployment. There is no handoff. The person writing the code is the person who sat with the stakeholders. I am the one asking what actually needs to happen on Monday morning.
AI-assisted development is a core part of my practice. It lets me ship faster than I used to, but only because thirty years of engineering judgment keeps the code clean. I can tell good AI output from bad output, and I rewrite the bad parts. I also build in the open when I can. Open source is how I stay sharp, how I test ideas before I bring them to clients, and how I give back to the tools I use every day.
Every engagement is a build, even when it starts as strategy. A rationalization study ends with a scoring engine. A turnaround ends with the systems running the new process. The deliverable is working software, not a slide deck.
I have been building software for thirty years. Across that time I worked as a developer, technical lead, solutions architect, CTO, and VP. Each title took me a little farther from the code. I came back to it on purpose.
These days I am at the keyboard on hard technology problems. I analyze the data, build the tools, write the deliverables, and present the findings myself. I use AI-assisted development as a core part of how I work, not a novelty. Knowing what good code looks like is what lets me direct AI output rather than accept whatever it hands back.
Plenty of my career has been spent as a project manager, technical lead, and executive. All of that is still in the toolkit, and I am a strong project manager when the role calls for it. But it is not what I am doing now. Right now I am the person writing the code and sitting with the user while they try it. At this level of experience, that is rare, and it is where I am most useful.
My most recent engagement was an application portfolio rationalization for a large municipal government, where I built the scoring engine, the financial model, and the tools that keep the program running after I leave. Before that, client work across energy, startups, and government.
I live in Houston with my wife and kids. When I am not at the keyboard, I would rather be outside with them.
If you have a hard technology problem, I would like to hear about it. I work with mid-market companies directly and with consulting firms as a subcontractor.