How to Use Instantly for Cold Outreach to Crypto Projects

TL;DR

• Audience fit first: This workflow is for agencies and service providers selling services to token-based crypto projects, not token issuers looking for investors or token buyers.
• Start with the pre-flight: Run this cold outreach pre-flight checklist before you scale volume.
• Warm up before outreach: Use the email warm-up plan plus the SPF, DKIM, DMARC setup guide.
• Map fields for personalization: Import a list that includes {tokenName}, {tokenSymbol}, {blockchain}, and {website} so your copy can stay specific without manual research.
• Keep duplicates and opt-outs out: Maintain suppression and exceptions using this LeadGenCrypto exceptions workflow.
• Copy lives elsewhere: For templates and a full outreach protocol, use the cold email step-by-step guide.

Crypto founders ignore generic pitches because they see scammy outreach all day. If you sell real services (PR, marketing, audits, dev, listings, tooling), your job is to look legitimate and relevant on the first read. This page is tool-focused. It shows how to use Instantly as your sending and sequencing layer, while keeping list quality, deliverability, and reply handling sane.

Who this is for (and not for)

This guide is for:

• Agencies and service providers running outbound to token-based crypto projects
• Teams that already have an offer and want a repeatable Instantly workflow

This guide is not for:

• Token issuers trying to find token buyers or investors
• Anyone looking to blast untargeted lists

Pre-flight: list quality and ICP before you touch Instantly

Instantly will not fix a wrong list or a vague offer. Do the basics first so you do not burn domains, annoy teams, or waste lead credits.

Do this first checklist (Instantly-ready)

• Define one service offer in one sentence (example: "security review for Solana programs").
• Pick a narrow ICP (chain plus lifecycle window plus one buyer role).
• Decide where replies go (one shared inbox, or one owner per segment).
• Prepare suppression rules (customers, prior conversations, unsubscribes, bounces).
• Start with a small test segment, then scale only after reply quality looks good.

Warm-up and deliverability basics (Instantly + your domain)

If your sending setup is cold or misconfigured, your emails will land in spam long before your offer gets evaluated.

Warm-up

Use Instantly warm-up to build a healthier sending history before you run real campaigns. Keep the ramp conservative and avoid sudden spikes in volume.

Authentication

You still need the fundamentals on your sending domain:

• SPF
• DKIM
• DMARC

Deliverability reality check

If you are sending to crypto teams without SPF, DKIM, and DMARC, mailbox providers often treat your messages as higher risk. Fix authentication before you scale outreach.

Run a deliverability test with Mail-Tester on your real template before scaling to catch content and auth issues.

Tracking (optional)

If you use open or click tracking, consider a custom tracking domain so your links look consistent with your brand. This is optional, and plain text emails with minimal tracking are often the simplest way to start.

List import and segmentation (LeadGenCrypto to Instantly)

LeadGenCrypto gives you outreach-ready context so you can personalize without a full research sprint. A typical lead includes a project website, token address, blockchain, token name and symbol, verified email(s), and often Telegram.

Export a clean CSV

Pull your leads into a CSV and add a few columns that make Instantly campaigns easier to operate:

• SegmentTag: short label like "EVM-Defi" or "Solana-Gaming"
• ServiceType: what you sell (audit, PR, growth, dev, listing)
• Lifecycle: pre-launch, launch, post-launch (if you track it)

Mid-workflow CTA: If you want to see the exact lead fields and export format, start with one free lead in the Leads docs.

Map only the variables you will actually use

When you import into Instantly, map columns to custom variables you can reference in copy.

Recommended variable map:

• Project name to {tokenName}
• Token ticker to {tokenSymbol}
• Chain to {blockchain}
• Website to {website}
• Token address to {tokenAddress}
• Project URL (if you store it) to {tokenUrl}

Build a simple 3-email sequence in Instantly

Keep the sequence short, specific, and easy to reply to. If you want a deeper copy framework and more templates, follow the cold email guide linked in the TL;DR.

Email 1: short opener with a micro-yes CTA

