PUMA, Figma, and Claude run their content on Sanity. So can you.

Here's a claim you've seen on a hundred agency websites: "trusted by leading brands." Usually it means someone once downloaded a whitepaper. So let's do this differently.

PUMA, Figma, and Anthropic's Claude run their content on Sanity. We didn't take that from a logo wall. This morning we checked the source code of their live websites: us.puma.com serves content from a Sanity project, figma.com loads its images from Sanity's CDN, and both anthropic.com and claude.com pull from one shared Sanity project. The receipts are in the HTML.

This post is about what those three companies figured out before most: your content system matters more than your design tool. And about how the same system scales down to a business your size.

• 55K+

  reusable content pieces PUMA manages in one system across global markets

• 6 engineers

  run Morning Brew's $50M+ media business with 13 brands on Sanity

• 30 sec

  for Tecovas to update 10,000 SKUs during Black Friday

Three companies, three different problems

PUMA's problem was sync. Content lived on regional servers and independent CMSes that kept drifting apart. Today one Sanity backend feeds puma.com, mobile web, and the iOS and Android apps, with custom workspaces for teams across the globe: more than 55,000 reusable content pieces, 4,000 hero banners, and around 12,000 product categories ingested every hour from their commerce platform. PUMA's e-commerce platform lead at the time called it "the connective tissue for all of our digital properties."

Figma's problem was speed without developers. The tool designers love runs its marketing site and blog on Sanity, with a block-based page builder that lets the team spin up localized pages without code. No splashy case study, just a quiet architectural choice you can see in their page source.

Anthropic's problem is pace. The company behind Claude publishes its news, research, and engineering content through Sanity, and claude.com runs on the same content project. When your launches move markets, your content system cannot be the bottleneck.

What they figured out

Strip the logos away and the pattern is identical. Content stored as structured data, not welded into page templates. One source of truth feeding every channel. Components that let non-developers assemble on-brand pages. Teams on three continents editing the same system without stepping on each other.

In other words: they invested in the content operating system, not the paint job. The design is what visitors see this quarter. The content system decides how fast you can change it every quarter after.

Two honest notes. The performance numbers above come from Sanity's own case studies, so treat them as vendor-told stories about real customers, not audited benchmarks. And the fingerprints prove these companies use Sanity, not that Sanity alone made them successful. What the evidence does show: companies with world-class engineering teams, free to choose anything, keep choosing this architecture.

The same platform, sized for your business

Here's the part that matters for you: there is no enterprise edition and toy edition of Sanity. The platform PUMA runs is the platform we build on. What changes is everything around it: a content model designed for your team instead of thirty global markets, a studio your marketers learn in an afternoon, components that enforce your brand, and founders who answer when something needs to change.

PUMA needed global sync. Figma needed speed without developers. Anthropic needed to move at AI pace. You probably need something simpler: a website your team can actually run. It's the same answer, sized differently.