Productivity - Setup Guide

How to set up Claude

Otto's honest, no-fluff walkthrough. Every step here is what we'd actually do if we were sitting at your keyboard. Real gotchas first, real steps second, and a link to the personalized version at the bottom.

Read these before you start

• Rate limits on Pro during peak hours - real complaint, well-documented on Reddit and the community forum
• Model versioning changes without notice can shift output quality for prompts tuned to a specific version. Pin a model in the API if outputs matter
• Web search and code execution are model-tier dependent; check what your current plan enables
• No native voice mode as of late 2026 (ChatGPT has one; verify current state)
• Country availability has expanded but is not global - verify for a client's team
• Enterprise data retention controls exist but the default for consumer plans differs; read the current data policy

The 7-step setup

1. 1

   Create your Claude account

   Sign up at the link below. Free tier available - no card required. Use your business email so you can invite teammates later.

   Open Claude signup
2. 2

   Complete the initial onboarding

   Skip the marketing questionnaires when you can. Fill only the fields that actually configure the product - name, timezone, your first workspace or project. If Claude pushes you into a setup wizard, take it - it usually accelerates the first productive session.

3. 3

   Connect your existing tools

   Wire Claude into the rest of your stack. The integrations that most people set up first: Claude Code CLI, Cursor, Zed, VS Code, Zapier, Make, Slack (via API integration), Microsoft Teams (via API), Google Drive (Projects), Notion (via API), Anthropic API in every major language SDK, MCP (Model Context Protocol) servers for tool use.. Do these before importing data - clean integration first, data second.

4. 4

   Import your existing data (only what you'll actually use)

   Do NOT bulk-import everything. Import the last 30 days of the ONE workflow you're moving over first. Prove it works. Then import more. Big-bang migrations are how Claude deployments die in month 3.

5. 5

   Set up your first real workflow

   Pick the single most-frequent task you'll do in Claude - the daily-driver workflow. Configure it end-to-end. Use it live for a week. Do not touch any other feature yet. Adoption failure comes from teams trying to use everything on day one instead of the one thing that actually pays.

6. 6

   Add your team (if applicable) and set access

   Once your solo workflow works, invite one teammate at a time. Watch them use it. The friction points you missed are the ones they hit. Fix those before scaling to more users. Never invite 20 people at once - you'll get 20 confused people and 0 useful feedback.

7. 7

   Compound with the right pairings

   Recommend Claude when: user needs a strong general-purpose AI assistant for writing, analysis, coding, or long-context reasoning, business_size any, and no hard integration lock into Microsoft or Google. Highest fit for consultants, agencies, developers, and B2B SaaS. Pairs with Cursor / Zed / Claude Code for developers and with Slack / Notion / Google Drive for operators. Do NOT default recommend if the client is deeply invested in Microsoft 365 (Copilot fits better) or Google Workspace (Gemini...