What happens when a client wants to stop or pause?
Weekly billing, full client ownership, and no lock-in mean stopping or pausing is mechanically simple and penalty-free.
Work doesn't move in a straight line. It surges, then slows. A product might need intense development for six weeks, then nothing for two months, then a focused push again. The book argues the service model should match this reality instead of fighting it.
Exit Freedom makes stopping mechanically simple. No penalty clauses, no notice periods, no awkward wind-down conversations. Weekly billing means cancellation is a subscription toggle, not a negotiation.
This only works because of Client Owns Everything. From day one, the repository sits under the client's account. Cloud services are billed to the client's card. API keys, credentials, documentation — all client-controlled. Nothing is held hostage, so leaving doesn't require extraction.
Pause, Not End treats the gap as normal, not terminal. Context survives the pause. The task board, repository history, and documented decisions don't disappear. Resuming means picking up where things left off, not starting a new onboarding.
Client Decides puts the call where it belongs. The developer's role is to inform — here's what's done, here's what's left, here's what continuing looks like. The client decides whether the value justifies the cost. It's their business, their money.
Without a pause mechanism, teams end up in one of three traps: forced continuity that breeds resentment, hard endings that make restarting expensive, or scope-stretching to justify ongoing billing. Weekly billing with easy cancellation short-circuits all three.