How OpenAI Builds for 800 Million Weekly Users: Model Specialization and Fine-Tuning
Summary
OpenAI’s distribution strategy is deliberately two-sided: ChatGPT reaches roughly 800 million weekly users, while the API may touch an even broader population through third-party products. Sherwin Wu says this follows the founders’ mandate to distribute AI’s benefits across as many surfaces as possible, despite customers’ recurring fear that ChatGPT might enter their market. At its current growth rate, the first-party product is such a force that internal competitive anxiety is limited: “10% of the globe uses it every week.”
Models are proving unusually resistant to commoditization because both users and developers form model-specific dependencies. Users form preferences among GPT-5, GPT-4o, and o3, while developers tune prompts, tools, and application harnesses until they are effectively “building a product around the model.” That combination produces surprisingly high API retention and weakens the classic platform risk that an application abstracts away its underlying supplier.
OpenAI has moved from expecting “one model that rules them all” to increasingly expecting room for a portfolio of specialized models. Cursor illustrates the emerging stack: GPT-5 in Max mode for planning, Composer for fast first passes, and other models for deeper bugs or tab completion. Sherwin expects “a proliferation of other types of model,” though he cautions that today’s view may change again; specialization is not presented as a retreat from AGI, but as evidence that the path is less predictable than assumed.
Reinforcement fine-tuning turns proprietary enterprise data from a retrieval asset into potentially differentiated model capability. Earlier supervised fine-tuning mostly delivered “instruction following plus” and tone changes; RFT can potentially produce a state-of-the-art model for a customer’s narrow use case. OpenAI is piloting discounted inference and potentially free training for customers willing to share valuable datasets—an explicit exchange around the “giant treasure troves of data” sitting inside companies.
The application bottleneck has shifted from clever prompts to context engineering and controlled orchestration. Better reasoning models still need the right tools, data, retrieval timing, and procedural boundaries; Martin Casado’s reductio is that classic RAG uses cosine similarity to choose what gets fed “into a super intelligence.” For enterprises, intelligence does not eliminate workflow structure: many jobs require deterministic SOPs, approved response catalogs, and enforceable limits on what an agent may do.
OpenAI treats agents as intelligence expressed through different interfaces, not as a separate product category. ChatGPT, Codex, Sora, and the API are “different interfaces and different ways of deploying” the same core intelligence; Codex became separate because a CLI suited coding better than ChatGPT. This creates room for startups to embed or build around Codex—the economy Casado jokingly calls “token laundering,” turning natural-language input into metered intelligence.
Usage-based API pricing has held because it maps cleanly to consumption, supports cost-plus margin discipline, and may already approximate outcome pricing. OpenAI sees usage pricing as a possible “one-way ratchet”: once customers pay closer to realized utility, deployment-style pricing becomes hard to restore. Outcome billing remains appealing but difficult across domains such as crop yields; Martin argues that as test-time compute rises with task difficulty and value, token usage may become a workable proxy for outcomes.
Open weights appear additive rather than cannibalistic, while efficient inference remains a meaningful operational moat. Sherwin says OpenAI has “not seen cannibalization at all” from gpt-oss because its customers and use cases differ from those of the major hosted models. Even hypothetically releasing GPT-5’s weights would not reproduce OpenAI’s serving performance: its largest two or three models receive concentrated resources, and the inference and training teams optimize together. Multimodal breadth likewise depends on specialized stacks—shared API infrastructure above separate text, image, and video inference systems.
Deep dive
Not yet available upstream; scheduled sync will retry.