How to track AI tool subscriptions across a team: ChatGPT, Copilot, Claude and Gemini

AI subscriptions are the fastest-growing line on a small company's software bill, and the hardest to see. They almost never arrive through procurement. Someone starts on a personal monthly plan, puts it on a personal or company card and claims it on expenses; a few months later a team plan appears beside the personal ones; and nobody owns the total. The result is the classic shadow-IT shape - real spend, renewing every month, with no single record of who is paying for what.

This guide covers the pattern rather than any one vendor's current price (those change more often than any other line on the bill): where AI subscriptions hide, how a personal plan differs from a team plan when someone leaves, what renewal date each seat carries, how consolidating onto one team plan helps, and how to get the lot onto a register. The vendor specifics below were checked on 27 October 2026; confirm the current plan and terms on each vendor's own page before you act on them.

Where AI subscriptions hide

Four places hold almost all of them, and only the last two are anywhere an admin would normally look:

• Expense claims. A personal ChatGPT or Claude plan bought on a personal card and reclaimed monthly shows up only in the expense system, described as whatever the claimant typed.
• Company card statements. The same plans bought on a shared card appear as a small recurring charge that reads nothing like a contract. The discovery sweep for software nobody owns is the way to pull these out.
• The Microsoft 365 admin center. Microsoft 365 Copilot is a per-user add-on to eligible Microsoft 365 plans, bought and assigned under Billing in the admin center (Microsoft also sells a Copilot Business add-on for organisations of up to 300 users on eligible Business plans). It is a seat on top of a subscription you already have, so it is easy to miss when you look at the base plan alone.
• The Google Workspace Admin console. Gemini is now a core service bundled into most Business and Enterprise Workspace editions and turned on per organisational unit under Generative AI, while separately-licensed per-user access has moved to Gemini Enterprise, assigned from Directory then Users. The older per-user Gemini add-on is being retired, so what you are paying for depends on when you bought it.

Personal plan versus team plan

The difference that matters is not the features; it is who owns the account and its data when the person leaves. A personal plan belongs to the individual: the login, the chat history and anything built on top of it go with them, and billing is tangled up with their expenses. A team or business plan puts the account under a workspace an admin controls, so a seat can be reassigned and the work survives a departure.

ChatGPT Business (the plan OpenAI renamed from ChatGPT Team in August 2025) and Claude's Team plan both put members under a workspace with an admin console and central billing, and both state that business data is not used to train models by default - the reason to move people off personal plans beyond simple ownership. Claude's Team plan runs from a minimum of two members up to 150 seats and bills on headcount at the start of each cycle. When you off-board someone, reclaiming their AI seat belongs on the same checklist as everything else: see the software off-boarding checklist.

Monthly versus annual seats, and the date each carries

AI plans are sold both monthly and annually, and the two carry very different renewal risk. A monthly seat renews twelve times a year, each a small charge that is easy to leave running long after the person stopped using it. An annual seat commits you for the year and has one date that matters - the last day to decide before it rolls over. Copilot's business add-on, for example, is an annual commitment that can be billed monthly or annually, so the invoice cadence does not always match the commitment. Record the actual renewal date for each, not just the billing frequency.

Consolidating onto one team plan

Once you can see the personal plans, the usual move is to fold them into one team plan per vendor: an admin owns the workspace, seats are assigned and reclaimed centrally, data stays with the company, and you negotiate and renew once rather than chasing a dozen personal expense lines. Do it per vendor - the people on personal ChatGPT plans are not always the people on personal Claude plans - and keep the single team renewal date where everyone can see it.

Record it in your register

Whatever you decide, the step that stops the problem recurring is writing each AI subscription down with the few fields that make it manageable. The register fields that matter guide covers them in full; for an AI plan the ones that earn their place are the owner (a named person, not "the team"), the renewal date and notice period, the billing cycle, the seat count, and whether it is a personal or a team plan so you know whose it is when they leave.

StackTrackr is the register for exactly this: one record per tool, an owner against each, the renewal date and notice period turned into a deadline, and an alert before the window closes. See the features overview for the full picture, or start free and add the AI plans your sweep turns up.