Architecture
Boundaries, state ownership, coupling and whether the design can absorb the change it is expected to carry.
Independent advisory / Services
Technical Due Diligence
Independent technical assessment of architecture, engineering, platform, reliability, security and delivery risk for strategic decisions.
What the technology really is
Due diligence should establish the difference between stated capability and observable evidence.
Architecture, operational reality, delivery capability and dependency are examined as one picture. Conclusions stay technical and evidence-based; legal, financial and investment advice is out of scope.
Assessment lenses
A rigorous, scoped technical assessment.
Depth on each lens follows the decision being informed. We do not perform a uniform checklist irrespective of what matters.
Engineering quality
How the code is structured, tested, reviewed and released — and what that implies for future change.
Platform and cloud
Infrastructure design, provider dependency, environment management and the cost of the operating model.
Reliability and operations
Incident history, observability, recovery, support burden and resilience of critical paths.
Performance and scale
Whether current infrastructure and data paths support expected growth without assuming unverified figures.
Data
Ownership, quality, lineage and the controls around data the business depends on.
Security posture
Architecture and engineering controls within the agreed technical scope, without claiming certification.
Delivery and dependency
Delivery process, knowledge concentration, third-party reliance and single-person exposure.
Evidence and uncertainty
Every statement carries its confidence.
Unknowns are findings. A report that presents everything with equal certainty is not useful to a decision maker.
| Theme | How it is reported | How it is used |
|---|---|---|
| Verified evidence | Observed directly in systems, code, configuration or operating records. | Carries weight in the conclusion without qualification. |
| Management assertion | Stated by the organisation but not independently confirmed. | Recorded as asserted, and clearly labelled as such. |
| Incomplete evidence | Partially available, contradictory or time-limited. | Presented with the gap named rather than filled with inference. |
| Professional judgement | An assessment that follows from evidence but is not itself provable. | Offered as judgement, not as finding. |
| Unknown | Not established within the agreed scope or timescale. | Reported as a question requiring a decision, not hidden as a gap. |
This distinction is what allows the reader to weigh the conclusion rather than accept or reject it wholesale.
Technical debt that matters
Separate constraint from cosmetics.
Not all debt is equal, and treating it as one number misleads the decision.
We distinguish debt that constrains delivery, debt that creates material risk, and debt that requires future investment from improvements that are merely desirable. The last category is named so it can be deprioritised honestly.
- Constrains delivery
- Creates material risk
- Requires investment
- Desirable only
How the assessment runs
Direct examination within an agreed scope.
Timeframes and access are agreed before work begins, and any limitation is recorded in the report.
- 01
Frame
Agree the decision being informed, the technical scope and the access available.
Agreed scope
- 02
Examine
System, code, platform, operating data and delivery process reviewed directly where access allows.
Raw findings
- 03
Test the important claims
Concentrate on the claims the valuation or decision most depends on.
Tested assumptions
- 04
Quantify
Express findings as material risk, future investment or constraint on the outcome.
Material findings
- 05
Report
A technical readout distinguishing evidence, assertion and judgement.
Leadership readout
When to engage
Decisions that benefit from independent technical assessment.
Investment
An investment or acquisition decision
Where the condition of the technology materially affects the case.
Partnership
A technology partnership or major supplier decision
Where capability claims need independent technical testing.
Dependency
A strategic dependency on one platform or product
Where the real cost of exit is not yet understood.
Programme
A programme whose technology assumptions are untested
Where delivery confidence rests on architectural claims that have not been examined.
Transition
An estate about to be taken on
Where operating responsibility is changing hands and the condition must be established.
Remediation
A remediation case that needs quantification
Where the organisation needs a defensible view of future technical investment.
What the engagement can produce
A technical position leadership can rely on.
Independent of the transaction. We are not an adviser to either party and do not provide legal or financial advice.
- 01Technical assessment within agreed scope
- 02Material-risk summary
- 03Architecture and engineering findings
- 04Debt and investment themes
- 05Operational and delivery findings
- 06Dependency and concentration analysis
- 07Priority questions for management
- 08Leadership readout
Engagement enquiries
Discuss a due-diligence requirement.
Tell us the decision, the timescale and what access is available. We will be explicit about what can be established and what cannot.
Useful links
Confidential by default. Conclusions remain technical and independent of the transaction.