The case for visible strategy
Why showing the thinking is the fastest way to build trust.
How we work, what we refuse, and the arguments we would rather have in week two than week ten.
2 articles · Agency practice
We write about our own practice for a specific reason: most of what goes wrong in a client engagement is decided by how the engagement is set up, not by how well anyone codes. Who can approve direction, what gets written down, when the honest disagreement happens.
These pieces cover what we refuse and why, how we price and scope, what we have got wrong and changed since, and the arguments we would much rather have in week two than in week ten.
Each topic collects the arguments we find ourselves repeating in first meetings, written down properly so you can read them instead.
Briefs, structure, platform choices and why accurate websites so often fail to persuade anyone.
Retention, states, release engineering and the decisions that separate an app people keep from one they delete.
Platform decisions, replatforming risk, checkout friction and where merchandising velocity actually comes from.
Core Web Vitals, accessibility, security and the compounding value of work nobody notices.
How we work, what we refuse, and the arguments we would rather have in week two than week ten.
We publish when we have learned something worth another team’s ten minutes, which works out at roughly one piece a month. There is no content calendar, no keyword-led brief and no ghostwriter, because articles written to fill a slot read exactly like articles written to fill a slot.
Everything here is written by the people doing the work, and every recommendation has been tested on a real engagement — including the ones where we got it wrong first. Where a claim is contested, we say so rather than presenting a preference as a finding.
Nothing is gated. If a guide is useful, it should be useful before you speak to us.
Bring us the hard thing. We will bring a point of view, a senior team and a clear next step.