Summary

Ben’s core call is that OpenAI’s API business consumes scarce capacity and demands backward compatibility, stability, and an enterprise culture that conflict with building a groundbreaking consumer product. His ideal split puts API maintenance and channel work at Microsoft, accepting its margin so OpenAI can improve the odds of its consumer “moonshot.”
Ben finds the memory vision compelling because “sign in with ChatGPT” could carry a user’s AI persona and circle into purpose-built apps, not merely authenticate identity. A Paprika-like recipe app illustrates why: text may be “the natural interface,” but the companion becomes more useful when expressed through interfaces suited to each task.
This concession does not rescue the existing API strategy: Ben calls the portable-companion concept compelling while describing today’s business as “backwards justification” for an API OpenAI started and now finds difficult to kill. He sees the companion concept as a different platform business from random companies using the API; a diminished Microsoft relationship may also prevent a seamless handoff.
Apple and Google have the cleaner integration path because their phone platforms can see screens, access device memory, and insert AI across applications. Ben says OpenAI is already large enough to make a “sign-in with ChatGPT button” attractive across the web.
Google Circles demonstrates that sound product logic is insufficient without timing, user cognizance, culture, and an installed social network. Ben’s broader lesson is that “success is about more than ideas”: users now manufacture separate circles through group chats, networks, and personas, but Google+ lacked the network when the feature launched.
ChatGPT’s 800 million users versus Anthropic’s 30 million make distribution—not technical capability—the decisive strategic advantage. Ben argues that only OpenAI, Apple, or Google can plausibly build the ubiquitous companion, and calls OpenAI’s “right place at the right time” an opportunity to become “the biggest company since Facebook.”

Deep dive

1. OpenAI should let Microsoft carry the API burden

Ben’s overarching critique: OpenAI’s API is “a distraction and a waste of resources.” Enterprise platforms must preserve standards and backward compatibility, while API customers consume capacity that OpenAI itself describes as constrained.
His preferred division gives Microsoft the channel and “all the dirty work” of maintenance. Andrew notes that this does not forsake consumer upside; Ben replies, “No, it enhances it,” because platform stewardship and groundbreaking product development demand fundamentally different cultures.

2. Memory turns login into a portable AI companion

What Ben found compelling in Sam’s interview was the memory/companion concept, not a reversal of his API critique: a ChatGPT login might carry “your AI, your circle” into another app rather than merely verify identity. Confining that companion to OpenAI’s interface would constrain a persona meant to follow users across contexts.
Ben also argues that the chatbot interface is underrated and text is the natural interface, but it is not the best interface for every task. His concrete example is recipes: a user could open Paprika and find the companion manifested in a purpose-built kitchen experience.
Andrew proposes that APIs preserve muscles for this next layer; Ben rejects that as “backwards justification” for a business OpenAI began and now finds difficult to kill. He treats the portable-companion idea as a different platform business from random companies using the API. A diminished Microsoft relationship may also prevent a clean handoff, though portable memory remains a real update to his critique.

3. Device owners begin with a structural integration advantage

Apple and Google can see what is on-screen, access device memory, and insert AI into conversations. ChatGPT must instead secure partnerships and persuade services to add its login.
Ben says OpenAI is large enough to ask services to add a “sign-in with ChatGPT button.” Andrew’s comparison: carrying an AI companion may be potentially far more valuable than dragging a Facebook profile—and its college photos—around the internet.

4. Google Circles failed because timing and path dependence dominate ideas

Ben calls Google Circles “a great idea,” but it lacked user cognizance, a social network, and the right company culture. Ideally, Google+ would have sorted people into circles, but sorting a life was useless when the relevant people were not there.
His systems lesson is broader: complex systems emerge from many interacting conditions and resist perfect top-down design. Today users approximate circles through group chats, separate networks, and different personas, though the absence of an installed network remains an obstacle.
The super-app comparison makes path dependence concrete: Americans moved from PCs and fragmented communications to smartphones, producing “a screen full of apps.” In China, most people’s first computer was their smartphone, letting WeChat become the natural place to launch services; Zuckerberg’s Facebook-phone vision arrived too late. Had the Facebook phone existed a decade earlier, Ben says, it might have worked.

5. ChatGPT’s installed base creates an option rivals cannot copy

Ben says there is “nothing technologically” preventing Anthropic from building the same companion, but contrasts its 30 million users with ChatGPT’s 800 million. Andrew crystallizes the constraint: “The hard part is getting to a billion users.”
Apple and Google remain plausible alternatives, though each is bounded by its phone platform. Ben’s categorical conclusion is that no other foundation model company can take ChatGPT’s place; OpenAI’s rare advantage is being “the right place at the right time.”

The Dual-Use Founder: Vets Now Building For America Dave CEO, Jason Wilk: The Best Performing Fund Would Only Back YC Founders on Their Second Time