Interactive graph
Client Site Pass-Off
Table of Contents
Before deposit, name who publishes next and price the pass-off so launch is not a guessing game.
Key Concept
- Pick exactly one primary model with Plain Commitments at Work - not “we will 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 will not 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 will not land but scope still fits static - quote CMS setup separately.
- Before deposit I pick one pass-off model - Git lesson, retainer batch, or showroom branch.
- Git lesson means repo access plus a short doc - edit markdown, commit, push without panicking at a terminal.
Level 1 - Recognize
Client site pass-off is choosing and pricing who will publish updates after launch.
Level 2 - Explain
Naming one model before deposit removes launch-day guessing about access, ownership, and support.
Level 3 - Use
Choose a Git lesson, retainer batch, showroom branch, or Git-Based CMS, then put that choice in the quote.
Level 4 - Connect
Client control, skill, update frequency, and support cost shape the model; the easiest handoff for you may be wrong for them.
Level 5 - Create
Create a pass-off kit for the chosen model and test whether the client can publish one safe update without you taking over.
Examples
- Glad the neighbor chose the 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 |
