Client Site Pass-Off
Table of Contents
Before deposit, I name who publishes next and price the pass-off so launch isn't a guessing game.
Key Concept
Pick exactly one primary model with Plain Commitments at Work - not “we'll figure it out at launch.”
Git lesson - client gets repo access plus a short doc (Getting Started shape: edit markdown, commit, push). Fits owners who want control and won't panic at a terminal. Retainer - they email copy or photos; I push on a batch schedule. Price per update batch, not fake monthly hosting. Showroom branch - The Garage Concept: my experiments stay off their deploy branch; what they see is clean.main only. Git-Based CMS - when Git lesson won't land but scope still fits static; quote CMS setup separately.
Bad pass-off: promise WordPress-style daily edits to five non-technical staff with no training, retainer, or CMS. That's a Static Site Client Scope lie that blows up on week two.
Deliver a one-page pass-off doc: repo URL, Cloudflare project, env vars, domain DNS, which branch deploys, who to call when build fails. Share What You Learn - the doc is the product, not hoarded in my head.
Examples
- Neighbor chose Git lesson - twenty minutes on edit, commit, push; she broke build once, fixed typo same night.
- Pastor emails bulletin PDF every Friday - retainer batch, one push, no CMS layer needed.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| contradicts | There Is No Perfect Solution | when I defer pass-off choice until launch and hope they adapt |
| extends | Git-Based CMS | Fourth pass-off path when buttons beat terminal |
| extends | Plain Commitments at Work | One publish model named before deposit |
| extends | Selling Static Sites | Pass-off is priced separately from build setup |
| extends | Share What You Learn | One-page doc leaves the team able to publish without me |
| extends | The Garage Concept | Showroom branch vs messy workshop drafts |
