Why we automate the boring parts first
The flashiest AI project is rarely the one that pays for itself. Here is the test we run before we build anything, and where automation quietly goes wrong.
01AutomationsApproach
Blog
Notes from the workshop
Written in markdown, committed to the repository, published on the next build. No CMS, no drafts sitting in a dashboard — if it is here, we meant it.
Two people, one AI studio
Why we are deliberately staying small, the stack we actually use, and the four kinds of work we now say no to without hesitating.
Building in the open: our first product
Client work pays the bills, products compound. What we are building, why we are publishing the messy middle, and the rules we set for ourselves before writing any code.
Nothing filed under everything yet. Try another tag.