Four patterns and fifteen practices from 25 Companies that rolled out AI across their business beyond simple LLM chat.
How this was built. We read 25 Claude customer stories and interviews published on claude.com/customers between June and August 2026. A practice made the list only if it appeared at three or more unrelated companies and a ten-person business or team could run it without engineers.
Read it with three caveats. Every source is vendor-published, so results are self-reported and the sample contains no failures. Three sources are engineering interviews; we kept only what transfers to office work. And the companies range from a two-person fabrication shop to 15,000-person firms, so the practices are the signal and the numbers are directional.
Four Patterns
1. Buy fluency with leaders' time, not employees' courses. No company here credits a training curriculum. They credit executives who used the tool before anyone was asked to, and first sessions engineered so every participant left with a finished output. Advantage Solutions trained its leadership team before any employee; Epic gave up a full leadership meeting to hands-on use; PwC walked 400 people through three real tasks in an hour. Fluency is bought top-down and hands-on, and the first metric is leadership hours in the tool.
2. Make usage visible, including the failures. Adoption spread through a bazaar, not a mandate. Champions were found by watching who shared unprompted. Written records of wins, failures, and wasted budget were the learning channel that scaled. League's COO posted overnight results in Slack and access requests followed; Spotify runs a prototype store its co-CEOs contribute to. Visibility also carried the message that mattered most: hours returned to people, named task by task, not headcount removed.
3. Set the fence, then get out of the field. The companies that moved fastest did not micromanage use cases. They built a fence with three rails: red lines on where AI never goes and who owns the final call, access scoped by role before anything was connected, and a hard date. Inside the fence, teams had what Cox calls carte blanche. Cyera mapped its data first and then went company-wide in 17 days; Mercy Corps assesses privacy per use case because the risk lives there, not in the tool.
4. Start small, capture everything, compound. The first step is small: the task people dread, a build that takes twenty minutes. The tempo is not slow. What turns small steps into organizational capability is capture. The best performer's method becomes a shared skill, the context becomes a file the AI reads every time, the failed idea is retried on the next model, and the personal automation graduates to team ownership. Brainlabs authored 400 skills in four weeks; YMCA South Australia's skills now outlast staff turnover. Without capture, week one feels magical and week five disappoints.
The carousel below gives fifteen concrete practices behind these four patterns, with the evidence and sources for each.