On the practice
of making things well.
I have spent my working life at the intersection of systems and judgment: building infrastructure that operates at scale, political campaigning in high stakes elections, making physical things with my hands. These are different disciplines with the same underlying demand: understand the system completely, or don't touch it.
Making fine furniture. Small bitch brandy distillation. Custom electronics repair. These things share a doctrine: the quality of the finished work is a direct function of the attention given to each decision along the way. You cannot compress that process without paying for it.
I build deliberate and considered software. Every decision is made with intent. Together we will understand the processes that make your business unique, the differences that draw clients to work with you, and we will build tools that honor that uniqueness. This is bespoke software: custom fit and finished to your organization's specific form, with deep functional excellence. Nothing in this software exists by accident, by default, or because it was the path of least resistance. Every abstraction and interface is there because it earned its place, every constraint was chosen, every invariant deliberated upon. The work is intentional all the way down.
I take a small number of commissions each year. This a quality and attention commitment. The kind of focus a commission deserves cannot be divided indefinitely. Two to four engagements a year means each one receives what it requires. The work reflects that, and I am accountable for the work.
Every engagement ends with complete transfer. The code is yours. The documentation is yours. There is no license to renew, no vendor relationship to manage, no data sitting on infrastructure I control. This is not a selling point — it is a precondition. Software you do not own is not an asset. It is a permanent, rented drain on your accounts.
I am available for an optional ongoing retainer for clients who want priority access and a standing relationship. But the software will work without it. It is designed to.
I choose clients carefully, based on whether the kind of software I build is the right solution to your challenges. Not every engagement is right for this practice, and I will say so clearly at the outset if that is the case. The conversation that precedes a commission is not a sales process — it is a calibration. I am trying to understand whether my approach will provide real value for you, and whether the way you work is a process around which I can shape software.
If it is, the result will be software that fits like a bespoke jacket — without ongoing adjustment, without compromise, without the pain points of a thing that was made for a fictional, abstract "ideal user profile" and then adapted imperfectly for you.