How to connect AI usage to business value

As more teams use AI, admins and business leaders need to understand where it creates value and where to invest next. Usage and spend tell part of the story, but admins also need to see what people use AI for and what it helps them accomplish.

Analytics in the ChatGPT Admin Console bring together usage and cost data, task insights, and outcome metrics across ChatGPT Work and Codex.

Here’s how admins can use these tools to understand adoption, support teams, and assess business value.

Understand AI usage and spend

Usage analytics show where adoption is growing and spend is concentrated, helping admins focus support, review costs, and assess capacity requests. The Usage view brings together active users, credits, and token usage across ChatGPT Work and Codex. For example, filtering by group or user can reveal where adoption is low, giving admins a reason to review starting workflows and training needs with the team owner.

The Usage overview shows active users and credit trends across ChatGPT Work and Codex. All screenshots use illustrative demo data.

See what work teams are doing with AI

The task classifier in Insights helps admins understand what work AI supports by grouping a sample of messages into use cases and tasks. Software engineering, for example, includes feature development and code maintenance, while sales & revenue include account research and planning. The Overview tab shows the mix of work at a glance; the Use cases tab provides a detailed table with task breakdowns. Admins can filter by group to see how teams use AI, then work with business owners to decide which workflows and outcomes to evaluate.

The Insights overview shows how credits are distributed across tasks, from implementing features to account research.

For the sales team shown below, account research and planning is the largest use of credits—a starting point for discussing how AI changes account preparation.

The Use cases table breaks down a team’s work by task, with credits, messages, and active users.

Identify where teams need training and support

In task details, the Models , Reasoning , and Speed breakdowns show each setting’s share of credits for a task. This helps admins assess whether the setup fits the work and target training on model selection. A routine brief, for example, may be worth testing with a faster or lower-cost setup, comparing quality and the time spent reviewing and correcting it.

The Plugin leaderboard and Skills view show which tools support a task, helping admins focus training and decide which workflows to maintain or share. Low use of a relevant plugin may point to an access or training need; a frequently used skill may need a clear owner and regular updates.

Track Codex contributions to engineering outcomes

The Outcomes view shows Codex contributions to merged commits and lines of code, alongside code-review activity. Trends and available group, user, or repository filters help admins and engineering leaders understand adoption and decide where to expand access or support teams.

If Codex contributes to a growing share of merged code, engineering leaders can compare that trend with review time, defects, and rework to assess whether it is helping the team ship software more effectively.

The Outcomes view tracks the share of merged commits and lines of code with Codex contributions over time.

The Admin plugin in ChatGPT Work lets admins compare adoption, spend, and tasks, then turn findings into reports for budget and rollout decisions. It can also create finished work, such as a leadership deck with charts, key findings, and recommended next steps, ready to share with cross-functional stakeholders.

With the Admin API, teams can automate reports in their own dashboards and combine analytics with business-system data. For example, a support dashboard could show credit use alongside ticket resolution time.

The Admin plugin compares team credit trends and summarizes changes for a monthly rollout review.

Connect analytics to business outcomes

Usage and task data are a starting point for admins to investigate value with business owners. Business owners add the context needed to assess it: what changed in the workflow, whether results improved, and what that improvement is worth. Together, they can connect product activity to measures such as delivery time, quality, or profitability.

Suppose the task classifier in the Admin Console shows that account research is common in a sales group. The admin checks whether model choices fit the task, provides training where a CRM plugin is underused, and shares a skill for consistent account plans. The sales owner then compares preparation time and plan quality with the team’s baseline. If time is saved, they track how much goes into customer conversations, which conversations become qualified opportunities, and which opportunities become sales. Revenue and contribution margin on that business help show whether the extra capacity produces a financial benefit.