Notes from the workshop floor.
Bits keeps a notebook. What we're reading, building, breaking, and figuring out. Updated when we have something worth saying.
Three teams, one pipeline. Why every project gets built three times.
Most agencies pick a lane: design or engineering or strategy. We don't. Here's how a single project moves through Bots, Bytes, and Bits — and why it ends up better when all three have touched it before it ships.
Recent.
The 1080p pipeline that kept melting our queue.
Six versions later, we figured out it wasn't the renderer. It was the way we were chunking work between stages. A short story about queues.
Why "we build anything" beats a feature list.
Listing 26 things you do is a tell. The agencies that win the interesting work are the ones who say "show us what you've got" and mean it.
What Bots actually asks on a discovery call.
The five questions that turn a vague brief into a buildable spec. Most of them aren't about the product at all.
n8n, but only when it earns its place.
Where automation actually pays for itself, and where it just adds an extra system to maintain. A taxonomy after 40-something workflows.
One typeface, six pages, no slop.
Picking a typeface for the new site. Why we avoided the usual suspects, and what we landed on instead.
The discovery call no one asks for, but everyone needs.
Why we always run a 30-minute call before quoting. Even on tiny projects. Especially on tiny projects.
A short letter when there's
something worth reading.
Once or twice a month. Nothing automated. Bits writes them by hand.