Folders
What I write about
Pick the one you came for.
About
Why I write this
I build products and write down what actually happens: the pricing I got wrong, the launch that landed flat, the week nothing shipped, and the small changes that quietly moved the numbers.
Approach
How I work
Ship weekly, in public.
A week without something shipped is a week I have to explain here. That pressure is the whole point: it keeps the work moving and keeps me honest about what actually got done.
Start with the person, not the feature.
Before anything gets built I want to know who opens this, what they are afraid of getting wrong, and what “finished” looks like on their desk. Most bad software is a good answer to the wrong question.
Boring beats clever.
The best compliment a product gets is that nobody talks about it. I would rather ship something obvious that works every day than something impressive that needs explaining.
Show the numbers, not just the wins.
Revenue, churn, the cost of running it, the months that went sideways. Selective honesty is just marketing with extra steps.
- The hardest part of building is deciding what not to build.
- A tool that saves someone ten minutes a day outlasts a launch that wins a room.
- Speed comes from clear decisions, not from cutting corners.
Updated August 2026
Right now
- Taking on a small number of client builds.
- Building and selling my own SaaS products, documented week by week.
Say hello.
Building something yourself, or want to compare notes? I read everything.