Claude Code for SDRs: The Daily Workflow Guide
Setup, three workflows, and the guardrails. The Claude Code patterns that save SDRs 60 to 90 minutes per day.
What an SDR Gets From Claude Code
An SDR spending an hour every morning researching the day's call list, drafting follow-up emails, and updating the CRM is doing the kind of work Claude Code handles fastest. Not the calling. Not the conversation. The administrative wrap and the pre-call prep around the calls. A working SDR with Claude Code installed gets back 60 to 90 minutes per day.
This guide is for the SDR who can use a terminal but isn't a developer. The patterns below are concrete: install, set up, three workflows that pay back immediately, and the guardrails to keep your manager happy.
The Setup, in 30 Minutes
1. Install Claude Code. Visit code.claude.com and follow the install instructions. On a Mac it's a single curl command. On Windows it's the WSL path. The CLI runs in your terminal.
2. Get a Claude Pro subscription. $20/mo gets you Claude Code Pro. Use a personal card if your company doesn't have a centralized AI budget. You'll expense it after week one when it's saving you hours.
3. Create a project folder. mkdir ~/sdr-tools && cd ~/sdr-tools. Write a CLAUDE.md file (the next section) so Claude Code knows your context.
4. Wire HubSpot or Salesforce via MCP. Run claude mcp add hubspot or follow the Salesforce MCP setup. The OAuth flow takes 5 minutes. After this, Claude Code can read your CRM directly.
Your CLAUDE.md Template for SDR Work
The CLAUDE.md is a markdown file in your project folder that tells Claude Code who you are and what you do. Paste this template and edit for your context.
# Rome's SDR Context
## My role. SDR at Acme Inc, mid-market segment, ICP is 200-1,000 employee SaaS companies in North America.
## My quota. 30 meetings booked per month, 60 SQOs.
## My tools. Outreach for sequences, HubSpot for CRM, Apollo for contact data, ZoomInfo for firmographics.
## My ICP. VP Sales, VP RevOps, Director of Sales Ops at qualifying companies. Champion: Senior Manager of Sales Ops. Economic buyer: VP Sales.
## My ICP rubric. Tier A: 500+ employees, Series B+, uses Salesforce, hiring SDRs in last 90 days. Tier B: meets 3 of those criteria. Tier C: meets 2.
## My voice. Direct, specific, brief. No "hope you're well." Always lead with one specific detail about the prospect's company.
Workflow 1: Morning Call List Prep (15 min)
This is the highest-value workflow for an SDR. Every morning, you have 20 to 40 accounts on your call list. Each one needs context before you dial: recent funding, hiring signals, tech stack, your last touch.
The prompt to Claude Code: "Pull the 20 accounts on my call list from HubSpot list 'today-calls'. For each account, get the recent funding from PitchBook (via MCP), recent SDR hires from LinkedIn (via the LinkedIn MCP server), and the last touch from HubSpot. Format as a one-line summary per account. Save to today-callsheet.md."
Claude Code reads your HubSpot, calls the relevant tools, and writes the file. You open it in any editor and read down the list while you call.
Workflow 2: Follow-Up Email Drafts (10 min for 15 emails)
After your morning calls, you have 15 follow-ups to write. Each one references the specific conversation. Each one has a different angle.
The prompt: "For each call I made today (pull from my Outreach activity log), draft a follow-up email. Reference one specific thing the prospect said. Suggest a clear next step. Match my voice in the CLAUDE.md. Don't send. Save each draft as a separate file in today-followups/."
Claude Code reads your call activity, drafts each email, and saves them. You review each one in 30 seconds, edit a sentence if needed, and paste into Outreach. The total time drops from 60 minutes to 15.
Workflow 3: Account Research Brief (5 min per account)
When you get a new account assigned, you need a research brief. Org chart, tech stack, recent news, common pain points for the ICP, suggested angle.
The prompt: "Research [Company Name]. Pull firmographics from my Apollo MCP. Get recent press from web search. Identify the top 3 contacts in my ICP titles (VP Sales, VP RevOps, Director Sales Ops). For each contact, pull their LinkedIn bio. Write a 1-page brief with company summary, recent signals, top 3 contacts with notes, and a suggested opening line for outreach."
Claude Code runs the research and writes the brief. You read it in 2 minutes. Total time from "new account assigned" to "ready to dial" drops from 25 minutes to 7.
Guardrails: What an SDR Should Not Do With Claude Code
Don't send emails without reading them. Claude Code can write 20 follow-ups in 2 minutes. Send any one without reading and you're one bad email away from a deal-killer. Read every draft before paste.
Don't write to the CRM autonomously without checking. Claude Code can update fields, log activities, and create contacts. The pattern that works: have Claude Code draft the update to a staging file, then you manually paste-approve into HubSpot. Don't give the agent write access to your CRM until you trust it and have tested every workflow.
Don't share your CLAUDE.md with private CRM data in it. Your ICP rubric is fine to share. The specific account list isn't. Keep account data in the working files, not the persistent CLAUDE.md.
Tell your manager you're using it. Most managers approve of any tool that saves their reps time. Tell them what you're doing and why. Don't hide it.
The Result, After 30 Days
SDRs who adopt Claude Code at this level typically report 60 to 90 minutes per day in time savings, mostly on pre-call prep and follow-up drafting. The time goes back into more calls, more research, or fewer hours worked. Your quota attainment probably improves because your prep is better and your follow-ups are tighter.
This is the SDR-specific entry point to the broader Claude Code patterns. For deeper workflows, see the Claude Code sales agent guide and 12 GTM use cases. For the build-vs-buy decision on AI SDR platforms (11x, Artisan), see that comparison.
Authoritative References
For Claude Code's CLI and setup, see Anthropic's Claude Code documentation. For the HubSpot MCP server, see the HubSpot MCP setup guide.
Frequently Asked Questions
Can an SDR use Claude Code without being a developer?
Yes. Claude Code is designed to be usable from natural-language prompts. An SDR who can use a terminal (open it, type commands, read output) can use Claude Code productively. You don't need to write Python or understand APIs. You describe the workflow you want, Claude Code does the rest. The first day's learning curve is 30 minutes; after that the friction drops to near zero.
How much does Claude Code cost for an SDR?
Claude Code Pro at $20/mo bundled with Claude Pro is the entry tier. For most SDR workflows (call list prep, follow-up drafting, account research), the Pro tier covers daily use comfortably. Heavier users move to Max at $100/mo. The cost typically pays back in the first week through hours saved.
Will Claude Code replace SDRs?
Not the SDR job, no. The conversations, the discovery, the multithreading inside an account, the negotiation, the customer relationships, none of that is automatable today. What Claude Code automates is the administrative wrap around the calls: prep, research, follow-up drafting, CRM hygiene. SDRs who use Claude Code well do more of the high-value human work and less of the administrative drudgery.
Should I tell my manager I'm using Claude Code?
Yes. Tell them what you're doing and why. Most managers approve of any tool that saves rep time. If your manager is skeptical, demo one workflow (typically the morning call list prep) and let them see the output. Hiding the tool creates a problem you don't need to have.
Can Claude Code send emails directly to prospects?
Technically yes, through your Outreach or Salesloft MCP server. Operationally no. SDR follow-ups should be reviewed by a human before send. The pattern that works: Claude Code drafts the email and saves it to a file. You read, edit, and paste-send. Sending autonomously is a quick path to a bad email going out and a deal blown.
Source: State of GTM Engineering Report 2026 (n=228). Combines survey responses from 228 GTM Engineers with analysis of 3,342 job postings.