Find savings on the Opportunities board

Read the Opportunities board, understand what each finding means, and act on the ones worth fixing.

The Opportunities page shows the changes most likely to lower your AI spend or improve how people work. Tokenize builds it from your organization's sessions, so it fills in once usage data is arriving.

Who can do this: Admins. See Roles and permissions.

Open the board

  1. Go to Opportunities in the sidebar.
  2. Pick a date range in the top-right corner. The default is Last 30 days. You can also choose 7 or 90 days.

Each column loads on its own, so some columns can fill in before others. If nothing qualifies, you see "No opportunities found".

The four columns

ColumnWhat it covers
Runaway SessionsSessions that run long or keep going after the work is done.
Context EfficiencySessions that rebuild context every turn or reset their cache mid-session.
CoachingHabits people can change, such as picking a better model for the task or giving clearer instructions up front.
ControlsSettings and inventory an admin can change, such as unused connectors and skills, failing MCP servers, and extras like fast mode left on.

What you might see

Tokenize checks every session and adds new checks as AI tools change, so the cards you see depend on how your organization works. A card only appears when Tokenize finds something worth acting on. Typical findings include:

  • Sessions that keep running after the work is done.
  • Context that's rebuilt every turn, or caches that reset mid-session.
  • Routine work running on a pricier model or setting than it needs.
  • Repeated work that a skill or scheduled task could take over.
  • Tools and MCP servers that fail and retry.
  • Connectors and skills that are set up but never used.

Read a card

Click a card to open its details. Depending on the finding, you see:

  • Summary: what Tokenize found, in plain numbers.
  • What to do: the concrete next step.
  • Est. savings: an estimate of what the fix could save. It only appears when Tokenize can estimate it.
  • Affected spend: what the affected sessions cost in the selected range.
  • Affected users: who the finding applies to. When the list is long, click Show all to see everyone.
  • Sessions: example sessions. Click one to open it on the Sessions page. See Sessions.

Some cards have no dollar figure. Unused connectors, for example, show counts instead.

Some cards come with a skill that helps people carry out the fix. When a card has one, its details include Recommendation: Session Revive Skill. This skill helps people pick up earlier Claude Code or Codex work in a fresh session without loading the whole transcript.

  1. Expand Recommendation: Session Revive Skill.
  2. Click Add skill. The Add a skill dialog opens with the skill filled in.
  3. Choose who it goes to under Send to, then click Add skill.

If your organization already manages a skill with that name, you see "Skill already managed" and your existing copy stays as it is. For the rest of the managed skill settings, see Managed skills.