Setting up Claude for your company

You've been handed this job

Where to start

What the first two weeks actually look like — the four things to figure out before you configure anything, how to find the right Project owners, and what good looks like at 30 days.

Which plan is right for your company?

Claude Plans

Free, Pro, Team, and Enterprise — what you actually get at each tier, the decision framework for choosing, and why most admins get this wrong in one of two predictable directions.

Your first 30 minutes as a Claude admin

Admin Setup

The exact sequence: provisioning accounts, setting org-level defaults, and the decisions you need to make before anyone on your team logs in for the first time.

Setting the rules your team will actually follow

AI Usage Policy

Most AI usage policies are either too vague to be useful or so restrictive they get ignored. The three-zone model that works in practice — what is open, what requires review, and what is off-limits.

Structuring Projects across the whole org

Claude Projects

How to architect Projects at an org level — naming conventions, who owns what, system prompt governance, and what to upload. One focused Project per team beats ten generic ones.

Which Skills to enable where

Skills

Not every Skill makes sense for every team. How to decide what to turn on, what to leave off, and how to avoid giving access to things your team isn't ready for.

What to connect — and what to leave off

Connectors

The framework for deciding which data sources to give Claude access to. Not everything should be connected — here's how to evaluate each integration before enabling it.

Controlling costs from day one

Tokens

How token usage translates to spend, where most teams leak budget without realizing it, and the configuration choices that keep costs predictable as usage grows.

Is it actually working?

Evals

How to measure whether your rollout is delivering — beyond adoption metrics. The lightweight evaluation process any admin can run, even without a data team.

Rolling out the new stuff responsibly

Cowork & Dispatch

Cowork and Dispatch are powerful and easy to misuse. How to introduce agentic features to your team in stages — so they extend capability without creating chaos.

Staying current as Claude evolves

Managed Agents

Claude ships major capability updates every few months. How to keep your organization's setup current without constant fire drills — and how to evaluate new features before rolling them out.

Month 3 and beyond

Ongoing Maintenance

The recurring admin work after the rollout is complete: user management, policy updates, connector reviews, spend monitoring, and the common incidents and how long they take. A realistic estimate of steady-state overhead.