The 45-Minute ChatGPT Seat Audit: Which Paid Seats Can You Cancel?

If half your team only ever types questions into ChatGPT, you may be paying for seats you no longer need — and finding out takes about 45 minutes with your own invoice.

What changed, and what to verify first

TechCrunch reported on August 6, 2026 that OpenAI brought unlimited text chats to ChatGPT's free users.

That is the only outside fact this post rests on, so treat it that way: read the article yourself, then open the plan comparison inside your own account and confirm what your current tier includes as of this month (we're writing this in August 2026). Feature lists and prices rot faster than blog posts do.

Also read the wording carefully, because it matters for your bill: it's about text chats. It is not a claim that every paid capability is now free, and it says nothing about your admin console, your data-handling terms, or your renewal date.

Our read, clearly labeled as opinion: for a lot of small businesses, the message limit was the main reason light users got pushed onto a paid seat in the first place. If that limit is gone for the way they work, the reason is gone with it. The rest of this post is the audit that tells you whether that's true for your team, using numbers off your own invoice rather than ours.

Step 1: Find out what you're actually paying

Pull the real number before anyone argues about it.

• Open your billing portal or last invoice and write down: number of seats, price per seat, billing cycle, and renewal date.
• Search your card and bank statements for the last three months for the vendor name. Watch for a second subscription someone expensed separately.
• Check whether you're monthly or annual, then read your plan's own cancellation and refund terms. Don't assume you'll get money back mid-term — assume you're planning for the renewal date until the terms say otherwise.
• List who each seat belongs to. If you can't name the human, that's your first cancellation.

That's the whole audit input. Fifteen minutes, one spreadsheet, no vendor call.

Step 2: Sort every user into three buckets

Don't ask people "do you use ChatGPT?" Everyone says yes. Ask what they do with it in a normal week. Three buckets:

Bucket A — typers. They paste in an email and ask for a shorter version. They draft job descriptions, rewrite quotes into plain English, brainstorm social captions, ask what a contract clause means. It's all typing and reading. If the reporting above holds for your account, this is the pattern free unlimited text chats is most likely to cover — confirm it in Step 3 rather than taking our word for it.

Bucket B — builders. They upload files, lean on saved memory or custom instructions, connect ChatGPT to other apps, or run something the rest of the team depends on. These are the people whose work would break if you downgraded them.

Bucket C — dormant. They logged in twice in March. Cancel and move on. Re-adding a seat later is a billing change, not a project.

Our expectation, not a measurement: most small teams skew toward A and C with a handful of genuine Bs. Yours might not. If you sort your list and it's all B, congratulations — you have an AI-heavy team and this post saves you nothing. Skip to the last section.

Step 3: Test the downgrade before you commit

The honest test isn't "is the free tier good enough in general." It's "is it good enough for the five things this person actually does."

Pick one Bucket A person. Have them work in a free account for a week and keep a one-line note every time something blocks them. At the end of the week you'll have either an empty list — cancel the seat — or a short list of specific blockers, which tells you exactly which paid feature they need and whether one shared paid seat would cover it.

One week of friction beats a year of paying for a guess.

The worked example (hypothetical numbers — use yours)

Everything below is a made-up example to show the arithmetic, not a customer result and not a quote of any vendor's current pricing. The $25 is an arbitrary round number; substitute the figure on your own invoice.

Say a nine-person services business pays for nine seats at $25 per seat per month: $225/month, $2,700/year.

The audit finds three Bucket B users (the ops lead who uploads spreadsheets, the estimator with a saved workflow, the marketer using connectors), four Bucket A typers, and two dormant accounts.

• Keep 3 paid seats: $75/month
• Move 4 typers to free: $0
• Cancel 2 dormant seats: $0

New cost: $75/month, $900/year. Saved: $150/month, $1,800/year — for roughly 45 minutes of work plus one week of testing.

Whatever your seat price is, the shape holds: savings are (seats you cancel) × (your seat price) × 12. Do that multiplication before you decide it isn't worth the afternoon.

Four traps before you hit cancel

1. You may be buying controls, not message volume. Before you move anyone, open your plan's own feature comparison and write down what you're paying for besides chat: admin and provisioning controls, and the data-handling terms that apply to your account. Then read the terms that apply to a free consumer account. We can't tell you what's in your contract — your account and your invoice can. Opinion: if your team pastes customer records, medical details, or anything under a client NDA into a chatbot, paying for a business-tier account is defensible on governance alone. The seat count is the thing to cut, not the governance.

2. Annual terms set your timing. If you're on an annual plan, put the renewal date in your calendar with a reminder two weeks out and make the change then, per whatever your cancellation terms say.

3. Shadow subscriptions. If you cancel company seats, some people will quietly expense their own. Tell the team what the plan is and which seats remain shared, or you'll pay more in reimbursements than you saved.

4. Free tiers change. What's unlimited in August can be metered later — that's a caution, not a prediction we can source. Re-run this audit quarterly; it's a 15-minute recurring calendar event, not a project.

What to do with the money

The savings here are real but modest. The bigger win is what the audit reveals: you come out of Step 2 with a written list of what your team actually does with AI all week. That list is the most useful automation document a small business can have, and it costs you one afternoon.

In our experience building this stuff, the Bucket B work — the repeated file-and-workflow tasks — is usually the part worth building properly instead of redoing by hand in a chat window every Monday. Chat seats are the cheapest part of an AI budget. The expensive part is people re-typing the same thing week after week.

Do the math on your own numbers

If you want a structured version of that second question — what's worth automating, and what it's likely to return — run our AI Readiness & ROI Calculator. It's a free five-minute assessment that projects ROI over 24 months based on your answers. Do the seat audit first with your real invoice, then run the calculator to see what the saved money could buy.