The policy your firm has to write anyway.

• 01

  Tool inventory and shadow AI

  What's actually in use — including the browser extensions and personal accounts — before writing rules about it.

• 02

  Confidentiality control design

  What may be pasted where, which tools have acceptable terms, and how client-imposed AI restrictions are tracked per matter.

• 03

  Client-facing AI disclosure

  A position on disclosure and billing for AI-assisted work, before a client's outside-counsel guidelines force one.

• 01

  Every claim carries its source

  Answers return the clause and the document, and refuse when retrieval is weak. An unsourced legal answer is worse than no answer, and the eval suite scores it as a failure.

• 02

  Privilege and confidentiality are architectural

  Matter-level access control in retrieval, deployment inside your tenancy, and no training on your documents — stated in the contract, enforced in the build.

• 03

  The lawyer signs, always

  The system drafts, redlines and flags. Advice and filing stay with an admitted practitioner, and no pathway lets generated text reach a counterparty unreviewed.

1. 1

   Stakeholder interviews

   30–45 minutes with each executive and team lead. We surface the real bottlenecks (not the ones the deck says).

2. 2

   Use-case pipeline

   Score 20–40 candidate AI use cases on impact × feasibility × strategic fit. Pick the top 3 with quantified ROI.

3. 3

   Build vs buy

   Honest answer for each pillar — sometimes the right move is Notion AI or a Zapier flow, not a bespoke build.

4. 4

   Governance framework

   Policy, approval workflow, prompt-injection / PII / IP guardrails. Aligned with your compliance posture.

5. 5

   90-day plan

   Quarter-by-quarter roadmap, hiring plan, budget, vendor selection, and KPIs the CFO will actually accept.

• iManage & NetDocuments
• SharePoint
• DocuSign & Adobe Sign
• Contract lifecycle management tools
• Microsoft 365 & Word add-ins
• Postgres with matter-level access control

FAQ

AI governance for legal teams: your questions.

• Our partners disagree about whether to use AI at all.

  That's typical, and the inventory usually settles it — the tools are already in the building. A policy that acknowledges reality gets followed; a ban gets routed around and produces the confidentiality incident it was meant to prevent.

• Do you write the client-facing language?

  We draft it; your risk partner owns it. It normally sits alongside outside-counsel guidelines rather than as a standalone policy.

• Is this just a deck?

  No. Every strategy engagement ships at least one working artifact — a costed roadmap, a governance template ready for legal, or a vendor negotiation outcome. Decks alone are useless.

• Do you work with non-technical executives?

  Yes — most of our strategy work starts with non-technical leaders. We translate between board-room and engineering-room.

• RAG for legal documents and precedentRetrieval across matter documents, executed contracts and internal know-how — every answer returning the clause, the document, and the matter it came from.Read
• AI agents for contract reviewAgents that triage incoming contracts, redline against your standard positions, and route to the right reviewer with the deviations already summarised.Read

• AI governance for financial servicesModel inventories, risk classification, evaluation policy and human-oversight design — written to survive an internal audit rather than a conference talk.Read
• Healthcare AI governance and readinessUse-case triage against clinical risk, a data-handling design that survives a HIPAA or DPDP review, and an oversight model your clinical governance body will actually accept.Read
• AI governance for insurersRisk classification, model documentation and oversight design for insurance use cases — built around what a complaint, an audit or an ombudsman review will ask for.Read