Half of the friction in client relationships, I have come to believe, is that the word "shipped" means different things to the engineer and the client. The engineer means "the code is in main and the deployment script succeeded." The client means "the thing I asked for is doing the job I asked it to do, reliably, on the production site, in front of real people, today."
After enough disagreements about that gap we wrote down what we now mean by "shipped" on every engagement, and we read it at the kickoff call so nobody is surprised at the end. The list is short. It is: the feature is on the production site, behind the production domain, accessible to the production audience. The feature has been tested end-to-end by a member of the studio on at least one mobile device and one desktop browser the client uses. The relevant pages have a Lighthouse score above the agreed budget. The deployment has been verified by someone other than the engineer who wrote the code. The runbook has been updated to reflect the change. A short loom walkthrough has been recorded and sent to the client.
None of those items are optional and none of them are obvious. Each one is on the list because at some point in the studio history a release got into trouble for skipping it. The Lighthouse-budget rule is on the list because we shipped a beautiful redesign in 2022 that cratered mobile performance for a week before anyone noticed. The runbook-update rule is on the list because in 2023 a colleague had to spend a Saturday afternoon untangling a deploy by reading code that had no record of why it was written.
The list is the closing ceremony of every engagement, and it is also the reason the studio can take a calm pace. We do not consider an Atelier Build shipped until every line on this list is green. We do not invoice the final tranche until every line on this list is green. The list, more than anything else we do, is the reason a client who comes back to us in 2027 still has a working site.