Know what is worth keeping.
Your software may already do valuable work, even when it is difficult to change or a build has stalled. We assess what exists, identify the risks and give you a practical basis for deciding where to invest next.
The initial conversation is free. Technical assessment is a separate paid engagement, with its scope and price agreed before it begins.
The first deliverable is a decision you can use
The assessment examines the agreed codebase, architecture and operating setup. You receive a written account of the system, the material issues found and a prioritised route forward.
It explains what needs attention, why it matters and what further investigation may be necessary. The report is yours to act on whether or not you continue with us.
Example format
Technical assessment · extract from the findings
| Finding | Business effect | Recommended action | Priority |
|---|---|---|---|
| Releases are deployed by hand from one machineConfirmed | Updates depend on one person being available | Script and document the release process | High |
| No automated tests cover checkoutConfirmed | Each change to checkout risks failed orders | Add tests around checkout before further changes | High |
| The search library no longer receives security updatesNeeds investigation | Future vulnerabilities would stay unpatched | Confirm which features depend on it, then plan the upgrade | Medium |
Finding
Releases are deployed by hand from one machine
Confirmed- Business effect
- Updates depend on one person being available
- Recommended action
- Script and document the release process
- Priority
- High
Finding
No automated tests cover checkout
Confirmed- Business effect
- Each change to checkout risks failed orders
- Recommended action
- Add tests around checkout before further changes
- Priority
- High
Finding
The search library no longer receives security updates
Needs investigation- Business effect
- Future vulnerabilities would stay unpatched
- Recommended action
- Confirm which features depend on it, then plan the upgrade
- Priority
- Medium
Keep. Fix. Rebuild.
Keep what serves the business
Retain useful functions and dependencies where they remain suitable. Identify which parts can support the next stage as they stand.
Fix the parts holding it back
Address defects, access problems, fragile connections or release issues that prevent the product from working or changing reliably.
Rebuild where the evidence supports it
Replace components when repair would leave important requirements unresolved. Set out what the change affects, including data, integrations and the people using it.
Make room for improvement while the product is in use
The next stage may begin with tests, documentation or a repeatable release process. Larger changes are broken into reviewable stages, with plans for migration and recovery where needed.
You can see what each stage is intended to achieve and where a decision is needed before more work begins.
Recommendations distinguish confirmed findings from areas that need more investigation. You see the proposed scope and price of the next stage before committing to it.
What do you have access to today?
A product link, a description of the problem and an outline of the available code, hosting and documentation help us scope the assessment. We agree a secure way to access anything sensitive.
The initial conversation is free. Technical assessment is a separate paid engagement, with its scope and price agreed before it begins.