Anthropic Client Workspace Setup (Onboarding)

Anthropic Client Workspace Setup (Onboarding)

1. 01

   Create the client workspace in the Anthropic Console and issue a dedicated API key per client

   Register the Anthropic account, then generate a separate key for each client engagement so token spend can be attributed and revoked without touching other accounts. Keep the Max plan at $200/mo in reserve for high-throughput builds (200+ requests per minute) and start new clients on the Free tier ($0) or Pro ($20 monthly, $17 monthly billed annually) while scoping.

2. 02

   Select the Claude model tier against the client's task, not the client's budget

   Claude Code and Claude Design variants exist for code generation and design work, and the model family spans Mythos, Fable, and Opus tiers. Match the tier to the deliverable: content and document analysis rarely need the top tier, while coding assistance and security analysis justify it.

3. 03

   Wire Claude into the client's existing stack through the native connectors

   Claude connects to Slack, Microsoft 365, AWS, and Google Cloud. Confirm which of these the client already runs before proposing a custom integration, because a Slack or Microsoft 365 connection shortens time-to-value to days rather than weeks.

4. 04

   Configure prompt templates and brand voice in a sandbox before touching client data

   Deploy a test integration in a sandbox environment first. Build the prompt templates that carry the client's brand voice and service descriptions, and validate output quality there. This is the step that makes the Claude Starter Content Kit deliverable repeatable.

5. 05

   Enable the features the retainer actually depends on

   Turn on web search, file creation, code execution, and memory across conversations where the workflow needs them. Extended thinking is worth enabling for complex work, but it consumes more tokens, so decide per client rather than globally.

6. 06

   Set usage caps and a token budget per client before go-live

   Consumption-based pricing on input and output tokens makes fixed-price retainers risky. Set a monthly token ceiling per client key and document what happens when it is hit, so a single runaway workflow does not erase the margin on the engagement.

7. 07

   Hand off the workspace with a written operating guide

   Document the key rotation schedule, the model tier in use, the connectors enabled, and the prompt templates. The Starter Content Kit handoff guide exists for exactly this reason: the client self-serves content generation after setup instead of filing tickets.