What we learned building it
How to brief a web project so the quote is accurate
Latest writing
How to brief a web project so the quote is accurate
What actually moved our clients from 4.1s to 1.3s LCP
Migrating a store without losing a single ranking
Why we quote fixed price instead of hourly
Choosing between WordPress, Shopify and a custom build
The accessibility work that takes an hour and matters most
Designing an integration that survives a vendor outage
What a maintenance retainer should actually include
What a booking rebuild changed for a field service business
The month's build notes, in one email
About the journal
The engineers who did the work, edited lightly for readability. If a post contains numbers, they came from that project.
Only with written permission. Otherwise we describe the sector and keep the numbers, which is the useful part anyway.
Two or three posts a month, whenever a project produces something worth writing down. We would rather skip a month than pad it.
Yes — reply to any newsletter issue or send it through the contact page. Several posts started as client questions.
With attribution and a link, yes. Ask first if you want to edit it.
One, at the start of the month, with no follow-up sequence. Your address is never shared or sold.
Reading is fine. Building is better.
If one of these posts describes a problem you have, send it over with your context. We answer with an approach, not a brochure.