What Apero does with Claude Code

What we do with Claude Code

Claude Code is the tool for jobs that cross several systems and do not need a UI. It calls the CRM, Clay, EmailBison, or Monday through APIs or MCP, with the SOP written in the repo.

The hard part is not syntax. It is knowing what should happen in the sales process. So this work pairs with operators who know the motion.

Example workflows

1. 01

   Bulk CRM surgery with the user's own permissions

   Trigger

   Owner assignment, stage hygiene, dedupe, or last-activity fields are wrong across hundreds of records.

   System

   Claude Code works through the CRM's API or CLI (the Salesforce CLI in particular) with the same permissions as the human running it.

   Output

   Records updated in bulk, for example opportunity stages based on last activity date.

   Operator outcome

   Cleanup that used to be a week of clicking, without giving the agent more access than the person has.

2. 02

   Slash-command GTM jobs

   Trigger

   An operator needs company enrichment, EmailBison ops, post-call notes into CRM, prospecting from a report, or follow-up drafts after a demo.

   System

   Commands call Clay, Exa, EmailBison, or Monday through APIs or MCP, with explicit SOPs in the repo.

   Output

   The job done, with the SOP it followed written down.

   Operator outcome

   Repeatable work instead of a one-shot chat that has to be re-explained every time.

3. 03

   Run an outbound campaign from the terminal

   Trigger

   A new campaign needs domains, hosting, sending, and personalization.

   System

   Benyamin (Ben) Holley's own setup (Apero's Head of GTM): Claude Code buys domains through Dynadot, hosts on Cloudflare, warms and sends through EmailBison, and personalizes from Apollo and Moz. Sonnet subagents check that cited facts in each email are true.

   Output

   A live campaign, with an exclusion list applied first (nobody already in an opportunity, nobody contacted in the last 14 days).

   Operator outcome

   The same setup runs thousands of leads, not 50 at a time.

4. 04

   Build a list Clay would make painful

   Trigger

   A one-off list where every requirement is different, for example dental offices within 100 miles with more than 20 people.

   System

   Claude Code pulls accounts through Serper and other APIs, then the CSV is audited by a human before use.

   Output

   A list built for one job, checked before it goes anywhere.

   Operator outcome

   Coverage that a database filter would miss, without setting up a new table for each idea.

How we work in your systems

Access

Ideally each user gets their own API key or MCP connection, mirroring their permissions. The Salesforce CLI, for example, only sees what that user's profile can see.

Change control

Before an agent gets write access: save contact state before enrichment so it can roll back, keep the write key in a separate env file, and make Claude ask twice. Destructive or campaign-changing actions stay behind approval.

Documentation

API docs are downloaded into the repo so the agent reads them instead of rereading the internet. SOPs live next to the commands that use them.

Handoff

Commands, SOPs, and scripts are committed to GitHub so the next person, or a cloud agent on that repo, can run them.

When we do not use Claude Code

• Shared work that the whole team needs to watch, like an enterprise TAM refresh. That goes in Clay.
• Turning account executives into GTM engineers. Do not make AEs learn Git.
• Anything without a rollback plan if it writes to the CRM.

FAQ