Competitor outbound, in one prompt

The 5-tool problem

Building an outbound campaign manually looks like this:

1. Apollo or LinkedIn Sales Nav to build the list
2. Hunter or Prospeo to find emails
3. ZeroBounce or NeverBounce to verify
4. ChatGPT or Claude to write personalized lines
5. Instantly or Lemlist to send

Each tool has its own login, billing model, and export format. A 200-contact campaign takes 2-3 hours of tab-switching.

How to build a campaign in one prompt

Step 1: Describe your ICP

Claude Code reads the Deepline campaign builder skill and searches the live Play catalog. If no prebuilt fits, it creates an owned Play:

deepline plays search "company contacts" --json
deepline plays describe prebuilt/company-to-contact --json
deepline plays describe prebuilt/name-and-domain-to-email-waterfall --json
# Claude Code authors eng-leaders-campaign.play.ts from the inspected contract.
deepline plays check eng-leaders-campaign.play.ts
head -n 6 icp-search.csv > pilot.csv
deepline plays run --file eng-leaders-campaign.play.ts --csv pilot.csv --watch

Step 2: Review the pilot

Deepline runs 5 contacts first. You see:

• Each contact with verified email
• The personalized first line
• Credits used

Step 3: Scale to full list

Claude Code reruns the same checked Play on the full input. Provider calls, scoring, and the idempotent sequencer write stay inside the Play so the run has durable receipts:

deepline plays check eng-leaders-campaign.play.ts
deepline plays run --file eng-leaders-campaign.play.ts --csv icp-search.csv --watch

Results land in your sequencer ready to send.

What happens under the hood

Cost breakdown

Personalization adds ~1 credit per contact. Sequencer push is BYOK; managed mode meters provider calls.

Who uses this

• GTM engineers building repeatable outbound systems
• Founders running founder-led sales
• Agencies spinning up campaigns across multiple clients

Deploy as a weekly workflow

Once the one-off works:

Claude Code adds the cron binding to the Play's definePlay options:

{
  cron: { schedule: '0 8 * * 1', timezone: 'America/New_York' },
}

It checks the source, publishes it, and verifies the live contract:

deepline plays check eng-leaders-campaign.play.ts
deepline plays publish eng-leaders-campaign.play.ts
deepline plays describe eng-leaders-campaign --json
deepline plays versions --name eng-leaders-campaign --json

Fresh leads, fresh personalization, every week. Run history in the dashboard.

Common questions