A proper handover
Review the code, database, hosting, domains and third-party accounts. Identify access that depends on a former team member, document ownership and agree how it will transfer.
Someone to call after launch.
An existing platform, a project approaching handover or software that has outgrown its original team. Start by understanding what it needs to stay useful.
Talk through your projectGive the “after” part an owner.
Readiness for real users
Scope the work needed around authentication, privacy, backups, monitoring and documentation. The review distinguishes urgent fixes from improvements and explains any limits in the inherited system.
An ongoing arrangement
Agree a named contact, support hours, response targets, escalation and included maintenance. Hosting, monitoring, security updates, bug fixes and small improvements can be included where specified in the service plan.
Support is an agreed service, not an unlimited promise. Annual budgeting can be discussed for grant-funded work. Response times, after-hours coverage, backups and third-party fees are confirmed in the proposal.
A future beyond the funded project.
For universities and research teams
A research prototype can remain valuable long after the original team moves on. We can review the handover, scope what is needed for launch and propose an ongoing support arrangement that can be considered in an annual budget or future grant application.
The first step is an inventory of the code, accounts and outstanding work. That gives the project owner a concrete basis for deciding what comes next.
Discuss a project handover