Start with the actual project state
I review source code, documentation, dependencies and operations. I check whether the project can be built, run outside production and changed safely.
We identify business-critical features and current user problems. For an early AI-built prototype, see AI application completion.
What a handover needs
- The source repository and available documentation.
- An overview of hosting, databases, domains and external services.
- Confirmation of rights to use and modify the code.
- Deployment and backup procedures, plus known operational problems.
- Contact with the previous maintainer where available.
When something is missing, I explain the impact and options for recovering it. Access is transferred through an agreed method and limited to the current phase.
A plan for repairs and gradual improvements
The assessment provides findings, priorities and unverified areas. I identify what needs attention before the first change and what can wait.
I compare retaining the solution, changing selected parts and replacing them. For data or hosting migrations, I prepare verification and rollback procedures.
Cost and ongoing support
The initial review has its own scope and deliverable. Repair estimates follow the code review, access checks and verification. I identify unknowns as assumptions that may affect the price.
After handover we can work on specific changes or agree ongoing maintenance. Responsibilities for hosting, backups and external services are defined explicitly.