You own it
Your accounts. Your data. A documented handover.
New accounts are created in your business name and billed directly to you. You retain your custom code and data when our engagement ends; we document access, dependencies, and the work needed to maintain the system.
What you hold
Every account, and exactly what we can touch
| What it is | What is in your name | What our access is | Your cost |
|---|---|---|---|
| Code | Your business repository and custom project code | Scoped collaborator access appropriate to the work | Plan-dependent |
| Hosting and domain | Your hosting and registrar accounts, billed to you | Deployment and DNS permissions; you remain the account owner | Hosting plan, domain renewal, and usage |
| Google presence | Your Business Profile and any Workspace subscription | Delegated management access; you retain primary ownership | Workspace subscription if used |
| AI and automation | Your provider accounts and workflow configuration | Project-scoped access with usage alerts and limits where supported | Subscriptions and metered usage |
| Messaging and booking | Your email, phone, CRM, and scheduling accounts | Integration access limited to the agreed workflow | Software plans, numbers, email, SMS, and call usage |
| Advertising | Your ad accounts and campaign data | Campaign management access when included | Ad spend paid directly to the platform |
Ownership and support are separate. Provider subscriptions continue in your name. Monthly support ends at the next renewal; Growth Partner has quarterly billing and a three-month minimum. Review active integrations before removing access or rotating credentials.
A handover you can use
Every implementation includes an account inventory, access list, renewal details, and a runbook covering normal operation, failure handling, and how another engineer can maintain the system.
A documented exit
You retain your accounts, data, and custom code when our work ends. The offboarding checklist covers access removal, credential rotation, active integrations, and replacement support. Provider subscriptions and maintenance remain your responsibility.
Ownership you can verify
You create the accounts and invite us with the permissions needed for the work. Third-party software remains subject to its own licensing and export limits, which we document before implementation.
Plan for failures
The scope includes monitoring and a fallback route for inquiries where the provider supports it. We test human handoff before launch and document dependencies. Outages can still delay replies or delivery, so escalation contacts and manual procedures matter.
Need help moving an existing setup?
Tell us which accounts you control and which provider manages the rest. We will check export options and migration dependencies before proposing work.