The original is one click away. Open original ↗
How Anthropic grew from $1B to $19B ARR in 14 months
Executive overview
Anthropic hit $1B ARR in early 2025 and crossed $19B by February 2026 — 10x year-on-year, the fastest sustained growth ever recorded at that scale. The company had no first-mover advantage, no free-cash-flow distribution machine, and no consumer launch momentum. Extreme focus on coding and B2B, world-class research, and a mission-driven culture closed the gap.
Amol Avasare, Head of Growth, leads a ~40-person team. About 70% of his time is firefighting "success disasters" — things breaking because growth is so fast. The remaining 30% is proactive: pricing, product sequencing, and larger-bet experiments that reflect an AI-first growth philosophy.
Because AI product value compounds exponentially, growth teams should skew toward larger bets and avoid optimizing for a local maximum that the next model leap will make obsolete.
How Anthropic approaches growth
- 10x YoY since 2023: $0→$100M, $100M→$1B, $1B→~$10B, and still accelerating
- Growth org is ~40 people — engineers, designers, PMs, data — organised into horizontal platforms (monetisation, growth infrastructure) and audience pods (B2B, Claude Code, knowledge workers, API)
- Linear charts are internally unfashionable; everything is logged at log-linear scale
- Larger bets dominate the portfolio (~50–70%) because future product value is 100–1000x today's; micro-optimisations still compound but can't be the centre of gravity
- Chrome extension — underpinning Cowork and Claude Code use cases — was built by the growth team on conviction, with no external mandate
Activation and onboarding
- Activation is the highest-leverage growth lever; getting users to the right product/feature early drives long-term retention
- Capability overhang is the core challenge: models improve faster than teams can design on-ramps for new capabilities
- Adding the right friction outperforms cutting it — onboarding quizzes at Masterclass, Mercury, and Anthropic all lifted conversion by surfacing relevance
- Mercury's single highest-impact growth quarter was spent purely on quality in the onboarding flow, no metric targets — significant uplift in start-to-completion rate followed
- Anthropic's current onboarding asks users about role and interests, then routes to the most relevant product; critics call it too long; data supports keeping it
- GPT-to-Claude memory import tackled the cold-start problem at a specific moment of competitive switching intent
Automating growth with Claude (Project Cache)
- Cache (Claude Accelerate Sustainable Hypergrowth) is an internal initiative to automate growth experimentation end-to-end
- The loop has four stages: opportunity identification → build → test/QA → analyse results
- Enabled by Opus 4.6; wasn't viable a few months earlier
- Current win rate is comparable to a junior PM (2–3 years experience), not yet senior-PM level — but improving week-on-week
- Brand review is still human-gated; a skill containing brand dos/don'ts is used to reduce that overhead
- Cross-functional stakeholder alignment is the one step that resists automation — until other teams also run as agents
How Amol uses Claude day-to-day
- Cowork on a schedule reviews 20–25 metric charts every morning and surfaces anomalies in Slack before he opens his laptop
- A weekly scheduled task scans Slack (via MCP) for misalignment across projects he owns — flags potential coordination failures proactively
- Claude handles admin: books meeting rooms, files expenses on Brex, processes reimbursements on Benepass, archives email
- Manager feedback loop: Claude reviews direct reports' output against team OKRs and discussion transcripts, then synthesises feedback prompts — and does the same for Amol, role-playing his manager Ami Vora
- PRDs exist for ~20–30% of projects; everything else starts on Slack or with a prototype
The PM/engineering ratio shift
- Claude Code gives engineers ~2–3x leverage; a team of 5 engineers effectively becomes 15–20, straining PM and design capacity
- Anthropic's response: engineers own projects under two engineering weeks end-to-end (legal, security, cross-functional stakeholders included); PM is advisory only below that threshold
- Product-minded engineers become high-value; PMs who can design become scarce and hard to replace
- At scale, a senior PM's highest leverage is improving the why and what — not shipping the 21st feature themselves
- PRDs are mostly obsolete for small work; a good kickoff meeting replaces documentation for larger projects
Focus, safety, and competitive strategy
- Anthropic deliberately chose not to launch its chatbot before ChatGPT — a safety call that ceded first-mover advantage to OpenAI
- The coding bet was made in 2021, years before agentic coding was a recognised market; the rationale: better models accelerate research, and coding is the fastest feedback loop
- Being smallest and least-funded forced focus — constraints eliminated excess choice and forced prioritisation
- Public Benefit Corporation structure legally permits prioritising safety over shareholder returns
- Growth team is "comfortable leaving money on the table" to protect brand, safety, and user experience — framed as a long-term competitive advantage, not a sacrifice
- Controversial tests are sorted into two buckets: hard no (brand/safety red line) vs. "run and require high return to justify the cringe"
Culture as compounding advantage
- Internal notebook channels (personal Slack feeds) let leadership scale beliefs and model behaviour as headcount grows — also feeds context to Claude agents
- No checked-out employees — a consistent observation across the company
- Talent density compared internally to playing for Real Madrid: Mike Krieger (Instagram co-founder), Ami Vora (CPO), researchers ranked best in world
- Openness is structural: public disagreement with Dario on his notebook channel is encouraged, not managed
Advice for PMs and growth practitioners in an AI-first world
- Use the tools constantly — each model release unlocks things that didn't work last quarter
- Identify the 1–2 interdisciplinary spikes where you have an unfair advantage and go deeper, not broader
- Product-minded engineers and design-capable PMs are the new unicorns — cross-functional range compounds
- Adaptability matters more than any specific playbook; ~50–70% of past operating patterns become irrelevant when joining an AI-first company
- Smaller companies: ship yourself; larger companies: your leverage is elevating team judgment, not adding one more feature
Failure and recovery
- Spent three years as a founder building a mental health quantification product; shut it down after raising capital and hiring 7–10 people
- The failure produced the cold-email skills, product instincts, and founder mindset that made the subsequent career path viable
- Suffered a severe traumatic brain injury in early 2022 from MMA sparring; nine months off work, six months relearning to walk, off screens entirely
- Re-injured one month into joining Mercury; two more months off
- Still not 100% recovered — manages dizziness and headaches with structured breaks, no alcohol, no caffeine, and annual silent meditation retreats
- Core takeaway: constraints force focus; contentment independent of outcomes is a skill, not a disposition
More like this — when you're ready for early access.
Join the waitlist for a personal account and content recommendations based on what you're working on.
No spam. Unsubscribe at any time.
You're on the list. We'll be in touch before launch.