What Did Anthropic's IPO Filing Actually Say?#
Anthropic's S-1, filed with the SEC on Monday, October 26, 2026, lays out its retention math in public for the first time. Over half of customers spending $100,000+ annually now use both the Claude Platform and a first-party app, up from about 30% at the end of 2025, and net revenue retention sat at roughly 900% at the end of Q3, per TechCrunch's review of the filing.
That's the headline. The mechanics underneath it matter more.
More than 11,900 customers spend $100,000+ a year with Anthropic. Over 1,900 spend $1 million+. About 250 spend $10 million+. The filing says customers start with the API, add Claude Code for engineers, then Cowork for everyone else, because "an advance at any layer compounds across all three layers." In Q3, the top 5% of Claude Enterprise customers using Claude Code spent roughly 20 times as much per month as enterprise users who skipped it.
Does This Change Anything for Your AI Subscription?#
At WebEpex, we build AI automation and chatbots for clients across the GCC, Europe, USA, Canada, and India, and we read a filing like this one the way a buyer reads a vendor's annual report, not as industry gossip.
If you're running one AI tool for one job (a drafting assistant, a single chatbot), this changes nothing for you today. Keep doing what you're doing.
If your business has adopted an AI vendor's full product stack (API plus coding agent plus internal workspace plus automations, all from one company), this is worth fifteen minutes this week. The filing isn't describing a flaw. It's describing the product roadmap. Anthropic says plainly that integration across layers is built to compound spend, and the 20x multiplier on Claude Code adopters is the proof it works.
What Are the Honest Pros and Cons of Going Deep With One AI Vendor?#
The pro case is real. Fewer integrations, one support relationship, and genuine product quality gains when the layers are built to reinforce each other. For a small team moving fast, that's time saved on glue code.
The con is pricing power. Once the whole stack lives with one vendor, renewal conversations happen on their terms, not yours. Anthropic's own filing admits a related risk running the other direction too: its cloud distribution partners, AWS, Google Cloud, and Microsoft Azure, "increasingly view Anthropic as a competitor," which the filing says could complicate its own compute supply. A few things worth checking before going all-in with any AI vendor:
- Can you export your automations, prompts, and workflows if you switch providers next year?
- Is your CRM or lead-routing integration wired directly to one vendor's API, or to a layer you control?
- Does your contract get cheaper per unit as you grow, or does usage-based pricing quietly compound the way the numbers above do?
How Is WebEpex Building Around This?#
We don't build client automation that only runs inside one AI vendor's orchestration layer, and filings like this one are exactly why. At WebEpex, we run client workflows on n8n, self-hosted on our own VPS behind PM2 and Nginx, and we build chatbots in Voiceflow, both of which talk to whichever model API fits a client's budget and region, Anthropic's included, without the client's operations living entirely inside one company's walled garden.
We reviewed every open build against this filing the day it dropped. None of them needed the orchestration layer rebuilt to swap a model provider. That was a deliberate call from day one, not luck. For clients in the GCC and India especially, where a small business's pull with a US-based AI vendor is already thin, a vendor-neutral orchestration layer is the difference between a renegotiation and a full migration project.
It's also why we've kept an eye on open-weight alternatives like Mistral Large 4 and the broader consolidation pressure hitting point-tool SaaS, alongside Anthropic's own Q3 revenue numbers and recent API changes. The pattern across all of it is consistent. AI vendors are optimizing for depth of integration. Businesses buying from them need to optimize for the opposite.
What Should You Check This Week?#
Pull up your AI vendor bill from a year ago next to this month's. If it's grown 3x or more and you can't point to a specific, measured business result that grew alongside it, you're the customer this filing is describing. Not necessarily a problem, but you've got nothing left to negotiate with at renewal. Check whether your integrations route through a vendor's API directly or through a layer you control. If it's the former, that's the fix. The AI tool itself is rarely the issue.
Where This Leaves You#
If you want a straight read on whether your current AI stack has you boxed into one vendor, not a pitch, just an honest look, send me what you're running and I'll tell you in two minutes. [cal.com/webepex/growth-review]
