00About this unit
Workshop participants will build skills and applications with Claude, the same kind of work done for ERUDITA. Before the workshop, someone has to decide how every participant gets a working Claude account that includes Cowork. This unit explains the two routes, the exact set-up procedure, the cost, and what happens to the licences after the workshop.
01The concept: a licence is an account with a plan
Cowork is not a separate product to buy. Its capabilities are part of Claude and are included in every paid plan (Pro, Max, Team, Enterprise). The Free plan does not include Cowork. What a participant needs is therefore a paid Claude account. The only real decision is who pays and how the accounts are created.
Cowork runs in the Claude desktop app on macOS or Windows (Windows needs the latest version). This applies to both routes.
02The two routes
Route A: Team plan, one payer
One organisation owner buys a number of Standard seats in a single purchase and invites each participant by email. Participants pay nothing.
- Monthly price: $25 per Standard seat (annual billing is cheaper per seat but commits you for a year)
- Example: 23 seats = $575 for one month, before tax
- Admin settings control skills and file creation for everyone
- Same setup and same usage limits for every participant
Route B: Pro, bought individually
Each participant subscribes from their own Claude account.
- Monthly price: $20 per person (about $17 on annual billing)
- Example: 23 people = $460 in total, paid by each person
- Each person switches on "Code execution and file creation" in their own settings
- No central admin view of the accounts
Side-by-side
| Point | Route A: Team Standard | Route B: Pro |
|---|---|---|
| Includes chat, skills, HTML files and apps, Cowork | Yes | Yes |
| Who creates the accounts | The owner invites each participant by email | Each participant |
| Who can pay for everyone | One payer, one purchase | No documented way for one payer to buy Pro for other people's accounts |
| Where skills and file creation are switched on | Organization settings > Skills, once for all | Settings > Capabilities, on each account |
| Usage per session | 1.25x Pro | Baseline |
| Admin can see and change settings | Yes | No |
| Cancelling | One cancellation by the owner | Each person cancels their own |
03Procedure for Route A (Team)
Payer, in a web browser
No special configuration of the payer's computer is needed, only a browser. The licences live in the Anthropic account online, so the payer's computer can be switched off without affecting anyone.
- Go to claude.ai/login and sign in with a business email address. Gmail, Yahoo and Hotmail addresses are not accepted for creating the Team plan.
- Choose the Team plan, select monthly billing, and set the number of Standard seats.
- In the organisation's admin settings, add the email domains the participants use (for example gmail.com or a university domain) to the allowed domains.
- Go to Organization settings > Members > Add member > Bulk add, and paste the participants' email addresses separated by commas or new lines.
- In Organization settings > Skills, check that "Code execution and file creation" and "Skills" are both enabled.
- Test with one extra account: create a small skill and ask Claude for an HTML file.
Each participant
- Install the Claude desktop app from claude.com/download (macOS or Windows).
- Accept the email invitation. It expires after 21 days; an expired invite can be resent from Organization settings > Members.
- Sign in to the Team account inside the app.
- Optional: run Anthropic's small compatibility checker, linked from the Cowork support page, to confirm the computer supports Cowork.
04Procedure for Route B (Pro)
- The participant signs in to or creates a personal Claude account.
- They subscribe to Pro at claude.ai/upgrade with their own payment method.
- In Settings > Capabilities they switch on "Code execution and file creation" and make sure skills are available. Greyed-out skills mean code execution or skills are disabled.
- They install the Claude desktop app from claude.com/download.
- After the workshop they cancel, or keep the plan.
05Cost
| Item | Calculation | Total (before tax) |
|---|---|---|
| Team Standard, monthly | 23 seats x $25 | $575 |
| Team Standard, monthly, with one extra seat for the owner | 24 seats x $25 | $600 |
| Pro, monthly, paid by participants | 23 people x $20 | $460 |
Prices are US list prices. VAT and the euro price in the EU are not confirmed here; the final figure appears at checkout.
06Timeline: before, during and after the workshop
| When | Action |
|---|---|
| 1 to 2 weeks before | Collect participant emails and their domains. Buy the seats (Route A). Add allowed domains. Send the invitations. |
| 2 days before | Confirm that skills and file creation are enabled. Test with one account. Ask participants to install the desktop app and accept the invitation. |
| Workshop day | Everyone signs in to the Team account and builds skills and applications. |
| After the workshop | The licences run for the paid month, so participants have extra days to keep working. |
| Before the renewal date | Cancel the plan, or reduce the seats so that only the people who will design the game keep a licence. |
07HeyGen: a separate cost question
Which tools the game designers need after the workshop depends on the kind of game they design. If the game uses AI-avatar video, HeyGen licences may be needed on top of Claude. Their cost is not covered by this unit and should be checked with HeyGen separately.
08Points to verify before buying
- Seat minimum. Anthropic's support page says Team requires at least 5 members. A July 2026 announcement reported by secondary sources says the minimum is now 2. With 23 seats this does not matter.
- Owner's seat. Whether the person who creates the organisation occupies one of the paid seats has not been confirmed. Check at checkout.
- EU price and VAT. Confirm at claude.ai/upgrade.
- Menu names. Anthropic's pages use both "Organization settings > Skills" and "Capabilities" for the same toggles. Look for the two toggles in either place.
09Pre-flight checklist
- Payer has a business email address (not Gmail, Yahoo or Hotmail)
- Monthly billing selected, Standard seats, correct number of seats
- All participant emails collected and checked for typos
- Participant email domains added to the allowed domains
- Invitations sent by email (invite link not shared)
- "Code execution and file creation" and "Skills" both enabled
- One test account created a skill and an HTML file successfully
- Every participant has a Mac or Windows laptop with the desktop app installed
- Calendar reminder set before the renewal date to cancel or reduce seats