How do I hand over my AI-built app to a professional?

Handing over your app is a moment of trust, and it can be done in a way that keeps you safe rather than exposed. The aim is to give a professional everything they need to help while keeping control in your hands, so that if the relationship ever ends, you can cleanly close the door. Here is how to do it well.

Step by step

1. Give the picture before the keysStart by sharing understanding, not access. Walk them through what the app does, where the code and data live, what it connects to, and what worries you, ideally over a screen-share so they see it in motion. A good professional wants this context first anyway, because it makes their work faster and their questions sharper. Handing over a clear picture before any credentials means the early conversation can happen with almost no risk, and it lets you judge how they engage before you grant them anything sensitive.
2. Grant access through proper, revocable channelsWhen they do need access, add them as a collaborator on your accounts with defined permissions you can withdraw, rather than sharing your own login. Most platforms let you invite someone with read-only or limited rights and remove them in one click later. Give the least access that lets them do the job at hand, and widen it only as needed. Never gather up passwords and secret keys into an email or chat message. Controlled, revocable access is the difference between lending a key and handing over the deed.
3. Never send raw secrets, and reset them afterwardsSecret keys and passwords should not travel through email or messaging, and a trustworthy professional will not ask them to. Where they genuinely need a secret, use the platform's own secure sharing or set it directly in the system yourself. Then, once the work is done or if the relationship ends, treat the secrets as needing a refresh: regenerate keys and passwords so that any access granted during the work is cleanly closed. This one habit means a handover never leaves a permanent open door behind it.
4. Put the plan and the ownership in writingBefore real work begins, agree in writing what they will do, roughly what it will cost, and, crucially, what you will own at the end. A short, plain-language agreement protects both sides and forces the ownership question into the open early, where it belongs. It need not be a legal epic; it needs to say who holds the code, who controls the data, and how the work is paid. Clarity here prevents the most painful handover disputes, which are almost always about ownership no one wrote down.
5. Keep your own copy and your own controlThroughout, make sure you retain your own access to everything and a copy of anything you cannot afford to lose. You should never be in a position where the professional holds the only keys to your own system. Keep the domain in your account, keep ownership of the code repository, and keep a backup of your data. A good professional expects and supports this, because it is how responsible handovers work. If someone resists you retaining control of your own system, that resistance is itself worth pausing on.