Client Owns Everything

The client owns the repository. The client owns all services. The client owns the billing for every tool and platform. The developer is a contributor. Never an owner.

From Day One

This isn't a policy bolted on at the end of an engagement. It's how things are set up from the start. Every repo is created under the client's account. Every cloud service is billed to the client's card. Every API key belongs to the client.

If the client cancels tomorrow, they lose nothing. No code held hostage. No credentials the developer controls. No proprietary framework the client can't run without the developer. The client takes their repo, hands it to another developer, and keeps going.

Why It Makes Exit Real

Exit freedom is meaningless if the developer controls the infrastructure. "The client can leave any time" rings hollow when the code depends on the developer's proprietary tooling or the deployment pipeline requires the developer's involvement.

No proprietary software. No custom frameworks that only the developer understands. Standard tools, standard patterns, standard deployment. If something needs to be proprietary, the developer is a contributor to it — not the owner of the asset.

The Business Logic

This connects directly to software as business cost. If development is a business expense like office supplies, then the outputs belong to the business. Nobody lets the office supply vendor own the filing cabinets.

When the client owns everything, the retainer is purely for the developer's time and expertise. Cancel and everything stays. Nothing disappears. Nothing breaks.

Portable by Default

Some clients will leave and come back. Some will graduate and outgrow the model. Some will hand the codebase to a bigger team. All of these are fine because the developer built zero dependency on themselves.

The best service providers make themselves easy to leave. Paradoxically, that's exactly why clients stay.