Yes. Inherited systems are common, especially when the original developer has moved on. We start with an assessment of the code, hosting, access, backups, dependencies, and known issues, and we document what we find.
Next comes stabilization. We secure access, confirm backups restore, update critical dependencies, and fix urgent problems. Only then do we take on new features or ongoing operations, because building on an unstable base wastes money.
You will receive a written summary of risks and recommendations, so you can make an informed decision about whether to maintain, improve, or replace the system.