Exit Policy

Effective date: 07/16/2026 · Last updated: 07/16/2026

Most providers make leaving hard on purpose. The domain is in their account. The site is on their platform. Your customer data lives in a system you can't export. Cancelling means starting over, and they know it.

I don't work that way. If you decide to leave, I hand you your business and help you carry it out the door. Here's exactly what that means.

What you own from day one

Your domain. Registered in your name, or transferred to you on request at any time. Not held as leverage.
Your data. Customers, leads, bookings, invoices, content. It's your business's record of itself, and you can export it at any time, for any reason, whether you're leaving or not.
Your accounts. Google Workspace and third-party services are set up in your business's name wherever the vendor allows it. I hold access to do the work, not to hold the keys.
Your public site, once the work that built it is paid for. Ownership of the public-site deliverables transfers on payment, the same as any trade. See the Terms of Service for the details.

If you cancel

Tell me you're done and this is what happens:

Care plans end at the close of the current billing period. No long notice requirement, no fee for leaving. Refund mechanics are covered in the Refund Policy.
Your data exports immediately. Everything in your system, in standard formats you can actually open and import elsewhere. This happens regardless of any outstanding balance. Your business records are never collateral.
Domain transfer. I unlock your domain and send the authorization code, or push it to the registrar of your choice.
Google Workspace handoff. Transferred to your ownership with email, files, and calendars intact. Moving to another provider instead? I'll help with the migration path.
Public-site package. Once work performed to date is paid, your public site is packaged so another developer can deploy it: code, content, assets, and enough documentation that whoever comes next isn't guessing. The admin platform is my software and isn't part of the package; your data exports separately, in full.
Access removal. I remove my access to your accounts and confirm it in writing.

Timeline: I start within days of your request and complete my side within 14 days. Domain and email transfers depend partly on registrar and Google timelines, which I don't control, but I initiate them immediately.

Cost: standard export and handoff is included. Extended migration work into another provider's system is billable, quoted before it starts.

Payments and Stripe

Client payments are processed through Stripe. When you leave, your customer and payment records export with everything else, and I'll help you stand up or reconnect your own Stripe account so you can keep taking payments without interruption. What Stripe itself can transfer between accounts is governed by Stripe's rules, and I'll walk you through exactly what carries over before anything changes.

Minimum terms and special arrangements

My standard agreements have no minimum term and no termination fee.

Occasionally a client and I agree to a special payment structure, like spreading a build cost across monthly payments instead of paying upfront. In that case the signed Order will say so in plain language, including what happens if you exit before the build is paid off. No arrangement like that is ever buried in fine print: if your Order doesn't mention a minimum, there isn't one.

What I can't hand over

Being straight with you about the limits:

The admin platform. The back office that runs your leads, scheduling, billing, and records is my software, provided as a service, not a deliverable you own. Everything in it that's yours, your data, exports in full and leaves with you. The platform itself stays with me.
Third-party subscriptions and licenses stay with whoever the vendor's terms say they stay with. Where the account is in your business's name, it stays with you.
Software I license from others that's embedded in your build transfers only to the extent the license allows. If anything in your project falls into this category, I'll tell you before we build it, not on the way out.
My internal tooling (deployment scripts, monitoring, the machinery I use across projects) isn't part of your deliverable. Your site and data don't depend on it to run somewhere else.

Money

Care plans cancel at the end of the current billing period. No refund for the partial month, no charge for the next one. See the Refund Policy for details.
Project work in progress is billed for work completed to date. You keep what's finished and paid for.
Outstanding invoices are due. Your data exports regardless; final public-site deliverables transfer once the work that produced them is paid.

Why this exists

I build tools for business owners, not subscriptions that own business owners. A tool you can't leave isn't a tool, it's a leash.

If you stay, I want it to be because the work is good, not because leaving is expensive.

This policy works together with the Terms of Service and Refund Policy. If a signed Order sets different exit terms, the Order controls, and it will say so plainly.

Questions about any of this before you hire me? Ask. I'd rather answer it now than have it be a surprise later.