What staying on after launch actually looks like
6 min read · August 2026
For years we described our process as working ourselves out of a job. It was true in one narrow sense — we do hand over the files, the CMS and the training — and misleading in every other.
The clients we are proudest of are the ones still on our calendar three years later. Close is one. Sabrina is another. In both cases the launch was the point where the work started being useful, not the point where it stopped.
Ownership and involvement are separate questions
A client can own every file and still want the two people who made the decisions to keep making them. Conflating those two things cost us work we should have kept, because we were telling people that leaving was the successful outcome.
A site is not a deliverable. It is a thing that has to keep working while the business behind it changes.
So the language changed, and so did the shape of the engagement. Every project now ends with a conversation about what the next twelve months look like rather than a handover call and an invoice.
What a retained month contains
Usually a mix: campaign pages, design for whatever the team is launching next, technical maintenance, and increasingly the search and answer-engine work that decides whether any of it gets read.
A standing call every other week, whether or not there is a deadline.
A shared backlog the client can add to directly.
A fixed monthly number, so nobody hesitates before asking.
You still own everything. We would just rather keep working on it with you.
Nelson Abalos Jr.
The build half of That One Couple. Front-end, CMS architecture, apps, and search.