Guides

Your first outbound campaign (in under an hour)

A founder's guide to outbound messaging, finding your first customers, and why copywriting is the last thing you should worry about.

Deepline

Your first outbound campaign (in under an hour)

By Jai Toor · April 2026

Cold outbound fails because founders write messages about themselves to people who don't have the problem yet.

That's the whole thing. Everything else is downstream.

I figured this out the hard way. Before we talk about what works, here are some real messages I sent. Depressingly real.

This one had a variable that never filled:

Subject: customer journeys?

[name], I love what you guys are building at <company>.

Is increasing revenue via product adoption and retention on your radar? If so, would love to get your expert advice on what we're building.

Two broken variables in four sentences. "I love what you guys are building at <company>" - they could see the template. They knew they were in a list.

Eventually we graduated to email sequences that looked more polished. Same logic, better formatting:

Subject: Quick one on pipeline this quarter

Hi [name] - founder asking for advice.

We help RevOps launch and measure growth workflows without waiting on data/eng (natural-language, unified layer). Live with Owner.com; ex-Uber/Lyft/Capchase.

Would you sanity-check our approach for 10-15 minutes this week?

Count the sentences about the reader: zero. "We help." "Our approach." "Founder asking for advice" - a manipulation hack dressed up as humility. Proof points from a customer they'd never asked about. A CTA that asks them to do work for us.

Three weeks later, after seven emails to someone who never replied once:

Final close-out.

If priorities shift or you want to see how we handle your specific RevOps challenges, I'm here. Case study and 1-pager ready to share.

Good luck with Q1 targets!

"Good luck with Q1 targets." I didn't know if they had a Q1. I didn't know if they had targets. I just needed to close the sequence and that's what the template said.

We ran the same playbook on LinkedIn. Thirty-seven unreplied messages in a single month, many ending with "Last note! Working on solutions to help find niche signals with the highest likelihood to close automatically..." - same spray-and-pray energy, different channel.

I spent weeks A/B testing subject lines and CTAs while the entire approach was pointed the wrong way. Optimizing the last sentence of a message nobody was reading.

The problem wasn't the copy. It was that I was describing my product to people who didn't have my problem on their to-do list that week.

You can't write your way out of not knowing the person.


What I learned from Rob Snyder

Rob Snyder is a 3x founder. He spent a year running office hours with early-stage companies - eleven sessions, which I synthesized into a framework I use every time I review a deal.

The first time we worked through it together, he changed how I think about sales entirely.

His point: most founders are looking for people with a pain. That's wrong.

Pains are everywhere. What you're looking for is someone with a project - a top-3 priority with a named owner, a deadline, and a forcing function. Pains you don't act on aren't projects. Pain doesn't close deals. Projects do.

He described it like this: you become a kind of gollum-like creature, obsessed with finding the person who has a top-3 project you can help with. Not pains. Projects.

His framework is called PULL. Four conditions, all of which have to be true at the same time:

P - Project : Something specific is already on their to-do list with a named owner. Not "we've been meaning to sort this." An actual initiative, happening now, with or without you.

U - Unavoidable : Something external is forcing this project to happen this quarter. A board question. A missed number. A new hire. A competitive threat. Not "important someday." Forced now.

L - Looking : They're actually evaluating options - asking peers, reading reviews, taking calls. Not complaining about the status quo. Actively shopping.

L - Limitations : The existing options have a flaw bad enough that they can't make progress. You're not "better." You're the only path that actually works for their situation.

When all four are present, you barely have to sell. You show up, don't confuse them, and they buy. When any one is missing, you're pushing. Pushing isn't selling. It's begging.

Rob's diagnostic question: "What was happening the week before you took this call?" (source) If they can't answer with something specific and external, there's no project. There's interest. Interest doesn't close.

The tell when PULL is absent, in his words: "Sounds cool. Sounds great, buddy. Yeah." That response means you're talking to the wrong person this week.

Further reading - Rob Snyder

The jargon problem

The messages above failed for two reasons. The first was PULL - the people we were contacting didn't have an active project. The second was subtler.

Here's one we sent, verbatim:

Reaching out to get your advice on analytics and data silos. We're working on eliminating custom data consolidation effort by using LLMs to effortlessly optimize and automate workflows data across silos, think analytics + Zapier/Workato so we know exactly what to automate.

Read that out loud. It doesn't mean anything. "Effortlessly optimize and automate workflows data across silos" is nine words doing the work of zero.

We weren't describing a problem. We were performing intelligence.

Here's another one from the same period:

We're working on making GTM more predictable by building a context engine that serves revenue-critical intelligence from product usage, CRM activity, conversations, and more - so teams can qualify, route, and act without manual data consolidation.

That one is even more embarrassing because it sounds polished. "Revenue-critical intelligence." "Context engine." "Act without manual data consolidation." These are words a person deploys when they haven't figured out what they actually do yet.