Subject: Quick question about `{tokenName}`

Hi there,

I saw `{tokenName}` is building on `{blockchain}` and took a look at `{website}`.

I run a small team that helps `{blockchain}` projects with [your service]. If I share 2 ideas that are specific to `{tokenName}`, would you like me to send them over here?

Thanks,
[Your name]

Email 2: follow-up with proof (no hype)

Subject: Re: `{tokenName}`

Hi,

Quick bump in case this got buried.

If it helps, I can share a short example of how we approach [your service] for `{blockchain}` teams, plus what we would do first for `{tokenName}`.

Is it better to send that by email, or should I reach out on Telegram if that is easier?

Thanks,
[Your name]

Email 3: polite close-the-loop

Subject: Closing the loop on `{tokenName}`

Hi,

No worries if now is not the right time. I will close the loop after this message.

If `{tokenName}` ever needs help with [your service] on `{blockchain}`, reply with "later" and I will follow up in a few weeks.

Thanks,
[Your name]

Reply handling and routing (so deals do not get lost)

Automation is only useful if replies turn into next steps.

A simple routing plan looks like this:

• Positive reply, reply within one business day, propose two time slots, then tag in your CRM
• "Not now", ask for timing, add to a low-frequency nurture track, then suppress from cold sequences
• Wrong person, ask who owns the area, update contact, suppress the wrong inbox

For a full CRM workflow with stages, reply SLAs, and automation patterns, see the six-step sales process for agencies selling to crypto projects.

Common failure modes (and what to check)

When results are weak, Instantly is usually showing you a system problem upstream.

• High bounces: list quality or domain authentication is off, revisit deliverability setup and verify your source.
• Spam folder placement: warm-up is incomplete, or you scaled too fast, slow down and re-check authentication.
• Opens but no replies: message is too vague, or the offer does not match the segment, tighten the ICP and use a clearer micro-yes.
• Angry replies or opt-outs: you are contacting the wrong roles, or repeating contacts, improve targeting and keep suppression up to date.
• Duplicate outreach: your exceptions list is missing customers and prior conversations, update it before the next import.

Optional: automate lead intake (CSV today, API later)

If you like the workflow but hate manual imports, you can automate lead intake. A common pattern is:

• Fetch fresh leads
• Dedupe against your suppression list
• Push net-new leads into Instantly

If you use an AI agent such as OpenClaw instead of or alongside Instantly, you can pull leads via the Public API into your agent.

Needs confirmation

Instantly API details and authentication schemes can change. Confirm the current request format in Instantly documentation before you use any automation in production.

function fetchAndSendLeadsToInstantly() {
  // ---- CONFIGURATION ----
  const INSTANTLY_API_KEY = 'YOUR_INSTANTLY_API_KEY';

  const CAMPAIGN_ID = 'YOUR_INSTANTLY_CAMPAIGN_ID';

  const LGC_API_KEY = 'YOUR_LEADGENCRYPTO_API_KEY';

  // Endpoint to get latest leads
  const LEADGENCRYPTO_API_URL = 'https://api.leadgencrypto.com/api'
    + '?module=lead&action=viewLatestLeads&limit=50'
    + '&apikey=' + encodeURIComponent(LGC_API_KEY);

  const INSTANTLY_API_URL = 'https://api.instantly.ai/api/v2/lead/bulkaddleads';

  // 1. Fetch from LeadGenCrypto
  let response = UrlFetchApp.fetch(LEADGENCRYPTO_API_URL, { muteHttpExceptions: true });

  let data = JSON.parse(response.getContentText() || '{}');

  if (!data.result || data.result.length === 0) {
    Logger.log('No new leads found.');
    return;
  }

  // 2. Map data for Instantly
  const leadsPayload = data.result
    .filter(l => l.email1)
    .map(l => ({
      email: l.email1,
      company_name: l.tokenName,
      custom_variables: {
        tokenName: l.tokenName,
        tokenSymbol: l.tokenSymbol,
        blockchain: l.blockchain,
        website: l.website,
        tokenAddress: l.tokenAddress || '',
        tokenUrl: l.tokenUrl || '',
        telegram: l.telegram || ''
      }
    }));

  // 3. Push to Instantly
  const options = {
    method: 'post',
    contentType: 'application/json',
    headers: { Authorization: 'Bearer ' + INSTANTLY_API_KEY },
    payload: JSON.stringify({
      api_key: INSTANTLY_API_KEY,
      campaign_id: CAMPAIGN_ID,
      leads: leadsPayload,
      skip_if_in_workspace: true
    })
  };

  UrlFetchApp.fetch(INSTANTLY_API_URL, options);

  Logger.log('Sent leads to Instantly: ' + leadsPayload.length);
}

