Before a platform handover, define what actually transfers
A practical starting point for discussing a website and app project: the available material, account responsibilities and the work after handover.
Start with the intended use
A platform acquisition begins with the work you want the platform to support. Describe the audience, the information people need and the steps they should be able to complete. Keep that description separate from a wish list of features. It gives both sides a concrete basis for reviewing a demonstration and discussing the available project. For Corablanca, the conversation is about the website and app project offered through NEPTOX; this guide does not establish a transfer agreement.
Request an inventory of the actual material
Ask which source files, design material, documentation and project accounts are available for review. A demonstration of a screen is different from confirmation that its underlying service, account or third-party licence is included. Record the purpose of each dependency and the person who will answer questions about it. Do not assume a domain, app-store account, brand right or customer dataset transfers simply because it is connected to a website. Specific ownership and contractual questions need suitable professional review.
Agree what happens after the handover
Identify the work needed before the next release: new branding, content, account configuration, testing or integration changes. Ask who carries out that work, how acceptance will be discussed and who maintains the result afterwards. White label means presenting an adapted product under another business’s brand, but the actual adaptation still needs a defined scope. NEPTOX can discuss an acquisition or white-label direction for Corablanca once the intended use and the available material are understood.
Keep access and recovery practical
A useful handover also explains how the new responsible person manages routine access, support and recovery. Document the providers involved without putting passwords or private access tokens in a public document. Review the provider’s own account and domain requirements before planning a change. This is a practical project checklist, not a legal assessment or confirmation of transfer rights.
Sources and further reading
AI-assisted NEPTOX publication. Sources checked by the editorial automation; no independent specialist review.