Keep, fix or redo: the real question
When a project is abandoned, there are two temptations: throw everything away and start clean, or ask the next provider to “just finish it”. Both are expensive when the decision is made blind. Starting from scratch throws away what you paid for. Finishing on a shaky base means building on sand.
Our audit settles it, part by part. We look at the code structure, the extensions chosen, the database, security and the gap with your specification. Each part gets a clear verdict: keep as is, fix, or redo. You see the cost of each option before you decide.
What we check in the existing work
- The code: readability, platform standards, changes made to the core instead of in separate modules.
- Extensions: versions, whether licences were paid, compatibility with each other and with the platform version.
- The database: structure, test data to clean up, content already entered that must be kept.
- Security: access left open, shared passwords, known vulnerabilities.
- The specification: features delivered, partial or missing, for a factual status report.
Delivery you can watch progress
An abandoned project understandably leaves some mistrust. So we work in the open: the code is in a repository in your name from the first day, progress is shown at each review on a staging site, and the balance is only due after a demo of the finished project.
Once the site is live, it keeps evolving. We can maintain it, or hand you everything needed to give that job to someone else.