Frequently Asked Questions (FAQ)

Is cold email outreach to crypto projects legal under GDPR?

Laws and enforcement vary by country, and details depend on your situation. In general, B2B outreach should be relevant, transparent, and easy to opt out from. Keep records, honor suppression requests, and talk to counsel if you are unsure.

How fast should I scale sending volume in Instantly?

Scale slowly. Use warm-up, watch bounces and complaints, and avoid sudden volume jumps. If you see spam placement or high bounce rates, pause and fix the root cause instead of pushing harder.

What should I personalize in a crypto outreach email?

Personalize only what you can support with real context:

• Chain they build on ({blockchain})
• Project name and token ({tokenName}, {tokenSymbol})
• One concrete reference from their site ({website})

Action Checklist

Use this checklist before you launch your next Instantly campaign.

• Data source: pull fresh leads, confirm you have {website} plus at least one verified email. Pre-validate contacts before import to reduce bounces.
• Dedupe rules: update suppression and exceptions before importing net-new contacts.
• Infrastructure: verify SPF, DKIM, DMARC are live on the sending domain.
• Warm-up: keep warm-up active and avoid sudden volume spikes.
• Sequence: create a 3-email sequence with a micro-yes CTA and no hype claims.
• Reply flow: decide who replies, and how replies get tagged in your CRM.

LeadGenCrypto • Blog & Newsletter

Stay in the loop without the noise

Timely updates, practical sales advice, and useful resources for teams selling services to crypto projects. Delivered straight to your inbox.

• Quick summaries of our latest articles so you can skim and decide what to read
• Actionable ideas to boost sales: sequences, templates, and reply-handling plays
• No hype. One-click unsubscribe anytime.

Subscribe for free

Browse the blog

No spam. Unsubscribe anytime.

---

Quick Reference Tables

Table 1: Crypto-Specific Spam Triggers

Avoid these words in your subject lines and body copy to reduce risk, especially in crypto-adjacent campaigns.

Category	High-Risk Words (Avoid)	Safer Alternatives (Use)
Financial	100x, Guaranteed returns, Free money, Airdrop, Pump	Growth, Pipeline, Launch support, Distribution, Traction
Urgency	Buy now, Act fast, Urgent, Last chance	Timeline, Roadmap, Next step, Priority
Hype	Best, #1, Top-tier, Moon, Lambo	Established, Trusted, Relevant, Consistent

---

Table 2: Outreach Channel Mix

While email is usually the primary channel, multi-channel follow-up can help when it is respectful and opt-in.

Channel	Role in Funnel	Best Practice
Cold email	Primary contact method.	Plain text, specific, and easy to decline.
Telegram	Secondary follow-up.	Only use if they share the handle. Keep it short: "Sent an email about {tokenName}."
Twitter/X	Social proof and research.	Engage with posts before emailing to build name recognition.
LinkedIn	Professional verification.	Connect with the founder to show you are a real person.

---

Table 3: Segmentation Strategy Examples

How to tailor your message based on the blockchain network.

Network	Focus Area	Messaging Angle
Ethereum (L1)	Security and institutional posture	"Security-first," "risk controls," "audit readiness."
Solana	Speed and consumer apps	"UX and onboarding," "high-throughput ops," "community loops."
Base / L2s	Cost efficiency and scaling	"Lower fees," "scaling users," "supporting L2 growth."