Independent Engineer
I build bespoke tech stacks for businesses whose problems don't fit off-the-shelf tools. Every engagement starts with the same question: what's the smallest, most boring system that solves this — and what does the client need to actually own?
Approach
The business arrives with a problem. I see a contract, a state machine, a place for the AI, a place for the queue, a place where the client needs to own the wire.
Most of the value shows up before any code does. The right composition for a problem is rarely the obvious one — and the smallest, most boring version of it is almost always the one that survives three years of business reality.
Selected Engagements
Different clients, different industries, different stacks. Same instinct: figure out the contract the work has to satisfy, build the smallest thing that satisfies it, deliver it on infrastructure the client can actually own.
01
Migration
A revenue-critical messaging system kept failing silently — buttons that didn't render, sessions that died mid-conversation, leads that disappeared between the form and the CRM. The right move wasn't another patch on top of a third-party platform. It was migrating off the whitelabel layer entirely, onto a stack the business owns end to end.
Read the case study02
Internal Automation
Daily personalized greetings for thousands of municipal employees, generated without any access to the employee list. The architecture separates the structure of the data — which I needed to specify — from its contents, which I never saw. The system runs inside the city's perimeter, on accounts the city already trusts.
Read the case studyContact
Send a note. Usually I reply within a day.