Who this is for
You own software you can’t fully see into.
The original developer is gone, and nobody left can explain the parts they wrote.
An agency delivered it and left. Documentation, if it exists, no longer matches the code.
The team that wrote it has turned over. It runs, but nobody can say what’s fragile.
The deliverable
A written report you keep, whatever happens next.
Six sections. The last one is the point: most owners in this position have never been told straight whether their system is salvageable.
How the system is actually built, not how a diagram says it is.
Single points of failure, security exposure, what breaks first and why.
End-of-life, unpatched and abandoned packages, named and versioned.
What only one person understood, and what happens now they’re gone.
Ordered by consequence, with rough effort sizing against each item.
Maintainable as-is, needs work, or needs replacing, and what doing nothing costs you.
What you hand over
Access is the price.
Read-only access to the repository. Nothing else, and no invoice. We have a mutual NDA ready and will sign yours instead if you prefer.
Scope and questions
The deliverable is the deliverable.
“While you’re in there, could you also…” is the paid engagement. Saying so up front is why 2–3 days is a real number.
Because money is the wrong filter at first contact. Read-only access filters better: it means there is a real system and someone with the authority to hand it over.
Takeover work means you read whatever the system already runs on. Django and PostgreSQL are in production across every system we’ve shipped; NestJS is almost entirely inherited.
No. The report is yours, including the parts that say the work is smaller than you feared. Some readers hand it to their existing developer and we never hear from them again.
Shamim Ferdous, who founded CodeNine and still writes production code, and Shofiqul Islam Miraz, our technical lead. No contractors, and no salesperson between you and them.
Sample
Read a real one before you grant anyone access.
A genuine review of a client system, run end to end and then redacted. Not a template and not a mock-up.
Report sent
Check your inbox.
Sent. The redacted sample report is attached to the email now in your inbox.
Already requested
It’s already there.
That address has already requested the sample. Check that inbox for the original email.
Request a review
Tell us about the system.
You write in. We reply the same working day with an NDA.
Signed both ways, you grant read-only repo access.
2–3 working days. The report arrives written, not presented.
One call to walk the verdict, if you want it. You revoke access.
10:00 – 19:00 UTC · 11:00 – 20:00 CET · 06:00 – 15:00 US Eastern
Submission received
It’s with us.
Received. One of the two of us reads these, and you will have an NDA back the same working day.