Skip to main content

How Cyera rolled out Claude Enterprise and Cowork to 1,500 employees: enterprise case study

· 23 min read
Vadim Nicolai
Senior Software Engineer
Loading diagram…

Figure 1 — the sequence this article argues for: map access, re-scope, provision, instrument the stop points, ship metric definitions as code, report catch rates, name a graduation owner. Adapted from Anthropic's Cyera case study and the companion Q&A; the ordering is mine. If the diagram does not render, read it as that linear list.

Cyera's product exists to answer one question: who in this company can reach which sensitive data? Then Cyera handed roughly 1,500 employees a model that inherits every permission its user holds, wired it to 40 tools, and let it draft replies, pre-review vendor NDAs and file GRC tickets (Anthropic).

The number everyone quotes from that rollout is 88%. The number that made it approvable is 4% (Anthropic).

How Rakuten uses Claude Code: enterprise case study

· 40 min read
Vadim Nicolai
Senior Software Engineer

The number everyone quotes from Rakuten's Claude Code rollout is 99.9%. It is also the number that gets read wrong most often.

Here is what actually happened, according to Anthropic's published customer material. An ML engineer named Kenta Naruse asked Claude Code to implement an activation-vector extraction method inside vLLM, the open-source LLM serving library. The agent ran for seven hours. Naruse, in Anthropic's telling, "didn't write any code during those seven hours." The result was reported at 99.9% numerical accuracy against the reference method (Anthropic 2026a).

Read that as a productivity claim and you will build the wrong thing inside your own company. Read it as a test result and the case study becomes genuinely useful.

Because 99.9% is not evidence that the model is good. It is evidence that the task had an oracle. Somebody, before the agent started, already knew how to compute the right answer independently — a reference implementation existed, and the agent's output could be diffed against it. That single structural fact explains more about why Rakuten's rollout produced results than any statement about model capability you will find in the marketing.

How Stripe Uses Claude Code: Enterprise Case Study

· 19 min read
Vadim Nicolai
Senior Software Engineer

The most load-bearing sentence in the most detailed public account of Claude Code at Stripe is not about Claude. It concerns a permissions programme that started in 2017 — nine years before Patrick Collison sat down for the interview this piece is built on.

Stripe spent a multi-year stretch tagging its data, annotating it, and building what Collison calls "semantically aware guardrails." All of it was for security. None of it was for AI. Then agentic coding arrived, and his description of the payoff is almost apologetic: the work "kind of accidentally put us in a better position when agentic development came along" (Collison (2026)).

How Salesforce Uses Claude Code: Enterprise Case Study

· 22 min read
Vadim Nicolai
Senior Software Engineer

Short answer: Salesforce uses Anthropic's Claude Code across its software development lifecycle, and its own account credits the tool with taking a decades-old, partly declarative platform to roughly 80–90% API coverage in weeks rather than the six-to-twelve months budgeted, growing dollar-per-effective-output 2x, and nearly doubling code volume without a proportional rise in defects (MK & Richard, Salesforce).

That multiplier is the least interesting thing in the sentence, and the one you should trust least.

Everything genuinely hard about this rollout sits in what Salesforce built around the agent. A new productivity metric. A four-rung maturity model. A skill marketplace with replay evals. A benchmark set seeded with tasks the models still fail. And, before any of that, a program to turn a 25-year-old platform into something a terminal agent could address at all. Copy the tool and you inherit none of that.

Instrument the Funnel Your LangGraph Agent Moves

· 7 min read
Vadim Nicolai
Senior Software Engineer

Operations has a number in front of it, and the number has not moved. A flat line can mean the thing measured is genuinely flat, or that the instrument stopped reading. Only one of those is a fact about contractors. The other is a fact about a reader that received a value it had not been taught, declined to parse it, and turned its entire lane into "missing" while the chart kept its axes. In LangGraph terms that reader is a node in a StateGraph, which is where the fix belongs.