A faster page in an afternoon
Before rewriting anything, try these fixes. How we take a slow marketing or product page and make it noticeably faster in a few hours.
The logbook
Blog.
Short essays from the workshop. How we scope, ship every week, keep servers quiet and tell clients the truth about timelines.
Write the launch checklist before the code
Launch day goes wrong in boring, predictable ways. Why we write the checklist in week one, and the items that catch most of the 2 a.m. surprises.
Small batches, shipped every week
Why Shipped releases small changes every week instead of saving them up, and what that habit does for risk, feedback and the people paying for the work.
Design the empty state first
The first screen a new user sees is usually blank. Why we design that screen before the full one, and what it teaches us about the whole product.
A backup you've never restored is a guess
Most teams have backups. Far fewer have ever restored one. Why we run a full restore drill every month, and the boring checklist that makes it painless.
Why your newsletter lands in spam
Most newsletters that land in spam have the same few problems. A plain guide to SPF, DKIM, DMARC, list hygiene and warming up a new sending domain.
The whole project on one page
Before we write any code, every project gets a single page that says what we're building, what we're not, and how we'll know it worked. Here's the template.
Boring servers are a feature
The quiet habits behind servers that rarely page anyone at night, from one box per project to backups we actually restore.
Say hello
Got something to ship?
Send a few lines about your idea or your stuck project. We'll reply with honest feedback and a rough plan to get it out the door.
How it starts
- 01A real person reads your note before the next working day ends.
- 02You get straight answers and a few sharp questions back.
- 03If we can help, we map out a first release on a 30-minute call.