One plan, free teammates: chat teams move to a shared usage pool

We used to bill ISMS Copilot chat the way most team software bills: plan price times the number of people. If your compliance team had six people on Pro, the subscription quantity was six: you paid for six seats. That number tracked headcount, which is easy to count, and had nothing to do with what the work costs us or what the product is worth to you.

That model is gone. As of today, a chat team is one plan and one shared usage pool. You buy Plus, Standard, Pro, or Business once. Your team can be up to 50 people. Nobody adds a seat, and nobody asks whether the junior deserves a license before the audit.

Why we killed the seat

Per-seat pricing made sense for software where every login consumes the same thing. An assistant is not that. What costs money is generation: the tokens the team burns, the files it uploads, the Agent Tasks it runs. A two-person team deep in a SOC 2 gap analysis can spend more than a fifteen-person team that checks in weekly. Billing the fifteen the same as the two was not a rounding error, it was the wrong meter.

The worse effect was behavioral. Every seat price is a small tax on inviting the next colleague, and the people you most want inside a compliance assistant are exactly the ones a seat budget makes you think twice about: the control owner who knows why the exception exists, the engineer who can answer the infrastructure questions, the new hire who needs to learn how your ISMS actually runs. Compliance work is a team sport with a shared evidence trail. The pricing should not be the reason the team works in fragments.

So we now bill the thing that actually has a cost: usage. One pool, real limits, visible to the owner.

What shipped

• One plan per team. The owner subscribes once. Teammates join by invitation and are free, and a team can be up to 50 people.
• One shared usage pool. Chat tokens, file uploads, and agent usage all draw from the owner's plan limits, on the same meters a solo plan uses: tokens in 4-hour windows, uploads as a monthly allowance, agent credits monthly.
• A hard stop, not a hidden meter. If the team reaches a limit, that thing pauses until its window resets (the next 4-hour window for chat tokens, the next month for the upload allowance and agent credits), or the owner upgrades the plan. There is no silent overflow billing for teams.
• An owner's usage pane. Settings shows the pool the way a solo user sees personal usage: tokens, uploads, and agent credits, with their reset windows, so the number that governs the pause is the number you can see.
• Solo plans are untouched. If you are not in a team, nothing changes: same plans, same limits, same overflow behavior as before.

Personal Plus stays personal. Joining a team does not cancel your own subscription, and your team membership does not eat your personal plan's allowance. heyGRC also did not change: on Standard, Pro, and Business it stays included for the plan owner, with 100 private reviews a month.

For teams already paying for seats

If you have a team with paid seats today, the quantity on your subscription drops to 1, so the extra seat charge comes off your next invoice. We are not issuing mid-cycle credits; the seat charge stops when the seat line stops. Team usage now draws from the shared pool instead of per-seat meters.

The trade we are making

This is not a discount dressed up as a principle. Teams that use the product heavily will now and then hit a pool limit and pause until that meter resets, or pay for the next plan up. That is the honest version of the trade: you pay for what your team consumes, at the limits shown on the pane, and inviting a colleague costs nothing but the work they add to the pool. If a team finds itself pausing often, that is the product telling you something true about your usage, and the answer is a bigger plan, not a smaller team.

One plan, free teammates, one pool. Invite the people who should have been there all along.