3 posts tagged with "claude"

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

We built an Architect agent — a fully autonomous code reviewer powered by Claude Opus 4.6 — that explores a repository, runs audits, and produces a comprehensive architecture report. One command, zero human intervention, a professional-grade review in under 10 minutes.

This article covers how the agent is structured, how it leverages Anthropic's agentic tool-use loop, and what we learned shipping it.