Uber expands ChatGPT Work from a pilot to more than 30,000 employees

Uber is expanding ChatGPT Work from a 1,000‑employee pilot to company‑wide availability for more than 30,000 employees, according to [OpenAI’s October 22 announcement](https://openai.com/index/uber‑chatgpt‑work‑rollout/). The agentic workspace operates within ChatGPT Enterprise and is intended to take on multi‑step knowledge‑work tasks. OpenAI describes it as Uber’s first company‑wide deployment of an agentic platform for that kind of work. The change is the scale and organization of access. A pilot gives a limited group a tool to try; a company‑wide rollout requires more teams to understand where it fits into their work. OpenAI names operations, finance, marketing and product among the functions that will be supported. Its announcement concerns Uber employees and does not announce an extension to the platform’s drivers, couriers or riders. The [Gemini small‑business hub covered by OpenTools](https://opentools.ai/news/gemini‑small‑business‑hub‑branding‑connected‑apps‑finance‑rollout) groups business tasks for owners using the Gemini app. Uber’s announcement instead concerns an employee deployment within ChatGPT Enterprise, with company‑approved integrations and training.

[OpenAI names Google Drive, Gmail, Google Calendar and Slack](https://openai.com/index/uber‑chatgpt‑work‑rollout/) as tools ChatGPT Work can connect with. The stated tasks include researching information, preparing meeting briefs, creating presentations, analyzing data and completing workflows across applications. That describes a broader role than answering a question in an isolated chat: the intended workflow uses information from existing workplace systems to produce a finished work product. OpenAI says GPT‑6.1 Sol will be the default capability within ChatGPT Work for Uber, alongside access to its broader model portfolio and multimodal tools such as voice and image generation. Uber’s developers and software engineering teams will also continue using Codex. These details describe the deployment’s intended capabilities; they do not show which connections every employee will have enabled or which actions any particular integration will permit.

The rollout will be backed by [Uber’s internal AI skills library, approved integrations and dedicated employee training](https://openai.com/index/uber‑chatgpt‑work‑rollout/), OpenAI says. Those are meaningful parts of the announcement because distributing access does not by itself define a repeatable workflow. Teams still need a shared understanding of the task, the information it requires and the standard a finished output must meet. For an employee, a useful first check is therefore which integrations and skills the company has approved for their team, followed by what review is expected before the output is used. The announcement does not publish a permissions matrix, an inventory of Uber’s internal skills or its detailed data‑governance rules. Those details should not be inferred from the names of the connected apps.

The scale figures come from [the companies’ announcement](https://openai.com/index/uber‑chatgpt‑work‑rollout/), which includes statements from Uber CTO Praveen Neppalli Naga and OpenAI president Greg Brockman. They establish what the rollout is intended to make available. They do not establish that all eligible employees are already active users, how often they use the agent or how reliably a particular workflow is completed. OpenAI says the companies plan to share more information about adoption, use cases and measurable outcomes as the rollout progresses. The post provides no measured productivity result for this company‑wide deployment, contract price or evidence of a change in staffing. Those remain separate questions. The useful next evidence will connect access to actual work: which teams adopt the workspace, what tasks they complete with it, how much human review remains and whether the results justify expanding a workflow. For now, the supported news is a substantial expansion of enterprise AI access, accompanied by training and an approved integration strategy. *Figure by OpenTools Team; no third‑party expressive material used. Original explanatory figure based on the linked primary source.*