Complete Guide
The Complete Claude Code Setup Guide — From Zero to Power User
90 minutes to a working system. 30 days to power user. Every failure point from 30+ real onboardings.
This guide assumes you're not a developer. If you can create files and folders, you can do this.
The six-phase path
Each phase builds on the last. You can stop at Phase 3 and have a useful system — but the compound value lives in Phases 4-6.
Installation
Desktop App or Terminal. Five common errors everyone hits.
Your CLAUDE.md
The 5-section template that makes Claude Code remember you.
First Skills
Meeting prep, deal research, content draft — build one per week.
Best Skills for Non-Engineers
Research, content, operations skill categories with evaluation filters.
Adoption Patterns
Daily startup habit, 5 essential commands, common failure fixes.
30-Day Power User Path
Week-by-week progression from foundation through team rollout.
Phase 1 — Minutes 0-20
Installation
Two paths: Desktop App (recommended) or Terminal. Same engine, different surface. Start with the Desktop App — move to terminal when you want speed.
Path A: Desktop App
Download from Anthropic. Click "Code" in the left panel. Full Claude Code capabilities without touching a command line.
Path B: Terminal
Open your system's native terminal (not an IDE terminal). Run the one-line installer from the official quickstart.
The 5 installation errors everyone hits
Installing from Cursor's terminal
Install from your system's native terminal. After installation, you can run Claude Code from Cursor fine.
claude: command not found
Close and reopen your terminal completely (not a new tab — close the whole application). Restart computer if needed.
Hidden .claude folder
Mac: Cmd+Shift+. in Finder. Windows: View > Show > Hidden items. This folder is where your skills live.
API key not recognized
Most common cause: extra whitespace. Key starts with sk-ant-. No quotes. Verify with claude --version first.
Permission prompts feel alarming
Respond y (yes), n (no), or a (allow all similar). Normal behavior, not a broken install.
Phase 2 — Minutes 20-45
Your CLAUDE.md
A plain text file Claude reads at every session start. Your ICP, voice, deal stages, tools — explained once, inherited everywhere.
The 5-section GTM template
Who I Am
Role, company, what you sell, tenure. The conference version, not the LinkedIn headline.
Who We Sell To
ICP: titles, company size, industries, specific pain points. 5-10 bullets.
How We Sell
Deal stages, methodology, tools in your stack. Maps Claude Code output to YOUR pipeline.
My Content Voice
How you write. Negative constraints work better: "Never use exclamation marks" > "write casually."
What I Need Help With
3-5 highest-frequency tasks. Becomes your skill-building roadmap.
Start with 20 lines. It'll grow to 200 as you notice what context Claude Code actually uses.
The prompt that builds it for you
Even faster: share your LinkedIn profile URL and let Claude Code extract your background.
Phase 3 — Minutes 45-75
Your first skills
A skill is a markdown file (SKILL.md) in your .claude/skills/ folder — a saved workflow triggered with a slash command. Build one per week.
Meeting Prep Dossier
Week 1Company + contact → structured briefing with ICP-mapped pain points and talking points. 90 seconds, replaces 20 minutes of tab-switching.
Deal Research Brief
Week 2Deep account intelligence: financials, tech stack, org chart, competitive landscape, objection map. Compounds because it references your positioning.
Content Draft Generator
Week 3Topic + format → first draft in YOUR voice. Week 1 drafts: 60% usable. Week 4 drafts: 85% usable. The CLAUDE.md voice section improves it.
Skill chaining (where it gets powerful)
One prompt. Multiple skills in sequence. All drawing from the same CLAUDE.md context.
Phase 4 — Month 1
Best skills by role
The skills that produce the most value depend on what you actually do Monday through Friday.
Sales / AEs
Start with:
Meeting prep + deal research + competitive positioning
Week 1 ROI:
Save 15-20 min per meeting prep × 5 meetings/week = 75-100 minutes recovered.
Month 1 compound:
After 20+ dossiers, institutional memory of your prospect landscape. Patterns emerge: which pains resonate, which angles work.
Accelerator skill:
Post-call debrief skill: captures outcomes, feeds back into prep for next similar prospect.
Marketing / Content
Start with:
Content draft + voice matching + competitive messaging
Week 1 ROI:
Voice-matched first drafts need 20 min polish vs 90 min rewrite for generic AI output.
Month 1 compound:
CLAUDE.md voice section refined through 15-20 drafts. Each refinement improves the next draft.
Accelerator skill:
Content repurpose skill: one blog post → 3 LinkedIn posts + email snippet + slide points.
RevOps / Operations
Start with:
Pipeline analysis + win/loss extraction + territory planning
Week 1 ROI:
Weekly pipeline review prep: 30 minutes instead of 2 hours.
Month 1 compound:
Win/loss patterns accumulate. System recognizes: "Deals with this competitor stall at Stage 3."
Accelerator skill:
Forecast risk skill: flags deals likely to slip before they actually do.
Customer Success
Start with:
Account health monitoring + renewal prep + expansion signals
Week 1 ROI:
Proactive outreach based on usage data before accounts become churn risks.
Month 1 compound:
Health profiles on every account. When a CSM leaves, institutional knowledge stays.
Accelerator skill:
Expansion signal skill: monitors usage patterns to ID upsell opportunities.
Phases 5-6 — Month 1-3
The 30-day power user path
Week 1: Foundation
- •Meeting prep daily for every external call
- •Refine CLAUDE.md after each session
- •Set up Git as your undo button (5 minutes)
Week 2: Expansion
- •Build deal research skill
- •Connect CRM if it has an API
- •CLAUDE.md should be 50-80 lines
Week 3: Voice
- •Build content draft skill
- •Feed it your best past content as voice examples
- •Try chaining: meeting-prep + deal-research for full account strategy
Week 4: Audit
- •Review what's working, delete what isn't
- •CLAUDE.md should be 80-150 lines
- •Identify next 3 skills based on recurring tasks
The month-three decision point
This is where most DIY setups plateau. You know 10-15 features. The gap from "basic user" to "operator with compounding systems" is architectural — connecting individual skills into a system where research feeds content, content feeds distribution, and everything compounds.
Rolling this out to your team
The champion model: one person gets good, shows results, shares skills. Adoption spreads through proof, not mandates.
Common team rollout mistakes
- 1Everyone starts at once — instead: one champion for 2 weeks, then 3-5 early adopters, then whole team
- 2Mandating usage without demonstration — show a meeting prep dossier in standup, let proof spread
- 3Sharing CLAUDE.md instead of SKILL.md — share workflows, let each person build their own context
- 4No feedback loop — when someone improves a skill, share the improvement so the team system compounds faster
Frequently asked questions
How much does Claude Code cost?
Pro subscription: $20/month. Usage on top: $20-50/month at daily GTM usage on Sonnet. Max plan ($100/month) for higher limits. Heavy Opus users: $100-200/month.
Do I need coding experience?
No. You need to be comfortable creating files and folders. If you can organize a Google Drive, you can build Claude Code skills.
What's the difference between Claude Code and the Claude chat?
Claude chat is a conversation. Claude Code is an operating environment: reads files, writes files, connects to tools, remembers context across sessions.
Can I use this with my existing tools?
Yes. Connects to CRMs (HubSpot, Salesforce), browsers (Playwright), databases, and APIs. Each connection makes skills more powerful.
What if I get stuck at the plateau?
Read our readiness assessment or the DIY vs professional comparison for the honest math on both paths.
How do I share skills with my team?
Skills are markdown files. Share via Git, Dropbox, Slack, or email. Each team member copies the skills folder and customizes their own CLAUDE.md.
What's the ROI math?
Conservative: AE saves 20 min/meeting × 5 meetings/week = 7 hours/month. At $150/hr loaded rate, that's $1,050/month from one skill vs $20-100/month subscription.
Ready for the full system?
This guide covers 80%. The other 20% — context engineering, knowledge graphs, systems that compound without maintenance — is architecture work. 20-minute discovery call to see if professional setup makes sense for your situation.