Every jargon phrase is a sign you haven't done the work of understanding what the reader cares about. When you know someone's problem well enough to describe it in their words, you don't reach for technical-sounding language. You just describe the thing.

I use jargon to convince myself other people should take me seriously. It has no intrinsic value.

Copywriting is mostly just not trying to sound like you're trying too hard.

The bar test: if you wouldn't say it to someone at a bar, cut it. "Context engine that serves revenue-critical intelligence" would make a person back away from you at a party. "I noticed you're scaling the SDR team - we help companies find the right accounts before they burn through headcount" is something you'd actually say.

The numbers back this up. Instantly's 2026 benchmark across 100M+ emails puts the platform-wide average reply rate at 3.43%. Campaigns targeting fewer than 50 recipients average 5.8%. Blasting 1,000+ drops to 2.1%. Smaller, more relevant batches win by a factor of three.

WIIFY - what's in it for you - is not a stylistic preference. It is the only thing that matters. If the first sentence of your email isn't about the reader's outcome, you've already lost. Doesn't matter how good the copy is after that.


What bad outbound looks like in the wild

Bad is one step closer to good. The fastest way to learn what's wrong with your messaging is to look at what it produces.

Here's a sample from our Dec-Jan outbound - three independent replies from three different people on the same campaign:

"Probably one of the worst automated messages I have received." - Charles T.

"From your message above it is unclear to me what you are exactly building and trying to solve." - Ram G.

"You are making this way too complex. Can you tell in one sentence what you offer?" - Dominykas R.

Four separate people, independently, said the same thing: unclear, too complex, too long. That's not outlier grumps. That's the message itself.

What triggered those replies was something that looked like this:

We help RevOps teams leverage AI-powered workflows to optimize GTM velocity and pipeline efficiency through a unified context layer that integrates with your existing stack.

Nobody knows what that means. We didn't either, really - we were using words to fill space where a real answer should go.

The contrast: six weeks later, after stripping everything back to what we actually do in plain language, we got this:

"Your tool has amazing potential!" - Johanna T., GTM Engineer

Same problem being solved. Different words. The second version described what the person got, in language they recognized, without making them work to understand it.

The difference between those two outcomes isn't copywriting skill. It's whether you've done the work to understand the problem well enough to describe it simply.

Before - Jan 2026

"Probably one of the worst automated messages I have received."

Charles T.

Before - Dec 2025

"Sorry to be blunt but it is unclear to me what you are exactly building and trying to solve."

Ram G.

Before - Jan 2026

"You are making this way too complex. Can you tell in one sentence what you offer?"

Dominykas R.

After - six weeks later

"Your tool has amazing potential!"

Johanna T., GTM Engineer


Message-market fit

This is the framework that made outbound click for me.

Kellen Casebeer, who runs The Deal Lab, distinguishes between product-market fit and message-market fit. You can have the first without the second — your product works, but the way you talk about it doesn't connect.

Kellen treats outbound like a clinical trial. Narrow segments — not "SaaS companies" but "Series A fintech SaaS that hired a VP of Sales last month." Then you test offers, not copy. Free audit vs. case study vs. competitive teardown. The offer matters more than the phrasing.

Run small batches - 50 to 100 contacts per segment, 3-email sequences. Don't scale anything until one segment pulls a 10%+ reply rate (Kellen's rule of thumb).

