Technology due diligence
Clarifies which data and intellectual property assets the target owns, which it licenses and where rights remain uncertain. Gives advisers a focused view of dependencies that may affect deal assumptions.
— Product & Tech
Maps a target’s data and intellectual property assets, clarifying ownership, licence obligations and portability constraints to support migration and exit planning.
1–2 weeks → ~15 minutes
For a typical multi-document review workflow
No coding required
— USE CASES
Clarifies which data and intellectual property assets the target owns, which it licenses and where rights remain uncertain. Gives advisers a focused view of dependencies that may affect deal assumptions.
Identifies restrictions on moving customer data and transferring licensed code across systems or organisations. Provides an evidence base for assessing migration scope and constraints.
Highlights assets whose ownership or transfer rights may complicate a sale or separation. Gives the advisory team a concise risk list to inform exit planning.
Researches obligations attached to named third-party licences and connects them to the relevant assets. Makes contractual dependencies easier to assess alongside technical ones.
— HOW IT BEHAVES
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
Every decision is captured in the same field structure, so records drawn from different documents and sources stay comparable.
All of your governance and authority documentation is processed as one set, so patterns across documents surface instead of being read one file at a time.
Current external sources on the decision set in scope are researched during the run rather than recalled from training data, and every source travels with the output.
Findings on the decision set in scope are written up as a document that reads like professional output, with each claim tied back to a decision.
A target’s systems can depend on data, code and intellectual property that it does not fully own or cannot freely transfer. Technology due diligence is the typical trigger — clarifies which data and intellectual property assets the target owns, which it licenses and where rights remain uncertain. Gives advisers a focused view of dependencies that may affect deal assumptions. Get it right and the conclusion holds up in the room; get it rushed and it gets picked apart. Either way it costs roughly 1–2 weeks of experienced attention.
As a Skill, the work is already sequenced. You bring the evidence, and the run produces data and intellectual property asset register plus system-to-data mapping with supported business decisions. The judgement is built in — how items are broken up, what standard they are held to, and where the run stops for a human review. Net effect: 1–2 weeks down to ~15 minutes, no drift between runs, and every conclusion traceable back to the evidence behind it.
Data & IP asset map exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.
Assesses a reported vulnerability against severity scoring, real exposure and the criticality of the affected asset, then returns a governed remediation decision — patch now, take it in the next cycle or formally accept the risk — with the reasoning recorded and a security lead sign-off before work is scheduled.
Builds a complete inventory of the technology estate — every system with its vendor, purpose, integrations, hosting and build-or-buy status — and flags where concentration, lock-in or vendor viability creates risk.
Assesses security controls and supporting evidence against relevant compliance frameworks, producing a risk-led remediation plan or an assurance summary grounded in documented findings.
Assesses infrastructure headroom against documented peak demand, projects the first constraints at 2× and 5× load, and identifies the bottleneck to prioritise before growth puts service reliability at risk.
Tests product roadmap commitments against engineering capacity, delivery history and dependencies to give investment committees a defensible view of what is likely to ship within twelve months.
Reviews data rights, AI use and model controls against governance maturity, producing a deal-risk memo or readiness summary that clarifies exposure and its implications for the transaction.