Why this matters

Most handover problems show up months later. The developer has moved on, something breaks, and the founder finds out that the app runs on an account they cannot log in to. Everything on this list is cheap to hand over at the end of a project and expensive to recover afterwards.

This is the list I hand over on my own projects. Use it with any developer or agency.

1. The code, in a repository you own

  • The full source code in a GitHub (or GitLab) organisation that belongs to your company, not in the developer's personal account.
  • The commit history, not a zip file. History is how the next developer finds out why something was built the way it was.
  • A note of any open-source licences that come with the libraries used.

2. The accounts, in your name

Every service the app depends on should be an account you created, on your card, with the developer invited as a member:

ServiceWhy you should own it
Hosting and databaseThe app keeps running if the developer leaves
Domain and DNSNobody else can move or lose your address
Apple Developer and Google PlayStore listings cannot be transferred quickly, and reviews are tied to the account
Email, payments, analytics, error monitoringCustomer data and money flow through these

Ask for a short table of these services with what each one costs per month, and what makes that cost go up.

3. Secrets, shared safely

API keys and passwords should reach you through a password manager or an expiring secret link, never through chat or a shared document. Once the handover is done, rotate anything the developer no longer needs, and remove their access to accounts they do not support.

4. Three documents

  1. A setup guide. How a new developer gets the project running on their machine.
  2. A release guide. How a new version goes live, with a backup step before it and a rollback step if it goes wrong.
  3. A user or admin guide. How your team does the everyday things: add a user, add a customer, change a setting.

A good test: could someone who has never met the developer release a small fix using only these documents?

5. A backup before the first real release

Before real customer data goes in, confirm that backups are switched on and that someone has restored one at least once. Some hosting plans have no backups at all on the free tier.

6. What happens after

Get these in writing before the final payment:

  • Warranty. How long the developer fixes defects for free, and what counts as a defect.
  • Support. How fast they reply, and what happens out of hours if the app is down.
  • Changes. The hourly rate or retainer for new work, and that new features are quoted before they start.
  • Test data. That test versions and any copies of your data on the developer's accounts are deleted.

The order I use

On my own projects, the code and the production setup move to the client's accounts as part of the final milestone, and ownership of the work transfers on the final payment. You see the product working in weekly demos long before that, so nothing about the handover is a surprise.

Book a 30-minute call if you want a project run this way, or a second opinion on a handover you have just received.