The Cone of Uncertainty
Don't build a single forecast — build a range of exponential scenarios across a 1–2 year horizon. Small movements in weekly growth rates compound into wildly different outcomes. Work backwards from each point in the cone to determine what resources you need to stay solvent and at the frontier regardless of where reality lands. The goal isn't precision; it's survivability across the full distribution of futures.
So what: Any exponentially growing business planning to a point estimate is almost certainly either over- or under-resourced. The right question isn't "what will happen?" — it's "what position do we need to occupy for any plausible outcome?"
Planning · Forecasting · Capital
Return on Compute — Not Gross Margin
Compute is not a cost to minimize. It's the single asset generating return across multiple time horizons simultaneously: inference revenue today, model capability in 6 months, internal productivity now. The same chip runs customer inference in the morning and model development in the afternoon. Traditional COGS/R&D separation completely misframes AI lab economics. The right metric is return on the full compute envelope.
So what: When evaluating AI labs, skip gross margin — it's the wrong frame. Ask: what's the ROC across all workloads, how is compute efficiency trending generation-over-generation, and is the gap between compute spend and revenue output widening or narrowing?
Investor Lens · Unit Economics
Jevons Paradox — Applied Twice
Lowering the price of a resource increases its consumption far beyond what you'd expect, expanding TAM rather than compressing margin. Krishna applies this in two places: (1) Cutting Opus pricing unlocked a new consumption band — usage exploded so much that net revenue impact was positive. (2) AI-assisted employees don't do less work — they surface more high-value work, because throughput multiplies what's possible for the whole team.
So what: In exponential-growth categories, pricing for margin capture is usually the wrong move. Find the price point where consumption explodes — the resulting usage depth, customer stickiness, and TAM expansion typically create more enterprise value than margin preserved at a higher price.
Pricing · Labor · TAM
Intelligence is Multidimensional, Not a Score
Benchmark leaderboards are saturated and easily gamed. Real model intelligence has distinct axes: long-horizon task completion, tool use, agentic speed, domain accuracy, reliability under load. Two models with equivalent "IQ" but different task completion speeds deliver radically different economic value — the faster one can be 7x more productive on the same assignment. Anthropic measures model value by what customers report, not leaderboard position.
So what: When comparing models for enterprise deployment, don't ask "which scored higher?" Ask: which dimensions matter for your workload, and which model optimizes those? Speed and reliability often matter more than raw intelligence for production use cases.
Product · Benchmarking · Enterprise
Compute Fungibility as Structural Moat
Most frontier labs are locked into one chip vendor. Anthropic runs Trainium, TPUs, and GPUs interchangeably — shifting workloads across all three intraday based on price-performance and workload type. This took years of compiler work and deep co-engineering with chip teams to build. The result: a dollar of compute goes further inside Anthropic than at any other frontier lab, by their own assessment. Flexibility that took years to build is not easily replicated overnight.
So what: Infrastructure flexibility is a moat that doesn't show up in any standard financial metric but shows up everywhere in the P&L over time. The companies that invest in it early create compounding cost advantages that become nearly impossible to close later.
Moat · Infrastructure · Strategy
Model-Led Growth (MLG)
Revenue acceleration at Anthropic is caused by model capability leaps, not by adding salespeople. Each new model generation unlocks new use cases, which pulls enterprise adoption forward. The GTM team accelerates the cycle but doesn't initiate it. The Sonnet 3.5/3.6 coding leap is the clearest example: capability threshold crossed, adoption followed, revenue followed. Anthropic now uses coding as the "analog" to predict what comes next in other domains.
So what: For AI companies, the most important leading indicator of revenue is model capability unlock, not pipeline or sales headcount. The right investor question: what new use cases does the latest model make economically viable that weren't before? That's the next revenue cohort.
GTM · Growth · Enterprise
Talent Density Beats Talent Mass
A tight team of exceptional people, empowered with the best tools, consistently outcompetes a larger team with average tooling. Headcount growth should be a consequence of productivity gains — not a prerequisite. Anthropic deliberately forgoes billions in potential inference revenue to accelerate employees with internal compute, treating workforce productivity as a compound investment. The best people want to work with other best people — density creates its own gravity.
So what: Before adding headcount, ask: have we made every existing person maximally productive? The leverage on a new hire is far higher in a high-productivity environment. Hiring into a low-productivity org to solve output problems typically makes the problem worse.
Org Design · Culture · Leverage
Platform Horizontal, Vertical Only Where You Have Unique Insight
Anthropic's default is platform — enabling the ecosystem to build. They go vertical in two cases only: (1) to demonstrate a model capability the market doesn't yet believe exists (Claude Code proving what an AI-native coding env looks like), or (2) to show how to compose the platform in a new way. The goal is never to compete with customers — it's to prove the platform's potential and let customers capture most of the resulting value.
So what: The platform vs. app tension at AI labs is real but often misframed. The question isn't "will they compete with me?" — it's "do they have unique insight that makes the platform more valuable if they demonstrate it first?" Fear of the former causes builders to miss the upside of the latter.
Product Strategy · Ecosystem