Working system · Last reviewed September 1, 2026

How I run cold outbound right now. By hand and with an AI agent.

Phase 1 uses Sales Navigator, research, a tracking sheet, and message templates. Phase 2 uses an agent to find signals and prepare drafts. The strategy, guardrails, and human judgment stay the same.

Open the playbook ↓Read the strategy first

Phase 1: Manual learning
Phase 2: Agent-assisted research
Send control: Human review

First: protect the account

These are my current operating limits. They are deliberately conservative because quality and account health matter more than squeezing out one more send.

Connection requests per day

My personal ceiling, spread across the day. It is not a platform guarantee or a target everyone must hit.

Open Profile messages per day

My working cap for profiles identified inside Sales Navigator. Availability and product rules can change.

1:1

Research before every send

One real detail from a post, announcement, job change, interview, or company page is the minimum.

The tool stack is short on purpose

I am not anti-tool. I am anti-paying for ten tools to perform one workflow that still needs human judgment.

Tool	What I use it for	Role
LinkedIn Sales Navigator	Filtering by title, industry, seniority, company size, and growth signals. It also helps identify Open Profiles.	Core
Regular LinkedIn	Profile research, posts, shared context, and the actual relationship layer around outreach.	Required
Apollo	Contact and company data, additional filters such as funding, and the email side of a coordinated sequence when the free plan is sufficient.	Data + signals
Vibe Prospecting	An additional source when I need company and contact information beyond the first data source.	Data
LeadsMonky	Secondary-domain inbox infrastructure when volume justifies separating outbound from the primary domain.	Scale

What this looks like each week

The manual version can stay under 30 minutes a day when the audience, offer, and tracking sheet are already defined.

01
Build the list across both tools
Start with role, industry, seniority, headcount, and business condition in Sales Navigator. Use Apollo to add funding and other criteria that can sharpen the search, then separate connection requests from Open Profile opportunities.
02
Do the 60-second research pass
Read the latest relevant post, company announcement, job change, interview, or product update. Find one fact worth referencing.
03
Send in small batches
Spread activity across a normal workday instead of releasing a large batch at once.
04
Follow up after the connection
The connection note earns the acceptance. The next message introduces the useful offer.
05
Add the email track when appropriate
If LinkedIn does not create a response, use verified business contact data for a short, coordinated email sequence.
06
Review the pattern weekly
Track acceptance rate, reply rate, positive replies, and meetings. Repair targeting or messaging before increasing volume.

LinkedIn scripts, with one job each

The connection note earns the accept. The second message earns the reply. Combining both jobs is usually where the message starts to sound like a pitch.

Message 1: connection note

About 200 characters

Hey {{FirstName}}, saw {{specific post, launch, raise, hire, or event}}. {{One honest sentence connecting it to your point of view}}. Would love to connect.

Message 2: the offer

One to two days after acceptance

Hey {{FirstName}}, thanks for connecting.

{{One sentence naming the specific pain point or opportunity}}.

I {{relevant credibility statement}}. Happy to put together {{a bounded, useful deliverable}} for {{Company}} and send it over. No strings. If you want it, I can have it back within 24 hours.

Open Profile message

No connection required

Hey {{FirstName}}, {{specific research detail}}. {{Pain point observation}}.

I created {{specific deliverable}} for {{a comparable company}} and it {{supported a concrete outcome}}. Want me to map the same opportunity for {{Company}}?

A real message that worked on me

This arrived in my own inbox. I keep it as a reference because the sender researched the gap, used credible proof, and made the next step easy.

Cold email received by Tiffany

Hey Tiffany,

Your name came up twice last month, so I went and looked at your site and then your LinkedIn. I like how you let the work do the talking, but LinkedIn looks like the channel you have not squeezed yet.

I run LinkedIn for another agency founder. Last month his content reached 267,000 people, 148% more than the month before, on fewer posts.

If you want, I will write a week of posts for your profile and have them back within 24 hours. Just reply yes.

Why I replied

It opened with a specific observation rather than praise.
The proof included a checkable number, not “amazing results.”
The gap was named without turning into a lecture.
The offer was bounded and required no meeting.
The first message had no links, images, or formatting clutter.
The follow-up added proof instead of pressure.

Email uses the same logic in a different inbox

Email runs parallel to LinkedIn. The structure stays the same: relevant research, a real problem, credible context, and a low-friction offer.

Cold email 1: opener

Plain text, under 100 words

Subject: {{specific observation or company name}}

Hey {{FirstName}},

{{Specific research detail}}. {{One sentence naming the problem or opportunity}}.

I {{one-sentence credibility statement}}. If useful, I can {{specific deliverable}} and send it over within 24 hours.

Just reply yes.

Cold email 2: add relevant context

Same thread, three to four days later

Hey {{FirstName}}, one thing I did not mention in my previous email is that we can also help you {{specific capability tied to the original problem}}.

Seeing that {{new relevant company signal or context}}, I thought that could be especially useful because {{one-sentence connection to their current priority}}.

If helpful, I can include that in {{the specific deliverable from email 1}}.

Cold email 3: audit video

A higher-effort offer

Hi {{FirstName}}, I was looking at {{Company}}'s marketing and noticed a few places where the journey may be leaking pipeline.

I recorded a four-minute audit with one website issue, one conversion gap, and one campaign opportunity worth testing. No pitch in the video. Is it okay if I send it?

Cold email 4: campaign outline

For a specific growth signal

Hi {{FirstName}}, saw {{Company}} is hiring and that you came from {{relevant previous companies}}. With a lean team, pipeline growth usually has to come from sharper campaigns before more headcount arrives.

I help B2B tech teams build connected campaigns for complex buyer journeys. I would map three campaign gaps that may be creating attribution noise or stalled pipeline, then outline what I would test over the next 90 days. Open to a short reply and I will send it?

Separate infrastructure when volume earns it

A few carefully researched emails and a scaled outbound operation are different systems. Treat them differently.

Lower volume

Protect the primary relationship

Use authenticated email, accurate records, and close manual review. Keep the volume low enough that every message can be checked.

Higher volume

Isolate outbound operations

Use a clearly related secondary domain, separate mailboxes, SPF, DKIM, DMARC, warming, suppression lists, and monitored sending health.

The daily checklist

The system stays useful only when the quality controls happen every day.

Stay within the conservative daily operating limits.
Spread activity across the day instead of releasing one large batch.
Include one specific, verifiable research detail in every first touch.
Make the offer useful, bounded, and connected to the observed problem.
Keep first-touch email plain and easy to read.
Log acceptance, replies, positive replies, and meetings every week.
Fix targeting and messaging before increasing volume.

The operating principle

Automate the repetition. Keep the judgment.

The system is useful because the research, message, offer, and review criteria stay connected. Technology should make that discipline easier to execute, not easier to skip.

Talk through your workflow →