Every engagement begins with seeing clearly.
What’s missing becomes visible. Then we provide it. It might be a semantic layer, an architecture review, a strategy, or one conversation with a trusted advisor. Whatever it is, it’s built around where you are, where you need to be, and the path between them.
For leaders who can feel the problem before they can name it.
You might have a vision and need a partner to build it with. You might have an AI initiative that dazzled in the demo and stalled in production. You might just know the next decision is expensive to get wrong.
My sweet spot is organizations flat enough that the people who matter fit in one room, where the distance between a good idea and a decision is short.
Advise. Build. Transform.
A trusted advisor, on call.
Strategy, architecture reviews, how your teams work, and the second opinion before a decision that’s hard to reverse. I see the system as it is, then tell you what I see, and help you lead the change.
- Architecture and technology strategy
- Architecture reviews
- Process, practices, and driving change
- Semantic layer and AI readiness
- Expertise on call
Hands on, in your systems.
Proofs of concept, spikes, modernization, and semantic layer builds. I work in your code and your data, and the result runs in production.
- Proofs of concept and spikes
- Modernization
- Semantic layer builds
- Agent-ready APIs
Your team builds it, and keeps it.
Your people build the real thing alongside me: a working system and the thinking that produced it. When the engagement ends, the capability stays in the building.
- Prep, on-site build, and handover
- Work product your team owns
- The mental model, installed
- A vision for what follows
Every engagement leaves two things behind: the work, and the thinking that produced it. We don’t just change the code, the architecture, or the data; we change the people and teams responsible for them.
Two practices, one discipline.
The semantic layer
AI guesses when the data has no meaning attached to it. When meaning travels with the data, expressed in open standards and owned by you, the cost of change goes down and keeps going down. I’ve been building and teaching this architecture since before the industry had a name for it.
Holistic software architecture
Architecture reaches well past the code and the cloud. It runs through your teams, your communication structures, your culture, your practices, and the market you compete in, so I design across all of it: driven by your business strategy, built to survive contact with reality, and ready to evolve as you do. It’s the model in Mastering Software Architecture (Apress, 2025).
Fun fact In more than half my architecture engagements, the real problem turned out to be somewhere else. That’s why I always start with the problem, never the solution.
I don’t come in to make myself indispensable. I come in to find what’s missing and build it into the organization. My measure of success is the day you don’t need me anymore.
What keeps you up at night?
Start there. The first hour belongs to the problem.