Consulting
Technical Due Diligence
An independent assessment of a target's software, team and technical debt, written for an investment committee rather than for engineers.
In short
Assessing software before you buy it.
What we deliver
- Codebase, architecture and infrastructure assessment
- Team capability and key-person risk
- Technical debt quantified as remediation cost
- A report written for non-technical decision-makers
A good fit when
- An acquisition or investment is being considered
- A vendor's technical claims need independent checking
- Post-deal integration cost is unknown
Technologies and methods
Chosen for each project, to fit your systems and your team.
- Code audit
- Cost modelling
- Reporting
How we deliver
From first conversation to production.
Four stages on every engagement, scaled to the size of the project.
- 1
Understand
Clarify the users, goals, constraints, and current systems.
- 2
Plan
Map the main components, data, and integrations before implementation.
- 3
Build
Develop and review the work in small, testable increments.
- 4
Prepare
Plan deployment, operations, documentation, and ownership.
More in Consulting
- Technology ConsultingAn engineering opinion, in writing.
- Transformation ProgrammesSequencing a multi-year change realistically.
- Solution ArchitectureDecisions recorded with their reasoning.
- Fractional CTOSenior technical judgement, part time.
- Product StrategyWhat to build next, and what to stop.
- Technology SelectionComparing suppliers on stated criteria.
Prefer to talk it through?
A private consultation, 30 minutes with the founder, in your time zone.
Interested in Technical Due Diligence?
Tell us what you are working on. We start by understanding the problem, the people, and the systems involved.