The Standard / Ownership
Your domain, content, and data stay yours.
The retainer buys an active service. It is not a trap that makes your business unusable the day you want to leave.
The standard arrangement in this industry is that the agency owns the website. You pay monthly, indefinitely, for something you can never take with you, and the leverage that gives them is the reason the service quality can decay without consequence. When leaving means starting from nothing, you do not leave.
What is yours
The domain, registered in your name in an account you control. The website and every word of its content. Your customer database, which is a dedicated project per client that you can be given access to on request rather than a shared table you have to trust me about. Your Google Business Profile, your analytics, your ad accounts, and the reviews you earned.
These transfer permanently. They are yours during the engagement, not just at the end of it, and the agreement says so in words rather than implying it.
What is mine, stated plainly
The automation layer. The intake routing, follow-up sequences, review requests, payment and autopay flows, and the reporting behind them are my own software, licensed to you while I run your account rather than sold with the site. It runs while I am on watch, and on exit it disconnects cleanly and your site keeps working without it.
You keep every record those automations produced: the leads, the customers, the history. Your next developer can rebuild equivalents. I would rather write this down here than let you discover it in a schedule at the back of a contract.
How leaving actually works
You tell me. I move hosting and the database to accounts you control, hand over every credential, and provide a relaunch guide written for a developer who has never seen the project: how it is built, how to run it, how to deploy it, and where everything lives.
The price for that is in your proposal before you sign anything. I do not hold the domain hostage, I do not charge a release fee invented after the fact, and I do not require a reason.
excerpt from a real client artifact, redacted
Exit checklist
Domain access | Client-controlled account | CONFIRMED
Content export | Complete site content | READY
Per-client database | Transfer ownership to client | REQUIRED
Credentials | Handover list, all services | REQUIRED
Relaunch guide | Developer-ready, project-specific | REQUIRED
Automation layer | Disconnect licensed service | Site remains available