Everyman Brand Archetype
Automotive
Content Management Platform
Sanity
To make content reusable across websites, apps and AI agents, Sanity built a developer-first Content Operating System with structured content, real-time APIs and customizable editorial workflows, enabling teams to treat content as data despite competition from Contentful, Contentstack and Strapi.
• BUSINESS MODEL
• REVENUE
• MARKET TYPE
• MARKET ENTRY
• GROWTH MODEL
• MOAT
• EDGE
1
MODEL
Sanity prioritized a developer-first content platform over a traditional page builder: it built the Content Lake as a real-time database for structured content, GROQ and GraphQL APIs for delivery, and Sanity Studio as a customizable editorial environment. This architecture let teams model content as code and deliver it to any frontend, app or AI agent. Sanity serves over one million users across 6,000+ teams, including Shopify, Figma, Spotify, PUMA and Anthropic. [468][469][470][471]
Question this model answers
We need to decide what to build first.
BUSINESS MODEL
PaaS
HOW THEY BUILT IT
'- Sanity was founded in 2016 and built a cloud-native Content Operating System for structured content.
- It created the Content Lake as a real-time database optimized for content operations.
- It built Sanity Studio as a customizable React-based editorial interface, with an App SDK for custom content apps.
- It monetized through a free tier, per-seat Growth pricing and custom Enterprise contracts.
- It expanded into AI with Content Agent, Agent Actions, Agent Context and an MCP Server for AI coding tools.
HOW TO ARCHITECT IT
1. Start with a structured data layer that can serve multiple channels, not a single-page website builder.
2. Build a customizable authoring interface so content teams can work without developer bottlenecks.
3. Make the content queryable and portable through APIs so it can feed websites, apps and AI agents.
4. Price by seats and usage so revenue grows with team size and content volume.
5. Add AI only when structured content can improve automation, personalization or agent context. Avoid selling a headless CMS without a strong editorial experience; developers may adopt it, but content teams will not.
DISTRIBUTION MODEL
Developer/API-Led, Product-Led Growth, Community-Led, Direct Sales
HOW THEY OPERATIONALIZED
'- Developer-led adoption: Sanity grew through open-source SDKs, documentation, GROQ and GitHub.
- Product-led growth: Free tier and self-serve Growth plan allow developers to start without sales.
- Community-led education: Guides, documentation and developer resources drive adoption.
- Enterprise direct sales: Larger customers with security, scale and distribution needs work with Sanity representatives.
HOW TO REPLICATE WHAT WORKED
What Worked
Treating content as structured data creates a developer wedge that expands into enterprise content operations.
Trap if Copied Blindly
Developer-led adoption fails if the editorial experience is weak; content teams need usable workflows, not just APIs.
Insight on Untapped Business Model / Gaps / Pitfalls
GOLDMINE
GOLDMINE 1 — AI-READY CONTENT LAYER. Structured content can become the context layer for AI agents, search and personalization.
GOLDMINE 2 — CONTENT OPERATIONS AUTOMATION. AI can automate tagging, translation, localization and content QA.
GOLDMINE 3 — COMPOSABLE CONTENT COMMERCE. Content can connect to ecommerce, CRM and ERP systems to power product storytelling.
THE TRAP TO WATCH
THE PIT — DEVELOPER-ONLY ADOPTION. If content teams cannot use the platform easily, expansion stalls.
THE SECOND PIT — USAGE COST SURPRISE. Pay-as-you-go pricing can create unpredictable bills as API and AI usage grows.
MOVE WITH CAUTION
Do not deploy AI agents into content workflows without governance; automated publishing and content generation can create brand, legal and accuracy risk.
2
MARKET
MARKET TYPE
Red Ocean
WHY THEY WON
Headless CMS is a Red Ocean: many vendors compete on APIs, flexibility and enterprise features. Sanity’s opening was the gap between rigid enterprise CMS platforms and developer-centric tools: teams needed structured content that could serve websites, apps and AI agents. Its Content Lake, GROQ and Studio addressed that gap. [468][469][477][470] The transferable lesson is that crowded developer markets reward vendors that change the content model from pages to structured data.
Sanity entered a crowded headless CMS market against Contentful, Contentstack, Storyblok, Strapi and Magnolia. It differentiated through developer-first architecture, real-time collaboration and structured content. [477][478][470][479]
Question this model answers
We are entering a crowded market.
ENTRY STRATEGY
Greenfield Entry
EXECUTION
Sanity entered by creating a new content architecture rather than displacing a legacy CMS. Its initial bet was that developers would adopt a structured, API-first content platform if it gave them flexibility without sacrificing editorial usability. This required a real-time database, query language and customizable Studio before enterprise features could scale. [468][469][470][471] The founder-level lesson is that greenfield entry works when the entrant defines a new abstraction—in this case, content as data—that makes the incumbent model feel limiting.
FOOTHOLD STRATEGY
Wedge Strategy
THE HOW
Sanity’s initial wedge was developer-led adoption through structured content, real-time APIs and customizable Studio. These users were reachable through open-source communities, documentation and GitHub. They could pay once teams needed collaboration, permissions, scale or enterprise support. The expansion path was into content operations, commerce, AI and enterprise media. [474][469][470][471]
MARKET TYPE PLAYBOOK
RULE 1 — CHANGE THE CAPABILITY FRONTIER. Move content from building pages to modelling and delivering structured content.
RULE 2 — WIN DEVELOPERS FIRST. A flexible schema and code-based studio earn adoption before editors or procurement.
RULE 3 — POSITION FOR AI CONTEXT. Structured content is the input AI agents and channels need, widening the budget beyond websites.
RULE 4 — EXPECT A CROWDED CATEGORY. Contentful, Storyblok and Strapi compete, so developer experience must remain the edge.
In a Red Ocean, the entrant must change the buyer’s capability frontier.
Sanity shifted content management from “build pages” to “model and deliver structured content,” enabling it to compete for platform and AI budgets rather than only CMS subscriptions.
GENERAL RULES
WHAT HAPPENS IN THIS MARKET TYPE
RULE 1 — Identify a workflow where the existing data model creates constraints.
RULE 2 — Build a structured data layer before adding AI or automation.
RULE 3 — Make the system usable for both technical and non-technical users.
RULE 4 — Reject greenfield entry when the buyer needs turnkey templates or low-code simplicity more than flexibility. For example, Contentful built enterprise-grade headless CMS; failure occurs when a developer-first platform offers flexibility without a usable editorial experience.
Greenfield entry works when the entrant can define a new abstraction that makes the incumbent model feel limiting.
A wedge strategy wins by solving one developer pain, then expanding into the broader content operations workflow.
HOW TO APPLY FOOTHOLD STRATEGY
RULE 1 — Choose a pain that is frequent, technical and tied to a business outcome, such as multi-channel delivery.
RULE 2 — Expand only after the first workflow creates habitual use or a clear monetization trigger.
RULE 3 — A wedge fails when it remains a developer tool rather than becoming the content team’s operating system.
RULE 4 — In content platforms, make the second use case editorial workflow or AI context, not merely more APIs. Sanity’s path from Content Lake into Studio and AI illustrates this; a failure pattern is launching AI before the content model is structured enough to be useful.
Sanity’s initial wedge was developer-led adoption through structured content; failure occurs when the second use case is more modelling rather than editorial workflow or AI context.
HOW TO APPLY MARKET ENTRY STRATEGY
Sanity created a new content architecture rather than disguising a CMS, making the incumbent page model feel limiting; failure occurs when the buyer needs turnkey templates or low-code simplicity.
PATTERNS OF THIS MARKETING MODEL
PATTERNS IN DEVELOPER-FIRST PLATFORM DISTRIBUTION:
1. Open-source SDKs create adoption. Developers adopt tools they can inspect, extend and integrate.
2. Structured data creates portability. Content stored as data can be delivered to any channel or agent.
3. AI creates a new consumption layer. Agents need structured, queryable content to operate reliably.
WEAKNESS
Developer-first platforms can create implementation drag. Without templates or opinionated workflows, time-to-value increases.
GROWTH CAMPAIGNS
'- Free tier and developer onboarding.
- GROQ, GraphQL and Content Lake positioning.
- Sanity Studio and App SDK for custom editorial apps.
- AI Assist, Content Agent and Agent Actions.
- MCP Server for AI coding tools.
- Enterprise content operations for media and commerce.
| So What
Sanity’s strongest commercial mechanism is using a developer wedge to create a structured content layer that expands into enterprise content operations and AI.
| Key Learning
In developer-first platforms, the data model is the moat; structured content enables multi-channel delivery and AI consumption.
| How to Use
If your product manages content or data, define a structured model that can serve multiple surfaces, then build an editorial or operational layer around it.
3
MONEY
REVENUE MODEL
Subscription, Usage-Based, Service Fee
Sanity monetizes through seats, usage and enterprise contracts. Its Growth plan costs $15 per user per month, with pay-as-you-go for higher usage; Enterprise pricing is custom. [474][475][476]
Question this model answers
We need to choose the right pricing metric.
PRICING STRATEGY
Freemium, Usage-Based Pricing, Custom Enterprise Pricing
WHY THEY WON
Customers pay recurring subscription fees based on seats, plus usage-based charges for API requests, bandwidth, compute and AI actions. Enterprise customers pay custom pricing for scale, security and support. Revenue expands as teams grow, content volume increases and AI usage rises. [474][475][476][471]
TARGET AUDIENCE
Developers and startups (Free; experimentation and small projects); content and product teams (Growth; collaboration, workflows and AI Assist); enterprises (Enterprise; security, scale and custom workflows); AI-first teams (Agent Context and MCP; structured content for AI agents). [474][475][470][471]
Sanity offers a Free plan, a Growth plan at $15 per user per month, and custom Enterprise pricing. Add-ons include SAML SSO, dedicated support, increased quota and extra datasets. [474][475][476]
CUSTOMER BUYING BEHAVIOUR
A developer often begins with a free project or open-source SDK, then upgrades when the team needs collaboration, permissions or scale. Buyers evaluate API flexibility, editorial usability and enterprise controls; adoption deepens as content volume and AI usage grow. [474][469][475][470]
WILLINGNESS TO PAY
CORE INSIGHT
Teams are buying content portability and operational control, not a CMS.
RULES OF ADOPTION
RULE 1 — PRICE THE CONTENT OPERATIONS LAYER. Seats and usage reflect the cost of collaboration, delivery and AI consumption.
RULE 2 — SELL STRUCTURED FLEXIBILITY. The buyer compares Sanity with the cost of rigid templates, custom builds and content silos.
RULE 3 — MONETIZE AI CONTEXT. Structured content becomes the input layer for agents and personalization.
RULE 4 — CONTROL USAGE COST. Pay-as-you-go pricing must be predictable; otherwise, customers resist scaling. The buyer is purchasing content infrastructure, proven by multi-channel delivery, team adoption and AI usage.
The buyer is really buying content portability and operational control, proven by per-user plans and add-ons for the operations layer.
REVENUE RISK
Usage-based pricing can create bill shock and churn if API, bandwidth or AI costs grow unpredictably. [475][471] Developer-only adoption can stall expansion if content teams find the editorial experience too technical. [469][471] Competition from Contentful, Contentstack, Storyblok and Strapi can pressure pricing and feature expectations. [477][478][479] AI commoditization can reduce differentiation if content generation and agent tooling become generic. [477][470] Enterprise sales can increase implementation and support cost if customers require custom workflows and integrations. [474][476][470] Funding/valuation: Sanity raised $80 million Series C in 2025; current ARR is not publicly disclosed. [480]
4
MOTION
Sanity uses product-led growth through a free tier, open-source SDKs and self-serve upgrades, then uses sales-led motions for enterprise customers with security, scale and custom workflow needs. [474][475][476][470]
Question this model answers
We need to choose between product-led growth and sales-led growth.
GROWTH EXPANSION MODEL
Land & Expand, Platform Expansion
HOW THEY EXPAND
Sanity lands developers through Content Lake and Studio, expands into content operations and commerce, then moves into AI-native content workflows. It expands the platform through GROQ, App SDK, MCP and Agent Actions. [468][469][477][470] The dependency is that new products must strengthen the content model; otherwise, Sanity becomes a collection of disconnected tools.
COMPETITIVE STRATEGY
Freemium User Acquisition
HOW THEY COMPETE
The loop begins when a developer adopts Sanity through a free project or open-source SDK. They model content as structured data, query it through GROQ and deliver it to a frontend or app. As teams grow, they upgrade for collaboration, permissions and scale. The compounding trigger is content reuse: each new channel or AI agent increases the value of the structured content layer. The engine breaks if the editorial experience is weak or usage costs become unpredictable.
GTM
Sanity’s GTM is developer-led with enterprise sales expansion.
$5–10M ARR
Free tier and open-source SDKs acquire developers; Studio and Content Lake drive adoption; self-serve upgrades convert teams; enterprise sales expands into larger organizations. The primary motion is developer-led, supported by enterprise sales.
SUSTAINING MOATS
Technology Advantage
The moat is Sanity’s technology advantage: its Content Lake, GROQ and Studio create a structured content architecture that generic CMS platforms do not replicate easily. As teams build content models and integrations, switching requires re-architecting both data and workflows. The moat weakens if competitors offer similar structured content or if AI tooling becomes commoditized.
| Why This Moat Lasts
Developer-platform lock-in lasts when the vendor owns the data model, query layer and authoring workflow.
| Standard Rules
RULE 1 — STRUCTURED CONTENT GRAVITY. Sanity’s Content Lake stores content as queryable data.
RULE 2 — CUSTOMIZABLE AUTHORING. Studio and App SDK create editorial workflows tailored to the customer.
RULE 3 — AI CONTEXT LAYER. Agent Context and MCP make Sanity a source of truth for AI agents.
| The Signal
Sanity’s scale—over one million users across 6,000+ teams and customers including Shopify, Figma and Spotify—shows that its developer-led model achieved durable adoption. The moat does not protect against developer-only adoption, usage-cost shock or a competitor with stronger enterprise content operations.
ARR
JOURNEY
Pre-$1M ARR
VALIDATE STRUCTURED CONTENT: Sanity’s early move was to prove that developers would adopt a structured, API-first content platform.
$1–5M ARR
BUILD EDITORIAL LAYER: It launched Studio and App SDK to make content usable for non-technical teams.
$5–10M ARR
SCALE SELF-SERVE: It introduced Free and Growth plans to drive adoption.
$10–50M ARR
EXPAND ENTERPRISE CONTENT OPS: It added security, scale and custom workflows for larger customers.
$50–100M ARR
ADD AI OPERATIONS: It launched AI Assist, Content Agent and Agent Actions.
$100M+ ARR
AI-NATIVE CONTENT OS: Sanity raised $80 million Series C in 2025 and expanded MCP and Agent Context for AI-first teams.
BREAKDOWN
THE STANDARD
Win developer-first content markets by defining a structured data abstraction, then expand into editorial workflows and AI only when the data model is trusted.
THE SEQUENCE
1. Build a structured data layer that can serve multiple channels; the gate is developer adoption and multi-channel delivery.
2. Add an editorial or operational layer before scaling enterprise; the gate is content-team usability and collaboration.
3. Introduce AI only when structured content can improve automation or agent context; the gate is evidence that AI creates measurable value beyond novelty.
Sanity’s Content Lake, GROQ and Studio created a durable path from developer adoption to enterprise content operations.