Loading
Writing
Build logs, automation teardowns and what happened next
What we build, what it cost, what broke, and what we learned. Written while it is still fresh.
Posts
Automate · GrowWhat one repetitive workflow actually costs youNobody knows what their manual process costs, which is why nobody fixes it. Here is the arithmetic, and the number it usually produces.6 min read
Automate · BuildI automated client onboarding end to endEleven manual steps across six tools, reduced to one approval click. The full map, the parts that broke, and what I would not automate again.9 min read
BuildWhen no-code stops being the cheap optionThere is a crossover point where a visual automation costs more than the code it replaced. Four signals that you have passed it.7 min read
Build · AutomateAI agents fail at the pipeline, not the modelNearly every disappointing agent project I have taken apart had the same cause, and it was never the model. It was what the model was allowed to see.8 min read
GrowSell it before you build itI can build almost anything in a week, and that is the problem. Notes on why the first 90 days are going into distribution instead of code.7 min read
Grow · ToolsFree tools are a distribution channel, not a productA calculator that answers one expensive question will out-earn a blog post every time. How I am building one every two weeks, and what I measure.6 min read
Start here
Have a problem worth solving?
Tell us what is slow, manual or missing. You will hear back within one working day — then get a written scope and a fixed quote, or an honest no.
brief.md
- # New project brief
- ## What is slow, manual or missing?
- - [x] Written scope
- - [x] Fixed quote
- - [x] Or an honest no
Reply within one working daySend brief