Skip to content
NewSee how

Industries · Web3

Web3 cold email software that reaches protocol teams with short emails about their launches, grants and roadmaps.

FirstSales finds protocol teams, founders and ecosystem leads who fit your product, spots something real like a mainnet date or a new grants program, and writes each one a short email about it. It follows up until they reply, then stops, so the conversation lands with your team.

Start your $1 trial See pricing

$1 for 3 days · Cancel anytime · No contract

FirstSales dashboard for a Web3 company: active campaigns, connected mailboxes, contacts, emails sent and a sending volume chart
  • 01

    Written only from the SDK, chains and proof you add to the knowledge base

  • 02

    Opens with a launch, grant or hire the team made public

  • 03

    Unlimited mailboxes, with a 21-day warm-up

  • 04

    Start for $1 for 3 days, then from $29/mo

The problem

Web3 teams move fast and trust slowly, and most pitches look like spam to them.

Protocol teams get pitched all day, often by people who never looked at the project. The Web3 companies who win write to the right person at the right stage, with a short, honest reason to talk, and keep showing up until the timing is right.

A wall of pitches

A founder or DevRel lead hears from tools, agencies and funds every day. A generic note that could go to any project gets ignored.

Trust is hard to earn

The space has seen a lot of scams. Hype, vague claims or pushy timing make an email look like one, even when your product is real.

Timing moves every week

A team that had no need last month may be launching next week. Outreach that stops after one email misses the moment the need shows up.

A real reason to write

Web3 teams change fast and say so in public, so write when you see the change.

Protocols post their roadmaps, launches, grants and hires in the open. Each one is a moment when a team needs new tools or partners. FirstSales finds teams where one of these is true and opens each email with it.

  • A testnet or mainnet launch

    A new network needs app teams, tooling and docs ready on day one. The team building it is looking for partners now.

    How the email opens

    Saw your mainnet date is set. What do app teams still need before they can ship on it?

  • A new grants or ecosystem program

    A grants program means the team wants more builders, and often needs tools those builders can use.

    How the email opens

    Noticed the new builder grants. Would a starter kit for grantees help them ship faster?

  • A new funding round

    Fresh funding often comes with a plan to grow the team, the product or the ecosystem.

    How the email opens

    Congrats on the new round. Is growing the app ecosystem part of the plan for this year?

  • Hiring for DevRel, BD or partnerships

    A new DevRel or partnerships role tells you who will own the problem you solve, and that they will need help soon.

    How the email opens

    Saw you are hiring a partnerships lead. Who handles integrations until that role is filled?

  • Support for a new chain

    A team that adds a new chain needs the same tools working there too, from wallets to indexing.

    How the email opens

    Noticed you are adding support for a second chain. Are your SDKs ready for it yet?

  • A hackathon or builder event

    Teams that run a hackathon want builders to have working tools and clear docs from the first hour.

    How the email opens

    Saw the hackathon next month. Would a ready-made kit for participants help?

How it works

From your product to a booked call, in three steps.

Set it up once, review as much as you like, and let FirstSales research, write and follow up.

  1. 01

    Connect a separate domain

    Add mailboxes on a cold email domain, not the one your users and partners rely on. SPF, DKIM and DMARC are checked and warm-up begins.

  2. 02

    Teach it your product

    Add your SDK or service, the chains you support, integration guides and security notes. Describe the teams you want and FirstSales builds the list.

  3. 03

    Send, follow up and book

    Each email names something real about the project. Follow-ups stop on a reply, and interested contacts get your meeting link.

Set up Web3 outreachthat keeps running while your team ships.

Four parts of the app do the work a BD lead and a research assistant would do by hand.

  1. Connect

    Send from a separate, trusted domain

    Add Gmail, Outlook or SMTP mailboxes on a cold email domain, so the email your users and partners rely on stays safe. Mailboxes are unlimited, so spread volume across as many as you need with sending rotation.

    • SPF, DKIM and DMARC checks. Per domain, with the exact fix if a record is missing.
    • 21-day warm-up. Three phases before full volume.
    • Health grade. Every mailbox gets a grade and hourly monitoring.
  2. Teach

    Teach it your stack and your proof

    Add what you sell, the chains and networks you support, integration guides and the security notes you can share. The AI writes only from what you add, so every detail matches what your product really does.

    • Knowledge base. SDK, chains and proof in one place.
    • Offerings. One offer per product or buyer, each with its own message.
    • Lead list from a description. Every contact checked before each send.
  3. Write

    Emails about their roadmap, not your token or pitch deck

    Each email opens with something true about the project, like a launch, grant or new chain, and asks one simple question. No blasts, no hype, no price talk.

    • Writing profile. Keeps your tone direct, short and plain.
    • Approval queue. Approve, edit or reject drafts before they send.
    • A/B tests. Test two openers and keep the one teams reply to.
  4. Reply

    Turn replies into booked calls

    Replies land in Unibox. Interested contacts get your meeting link, and the sequence stops on any reply or opt-out, so the conversation lands with your team.

    • Unibox. Every reply from every mailbox in one inbox.
    • Stop on reply or opt-out. No follow-up after a no.
    • Meeting link. Interested replies get your booking link.
