Service
Find the path from a stalled build to a working product.
Review an inherited codebase, investigate the failures, and decide what to repair before committing to a rebuild.
The problem
What this actually looks like
The happy path may work while permissions, data handling, integrations, or deployment still prevent release.
A useful next step is a diagnosis of the specific blockers and the decisions needed to move forward.
Deliverables
What you get
Concrete artifacts, not activities. Everything below is something you can point at and say you received it.
- Assessment of the agreed problem areas
- Prioritised repair recommendations
- Repair and rebuild options
- Implementation scope for the chosen path
Timeline
How it works
Ranges, not best cases. The dates below are what it usually takes, including the week something goes wrong.
- 01Understand
Describe the blocker
Collect known failures and the result the product needs to achieve.
- 02Inspect
Review the existing system
Examine the agreed code, architecture, dependencies, and deployment path.
- 03Decide
Compare the options
Explain what can be retained and what needs to change, with assumptions made explicit.
- 04Deliver
Work through the priorities
Agree an implementation scope and verify the behavior that was blocking progress.
Approach
Our approach
A rebuild is one option, not the starting assumption. The review should distinguish code that is useful from the decisions and defects that block the product.
What we avoid
- Recommending a rewrite without examining the existing system.
- Quoting a rescue from screenshots alone.
Engagement
Engagement options
Shape
Engineering review, then an agreed plan
Pricing
Scoped quote
Begin with the codebase, known failures, and the decision you need the review to support.
View engagement optionsFAQ
Frequently asked questions
Does a stalled build need a full rewrite?
That depends on the system. A review can compare targeted repairs, partial replacement, and rebuilding with the tradeoffs explained.
Can you review a build made with AI tools?
Yes. The relevant questions are how the resulting application behaves, how its data and permissions work, and how it can be tested and operated.
Do we need to commit to implementation first?
No. Discuss the review scope and the decision it needs to support before considering a subsequent build.