The developer disappeared. What should you recover first?
You may have a running website, a folder of code or an unfinished preview, but no clear handoff. Start by finding out what the business has and what it needs to run the project.
List the accounts the project depends on
Start with the domain name, hosting, source-code account, database and outside services. Record who controls each account, which ones the business can access and any renewals that are coming up.
If access is missing, use the account owner or the provider’s recovery process. If the agreement leaves software ownership or usage rights unclear, get the appropriate advice before the affected work proceeds.
The first inquiry does not need passwords, recovery codes or private customer information.
Find the source files and instructions
Look for the source code, version history, setup instructions and release notes. Include any files supplied separately, such as uploads or custom design assets. A source archive can still be useful even when the full history is unavailable.
The newest-looking folder may not be the version running on the live system. Comparing the available code with the live version helps prevent a useful working release from being overwritten by unfinished work.
Check whether the project can run elsewhere
A new developer needs to know how to build and run the software on a separate test system. That includes the software versions it needs, the services it connects to and the names of required configuration settings. Secret values should be handled through an agreed private channel.
Test work should use appropriate test data and avoid live customer emails, charges or updates to connected business systems. A successful build is a useful starting point; important customer and staff tasks still need checking.
If it was built with an AI coding tool
Include the exported code and any instructions for running it outside that tool. A screenshot or working preview does not by itself show whether the complete application can be maintained. The review still needs to establish which code runs, which services it needs and which tasks work.
Choose the first business task to review
Describe the task that matters most: a customer signs in, a booking is recorded, a member pays or a report is produced. Explain what currently happens and what should happen instead. Include a deadline and any information that must be preserved.
This makes the first review more useful than a general request to “finish the app.” It can identify a repair, a completion stage or the questions that must be resolved before estimating further work.
Use what you know to start a conversation
The recovery inventory worksheet helps list missing pieces. The repair-or-rebuild guide explains the main options once the project is understood.
Read what a takeover assessment can include or tell Faith Forge Labs where the handoff stopped. You can get in touch before every file or account has been recovered.