ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsMaterial4 min readDisconfirmAI Editorial

OpenAI Enterprise Product Lead Alexander Embiricos: The Key to dots Is Not Adding Features, But Framing It as 'One Entity'

Alexander Embiricos, head of enterprise product at OpenAI, explained the design philosophy of dots at TechCrunch Disrupt: the core is not creating new technology, but framing the assistant experience as 'one entity, one conversation'; the product evolved from the coding tool Codex, proactively researching how to help in the gaps between conversations, but the tension between conservative default permissions and intuitive experience remains unresolved.

2026-10-27 10:00 GMT+8

At TechCrunch Disrupt, Alexander Embiricos, who leads OpenAI’s enterprise product team, explained the design philosophy behind dots, summarizing the product team's work in one sentence: "A lot of that isn’t building some new piece of tech into the product; it’s how you frame it to the user and how it feels." This may sound like public relations boilerplate, but it points to a specific design decision—defining dots as "one entity, one conversation," rather than a collection of many different conversations.

Embiricos said, "There’s kind of this convergent evolution happening," referring to the efforts by various companies to build AI assistants. He noted that the OpenAI team realized if they could frame the product as "an entity and it’s a single conversation, not many different conversations… it starts to become intuitive." This choice was cognitive rather than technical—the underlying model did not change—but it meant users were not facing a system requiring them to manage multiple session windows, but rather a "person" that continuously understands them and proactively thinks about how to help.

The evolutionary path of dots also confirms this logic of prioritizing framework over technology. Embiricos pointed out that users could actually achieve most of dots’ functionality using Codex, OpenAI’s coding tool released earlier in the year, "but that requires more work and hand-holding." What the product team did was repackaging the underlying capabilities of Codex so that non-engineers could use it. This path aligns with OpenAI’s move to spin ChatGPT Work out of agentic coding tools built for software engineers: the technology already exists, and the product team’s job is to make it intuitively accessible to more people. Even the name itself—derived from the negative space in OpenAI’s logo—is intended to "feel like just something that could eventually be ubiquitous."

Sign in / Sign up
ReadingResearchRadarInvestment framework

"Proactive research" is the core mechanism distinguishing dots from traditional chatbots. Embiricos described its operation: "On a cadence, it will think about what it knows about you, what is the conversation that it’s had, and then what have you given it access to that it can think about, and then it will go and research, ‘What could I do to be more helpful to you?’ And then, basically, it will propose that." This means dots works even when the user is not asking questions, implying more token consumption for OpenAI and an assistant that is "thinking about you and thinking how to help you" for the user.

However, testing by TechCrunch found that while this proactive thinking ability is apparent and often useful, it is not yet mature. Embiricos cited his own example: the first time dots alerted him to a calendar conflict, it was only three minutes before the event. "It’s like, ‘Hey, this thing is coming up. You might want to do something about it.’ I only have three minutes!" He expects timing precision to improve, but emphasized that being "proactive" is key to the product. Another example he cited came from an engineer at a drone delivery startup: during a service outage, dots had already noticed the issue, analyzed it, and come to the engineer with a solution.

OpenAI’s approach to permissions has seen significant shifts. Embiricos recalled that upon launch, they set "really conservative defaults," causing dots to frequently request permission, which drew criticism. He knew such feedback would come but believed "this is okay, we can tune that over time." Currently, dots refuses read-only access to cloud drives, demanding higher-level control; users can turn off model training and control resource access in ChatGPT settings, but "those controls aren’t granular." Embiricos stated, "What I think we need to do is basically build out super, super, super granular controls," while acknowledging that the model’s "intelligence and discretion" are the other side of this coin.

Perhaps most intriguing is Embiricos’s personal stance on scaling. He mentioned having a human assistant because OpenAI’s corporate partners want to interact with a real person, adding, "I personally never intend to have a meeting with someone else’s agent." This reveals an unresolved fundamental tension: if everyone has an agent, can agent-to-agent interaction truly replace human-to-human interaction? OpenAI is "deep in lots of conversations with payment processors," but Embiricos admitted, "we’re not always moving the fastest in terms of shipping the next ability for the agent to work with the world." Allowing AI assistants to spend money could be OpenAI’s first potential revenue source, but it represents a massive trust threshold for consumers.

Sources

  • techcrunch.comTechCrunch↗
Continue researching →