Client Site Handoff

Client site handoff = after Selling Static Sites build, one clear path for who publishes next - priced and named in the proposal before deposit.

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 handoff: 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 handoff 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.
• I kept client experiments on a draft branch - showroom main stayed clean; garage mess never hit their live site.
• Client assumed “hosting included unlimited edits” - should have been retainer line item; fixed on client two with plain scope up front.

Note Relationships