His clients regularly get 13%+ reply rates this way (Kellen's breakdown). They don't write better emails than anyone else. They find the right segment-offer combination first.

The question shifted for me from "how do I write a better email" to "which 50 people are most likely to have this specific problem this week."

The message-market fit testing loop
Further reading - Kellen Casebeer

The Mom Test, and where it stops working

The Mom Test by Rob Fitzpatrick is one of the best books for early founders. Stop asking people if your idea is good - they'll lie to be nice. Ask about their life, their problems, their behavior.

But there's a limit.

The Mom Test gets you good conversations. You'll hear "yeah, that's a pain point" — and feel validated. But "I'd use that" and "take my money" are different sentences.

The Mom Test teaches you how to listen. It doesn't teach you how to find the right people to listen to.

That's where PULL picks up. The Mom Test is what to say in the conversation. PULL is who to have the conversation with. Message-market fit is how to reach them at scale.

Most founders read The Mom Test and stop there.

This doesn't work if you have zero customers and no signal at all. In that case, don't start with a campaign — start with five conversations.

Ask people what they're working on this quarter. If none of them have a top-3 project you can help with, you don't have a targeting problem. You have a hypothesis problem.

Four frameworks, one system
Further reading - Mom Test + YC

What it feels like when it works

I went from sending 500 emails and getting 3 replies - two "not interested," one ghost - to sending 50 emails to a narrow segment and getting 8 replies. Five wanted a call. Three went somewhere real.

Ten times fewer emails, ten times the results. And the emails were shorter and took five minutes to write instead of two hours.

Ben Holley said something at April Tools Day that stuck: if you get someone at the right time with the right context, your message can say basically anything.

He's right. When it works, you're describing someone's specific Wednesday to them. They respond because you understood what they were dealing with, not because your email was clever. You could send a three-sentence email with a typo and they'd reply.

You can't shortcut your way there. The work is understanding the pain well enough to describe it better than the person experiencing it.

Once you can do that, the message writes itself.

I didn't believe people when they said "it feels different." Then I felt it.


Start with LinkedIn, not email

Here's something most outbound guides skip: before you touch email infrastructure, you should be doing LinkedIn until it stops working.

Not because LinkedIn converts better. Because it's slower, more personal, and forces you to be human about it. You can't spray 500 LinkedIn messages without it feeling wrong. That friction is the point. It forces you to actually think about who you're talking to before you hit send.

The playbook: post daily. Comment on 10 prospect posts for 30 days. By the time you send the DM, they recognize your name. When you do reach out, keep it to one sentence - "noticed you're scaling the SDR team, curious if signal quality is the bottleneck" - and stop there. No pitch. No deck. No call link.

You have an unfair advantage as a founder. Use multiple accounts - you, your co-founder, early team members, advisors who believe in what you're building. Five people doing 20 conversations a week is 100 real conversations a month. That's more than most early email campaigns convert.

Email infrastructure only makes sense when you're already nailing PMF. When you know exactly who to send to and what to say, and you want to reach more of them faster. If you're still figuring out the message, email just lets you be wrong at scale.

Start on LinkedIn. Run it until it can't scale. Then add email.


Tools

You need two things: something to find people and something to send messages.

For LinkedIn-heavy outbound: HeyReach is the best dedicated tool. For multi-channel (LinkedIn + email): Lemlist handles both in one platform. For high-volume email only: Instantly is cheapest. I use Lemlist. Most customers use HeyReach and Smartlead. Pick one and start.

For finding people: that's the hard part, and that's where Deepline fits.

The outbound tool stack

The tool doesn't matter. Whether the person receiving your message has the problem you solve, right now, and you can describe it in their words - that matters.


Email infrastructure

Most cold email campaigns die before anyone reads a word. Not because the copy was bad - because the emails landed in spam.

Everyone skips infrastructure, then blames their copy. Do this once, do it right, then forget about it.

Buy separate domains

Never send cold email from your main company domain. If your primary domain gets flagged, your regular business email goes down with it.

Buy 3-5 domains that look related to your main brand. If your company is acme.com, buy getacme.com, acmeapp.com, tryacme.com. Let new domains age at least 2 weeks before sending.

Where to buy:

Set up mailboxes (3 per domain)

Google Workspace ($7.20/user/month) has the highest baseline deliverability. Microsoft 365 ($6/user/month) is a good secondary lane - mixing providers gives better coverage.

Add a profile picture and signature to every inbox. Inboxes without photos get flagged as automated.

Set up DNS authentication

In 2026 this is non-negotiable. Domains with SPF, DKIM, and DMARC all configured correctly achieve 89% inbox placement vs. 61% for SPF-only (InboxKit, 2026).

SPF - who's allowed to send from your domain. Add a TXT record: v=spf1 include:_spf.google.com ~all

DKIM - proves the message wasn't tampered with. In Google Workspace Admin: Apps > Gmail > Authenticate email.

DMARC - what happens when someone fails the checks. Start with v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com for 2 weeks, then move to p=quarantine.

DNS setup guides

Turn off open tracking

I don't track opens anymore, just replies. Open tracking embeds invisible pixels. Click tracking rewrites your links. Both are signals that spam filters use to identify bulk outreach.

Warm up your inboxes

Week 1: 5-10 warm-up emails per day. No cold sends. Week 2: 15-25 warm-up emails per day. Still no cold sends. Week 3: Start adding 5-10 cold emails per day alongside warm-up. Week 4: Ramp to 15-25 cold emails per day per inbox.

After warm-up, stay at 15-25 campaign emails per inbox per day. With 3 inboxes across 4 domains (12 total), you can send 180-300 emails per day.

Instantly, Smartlead, and Lemlist all handle warm-up automatically.

Verify your list

Before loading contacts into your sending tool, run every email address through a verification service. Aim for a bounce rate under 3%.

NeverBounce, ZeroBounce, MillionVerifier - most charge $3-5 per thousand.

The full checklist

Before you send your first cold email:

  • [ ] 3-5 separate domains purchased (not your main domain)
  • [ ] Domains aged at least 2 weeks
  • [ ] 3 inboxes per domain set up
  • [ ] Profile picture and signature on every inbox
  • [ ] SPF, DKIM, DMARC configured for each domain
  • [ ] Open/click tracking turned off
  • [ ] Warm-up running for 2-4 weeks (or pre-warmed inboxes purchased)
  • [ ] Email list verified, bounce rate under 3%
Infrastructure resources

How Deepline works

The hard part of outbound isn't writing the email or picking the tool. It's answering the question most founders can't: what signals tell me someone has this problem right now?

Traditional outbound finds companies that match demographic criteria and blasts them all. Signal-based outbound finds people exhibiting behavior that suggests they have the problem today.

A company posts three SDR job listings - they're scaling outbound. A VP of Marketing writes a LinkedIn post about struggling with attribution - they have a measurement problem. A competitor raises a round and your prospect's board starts pressuring them - urgency exists. These are niche signals. Finding them manually takes hours.

This is what we built Deepline for. You start with your wins, your losses, who bought, who didn't, why. Feed that hypothesis in and look at what your market has been saying over the last 30 days. What phrases do they use when describing the pain. What events are creating urgency.

Then you find the 50 people who match those signals. LinkedIn profiles, emails, context. You write a short email that references the specific signal. You send it. You see what happens.

The research part used to take weeks. Now it takes maybe 15 minutes.


Building your first campaign

If you're starting from zero, here's what an hour looks like.

Zero to live campaign in under an hour

Minutes 0-5. Write down who you think your customer is - painfully specific. Not "Series A SaaS companies." More like "Series A vertical SaaS founders who just hired their first SDR, are burning through Apollo credits, and realized their enrichment data is 40% stale." What problem you solve for them, in one plain sentence. And why now - what's happening in the market that makes this urgent.

Minutes 5-20. Open Deepline. Feed in your hypothesis. Run niche signals for the last 30 days. Note the specific phrases people use when describing the pain. Note what events are creating urgency. Write down the top 3-5 signals.

Minutes 20-30. Use Deepline to find 50 people per signal. For each person, you should know why they're on this list and what their pain probably is.

Minutes 30-45. Write one email per segment. WIIFY from the first line - not what you do, what they get. Open with the signal: what they posted, hired for, or announced. Name the pain in their words, not your product language. Offer something specific: a teardown, an audit, a relevant case study. Keep it under 75 words.

A template:

Subject: [the signal]

Hey [name],

[What's in it for them - the outcome they'd get, tied to the signal you noticed.]

[One sentence about the pain that usually comes with that signal, in their language.]

[One specific offer - teardown, audit, case study.]

Worth a look?

No "I hope this finds you well." No three-paragraph company backstory.

Minutes 45-60. Load the list into Lemlist. Three emails: the one above, a one-line follow-up on day 3, and a breakup on day 7: "Figured this isn't relevant right now. If it is, I'm here." Hit send.

After day 7. 5%+ reply rate means you're onto something. 2-5% means the segment might be right but the offer needs tweaking. Under 2% means try a different signal.


What I've noticed

"I saw you went to Ohio State and you like paddleboarding" isn't personalization. Everyone knows you scraped their LinkedIn. The only thing that reads as personal is proving you understand their problem.

You need more clarity, not more tools.

AI cold messages still sound like garbage. Write it yourself.

Where it helps: research. Finding who to contact, why they'd care, and building a list of 50 people who match that signal — in minutes instead of days. Write the message yourself.

Short wins. The message that booked 50 meetings was five lines. The one that booked zero was three paragraphs. The founder spent more time on the one that didn't work.

Data beats copy. Get the targeting right first. Infrastructure second. Copy third.

If it feels like sales, you're talking to the wrong person. When it's working, it feels like helping. You're describing someone's problem and offering to solve it.

Speed beats perfection. Send 50, read the data, iterate. Three campaigns of 50 teaches you more in a week than a month spent on the perfect first message.

Nobody wakes up excited to read your cold email. Respect that.

Further reading - cold email

The framework stack

Four questions. Answer them in order.

| | Question | Framework | |-|----------|-----------| | 1 | Is this person actively working on a problem I can solve? | PULL - Rob Snyder | | 2 | What do I ask to find out what's actually true? | The Mom Test - Rob Fitzpatrick | | 3 | Which segment responds to which offer? | Message-market fit - Kellen Casebeer | | 4 | Who has the problem this week, not just in theory? | Signal research - Deepline |

Most founders skip straight to 3. The sequence matters.


The gap is not tools, or copywriting, or AI. The gap is understanding the pain well enough to describe it better than the person experiencing it.

Once you can do that, the message writes itself.


Jai Toor builds Deepline. He writes his own cold emails. They're usually under 50 words.

Run your entire GTM motion from Claude Code

Install Deepline and get 45+ GTM data providers in your terminal. Enrich, validate, and sequence - all through natural language.