Four steps, and no discovery theatre.
You will know inside half an hour whether this is worth doing, and the report is yours either way. I lead every engagement myself, and bring in engineers I’ve worked with when a job needs more hands.
- 01A call
Thirty minutes on what worries you and what the repository looks like. I tell you whether this is worth doing.
- 02Read-only access
One clone, or I run it on your machine and never take a copy. Air-gapped works.
- 03The report
Scored, prioritised and priced. Yours whether or not anything happens next.
- 04The work
Changes land as reviewable diffs on a branch you own. Nothing merges without your review.
Start at the first. Stop when you have what you came for.
- about a week
Assess
A health check. I scan the whole repository, read the output myself, and walk your engineers through it.
- Scored report
- Findings priced by tier
- A roadmap ordered by risk
- A walkthrough
- two to three weeks
Mend
The assessment, plus the work. Verified changes applied, bounded refactors one function at a time. Architecture stays yours.
- Reviewable, scoped diffs
- Before and after scores
- A record of every change
- Structural findings with evidence
- ongoing
Sustain
It sits in your CI and re-checks every commit. I stay on for the judgment calls and go deep once a quarter.
- Checks on every commit
- Monthly trend reports
- A quarterly deep dive
- Team conventions as rules
Scoped per repository. Every engagement ends with the artifacts in your hands.
Your code, your branch, your call.
Start a conversation- Your code stays inside your perimeter unless you say otherwise.
- Every artifact is a file in your repository.
- Changes land on a branch you own and merge only after your review.
- No lock-in. The engine is open source under Apache 2.0.