Case Studies
The thinking and the building, in the same place.
Two deep dives — one into a product where the market thesis decided the architecture, and one into how the work gets done at all.
Strategy → Architecture
Find the market need, then build the solution.
Youth sports programs run on software written in 2014. Understanding why they tolerate it decided the product — and then four architecture decisions, each of which is a business judgement that only looks like a technical one.
- Why the incumbents are bad and entrenched
- Row-level security because the data is children's
- Double-entry accounting because treasurers hand off
- Connected accounts so the money is never mine
How the work gets done
AI-augmented delivery, and where it breaks.
Everyone says they use AI now. The useful question is what happens when it's wrong — because it will be, and whether you catch it is the whole difference between leverage and liability.
- A recovered transcript that changed two recommendations
- The model is a research assistant, not a source
- Failure modes are predictable, so check there first
- Leverage on execution, none on judgement
This is how every engagement runs.
Market first, then the system that serves it — from the same person.