What you get

Outreach that sounds like someone who reads the team's docs and updates.

Everything a Web3 team needs for steady outreach to protocols, founders and ecosystem leads, on every plan.

  • Only your real product

    The AI writes only from your knowledge base, so it never claims a chain, feature or audit you do not have.

  • A real reason to write

    Each email starts with something true about the project, like a mainnet date, a grants program or a new hire.

  • A campaign per buyer

    Run protocol teams, app teams and ecosystem funds as separate campaigns, each with its own list, offer and voice.

  • Clean lists

    Every contact is checked before each send, and Dirty contacts are left out to protect your domain.

  • Follow-ups that stop on reply

    Spaced follow-ups that end the moment someone replies or opts out, so no busy founder is chased after a no.

  • A workspace per product or region

    Run each product, region or BD lead in its own workspace. Unlimited workspaces and team members.

Timing is the job

A protocol needs different things at each stage, so match the email to where they are.

What a team needs while it builds on testnet is not what it needs a year after mainnet. Write about the stage they are in now, and the email reads like it came from someone who follows their work.

  1. Building on testnet

    Help them get ready

    The team is still shaping the stack. Ask what they plan to offer app teams at launch, and where your tool fits.

  2. Mainnet launch

    Help the first apps ship

    Launch week is busy. Keep it short and offer one thing that helps the first app teams ship on the new network.

  3. Grants and ecosystem growth

    Help builders succeed

    The team wants more apps built. Offer something grantees and hackathon teams can use, like a guide or starter kit.

  4. Scaling up

    Help them handle more users

    Usage is growing and old tools start to strain. Ask what breaks first as more people use the network.

  5. Upgrade or migration

    Help the move go smoothly

    A network upgrade or chain move touches every integration. Offer to check that your part keeps working after it.

Who you are writing to

In Web3, the person who owns your problem often has a title you will not see elsewhere.

Teams are small and roles are wide. One person might own developers, partners and community. These are the people you will meet, what they care about, and the angle that gets a reply.

  • 01

    Founder or core contributor

    What they care about
    Shipping the roadmap, a small team that stays focused and partners that save time.
    The angle that gets a reply
    Name one roadmap item you saw and ask a single question about it. Keep it to a few lines.
  • 02

    Head of Developer Relations

    What they care about
    Builders who get started fast, clear docs and fewer questions in the support channel.
    The angle that gets a reply
    Offer something builders can use today, like a guide or sample app, and ask what they hear most from developers.
  • 03

    Head of BD or partnerships

    What they care about
    Integrations that bring users, partners that show up and deals that move.
    The angle that gets a reply
    Say plainly what the integration gives their users and ask who should be part of the first call.
  • 04

    Ecosystem or grants lead

    What they care about
    More apps on the network, grantees who finish and programs that show results.
    The angle that gets a reply
    Offer a kit or office hours for their grantees, tied to the program they just opened.
  • 05

    CTO or protocol engineer

    What they care about
    Security, reliability and tools that do not add risk to the stack.
    The angle that gets a reply
    Share your security notes and supported chains up front, and ask what they check before they add a dependency.
  • 06

    Head of growth or marketing

    What they care about
    More active users, launches that land and partners who help spread the word.
    The angle that gets a reply
    Talk about a launch or campaign they have planned and the one way you could help it reach more people.
“His honest and insightful feedback helped us transform @synchrowork when we started on LTD to what we are building now.”
Sushant Kumar@sushantkr49 · X
Plain guide

How to cold email protocol teams and Web3 founders.

What works when you write to busy builders who have seen a lot of pitches and trust only what they can check.

  1. 01

    Read their updates first

    Teams post roadmaps, launches and grants in public. One true detail from them is worth more than a long list of features.

  2. 02

    Skip the hype

    Leave out price talk, big promises and words like moon or alpha. Plain words read as honest, and honest gets replies.

  3. 03

    Lead with what builders get

    Say what changes for the developers on their network. Leave deep technical detail for the follow-up.

  4. 04

    Share proof they can check

    Point to docs, guides or security notes they can read themselves. Never claim an audit or partner you do not have.

  5. 05

    Ask for a small step

    A short call, a guide for their docs or a kit for one hackathon is easier to say yes to than a full partnership.

  6. 06

    Use a separate domain

    Keep cold outreach off the domain your users and partners rely on, so that email stays safe.

Real objections

What Web3 teams say to a cold email and what to say back.

Web3 teams get a lot of pitches, and many are wary of anything that looks like spam or a scam. These are the objections you will hear most, with a calm reply to each.

  • “We get pitched all day. Why is this different?”

    Point to the one thing you noticed about their project and the one problem you solve. Then ask a single question and stop.

  • “We already built this in-house.”

    Agree that it makes sense for some teams. Ask what it costs them to keep it running, and offer to compare only that part.

  • “Is this secure? We cannot add risk.”

    Answer only with what is true today for your product, and offer your security notes or audit reports if you have them.

  • “Hit me up on Telegram or Discord instead.”

    Thank them and move the chat where they asked. Keep the email thread as a short summary so nothing gets lost.

  • “We are heads down until launch.”

    Respect it. Ask if a short note after launch would be welcome, and set the follow-up for then.

  • “How did you get my email?”

    Say plainly that you found their project or role through public sources, and offer to take them off your list.

