Matan Grinberg

The model war likely has no single winner. Matan’s biggest change of mind in 12 months: he used to think one or two labs would run away with the frontier — now “it’s probably going to be at least four that are going to probably be approximately as good. And that is a win… the bad case for humanity is when there’s one that’s really really good.” Factory’s own bear case is the mirror image: it dies only if one lab pulls decisively ahead — “but then that’s a monopoly for the entire economy to be worried about.” Forced to pick one on IPO day, he takes Anthropic purely on volatility: “more random chaotic turbulent events at OpenAI.”

Enterprise AI has hit the hangover phase. The sequence: board yells at CEO → token maxing written into performance reviews → “you go and look at the bill and it’s like, oh my god, we are spending so much. I have no idea what the ROI is.” A CIO he knows found hundreds of thousands of dollars per month going to employees asking Opus 4.8 “how’s it going” and what the weather is. Uber’s $1,500-per-individual cap “has happened privately” at dozens of Factory customers, and he expects a short-term contraction in frontier-model usage — which he calls healthy.

80–90% of tasks now running on frontier models could run on open models; typically “the planning” needs frontier models. Harry’s pushback: isn’t that “the biggest bear case ever” against Claude Code and Codex? Matan’s answer: the surviving 10–20% are “decision-making tokens” — like leadership hours, few but the most valuable — and per-token frontier spend is rising even as share shrinks. Also: “it’s pretty embarrassing that we don’t have frontier open models in the United States.”

Token spend is likely comparable to salary. Against Harry’s benchmark (likely Marc Benioff’s $300M Anthropic spend = 3.8% of dev salaries), Matan says the median within three years is “order of magnitude… comparable to salary” — but dispersion runs from 0% to “tens of thousands of percent” per individual, so a standard per-engineer budget is “painting with way too wide a brush.”

Value accrual is a time-dependent phenomenon — models, apps, and infra are all “trying to commoditize the one that’s not them,” so he strongly disagrees that the next 12 months belong to AI infrastructure. Kirkland’s $500M internal AI build is the counter-lesson: “building AI technology is not a core competency of that firm,” and it’s “actually good for Harvey.” The deeper shift: “there is going to be nothing that no one can build” — moats move from capability to resource allocation.

Labour displacement rhetoric is fundraising strategy, not forecast. Dario’s “we’re going to take your jobs” line “really upsets me… it’s for selfish reasons” — when raising hundreds of billions, “the best way to convince people is to say all of capitalism is gone” — and it will flip at IPO when those same humans are the buyers. Harry’s addendum: likely Zuck and Demis, who never needed the money, never said it. Short-term displacement worries him; long-term no. Infra bubble? “Long-term absolutely not. Like not even close.”

Talent and go-to-market are being repriced together: the Olympiad-funnel résumé is now “kind of anti-signal,” the “age of the polymath is back,” and treating sales/marketing as dirty work is a time bomb — AI companies coasting on the gold rush are “astronauts in space where there’s no gravity. Your muscles will atrophy. Gravity will come back.”

🔗 Original source & video: OpenAI vs Anthropic vs Open-Source | Token Maxing, AI Hangovers & The Coming ROI Reckoning

Factory’s core bet is that enterprise software development will move from in-IDE collaboration to cloud-based delegation across the full SDLC. It targets hundreds of thousands of developers maintaining 30-plus-year-old codebases, where the prize is not working “15% or 20% faster” but handing complete tasks to parallel cloud agents. As human-authored code declines, planning and coordination will remain human-driven while code and documentation execution will probably become fully delegated “very soon”; testing and verification are expected to take more human attention.

The product’s differentiation is orchestration rather than a single coding model: specialized “droids,” enterprise-wide context, selective retrieval, and asynchronous execution. Knowledge, code, and reliability droids connect to systems including Linear, Jira, Slack, GitHub, Sentry, and PagerDuty; the agent asks clarifying questions instead of requiring prompt engineering. In the demonstration, it modified or created roughly 12 files using 43% of its context and could then be instructed to open a pull request, while exposing an “X-ray into its brain.”

Legacy modernization is the clearest enterprise ROI wedge offered in the episode. The founders cite one large public company whose migration reportedly fell from four months to roughly three and a half days, with no downtime. Their representative workflow turns codebase analysis, documentation, dependency mapping, Jira tickets, and parallel implementation into agent sessions, condensing a process bottlenecked by “bureaucracy and technical complexity and understanding.”

Usage-based pricing makes retrieval efficiency a commercial requirement, not merely a technical preference. Customers pay small fixed access and per-user fees, but most spending flows through “standard tokens”; Factory therefore retrieves only relevant code and organizational context rather than dropping an entire monorepo into a growing context window. Enterprise quality is partly tracked through code churn: mature codebases may run at 3%-4%, while poorly maintained or rapidly changing ones can reach 10%-20%.

The founders see the harness and evaluation stack as the higher-leverage layer while frontier models keep changing underneath it. They combine task-based code evals with behavioral specifications for questions, planning, and tool use, while the host cited estimates that a SWE-bench run can cost $8,000-$15,000 and Matan noted that benchmark charts can function as “big bar versus little bar” marketing. Their probably biggest model request is post-training on goal-directed trajectories lasting one to three hours, without the provider-specific CLI habits that currently make models favor Grep or Glob over better tools.

By the founders’ account, commercialization is now constrained more by adoption and top-of-funnel than by initial product pull. After spending roughly the first year and a half of a little over two years refining the enterprise interaction model, they say Fortune 500 deployments accelerated sharply over the preceding 90 days, largely through word of mouth. One January user reportedly said that even if he were the only person at his company using Factory, he would still tell the company to let him use it instead of hiring “three engineers for myself”; Factory is now hiring deeply technical customer-facing operators described internally as “a junior Eno.”

🔗 Original source & video: The AI Coding Factory