Anthropic marketer uses Claude Code to automate personalized weekly sales briefings
Key point
The system pulls data from BigQuery via MCP to generate unique Monday digests for every account executive, doubling event registrations in one week.
Details
Adam Ward, a field marketer at Anthropic, replaced manual Sunday evening slide preparation with an automated workflow using Claude Code. The system generates personalized Monday morning Slack briefings for every account executive, tailoring content to their specific accounts and territories.
How the workflow operates
The process begins with a plain-language prompt explaining the business goal to Claude, treating the marketer as a product manager rather than a coder. Claude connects to BigQuery via MCP to access the marketing team’s source of truth, which aggregates data from HubSpot, Clay, and Salesforce.
To personalize each update, Claude pulls the rep’s territory from the CRM and relevant account updates from Slack. The digest includes:
- Top three priority actions for the week
- Field events relevant to the rep's accounts
- Contacts who have registered for upcoming webinars
- Relevant marketing content such as blog articles and ebooks
Iterating with user feedback
Initial rollout involved a test group of 10 sales reps to catch errors. Feedback drove the addition of nine specific content rules, such as preventing Claude from inventing URLs and filtering out events where the contact title does not match the intended audience. The prompt was also updated to dynamically read header rows in data sheets, preventing errors when column structures change.
Scaling and impact
The system now supports all sales segments, including Business Development Representatives (BDRs), customer success, and alliance teams. Each message is unique, composed from the recipient's own account list. The automation resulted in a doubling of registrations for an executive dinner in a single week. The workflow is fully autonomous, running without manual approval even when the author is on holiday.
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.