A business should know what it owns, what it licenses, what remains with a vendor, who controls each account, and what happens when the engagement ends. OneZero makes those answers part of scope and handover rather than a last-minute surprise.
Build the exit path while building the system.
The proposal and agreement should distinguish client materials, newly created deliverables, OneZero pre-existing tools, open-source components, stock or third-party licences, hosted services, accounts, data, and continuing support.
What we will not pretend: This page is general service information. The signed agreement, proposal, licence terms, platform terms, and applicable law determine ownership and handover for a specific engagement.
What should be clear before launch
Domains, hosting, platforms, and administrator accounts
Identify the legal account holder, billing owner, administrators, recovery contacts, access method, and offboarding route.
Code, design, content, data, and licences
Separate custom deliverables from client inputs, pre-existing methods, open-source packages, fonts, stock assets, plugins, models, and vendor services.
Documentation, training, support, and transition
Give the responsible team enough information to operate the agreed system and understand what still requires a specialist or paid service.
A practical handover package may include
The exact package follows scope and the technology used. A marketing website, licensed platform configuration, automation, prototype, and custom application do not create identical ownership rights.
- Account and asset inventory with named owners and administrators
- Agreed source files, repository or export, content, media, and data export
- Environment, deployment, integration, domain, and vendor overview
- Licence, subscription, renewal, attribution, and dependency list
- Credential transfer through an approved secure method—not embedded in a public document
- Operating instructions, known limitations, training, acceptance, and outstanding items
- Maintenance, warranty, support, incident, cancellation, and transition terms
Client-owned accounts are preferred where practical
Domains, advertising platforms, analytics, business listings, payment providers, core hosting, and other strategic accounts are generally easier to govern when the client is the legal owner and grants appropriate access. Technical or vendor constraints can create exceptions, which should be documented.
Handover does not erase third-party terms
Open-source licences, stock assets, fonts, plugins, APIs, cloud services, AI providers, ecommerce tools, payment platforms, and app stores retain their own terms and fees. Custom ownership cannot transfer rights OneZero or the client never possessed.
Ownership from proposal to exit
- Inventory inputs and accounts. Record who owns existing content, data, domains, software, credentials, and licensed assets before work starts.
- Define deliverable rights. State what is assigned, licensed, retained, restricted, or dependent on payment, acceptance, or third-party terms.
- Prepare handover during the build. Keep repositories, files, configuration, decisions, licences, and documentation organized rather than reconstructing them at the end.
- Close or transition cleanly. Confirm final deliverables, access, exports, outstanding fees, support state, deletion or retention obligations, and the next responsible owner.
Questions buyers usually ask
Will we own our website?
The agreement defines ownership. A typical build can hand over agreed custom content and files, while themes, plugins, fonts, stock assets, hosting, and other licensed components remain subject to their own terms.
Will we receive custom software source code?
It can be included when agreed. The handover should distinguish custom code, OneZero pre-existing components, open-source packages, secrets, infrastructure, vendor services, and data.
Can we leave an ongoing retainer?
Cancellation, notice, final billing, support, access, exports, transition assistance, and data handling follow the signed agreement. A clear exit process should be agreed before ongoing work begins.
Who owns advertising and analytics accounts?
Client ownership is generally preferred for strategic accounts, with role-appropriate access granted to OneZero. Existing account ownership and platform rules must be reviewed during onboarding.
Ask the ownership questions before approving the build.
Bring the current domains, platforms, accounts, licences, data, and internal owners so the proposal can define a clean handover path.