Project Handoff
Wrapping up the engagement and giving you everything you need to run the app on your own.
Handoff is the moment the project transitions from "Calda is driving" to "you own it." We do this deliberately, with a single working session where we walk through the deliverables together so nothing is left as tribal knowledge.
What you'll receive
- Source code on your GitHub / GitLab organisation, with Calda removed as an owner (or kept on as a collaborator if you've extended our contract).
- Production credentials moved into your password manager, with Calda's access revoked.
- Design files (Figma) transferred to your workspace.
- Architecture overview document — a single page that explains how the app fits together so a new engineer can ramp up quickly.
- Runbook covering the most common operational tasks (cutting a release, rotating keys, restoring a backup, responding to a Sentry alert).
Credentials and access transfer
We use a structured checklist to make sure every account is moved over cleanly:
Apple Developer & App Store Connect
- Your team transfers the app to its own Apple Developer account (if it currently lives under Calda's).
- Calda is removed from App Store Connect — or downgraded to a read-only role if you've requested ongoing support.
- Signing certificates and provisioning profiles are regenerated under your account.
Google Play Console
- Ownership of the Play Console developer account is transferred (or the app is migrated to your existing account).
- Calda is removed from the user list.
- The upload key — if Play App Signing isn't enabled — is rotated.
Third-party services
For every integration listed in the Integrations section, we walk through the same flow: transfer ownership, rotate keys where it matters, and remove Calda's users.
Support & warranty
Every project ships with a 30-day warranty window after the App Store release. During that period:
- We fix any regressions traceable to code we shipped, at no extra cost.
- Sentry alerts are still routed to our shared Slack channel.
- We answer questions about the codebase within one business day.
After 30 days, you can either:
- Wrap up — at this point, the project is fully yours and the engagement is closed.
- Continue on a retainer — a fixed monthly block of hours for feature work, maintenance, and on-call.
After handoff
A few things to plan for on your side once we step away:
- Keep the runbook up to date. As your team adds infrastructure, add it to the runbook so the next engineer doesn't have to discover it.
- Schedule a quarterly dependency upgrade. Mobile SDKs, RevenueCat, Firebase, and Sentry all release breaking changes a few times a year.
- Plan for the next OS releases. Apple and Google both ship major OS updates each autumn, which usually require small adjustments.
That's it. We're proud of what we shipped together — and you know where to find us if you need anything.