The complete framework for deploying Claude Cowork in an SDR role is covered in our Claude Cowork for SDRs pillar guide. This article focuses on eight specific techniques — most of them non-obvious — that separate SDRs who get 2–3x the output from teams that bought Cowork but treat it like a faster Google. If you're also looking at workflow integrations, see our companion guides: ICP scoring and prospect research at scale, writing personalised email sequences in 20 minutes, Outreach and Salesloft integration workflows, and the analysis of booking 2x more qualified meetings.
Claude Cowork is Anthropic's agentic AI workspace — it reads files, connects to your sales stack, and executes multi-step reasoning tasks. The eight tips below assume you've connected Cowork to at least your CRM and have a basic canvas set up. If you haven't started yet, the Claude Cowork deployment service handles full team setup.
Pin Your ICP and Value Prop Files — Never Repeat Context
The single biggest mistake SDRs make with Cowork is re-explaining their ICP in every prompt. Cowork's canvas supports persistent pinned files — documents that remain in context across all tasks in a session. Create three foundational files once: ICP-Criteria.md (firmographics, technographics, trigger events, disqualifiers), Value-Prop.md (your solution's 3–4 primary pain points addressed, with specific outcomes and metrics), and Persona-Guides.md (the 2–3 buyer personas you target most: their KPIs, typical objections, and preferred communication style).
With these pinned, every subsequent prompt inherits the full context. Your research briefs, sequences, and objection responses will be calibrated to your exact product and market without you repeating a word of it.
Use Tier-Based Scoring Before You Research Anything
Running deep research on every prospect in a raw list is the most common time drain in SDR workflows. Cowork can score an entire 200-row LinkedIn Sales Navigator export against your ICP criteria in under 3 minutes — before you do a single minute of manual research. The scoring output assigns A/B/C tiers and surfaces the primary qualifying signal for each prospect.
Only run the deep research prompt on A-tier accounts. B-tier gets a lighter touch. C-tier gets removed or queued for a future segment review. This prioritisation alone reduces wasted research time by 60% for most SDRs.
Scoring PromptBuild Competitor-Aware Sequences Using Battlecard Files
Most SDRs write sequences without knowing which competitor the prospect is already using. But Apollo, Clearbit, and BuiltWith data often reveal tech stack signals — and Cowork can use that information to write sequences that proactively address the competitive context rather than ignoring it.
Add your battlecard files to the Cowork canvas (one file per main competitor: their strengths, weaknesses, where you win, where you lose, common objections). When you know a prospect uses Competitor X, instruct Cowork to write a sequence that acknowledges that context — not attacking the competitor, but referencing the specific problem that drives migration conversations.
Competitive Sequence PromptSet Up a Daily Trigger Event Scan with Cowork Dispatch
Trigger-event outreach outperforms cold outreach by 3–5x on reply rates — because you're reaching out when the prospect has a live problem, not at random. The challenge is that monitoring trigger events manually across 500 prospects is impossible. Cowork Dispatch solves this with scheduled autonomous scans.
Configure a Dispatch skill that runs every morning at 7:00 AM. The skill checks your prospect list for signals: LinkedIn job postings at target accounts (indicates growth or new initiatives), press release activity, leadership changes (new CMO, new VP Sales — common entry points), and funding announcements. Cowork delivers a ranked "Today's Triggers" briefing to your inbox or Slack channel by 7:30 AM, with a suggested outreach angle for each flagged account.
SDRs who run this consistently report reaching trigger-event prospects within 2 hours of the signal appearing — first-mover advantage that converts to 3–4x higher response rates versus waiting until the end of the week.
Generate LinkedIn Messages That Sound Like You
Cowork's default LinkedIn message generation is good — but it's better when you give it a few examples of messages you've personally sent that got responses. Add a file called "My-Best-LinkedIn-Messages.md" with 5–8 examples of LinkedIn messages you've written that got replies. Note why each one worked (trigger event reference, shared connection, relevant insight).
When you run the LinkedIn message prompt, instruct Cowork to "match the tone, length, and structural approach of [My-Best-LinkedIn-Messages.md]." The output will adopt your personal voice and the patterns that have worked for you specifically — not a generic AI writing style. SDRs who personalise Cowork's generation to their own successful examples see 40–60% better connection acceptance rates than those using default generation.
Use the 3-File Multi-Source Research Method
Single-source research produces shallow briefs. The most effective SDR research approach with Cowork uses three sources simultaneously: (1) the prospect's company website or recent blog post, (2) their LinkedIn profile, and (3) their company's most recent press release or funding announcement. Upload or link all three before running the research brief prompt.
Cowork synthesises across sources, identifying inconsistencies, extracting the most salient talking points, and producing a brief that reflects the company's real strategic context — not just their homepage messaging. The output quality difference between one-source and three-source research is substantial. Prospects notice and respond to it.
Multi-Source Research PromptCreate a "Hot Reply" Response Protocol
When a prospect replies to your sequence — especially with questions or soft objections — response speed matters more than almost anything else. SDRs who reply within 5 minutes of a hot reply convert at 8x the rate of those who respond hours later. But crafting a good, personalised response in 5 minutes is hard when you're mid-prospecting-sprint.
Set up a Cowork canvas file called "Reply-Protocol.md" with your conversation history template and response framework. When a reply arrives (flagged by the Gmail or Outlook connector), paste the reply thread into Cowork with the instruction to "draft a reply that advances toward a 15-minute call booking, handling the stated objection directly."
Cowork reads the full context — your sequence, their reply, your ICP file, your product value prop — and drafts a response in 20–30 seconds. You review, personalise the opening line, and send within 2 minutes. This protocol consistently delivers 5x the meeting booking rate from replies versus a standard response-when-you-have-time approach.
Build a Team Skill Library for Shared Best Practices
Individual SDR productivity with Cowork is significant. Team-level productivity is transformational — but only if teams share what works. Cowork supports team skill libraries: shared, reusable prompt files that encode your best practices, ICP refinements, winning sequence structures, and persona insights.
Designate a weekly 15-minute team ritual where each SDR contributes their best-performing prompt or technique from the week. Compile these into a shared team canvas file. Over 8 weeks, your team builds a proprietary playbook that reflects your specific market, buyer personas, and what actually converts — not generic SDR advice.
Teams that implement this library approach see continuous improvement in Cowork output quality month-over-month, while teams using only individual configurations plateau. If you're deploying Cowork across a team, our Claude Cowork deployment service includes structured team skill library setup as part of the onboarding.
These Techniques Work. Get Them Running in Your Team.
Our certified architects have deployed Claude Cowork across SDR teams from 8 to 60 reps. We scope the full setup — connectors, canvas configuration, skill libraries — in a free 30-minute call.