Before and after

Web3 outreach, before and after FirstSales

What changes when each email sounds like it came from someone who follows the project.

The usual way

DMs, conference hallways and the same pitch to every project.

  • The same pitch to every projectFounders can tell it went to everyone.
  • Hype firstReads like a scam and gets ignored.
  • One email, then silenceForgotten before the launch that would have made it useful.
  • Protocols and funds on one listNothing fits any buyer.
  • Scraped lists uncheckedBounces hurt the domain.
  • Replies scattered across mailboxesInterested teams go unanswered.
With FirstSales

Project-by-project outreach.

  • One real detail about their projectA reason to reply.
  • Plain words, no hypeEasy to trust and quick to read.
  • Follow-ups until they replyStopped on any reply or opt-out.
  • One buyer per campaignEach email fits the reader.
  • Contacts checked firstDirty contacts out before each send.
  • UniboxEvery reply in one inbox.
Why Web3 teams switch

Web3 outreach: FirstSales vs a typical tool

Many tools send one template to a list. FirstSales writes each email from your product and something real about the project.

Outreach features for Web3 teams in FirstSales and a typical cold email tool
What you getTypical toolFirstSales
Emails written only from your productVariesAI writes only from your knowledge base
Opens with a real detail about the projectVariesIncluded
Separate campaigns per buyerVariesUnlimited workspaces
SPF, DKIM and DMARC checksVariesIncluded, per domain
MailboxesVariesUnlimited on every plan
21-day warm-upVariesIncluded
Contact checks before each sendVariesOn every send, no add-on
Starting priceVaries$29/mo
Start your $1 trial
Before you send

Web3 outreach checklist

Run through this before each new campaign. FirstSales handles most of it for you.

  • A cold email domain that is not your main domain
  • SPF, DKIM and DMARC set up on every sending domain
  • Warm-up running for 21 days
  • SDK, supported chains and integration guides in the knowledge base
  • Security notes that are true for your product today
  • No price talk, token promises or hype in the copy
  • Every contact checked and Dirty contacts left out
  • One buyer per campaign: protocols, app teams or funds
  • Drafts reviewed in the approval queue
  • One clear next step, like a short call or a guide for their docs
What people say

From people who use it

Real words from real users. No paid reviews.

“One of the biggest pains in cold email is making sure that you have your DNS setup correctly. Firstsales has created a system to make sure you have done this correctly.”

Mike O

Trustpilot review

Trustpilot

“I've been using FirstSales.io for several months now, and I can confidently say it has revolutionized how I approach lead generation and customer acquisition.”

Paweł Stelmach

Small business owner

Trustpilot

“User Interface, Ease of Use, Able to hit the inbox in the first attempt.”

Sadashiv B.

Founder, small business

G2
Read all reviews

Go deeper

Questions,answered plainly.

Can’t find yours? Write to us.

01Does cold email work for selling to Web3 teams?

Yes, when each email is about the project, names something real and asks for a small step, like a short call or a guide for their docs. FirstSales writes only from the product and proof you add, and follows up until the contact replies.

02Is it OK to cold email protocol teams and founders?

Business email to people in their work role is common, but rules differ by country, and some regions have extra rules for anything that touches crypto marketing. Keep every email honest, make opting out easy and check the rules where you send. This is general information, not legal advice.

03How do I write to teams that are wary of scams?

Use plain words, skip price talk and hype, and point to docs or notes they can check. Send from a real person on a domain you own, and never ask for keys, funds or a wallet connection in an email.

04How do I keep up with projects that change every week?

Open with what the team made public, like a launch date, a grants program or a new hire. Run each kind of buyer as its own campaign, and let spaced follow-ups keep you in touch until the timing is right.

05Who should a Web3 company write to?

Usually founders and core contributors, heads of DevRel, BD or partnerships leads, ecosystem and grants leads, and protocol engineers. Run each buyer as its own campaign, with its own list and offer.

06How do we protect the domain our users rely on?

Send from a separate cold email domain. FirstSales checks SPF, DKIM and DMARC, warms each mailbox up for 21 days in three phases, and gives it a health grade with hourly monitoring.

07How do I try it?

Start for $1 for 3 days. Connect a mailbox, add your product and proof, and read the first drafts in manual mode. No contract: cancel any time in your dashboard.

Outreach that keeps going after you log off.Leads, emails, follow-ups and replies, handled.

Connect unlimited mailboxes and let AI agents find leads, write each email and follow up. Or send your own templates in manual mode. From $29/mo.

Start your $1 trial See pricing

$1 for 3 days · Cancel anytime · No contract

Install with AI

Your coding agent sets up the FirstSales CLI and skills for you.

Prompt for Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.
Developer docs ↗npm: @firstsales.io/cli ↗GitHub: firstsales-skills ↗