Claude for Your Team · Lesson 7 of 7

Capstone: the 30-day check

15 minutes, 30 days after setup. The owner leads; the team helps. Find out who's using Claude, who needs a different seat, which settings need a second look, and what to fix next.

---

Thirty days in, you have a real month of use to look at. Not a guess about how the team *might* use Claude. What they actually did. This check turns that month into a few clear decisions, and it only takes fifteen minutes if you've kept the checklist from Lessons 1, 2 and 6.

Open the 30-Day Check template. Put a reminder on your calendar for the same day every month after this, too. The first check is the longest. After that, it's five minutes.

Go to Organization settings > Members and Organization settings > Usage. Fill in the seat table on the template, one row per person.

For each person, ask three questions:

• Did they use it? If someone hasn't touched it in a month, ask them why before you cut the seat. Sometimes the answer is "I didn't know how to start," and Lesson 3 fixes that. Sometimes it's "I don't need it," and that's a seat you can remove at renewal.
• Did they hit their limit? If you turned on usage credits, the MTD Spend column shows who went over. If you didn't, ask the team who got stopped.
• Is their seat type right? Someone hitting the limit every week may need Premium. Someone on Premium using it lightly may be fine on Standard (that change takes effect at renewal).

Also check:

• Pending invitations nobody accepted. Each one takes a seat.
• Anyone who left the business. Remove them from Organization settings > Members. Anything they shared stays available; anything only in their private chats doesn't (Lesson 4).

Write down:

• Seat cost this month, from your bill.
• Usage credit spend this month, if you turned them on. Was it under your organization limit? Did the limit stop anyone at a bad time?
• API credits. Did they arrive in the Console's Promotional credits section? Did anyone use them? If no one did, that's fine. Note it and move on.

Then compare the total to what you expected in Lesson 6. If it's higher, the seat table will tell you why.

Walk your Team Setup Checklist from Lesson 2 and confirm nothing has drifted:

• Rate chats is still set the way you chose.
• Connectors: every one on the list in Organization settings > Connectors still has a named job. Remove any that don't.
• External sharing for artifacts is still set the way you chose. If it's on, ask who has shared something by public link, and whether it should still be live.
• Restrict organization creation is still on.
• Owners: you still have two people who can manage the organization, and both still work here.

Ask three questions at a team meeting or in a quick message. Write the answers on the template.

• "What's one task Claude now saves you real time on?" This tells you what's working. Make it a shared Project if it isn't one yet.
• "Where did it get something wrong?" This tells you which project file or instruction needs fixing. A wrong price is almost always a stale price book.
• "Did you ever use a personal account or another AI tool for work this month? Why?" Ask it kindly and mean it. If the answer is "the company account hit its limit" or "I couldn't find the project," that's a setup problem you can fix, not a person problem. The rule from Lesson 3 only holds if the company account is the easy choice.

You'll have a list. Pick no more than three things for the next 30 days. Common ones:

• Remove or downgrade a seat that isn't used (at renewal).
• Upgrade the one person who hits the limit every week.
• Build the next shared project for the task people mentioned most.
• Fix the stale file behind the most common wrong answer.
• Retrain one habit from Lesson 3, usually "leave the person out" or "check before sending."

Write the three fixes, an owner for each, and a date.

• Every month: five-minute check. Seats, spend, one question to the team.
• Every quarter: walk the full Setup Checklist again. Claude adds features and changes menus often. Reread the settings pages for anything new that's on by default.
• When someone joins: Company Account Rule Card on day one, a seat with a named job, and access to the shared projects they need.
• When someone leaves: remove them the same day, check their seat count, and make sure anything the business needs was in a shared project.

Use your three templates and tick every box:

• [ ] The Team Setup Checklist shows the plan, seat types, two Owners, and every setting from Lesson 2 chosen on purpose, with who changed it and when.
• [ ] Every person who uses Claude for work has a seat in the company organization, signs in with a work email, and has signed the Company Account Rule Card.
• [ ] At least one shared Project is in daily use, with one or two editors and current, dated files.
• [ ] Anything sent to a customer or touching money was checked and sent by a person.
• [ ] Usage credits are off, or on with a limit; the API credits are claimed to a business-owned Console organization.
• [ ] The 30-Day Check is filled in, with no more than three fixes, each with an owner and a date, and a reminder set for next month.

You started with Claude scattered across personal accounts, with nobody sure what was where. Now the business owns one organization. The settings that matter were chosen on purpose. Everyone knows the one rule. Shared work lives in shared projects. The bill has a ceiling, and the credits that came with the plan are claimed.

Most of all, the setup is the easy path. That's what keeps company work in company accounts: not a policy, but a setup that's simpler to use than the alternative.

Next steps, when you're ready:

• [Cowork: Hand Off a Job](/courses/cowork-hand-off-a-job) to give Claude a whole task with you checking the result.
• Write Your Team's AI Rules in an Afternoon to turn the Rule Card into a signed policy.
• Answer Customers Faster with AI to build your first customer-facing shared project in full.
• Lock the Doors: AI Security Basics for a Small Office for the passwords and sign-ins behind all of this.

Previous: Costs, seats and the monthly API credits · Back to the course