Codebase audit
Read every meaningful module. Map dependencies. Identify load-bearing patterns and brittle ones.
// architecture review
Architecture review, written down.
Review work for engineering leaders evaluating their own systems pre-fundraise, pre-scale, or pre-rebuild. We read the codebase, talk to the team, and write down what we find.
// where teams get stuck
You know there's tech debt. You don't know where the bodies are.
- A codebase you inherited and need to defend in a fundraise.
- Engineers leaving and taking institutional knowledge with them.
- A roadmap that depends on assumptions nobody's tested.
- A vendor pitch that says "trust us" with no evidence.
// what's included
What you get.
Team interviews
Talk to engineers about what scares them. The map of fear is usually more accurate than the map of features.
Risk register
What breaks, when, and what it costs. Scored by likelihood and impact.
Prioritized roadmap
What to fix first, what to leave alone, what to rebuild. With sequencing rationale.
Written report
PDF you can hand to your board, your investors, or your next CTO.
// how we work
Three phases. Confidential.
01 · Calibrate
NDA. Repo access. Written scope.
02 · Review
Codebase audit, team interviews, findings memo mid-week.
03 · Deliver
Final report. Walkthrough. Optional pair-programming follow-up.
// common questions
What teams ask before signing.
Architecture, dependencies, test discipline, deploy pipeline, security defaults, scaling assumptions.
Standard NDA. Findings are yours. We never name clients without permission.
Optional. The review is the deliverable. A pair-programming follow-up is scoped separately if you want it.
Scoped per codebase. We share the timeline in the written proposal after the discovery call.
Scoped per review. Pair work billed separately. We send a written proposal after the discovery call.