Code audit for a codebase nobody owns.
Three to five days of forensic reading, then a costed roadmap. You find out what is solid, what is rotting, and what each fix costs before you commit to anything.
The symptom
"The only person who understood the codebase left in April."
You get your own codebase back in writing: what is solid, what is rotting, what it costs to fix. A week of forensic reading, then a costed roadmap any developer - me or yours - can execute.
What lands in your accounts
How it runs
Read it cold
Repo, deploy config and database. What the code cannot answer goes in the report as an open risk, never as a guess.
Measure, don't opine
Bundle weight, Core Web Vitals, dependency and security risk, accessibility pass. Numbers you can re-run yourself.
Call every area
Keep, refactor or rewrite, each with a cost and a reason, so you can argue with the reasoning instead of a vibe.
Hand you the roadmap
Ordered, costed, risky items flagged, written for whoever executes it. Hiring me for the fixes is optional.
The terms
Before you ask
Can you read a codebase cold, with nobody left to ask?
That's the job. I work from the repo, the deploy config and the database; what the code can't answer goes in the report as a risk, not a guess.
Do you rewrite it, or just tell us it's bad?
Neither alone. Every area gets a keep / refactor / rewrite call with a cost and a reason, so you can argue with the reasoning instead of a vibe.
Can our own developers execute the roadmap?
It's written for them: ordered, costed, risky items flagged. Hiring me for the fixes is an option, not the point of the document.
How fast do we know if it's salvageable?
Three to five days for the full read. If it is structurally doomed you hear that on day two, not at the end of the week.