OpenAI Is Bidding for the Seat Between You and Your Customer
Each launch claims a different control point, and your leverage to refuse lies in the systems of record that agents cannot work without.
Read the four launches as one architecture and each one claims a different control point. Dots captures user intent. Plugins capture distribution. ChatGPT Space captures the working context. Sign in with ChatGPT captures identity and billing. Ben's Bites names the target plainly: the layer between your users and your software.
The Pragmatic Engineer fills in the enterprise half of the same move. OpenAI renamed Codex to ChatGPT Work and moved its own finance, recruiting and legal teams onto it in June. ChatGPT spend can now flow to 16 partners' models and offerings. That is the AWS playbook: accept that the underlying model becomes a commodity, then own the workflow and the bill.
Where your leverage sits
Dots have a structural weakness. Ben's Bites notes they become useful only once they are connected to calendar, email, Slack, Notion and Jira, and they lack user-authored memory files. Their value is borrowed from systems of record. If you own a system of record, agents will drive more usage of your data, as long as you expose it on your terms. If your product is a workflow screen over someone else's data, the agent reduces you to a tool call.
TLDR IT reaches the same split. Systems of record, compliance-heavy products and proprietary-data businesses get stronger. Products whose value is mostly their interface get weaker. Even holdouts are conceding. Pi adopted MCP, the emerging standard for letting agents call software, after saying publicly that it never would.
The wallet is a margin gift on platform terms
Sign in with ChatGPT lets users spend their existing ChatGPT allowance inside your AI features. That means zero inference cost for you on those features. The price is that OpenAI sees your customers' identity, billing and usage. The wallet is not exclusive, though. A third-party builder has already paired ChatGPT sign-in with Claude subscriptions. If you support several wallets, the customer relationship stays yours.
Standing access arrives before your policy does
Any employee on an eligible plan can now run an agent on a computer you don't control. That agent is built to connect to corporate email, calendars and Jira. TLDR IT's core point is that security models were designed for agents with temporary, task-scoped permissions. They break when agents hold standing access. Non-human identity management (named owners, scoped permissions, periodic review, offboarding) now sets the speed limit on adoption. If plans are bought individually, adoption can start outside procurement.
The vendor is also less predictable than its launch list suggests. CSO reports that OpenAI abandoned its planned October GPT 6.1 Astra update after internal testing found safety and alignment problems. Any customer commitment pinned to one lab's release date carries risk you don't control.
Where the reporting disagrees
Ben's Bites flags that earlier attempts at apps inside ChatGPT underperformed. Its positive read on Plugins comes from one observer. The Information sees the agent contest as still open: Meta's Muse has passed 4M weekly users, and Apple's identity-aware Siri hub launches October 13. No single agent surface has won yet. That argues for being callable from all of them rather than living inside one.
Make your product easy for any agent to call, and never give the agent your permissions, your data or your bill.
What to do
Run a 'Dot-test' by October 31. Have an agent try to complete your top five customer jobs through only your API or MCP server, and classify each job it fails as either a moat or a gap.
Issue a non-human identity standard this week, covering a named human owner, least-privilege scope, a review cadence and an offboarding trigger. Make it a precondition for approving any Dots plan or plugin.
Pilot Sign in with ChatGPT on one AI feature this quarter, built to accept more than one wallet. Model the inference savings against what you lose in billing and usage visibility.