By Steven R. Combs, Co-Founder and Principal, Cocha Technology Inc.
Cocha Technology works with law firms on governance and pilot readiness for Claude Enterprise rollouts. On the two engagements below, we designed the controls and helped each firm’s team implement them: pilot boundaries, admin roles, connector posture, personal accounts and monitoring. Both clients are anonymized because of NDAs, so this page describes scope and Cocha’s role, not the firms. If you want to know whether work like this fits your firm, start with the free AI Readiness Snapshot.
Each law firm Claude Enterprise case study below says what Cocha was engaged to do and where its role stopped.
| Client A | Client B | |
|---|---|---|
| Client type | A large Canadian law firm | An Atlanta-based Am Law 200 firm |
| Platform | Claude Enterprise, net-new rollout | Claude Enterprise and Claude Cowork |
| Cocha’s role | We designed the controls and helped the firm’s administrators implement them. | We designed the controls and helped the firm’s engineers implement them. |
| Scope areas | Governance framework, console roles, personal account migration plan | Current state assessment, secure launch plan, client-matter data boundary |
| Also in scope | Connector and MCP evaluation, monitoring plan, pilot criteria | Pilot acceptable use policy, risk register, go or no-go recommendation |
| Status | First-phase work delivered. Pilot of 20 attorneys launched. The firm plans to expand to more than 100 users in January. | First-phase work delivered. Pilot launched. Cocha engaged for a second-phase assessment and ongoing change monitoring. |
The firm was bringing in Claude Enterprise as a net-new platform. The first phase followed one rule: settle governance before access goes past an initial pilot group. The firm’s administrators would carry out the changes in the Claude console, with Cocha’s help.
Cocha designed the controls for that first phase and helped the firm’s administrators implement them. The scope included:
Cocha’s first-phase work was delivered and the pilot launched with 20 attorneys. The firm plans to expand to more than 100 users in January. That expansion is the firm’s plan. It hasn’t happened yet, and it isn’t a Cocha result.
Personal accounts need their own line. A firm can buy Claude Enterprise and still have lawyers working in personal Claude accounts, and the enterprise agreement does not protect work done outside the enterprise organization. I wrote about that in my ILTA article, Crawl, Walk, Run: A Practical Way to Deploy Claude Enterprise in a Law Firm. Planning that move was part of the first phase for exactly that reason.
Cocha designed the controls and helped the firm’s administrators implement them in the console. Several things sat outside this scope and were left for later phases: firmwide production rollout, full user migration, SSO and SCIM execution, endpoint and data loss prevention builds, network egress controls and AI gateway work.
Cocha publishes this as an engagement summary, not a direct quotation. Client feedback, paraphrased: Cocha brought considerations into the rollout that the team had not identified.
No adoption figures, time saved, cost or incident data. The pilot size and the January plan belong to the firm. Nothing here describes the firm’s identity, endpoint, DLP or network controls, which sat outside the first phase.
The firm wanted Claude Enterprise and Claude Cowork in front of a defined pilot group. The scope put the weight on what to keep switched off at launch.
Cocha designed the controls for a secure launch of the pilot and helped the firm’s engineers implement them. The scope included:
Cocha’s first-phase work was delivered and the pilot launched.
Cocha was then engaged for a second-phase hardening assessment and a prioritized action plan. It covers user lifecycle provisioning, blocking personal accounts, sending telemetry to the firm’s security monitoring, and data security alignment. It also covers endpoint data loss prevention, connector and MCP governance, and outside counsel guideline governance for AI on client work. It is an assessment and an action plan. It is not an implementation.
Cocha was also engaged to develop a repeatable process for vetting first-party and third-party MCP servers, written for the firm to reuse. And Cocha was engaged to provide recurring monitoring, reporting and advisory support for the firm’s Claude Enterprise environment. That includes a weekly impact-rated change digest, usage and settings review, change review meetings, and monthly cost, security and adoption reports.
Cocha designed the controls and helped the firm’s engineers implement them. The risk calls were the firm’s, recorded in a register the firm formally accepted.
We needed Claude Cowork live without opening the firm to oversharing risk. Cocha designed the controls so we could move forward with confidence.
IT / Security leader, Atlanta-based Am Law 200 firm
This is the only client quote Cocha publishes, and it also appears on the Cocha homepage. The words are the client’s.
No pilot headcount, user mix, dates or outcome figures. The second-phase items are an assessment and a plan. This page doesn’t claim any of them are in place at the firm.
Cocha supports a large U.S. law firm with its Copilot rollout and ongoing advice as the ecosystem changes. Client feedback, paraphrased: The CISO described Cocha’s involvement as essential to keeping up with the work.
That is everything Cocha publishes about that engagement, so it gets two sentences instead of a case study. The page leads with Claude because those engagements have a published scope. On the Copilot side, Microsoft’s own documentation explains why permissions come first: Copilot only surfaces organizational data to which individual users have at least view permissions. More on how Cocha works with law firms is on the law firm AI governance page.
This is how Cocha approaches the work. It isn’t a list of things done for either firm unless that firm’s scope above says so.
Decide what the tool can reach before the rollout widens. Copilot follows the user’s existing permissions, and Anthropic says Claude connectors respect the permissions users already have in the underlying systems. An overshared matter folder becomes an AI answer. Our guide to Purview sensitivity labels for law firms shows one way to organize labels by matter type, alongside data loss prevention.
Start with a bounded pilot. Named users, named use cases and named data exclusions. Small size doesn’t make a pilot safe. Knowing who is in it, what Claude can reach and which capabilities are withheld does. Our guide to Claude Enterprise governance and the pilot boundary goes further.
Keep connectors and agent autonomy off until someone has vetted them. Each connector widens what Claude can touch, so approval needs an owner and a repeatable process. See MCP gateway security for law firms.
Write the acceptable use policy for privileged and client-restricted matters. ABA Formal Opinion 512 ties a lawyer’s confidentiality duty under Model Rule 1.6 to generative AI use. The policy is where the firm turns that into rules lawyers can follow. Our AI acceptable use policy template includes a law firm version.
Plan for personal accounts. As of November 2026, Anthropic offers SCIM directory sync on Enterprise plans, and its documentation says just-in-time provisioning never removes members automatically. Our shadow AI guide for law firms covers where unapproved use hides.
Plan monitoring before expansion. Audit logs are an Enterprise feature, and only the organization’s Primary Owner can turn on the Compliance API. Someone has to decide where that data goes and who reads it before the pilot grows. The Claude Enterprise rollout runbook walks through the sequence, and Atlanta firms can start with Claude governance for Atlanta law firms.
The AI Readiness Snapshot is a 60-minute working session followed by written findings and a 30-minute review. It’s free and read-only. It makes no changes to your environment and installs no software. It is a bounded diagnostic, not a complete tenant audit, penetration test or regulatory certification.
A Snapshot is where a firm learns whether work like the engagements above applies to it.
Yes. This page describes two anonymized engagements: a net-new Claude Enterprise rollout for a large Canadian law firm and a secure Claude Enterprise and Claude Cowork pilot for an Atlanta-based Am Law 200 firm. Client names stay private under NDAs. Each description covers what Cocha was engaged to do and where its role stopped.
We designed the controls and helped each firm’s team implement them. At the Canadian firm, that meant working with the firm’s administrators in the Claude console. At the Atlanta firm, it meant working with the firm’s engineers. The second-phase assessment at the Atlanta firm is an assessment and an action plan, not an implementation.
NDAs. Both engagements are covered by nondisclosure agreements, so the descriptions are anonymized and limited to scope. They describe the work Cocha was engaged to do. They are not a claim that a firmwide rollout is complete, and they include no outcome figures for either firm.
Named owners and admin roles. A pilot boundary covering users, use cases and data that stays out. A connector and MCP posture, usually off at launch. An acceptable use policy that handles privileged and client-restricted matters. A plan for personal Claude accounts. A monitoring plan that says where activity data goes and who reads it.
Yes. Cocha supports a large U.S. law firm with its Copilot rollout and ongoing advice as the ecosystem changes. This page leads with Claude because those engagements have a published scope. For Copilot permissions and oversharing, start with our guide to SharePoint oversharing before Copilot and our Claude vs Copilot comparison for law firms.
A 60-minute working session followed by written findings and a 30-minute review. It’s free and read-only, makes no changes to your environment and installs no software. It is a bounded diagnostic, not a complete tenant audit, penetration test or regulatory certification. It tells you where to look next.