$ man apollo-wiki/sdr-enablement-track

☾

The hacker track is for technical operators who want full control. But most sales teams do not have a GTM engineer on staff. They need something simpler - a workflow that uses Apollo data but does not require writing Python scripts or managing databases. The SDR enablement track uses Claude Co-work (Claude's project/folder system) to organize Apollo exports, run research, and produce CRM-ready output. No code required. Just structured folders and good prompts.

PATTERN

Create a Claude project with three folders: 1. Raw Data - Apollo CSV exports, company lists, conference attendee lists. 2. Research - company briefs, tech stack analyses, competitive intel. 3. Output - icebreaker drafts, personalized email sequences, CRM import files. Claude Co-work reads across all folders. When you drop an Apollo export into Raw Data, Claude can cross-reference it against your research folder to produce personalized icebreakers. The folder system IS your workflow. No pipeline code needed.

PATTERN

Step 1: Export target accounts from Apollo (CSV). Drop into Raw Data folder. Step 2: Ask Claude to research each company - recent news, job postings, tech stack, funding rounds. Claude writes briefs to Research folder. Step 3: Ask Claude to generate icebreakers for each contact based on their title + company research. Output goes to Output folder as a CSV ready for CRM import or email tool upload. The whole flow takes 10 minutes for 50 contacts. An SDR doing this manually would spend 2-3 hours.

PRO TIP

The output folder produces CSV files formatted for your CRM's import tool. For HubSpot: include email, first_name, last_name, company, title, and any custom properties in the header row. For Attio: map to record attributes. For Salesforce: match to lead object fields. The key is standardizing your output format once and reusing it. Claude Co-work can learn your CRM's field mapping and produce import-ready files every time. No Zapier, no middleware, no integration tax.