The strategic fork
Every infrastructure company eventually faces the same question: do you stay invisible under the hood, or do you own the product that customers actually use?
Think of it like this. Anthropic is a brain surgeon — the best in the world. But right now, other companies are hiring the surgeon, putting their own name on the practice, and keeping the patient relationship. Anthropic does the hard work; everyone else captures the value.
This isn't hypothetical. It's happened before:
- AWS chose to stay as infrastructure — and won, because cloud computing kept getting more complex. More complexity = more value in the plumbing.
- Stripe stayed in payments infrastructure — and watched vertical SaaS companies capture the customer relationships.
- Twilio stayed in communications APIs — then watched its stock decline 80% from peak as AI made its APIs a commodity.
The pattern: infrastructure companies that don't move up the stack get commoditized when the technology matures. For AI, the maturation is happening faster than anyone expected — because every competitor (OpenAI, Google, Anthropic) is racing toward the same finish line.
The core tension: When Claude, GPT, and Gemini all score similarly on benchmarks, the model stops being the differentiator. What matters is who owns the workflow, the data, and the customer relationship.
Why customer support is the move
There are dozens of enterprise categories Anthropic could chase. Customer support is the right one for five compounding reasons:
1. It's the largest proven AI use case
Customer support is a $50 billion market heading to $95 billion by 2031. These aren't projections based on hype. Companies are already spending:
- Sierra: $0 to $100M ARR in 21 months
- Decagon: $0 to $35M ARR in 18 months
- Zendesk: $200M in AI-specific ARR in 2025, projecting $500M in 2026
Enterprise buyers are already comfortable writing 7-figure checks for AI customer support. Anthropic doesn't need to educate the market — it needs to redirect spending that's already flowing.
2. The economics expose the gap
This is the most important comparison in the analysis:
| Dimension | API Layer (Anthropic) | App Layer (Sierra, Decagon) |
|---|---|---|
| Revenue per interaction | $0.03 | $10 |
| Switching costs | Low — easy to swap models | High — deep integration |
| Pricing power | Declining | Increasing |
| Data ownership | None | Full customer data |
3. The data flywheel is the real prize
Every support interaction generates valuable signal: what customers complain about, what products fail, what language works. This data compounds in three ways:
- Model improvement: Fine-tuned models trained on a company's support data outperform general models on that company's tickets
- Cross-functional intelligence: Support data feeds product roadmaps, sales forecasting, and marketing
- Switching costs: An AI agent that's processed 2 million of your interactions and learned your brand voice is extraordinarily hard to replace
Today, Sierra and Decagon capture this flywheel. Anthropic provides the base intelligence but gets none of the compounding value.
4. The window is closing
Application companies are actively building "model swap" layers — architectures designed to make the foundation model interchangeable. Decagon already uses multiple models. Sierra's Agent OS can swap between providers. Zendesk and Salesforce support multiple AI backends. Their customers never know or care which model powers the response.
5. Cowork + MCP makes it possible now
Before January 2026, Anthropic had no credible path to the application layer without building a standalone product. The Cowork plugin architecture changes this: a CS plugin is a set of markdown skill files and MCP connectors — not a multi-year product build. Companies already paying for Claude Enterprise can activate CS workflows for zero incremental cost.
What happens if Anthropic doesn't act
Commoditization isn't sudden. It's a gradual erosion that compounds quarter over quarter:
Apps route queries to whichever AI is cheapest. Anthropic's brand becomes invisible.
Apps fine-tune proprietary models on customer data. General Claude loses its edge.
With model-swap capability, apps negotiate prices down. Margins compress.
Buyers evaluate the app, not the model. Anthropic competes on price alone.
Three advantages nobody else has
Anthropic has three asymmetric advantages. The strategy should be built on these — not on imitating what Sierra or Decagon have already built.
The whitespace is specific: healthcare, financial services, insurance, and government customer support is ~40% of the total market — and the most underserved by AI-native startups like Sierra and Decagon, whose customer bases skew toward internet-native companies (Notion, Duolingo, Eventbrite).
The playbook: three horizons
The strategy has to navigate a partner tension. Anthropic can't alienate Sierra and Decagon (who drive significant API revenue) while competing with them. The answer is market segmentation:
Ship ticket triage, response generation, and brand voice customization via the existing Cowork plugin architecture. Build MCP connectors for Zendesk, Salesforce, Intercom.
HIPAA/SOX/PCI compliance templates. Voice-native CS. "Powered by Claude" partner certification. Proactive support: AI initiates before issues escalate.
Unify CS data across product, sales, and marketing. Per-resolution pricing (300x API revenue). Agent-to-agent protocol via MCP.
The beauty of H1 is the math. Cowork + plugin architecture already exists. The target buyer already has a Claude Enterprise account. The procurement cycle is weeks, not months. There's no partner conflict because mid-market self-serve isn't Sierra's or Decagon's segment.
The decision
Every infrastructure company faces a moment where staying in the infrastructure layer stops being a choice and starts being a constraint.
For Intel, it was mobile. For IBM, it was cloud. For Twilio, it was AI. The companies that recognized the shift and moved up the stack survived. The ones that didn't became commodity inputs in someone else's value chain.
Anthropic is at that moment now. The numbers are extraordinary — $14 billion ARR, 10x annual growth, $380 billion valuation. But 80% of revenue comes from API consumption, which means 80% depends on other companies' decisions about which model to use.
Customer support is where the vulnerability is most acute — and where the escape is most clear. The question isn't whether to act. It's whether to act now, while the window is open.