Technology due diligence
Provides an evidence-based view of a target company’s security and compliance posture, highlighting control gaps and inherent risks that inform investment or acquisition decisions.
— Product & Tech
Assesses security controls and supporting evidence against relevant compliance frameworks, producing a risk-led remediation plan or an assurance summary grounded in documented findings.
2–3 weeks → ~25 minutes
For a typical multi-document review workflow
No coding required
— USE CASES
Provides an evidence-based view of a target company’s security and compliance posture, highlighting control gaps and inherent risks that inform investment or acquisition decisions.
Maps available evidence to relevant framework requirements and identifies gaps that need attention. Produces a remediation plan where material risks undermine readiness.
Tests vendor security claims against questionnaire responses, supporting reports and public breach or regulatory history. Gives advisers a documented basis for risk discussions and assurance judgements.
Produces an assurance summary where assessed risk is low, with clear links to supporting evidence and remaining gaps. Keeps the conclusion proportionate to what the available material substantiates.
— HOW IT BEHAVES
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
Risks are sorted into your categories using the same rules each time, which is what makes a large volume of risk registers, controls and policy documents readable.
Each risk is assessed against criteria you control and weight, so the same standard applies to every risk in the risk universe in scope.
Every risk is captured in the same field structure, so records drawn from different documents and sources stay comparable.
Dates and sequence are lifted out of risk registers, controls and policy documents into a timeline, exposing the tenure, gaps and overlaps that prose hides.
All of your risk registers, controls and policy documents is processed as one set, so patterns across documents surface instead of being read one file at a time.
Current external sources on the risk universe in scope are researched during the run rather than recalled from training data, and every source travels with the output.
Security and compliance reviews often draw on fragmented reports, questionnaire responses and incident records, making it difficult to distinguish evidenced controls from unsupported claims. Technology due diligence is the typical trigger — provides an evidence-based view of a target company’s security and compliance posture, highlighting control gaps and inherent risks that inform investment or acquisition decisions. Done properly it is defensible; done at pace it becomes a judgement call nobody can retrace. And "properly" usually means 2–3 weeks of manual work.
Here the same job runs as a Skill. Your material goes in; control, evidence and gap mapping against relevant frameworks comes out, alongside inherent risk assessment. 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. The practical effect: 2–3 weeks of manual work becomes a ~25 minutes run, held to an identical standard on the tenth engagement as on the first.
Security & compliance posture scan 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.
Maps a target’s data and intellectual property assets, clarifying ownership, licence obligations and portability constraints to support migration and exit planning.
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 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.