Repeatable client analysis
Run the same structured analysis for every client or business unit so quality no longer depends on who picked up the work.
— Product & Tech
Reads data-sharing and customer agreements, AI/model inventory and documentation, governance policies and any DPIA / model risk assessments.
2–3 weeks → ~25 minutes
For a typical multi-document review workflow
No coding required
— USE CASES
Run the same structured analysis for every client or business unit so quality no longer depends on who picked up the work.
Turn raw source material into a working draft in minutes and spend your time on judgement instead of assembly.
Produce the same shape of output each cycle so movement is measurable rather than re-argued.
— HOW IT BEHAVES
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
Decisions are sorted into your categories using the same rules each time, which is what makes a large volume of governance and authority documentation readable.
Each decision is assessed against criteria you control and weight, so the same standard applies to every decision in the decision set in scope.
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.
Thin cases and strong cases among your decisions are handled differently by design, based on what the analysis actually found.
Data, AI & technology governance review is routine in name only: the inputs are messy, the standard is unwritten, and two people rarely reach the same answer. Repeatable client analysis is the typical trigger — run the same structured analysis for every client or business unit so quality no longer depends on who picked up the work. 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.
As a Skill, the work is already sequenced. You bring the evidence, and the run produces a structured, review-ready deliverable plus a traceable record of what informed each conclusion. The criteria, ordering and review points that make the answer trustworthy are encoded in the Skill itself — which is the difference between a structured method and a prompt someone pastes in. 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.
Data, AI & technology governance review 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.
Product roadmap realism check
Reads the roadmap, the backlog, engineering capacity data and shipped-on-time history. Extracts committed items and timelines, computes available capacity against claimed scope, scores roadmap realism, and flags items with no owner or no dependency coverage.
Tech stack & architecture inventory
Reads the target's technology documentation, architecture diagrams and vendor list, extracts every system with its vendor, purpose, integrations, hosting and build-or-buy status, then researches each vendor's viability, ownership changes and end-of-life risk.
Security & compliance posture scan
Reads pen-test and security review reports, SOC 2 / ISO evidence, vendor security questionnaire responses and the incident log.