Agencies

Agencies hire me when they need a developer who will treat the client relationship as the agency's, not theirs. These posts are about how that arrangement actually works: what makes white-label development feel natural rather than awkward, what an agency should expect to brief in versus what should be left to the developer, and how to scope work in a way that does not leave the agency on the hook for technical decisions they did not make.

The posts cover the practical bits: how to hand over a project cleanly, what documentation an agency needs to keep so the client stays under their roof, how to bring in a developer for a single project without giving up margin and what to do when an agency inherits a site built on a stack their team does not know.

They also cover the trickier bits: when to tell a client their original budget is not realistic, how to handle a project where the brief and the code have drifted apart and how to price ongoing care in a way that the agency can resell without losing money. Most agencies I work with are good at clients but uneasy with code; the goal of these posts is to make code one less thing for the account team to worry about.

If you run an agency and you have a project that needs a developer, the agency page sets out how I work with you. For a longer view on white-label arrangements, browse the posts below.