3 posts tagged with "enterprise"

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.

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)).

Most "AI memory" demos stop at memory.add() and memory.search(). That works on a laptop. It does not survive contact with production. The real questions are: When this recall is slow, which store is to blame? When a graph's spend triples overnight, which feature caused it? When a customer asks "what did your agent remember about me, and when?", can you answer from an audit log instead of a shrug?

TL;DR — This field report shows how to build an agent memory layer where every operation honors a contract: fail-open, PII-safe, and fully instrumented. Three stores (mem0, Qdrant, LangGraph) are funneled through single chokepoints, and each chokepoint fans out to five telemetry sinks. The result is a stack that answers the hard production questions without guesswork.