The client handoff playbook: ending the change-request treadmill

There are two classic endings to an agency website project, and both are bad.

Ending one: you keep the keys. Every hours change, staff photo, and typo becomes a ticket. You're now billing $150 increments of resentment, and the client quietly wonders why their website has a subscription to you.

Ending two: you hand over the keys to a page builder. Within a quarter, the design system is wearing three fonts and a gradient you didn't choose. Their site, with your name in the footer - is now your worst portfolio piece.

The problem isn't the client. It's that most platforms offer only two permission levels: spectator and demolition crew.

The third option: structured handoff

The workflow below assumes a platform with real roles and structured content - clients edit fields, never layout.

1. Build on structure from day one. Services, team, menus, FAQs as collections and typed fields, not text boxes floating in a canvas. This is what makes every later step possible.

2. Set roles at launch, not after the first incident. Client = editor: content fields, media, forms, AI chat. You = admin. Your developer keeps code access. The client cannot touch structure, not as policy, as architecture.

3. Run the 20-minute handoff call. With editing this constrained, training collapses to: here's the chat, here are the forms, everything previews before publishing, nothing you do is irreversible. Record it; you won't need to.

4. Let the AI absorb the long tail. The requests that used to be tickets - "update the hours," "add the new hire," "swap those photos" - the client now types into chat. Every change is versioned, so even a bad headline is a 30-second rollback, by them.

5. Re-scope the retainer upward. With typo patrol gone, the retainer stops being maintenance and becomes strategy: quarterly SEO passes, new landing pages, seasonal campaigns - the work you actually want, at the rate it deserves. (The seasonal playbook is a ready-made retainer deliverable.)

The component flywheel

The second-order win: the custom blocks you build for one client become part of what the AI composes with for the next. Your booking widget, your rate table, your case-study layout - generation handles the 80% using your components, your team art-directs the 20%, and delivery time drops from weeks to days without touching your price.

Agencies running this loop describe the same arc: margins up, inbox quiet, clients weirdly happier, because the thing they bought stays alive without either of you resenting it.

Unlimited collaborators on every plan is what makes this workflow affordable - you never pay per client seat. See the full agency story.