Technical assessment service
Independent technical due diligence for software, startups and technology companies based on documented code, architecture, development evidence, dependencies and technical maturity.
Technical due diligence for software and technology companies
A technical due diligence examines the documented technology state of a software or technology product at a defined review date. Depending on scope, the assessment can cover codebase, architecture, repositories, version and release history, development and operational evidence, dependencies, testing and deployment capability, technical risks, data and AI components.
Examination focus
- Software architecture, codebase, module boundaries, interfaces and technical maturity.
- Repository, commit, branch, tag, build and release history.
- Build, test, CI/CD and deployment capability and reproducibility.
- Maintainability, technical debt, dependencies and key components.
- Scaling assumptions, performance risks and technical bottlenecks.
- Development process, technical documentation, knowledge concentration and handover capability.
- IT security and technical controls within the agreed scope.
- Technical provenance and licensing indicators without replacing legal IP or licence evaluation.
- Data and AI components where decision-relevant.
Methodological approach
The review separates the question, subject and system state, reference criteria, technical findings and professional assessment. Software, architecture, data, security and provenance aspects are combined only where they are relevant and technically supported. The general decision-making step of a problem-solving cycle is not equated with the investment decision.
Typical applications
- Financing rounds, participations and technology partnerships.
- Software due diligence in preparation for M&A or investment processes.
- Technical baseline before taking over a product, team or development project.
- Assessment of product, platform or AI maturity from a technical perspective.
- Review of handover capability, key-person concentration and critical dependencies.
- Second opinion on existing technical reports or risk registers.
Technical statement boundary
The report provides an objective technical decision basis and documents substantiated strengths, weaknesses, risks, dependencies, uncertainties and open points. It is not a company valuation, legal/tax/financial due diligence or investment recommendation.
Example scope of an assessment
- Architecture, codebase, repository and technical documentation review.
- Reconstruction of relevant build, test, release and deployment states.
- Assessment of development process, dependencies, maintainability and handover capability.
- Technical review of security, provenance and licence indicators within scope.
- Assessment of decision-relevant data or AI components.
Indicative fee range: approximately €1,800–€4,800 net, depending on system complexity, data volume and report depth. The amount is for orientation only and is not a binding offer.
Related technical knowledge
Constructed case study: technical due diligence
A technical evidence review for software and technology decisions without making the investment decision itself.
Constructed examination scenario: This is a methodological example, not a real mandate, a real court appointment or a report of actual findings.
Diagnosis – determine the actual technology state
Identify codebase, architecture, repositories, releases, deployment evidence, technical documentation, dependencies and relevant data or AI components.
Objectives – define decision-relevant technical questions
Agree the technical criteria, exclusions, evidence requirements and decision-relevant risks to be examined before scoring maturity or risk.
Analysis – test maturity, reproducibility and dependencies
Examine architecture, build and deployment capability, testing, maintainability, security-relevant evidence, knowledge concentration and critical dependencies.
Expert synthesis – technical decision basis
Prioritise substantiated strengths, weaknesses, risks and unknowns. Company valuation, investment recommendation and legal, tax or financial due diligence remain outside scope.
Methodological inspiration: Nicolai Andler, Tools für Projektmanagement, Workshops und Consulting – Kompendium der wichtigsten Techniken und Methoden, 6th revised and expanded edition, Publicis, Erlangen, 2015, ISBN 978-3-89578-453-8. The examination sequence and expert synthesis used here are independently formulated for technical expert work.
Initial technical classification of an enquiry
Before accepting an assignment, the technical question, subject of examination, available records, potential conflicts of interest and the required scope are reviewed. An individual non-binding proposal can then be prepared.
Contact Mathias Ellmann