Booking new projects

EndekoApp

What a proper handover package contains

Whether you keep working with us or not, you should be able to hand the product to another team tomorrow. This is the checklist we use to make that true.

Written by
Delivery team
Published
24 June 2026
Reading time
5 minutes
A single key on a wooden table

Good studios plan for the day they leave, even when they expect to stay for years. It keeps us honest, and it protects clients from the situation many of them come to us from: a product nobody fully understands, built by a team that is gone.

Everything lives in your accounts

Repositories, cloud resources, app store listings, domains, analytics and third-party services are created in the client's accounts from day one. We are invited as members. Nothing needs to be transferred at the end because nothing was ever ours.

The package itself

  • Architecture overview: services, data flows and key decisions with their reasons.
  • Setup guide that gets a new developer from zero to a running app in one day.
  • Runbooks for deployments, rollbacks, incidents and common support tasks.
  • A list of every external service, what it does and who pays for it.
  • Known issues and technical debt, written honestly and prioritised.
  • Design files and the component library, matched to the code.

None of this is written in a rush at the end. It grows with the project, reviewed in the same pull requests as the code it describes.

Keep reading

Have a product in mind?

Send us a short brief, a sketch or a link to what exists today. You will get a reply from an engineer, not a salesperson.