What plan should my team be on for ChatGPT Work?

Start with the owner and heavy operators on individual $100 per month plans, not the $25 per seat Business tier, which will not carry anyone who actually operates agents. Once your agent operations have rules and standards, you can consider a pooled plan for the wider team, with the caveat that one runaway project can drain a shared pool for everyone.

What goes wrong when a whole team gets agents at once?

Collisions. Two people have the same idea, both send their agents into the shared Google Drive, and the second agent rewrites what the first one organized. Or a marketing team member's agent is asked to publish one blog post and takes down the entire website. Without a shared log, nobody can even tell whose agent did what, and reverting is guesswork.

A Human-Agent Standard Operating Procedure: the successor to SOPs written for humans only. A HASOP defines how humans and agents work together on a process, which agent touches what, what requires human approval, and where actions get logged, so work stays coordinated as agents multiply.

Should employees use their own ChatGPT accounts for company work?

No. Pay for the subscription and tie it to an email on the workspace domain you own. When someone builds business infrastructure under a personal account, retrieving it later is hard, and technically you do not own it.

Who should get agents first in a small business?

The owner-operator. Establish the structure, naming standards, and rules with your own agent first, then onboard team members and their agents into that system. Onboarding everyone simultaneously into an unstructured environment is how the chaos stories start.

ChatGPT Work for Teams: Roll It Out Without the Chaos

The question I get most from owners with small teams: "What do I get for my people? What plan should we be on?"

The honest answer starts a step earlier, because the plan is the easy part. The hard part is that when your team gets agents, your business goes from one actor changing things to many, and most small businesses have no structure for that. OpenAI's plans really appeal to enterprise, and enterprises have IT departments to absorb the chaos. You have you.

The full ChatGPT Work tutorial, including the team plan discussion this guide expands on.

The Two Collisions Coming for Your Team

The Drive collision. Your agent goes into the shared Google Drive and organizes everything: structure, naming, the works. Your co-owner has the same idea the same week. Their agent goes in and reorganizes it according to its own logic, rewriting what your agent built. Neither of you finds out until things stop being findable. And because the two agents ran in separate accounts with no shared record, there is no log of whose agent did what, and no agent can see the other's work to fix it.

The website collision. The one from the top of this page. An agent scaffolds your custom website and it looks beautiful. A marketing team member's agent goes in to publish a single blog post and takes the site down, or quietly rewrites things it was never supposed to touch. "Revert it to what it was" only works when there is a record of what it was, and across two disconnected agent accounts, there is none.

Both stories have the same root. Every human on your team suddenly has hands that work at machine speed, and nobody agreed whose hands touch what.

The Rollout Order That Works

First: the owner-operator, alone, on a $100 plan. Before any team member gets an agent, you establish the foundation with yours: how files are named, where things live, what the agent may touch, what needs your approval. My setup tutorial covers the personal side; the point here is sequence. The structure has to exist before the team arrives, because agents inherit whatever environment they land in, including a lawless one.

Second: heavy operators, on their own $100 plans. Skip the $25 per seat Business tier for anyone who will actually operate agents; $25 of monthly usage disappears in days for a real operator, as the pricing guide lays out. Onboard operators one at a time, into the rules you already proved with your own agent.

Third, and only after the rules hold: consider pooling. Once operations are figured out, a pooled team spend, say a thousand dollars a month, can be simpler than a stack of individual plans. Know the failure mode before you choose it: tokens in a pool bill differently, and one employee's project going rogue can drain the spend for the entire team. Pools reward teams that already have discipline and punish teams acquiring it.

Write the HASOP Before You Need It

You have SOPs, standard operating procedures written for humans. Agents need the next version, and I call them HASOPs: Human-Agent Standard Operating Procedures. What is going to happen, and how are we going to work together, when some of the "we" are agents?

A starter HASOP for a five-person team fits on one page:

Rule	What it prevents
One agent owns each shared system (Drive, website, CRM). Other agents request, never write.	The Drive collision. Two organizers with equal authority guarantee a rewrite war.
Every agent action on shared systems gets logged where the whole team can see it.	The "whose agent did this?" dead end. A revert is only possible when the record exists.
Naming and filing standards are written down where agents can read them.	Each new agent inventing its own organizational logic on arrival.
Customer-facing sends, publishes, and payments require a named human approval.	The website collision, and every version of it involving invoices and inboxes.
Contractors working under your domain follow your recording and context protocols.	Half your client conversations being invisible to the agents that need them.

Hand the drafting to your own agent once your structure exists:

Paste into Work mode

I am onboarding two team members and their agents next week. Based on the folder structure and naming standards we have established, draft a one-page Human-Agent SOP for them: which agent owns which shared system, what their agents may read but not write, where every agent action gets logged, and what requires my approval before it happens. Then test it: spawn sub-agents playing the role of a new team member's agent and see whether the rules actually stop them from rewriting what we built.

The Ownership Rule That Saves You Later

One more, learned from watching it go wrong. If your team uses agents, you pay for the subscriptions, and every seat is tied to an email on the workspace domain you own.

I have seen people log into the agent with the wrong email and build something custom for one business inside another email's account. Retrieving that work later is very hard, and technically you do not really own it. The infrastructure your agents build, the sites, the tools, the automations, should accumulate under accounts that belong to the business, including the GitHub and Cloudflare accounts it builds with. Your business's agent layer is an asset. Hold the title.

Common Questions

What plan for a team of five? Owner plus heavy operators on individual $100 plans first. Pool later, if ever, once the rules hold.

Can my whole team just start at once? They can, and that is how the Drive and website stories happen. Owner first, structure second, team third.

What is a HASOP again? A standard operating procedure written for humans and agents working together: full framework here.

Do contractors need to follow this too? When they work under your domain doing your business's work, yes, including recording protocols. Otherwise their slice of your business is invisible to your agents.

What if collisions already happened? Stop adding agents, establish single ownership per system, and have one agent rebuild the structure with logging on. Then onboard the others back in, one at a time.

Bottom Line

Agents multiply whatever operational discipline your team already has. Build the rules with one agent before you hand out five.