Solanasis AI-Native Outreach Playbook v1

Owner: Dmitri Sunshine, Founder & CEO Date: 2026-03-10 Purpose: The definitive comparison of Cold Email vs. LinkedIn outreach — scored by what Claude (Cowork + Chrome + Gmail MCP) can actually automate — with a consolidated daily execution plan. North Star: Prove that an AI-native fractional agency can run a GTM engine that would normally require 2-3 SDRs (Sales Development Reps).

The Core Question

You have two outbound channels: cold email and LinkedIn. The question isn’t which one is “better” — it’s which one Claude can automate more of, so that Dmitri’s actual human time goes to the highest-leverage activities: taking calls, closing deals, and delivering ORB (Operational Resilience Baseline) engagements.

1) The Head-to-Head Comparison

Raw Channel Comparison

Dimension	Cold Email	LinkedIn
Monthly reach	500-1,500 contacts (at 20-50/day)	150-200 contacts (at 10-20 connection requests/day)
Reply rate	3-5% (good), 8%+ (great)	15-25% (connection request acceptance), then 10-20% reply to first message
Effective response rate	3-5% of total sent	2-5% of total sent (acceptance × reply × positive)
Cost	$40-70/mo (domain + Workspace + tool)	$100/mo (Sales Navigator) — already budgeted
Time to first send	3-4 weeks (domain warmup)	Immediate (Sales Navigator already active)
Account risk	Low — separate domain isolates everything	REAL — LinkedIn can restrict/ban for automation
Personalization floor	Medium — templates feel automated without effort	High — LinkedIn messages inherently feel more personal
Automation ceiling	Very high — tools handle everything after copy is written	Low-medium — LinkedIn detects and punishes automation
Claude automation %	~70-80% of total workflow	~40-50% of total workflow
Multi-touch	Automated sequences (3-5 emails over 10-14 days)	Manual follow-ups required
Data you get back	Open rates, click rates, reply rates, bounce rates	Acceptance rate, profile views — less granular

The AI-Automation Lens (This Is What Matters)

Workflow Step	Cold Email — Claude’s Role	LinkedIn — Claude’s Role
1. List building	Claude processes Apollo/Outscraper CSVs, deduplicates, segments, formats. 90% automated.	Claude in Chrome reads Sales Navigator results, triages prospects, extracts data. 60% automated — requires supervised browser session.
2. Research/enrichment	Claude researches company websites, generates “I noticed” personalization lines from CSV data. 85% automated.	Claude in Chrome reads LinkedIn profiles, company pages, recent posts. 70% automated — stronger context but slower per prospect.
3. Writing messages	Claude drafts full email sequences in Dmitri’s voice. 95% automated.	Claude drafts connection notes and follow-up messages. 95% automated.
4. Sending	GMass/Instantly sends automatically on schedule. 100% automated (after initial setup).	0% safely automated. LinkedIn detects browser extensions. Must be manually sent or risk account ban.
5. Follow-ups	Automated sequences — tool handles Day 4, Day 9 emails. 100% automated.	Must be manually sent. Claude can draft, but you click Send. 30% automated (drafting only).
6. Reply handling	Claude reads replies via Gmail MCP, drafts responses. You review and send. 70% automated.	Claude reads LinkedIn messages in Chrome, drafts replies. You review and send. 60% automated.
7. Tracking/CRM	Tool provides dashboards. Claude analyzes and recommends optimizations. 80% automated.	Manual logging to spreadsheet/Baserow. Claude can help format. 30% automated.
8. Iteration	Claude A/B tests subject lines, analyzes which segments convert, rewrites underperforming sequences. 80% automated.	Limited data. Claude can review what’s working qualitatively. 40% automated.

The Automation Score

Channel	Average Automation %	Dmitri’s Weekly Time	Contacts Reached/Month
Cold Email	~75%	2-3 hours/week (after setup)	500-1,500
LinkedIn	~45%	4-6 hours/week (ongoing)	150-200
Both combined	~60%	6-9 hours/week	650-1,700

The verdict: Cold email is dramatically more automatable. LinkedIn has higher per-contact conversion but requires more human time. The AI-native play is to use cold email for volume and LinkedIn for precision — with Claude handling different layers of each.

2) What Claude in Chrome Can SAFELY Do on LinkedIn

Your existing Claude in Chrome GTM Playbook nailed this. Here’s the refined version with the 2026 risk data:

GREEN — Safe and High-Value

These are the activities Claude in Chrome should handle daily:

Prospect triage from Sales Navigator
- Open Sales Navigator search results
- Claude reads the visible profiles and scores them against your ICP (Ideal Customer Profile)
- Outputs a ranked shortlist with: company, person, title, why they fit, likely pains, suggested next step
- Time saved: 30-45 min/day → 10 min review
- Risk: Zero — Claude is reading, not acting
Account brief creation
- Open a prospect’s LinkedIn profile + their company website in separate tabs
- Claude synthesizes: what they do, their scale, likely pain points, best outreach angle, one “why now” line
- Time saved: 15 min per prospect → 2-3 min
- Risk: Zero — reading only
Message drafting
- Based on the account brief, Claude drafts 2-3 connection note options (under 300 chars) and 1-2 follow-up messages
- Drafts are in your voice using the style blocks from the Chrome GTM playbook
- Time saved: 10 min per message → 1 min review
- Risk: Zero — Claude writes, you copy-paste and send
Content mining for engagement
- Claude reviews posts from your target prospects
- Drafts thoughtful comments you can post to warm up before connection requests
- Time saved: 20 min/day → 5 min
- Risk: Zero — Claude drafts, you post
Browser-to-CRM handoff
- After a research session, Claude formats everything into structured notes
- Output goes to Baserow, Google Sheets, or a markdown file
- Risk: Zero — data extraction only

YELLOW — Possible But Use Caution

Sending connection requests (Claude clicks “Connect” and pastes the note)
- Technically possible — Claude in Chrome can navigate to a profile and click the Connect button
- Risk: MODERATE. LinkedIn’s behavioral AI tracks patterns. If Claude sends 20 requests in 15 minutes with perfectly even timing, it looks robotic. If Claude sends 5-8 over a 30-minute supervised session with natural pauses, it’s probably fine.
- Recommendation: Let Claude do this for a SMALL batch (5-8/session) while you supervise. Never leave it unattended for mass sending.
Sending follow-up messages to existing connections
- Claude navigates to the messaging tab, pastes a drafted message
- Risk: LOW-MODERATE. Less risky than connection requests because you’re messaging people who already accepted you. But still — unnatural patterns get flagged.
- Recommendation: OK for 5-10 messages per session, supervised.

RED — Don’t Do This

Mass connection request sending (20+ per session)
- 23% of users using browser automation face restrictions within 90 days
- LinkedIn detects browser extensions injecting code into the DOM (Document Object Model)
- Perfectly linear timing (one action every 45 seconds) is a ban trigger
- Your LinkedIn profile is your MOST valuable professional asset. A ban is catastrophic.
Auto-commenting at scale
- LinkedIn’s algorithm specifically watches for repetitive engagement patterns
Unattended long-run sessions
- The more steps without human supervision, the more likely something breaks or gets flagged
- A modal popup, a CAPTCHA, or a layout change can derail the whole flow

Pro Tip: The Real Risk Calculation

LinkedIn ban risk isn’t about whether Claude CAN do it. It’s about the asymmetric downside:

Upside of automating LinkedIn sending: Save 15-20 min/day
Downside of a LinkedIn ban: Lose your entire professional network, all connections, all social proof, your Sales Navigator subscription, and your #1 outreach channel

The expected value math doesn’t work. Save the automation for cold email (where a burned domain costs $12 to replace) and keep LinkedIn human-supervised.

3) The AI-Native Two-Channel System

Here’s how Solanasis runs outreach as an AI-native operation:

Channel 1: Cold Email (Volume Layer — 75% Automated)

CLAUDE DOES THIS (automated/assisted):          YOU DO THIS (human judgment):
─────────────────────────────────────           ─────────────────────────────
Process Apollo/Outscraper CSVs               →  Review cleaned list (5 min)
Generate personalized first lines            →  Spot-check 5-10 for tone (5 min)
Write email sequences + A/B variants         →  Approve copy (5 min)
Format Instantly/GMass import files           →  Upload and launch campaign (5 min)
Monitor campaign stats + recommend changes   →  Decide what to adjust
Draft replies to positive responses          →  Review and hit Send (2 min each)
Log results to CRM                           →  Weekly review (15 min)

Dmitri’s time: ~2-3 hours/week Contacts reached: 500-1,500/month Tool stack: Apollo (free) + Outscraper (free) + GMass ( $25 - 30/ m o) or I n s t an tl y ($ 37/mo) + Google Workspace on cold domain ($2.50-7/mo)

Channel 2: LinkedIn (Precision Layer — 45% Automated)

CLAUDE DOES THIS (Chrome + Cowork):             YOU DO THIS (human judgment):
─────────────────────────────────────           ─────────────────────────────
Triage Sales Navigator results (10-20/day)   →  Review shortlist (5 min)
Create account briefs for top prospects      →  Review briefs (5 min)
Draft connection notes (3 variants each)     →  Pick best variant (1 min each)
Draft follow-up messages                     →  Review and personalize (2 min each)
Draft comment engagement                     →  Post comments (5 min)
Format CRM notes from browser session        →  Log in Baserow (5 min)
                                             →  YOU send connection requests (10 min)
                                             →  YOU send messages (10 min)
                                             →  YOU take calls and close

Dmitri’s time: ~4-5 hours/week (30-45 min/day) Contacts reached: 150-200/month Tool stack: Sales Navigator ($100/mo — already have) + Claude in Chrome (existing)

Channel 3: Reddit/Community Intelligence (Warm Lead Layer — 80% Automated)

CLAUDE DOES THIS (scheduled task):              YOU DO THIS:
─────────────────────────────────────           ─────────────────────────────
Daily scan of r/msp, r/sysadmin,             →  Review flagged posts (5 min)
  r/smallbusiness for relevant posts
Flag warm leads who posted about security,   →  Reach out with personalized
  DR, compliance needs                          message referencing their post
Surface the exact language they used         →  Use THEIR words in your outreach

Dmitri’s time: ~30 min/week Expected reply rate: 15-30% (vs. 3-5% for standard cold email) Tool stack: Cowork scheduled task (existing subscription)

4) The Daily Execution Playbook (Easy-to-Follow Version)

Morning Block: 45-60 Minutes Total

Step 1: Check Replies (10 min)

Check Gmail for cold email replies (or have Claude via Gmail MCP surface them)
Check LinkedIn messages
For each positive reply: paste to Claude → Claude drafts response → you review and send

Step 2: LinkedIn Outreach Session (20-25 min)

This is your supervised Claude in Chrome session:

MINUTE 0-5: Open Sales Navigator
─────────────────────────────────
- Navigate to your saved lead list
- Tell Claude: "Triage these results — shortlist
  the top 10 that fit Solanasis ICP"
- Claude reads the visible profiles and scores them

MINUTE 5-10: Account Briefs
────────────────────────────
- Pick top 3-5 prospects from Claude's shortlist
- Open each profile + company website
- Tell Claude: "Create account brief for this prospect"
- Claude outputs: what they do, pain points, best angle

MINUTE 10-15: Draft Messages
─────────────────────────────
- Tell Claude: "Draft 2 connection note options
  for each prospect based on the briefs"
- Claude outputs 2 variants per prospect (under 300 chars)
- You pick the best one for each

MINUTE 15-25: SEND (You Do This Part)
─────────────────────────────────────
- Send 8-10 connection requests with the notes Claude drafted
- Send 5-10 follow-up messages to people who accepted recently
  (using Claude-drafted messages)
- Like/comment on 3-5 posts from prospects (using Claude-drafted comments)
- Log activity in Baserow/tracking sheet

Step 3: Cold Email Management (10-15 min)

If campaigns are running: check Instantly/GMass dashboard for bounce/spam alerts
If not yet launched: work on list building (Apollo export → upload to Claude → Claude processes)
Claude drafts next batch of personalized emails if needed

Step 4: Reddit Quick-Check (5 min)

Review any flagged posts from Claude’s scheduled scan
Reach out to warm leads via LinkedIn DM or email

Weekly Review: Friday, 15 Minutes

Cold email metrics: Open rate, reply rate, bounce rate, calls booked
LinkedIn metrics: Connection requests sent → accepted → messaged → replied → calls booked
Pipeline update: Log new prospects, move stages, note follow-up dates
Claude performance review: Which drafts got the best responses? What needs tuning?

5) The Claude in Chrome LinkedIn Session — Detailed SOP

This is the step-by-step SOP for your daily LinkedIn session:

Pre-Session Setup (One-Time)

Have your ICP block saved (paste this to Claude at the start of each session):

Solanasis ICP: SMBs and nonprofits in Colorado, 10-150 employees.
Strong fits: operational mess, systems sprawl, growth strain, no security
owner, compliance sensitivity, untested backups, disconnected tools.

Our wedge: 10-day Resilience Checkup (security baseline + real restore test
+ 30/60/90 plan). $3K-15K per engagement.

Target titles: CEO, Founder, Executive Director, COO, CFO, IT Director,
Office Manager, MSP Owner, PE Operating Partner.

Don't target: companies with existing strong security offerings (they're
competitors, not prospects).

Have your voice block saved:

Write in Dmitri's voice: warm, direct, slightly casual, not corporate.
Uses "Hey" not "Hi." Contractions are good. Short paragraphs.
Leads with curiosity or empathy, not features. Sounds like a founder
who's been in the trenches, not a sales rep.

Session Flow

Open Chrome. Open Sales Navigator. Start Claude in Chrome.

Prompt 1 — Prospect Triage:

Look at the Sales Navigator results on this page. Score each visible
prospect against Solanasis ICP. For each good fit, give me:
- Company | Person | Title
- Why they fit (specific, not generic)
- Likely pain points
- Best outreach angle
- Confidence: high/medium/low

Skip anyone who looks like they already have strong security offerings.

Prompt 2 — Account Brief (for each top prospect):

I'm looking at [Name]'s profile. Open their company website in a new tab.
Create a quick account brief:
- What this org does and their scale
- Likely operational/security pain
- Any warm signals (recent post, job change, growth)
- Best outreach angle for Solanasis
- One "why now" sentence

Prompt 3 — Draft Connection Notes:

Based on the brief for [Name], draft 2 connection note options.
Rules: under 300 characters, in Dmitri's voice, don't pitch in the note,
the goal is to get ACCEPTED not to sell, include one specific detail
about them or their company.

Prompt 4 — Draft Follow-Up Message (for accepted connections):

[Name] accepted my connection request yesterday.
Their brief: [paste brief].
Draft a follow-up message. Keep it under 100 words. Lead with something
specific about them, then bridge to the Resilience Checkup.
One CTA only: "Want the one-pager?" or "Would a quick call make sense?"

Prompt 5 — Draft Comment Engagement:

[Name] posted about [topic]. Draft a thoughtful comment (2-3 sentences)
that adds genuine value to the conversation. Do NOT mention Solanasis
or pitch anything. The goal is to be visible and helpful so they
recognize my name when the connection request arrives.

Prompt 6 — Browser-to-CRM Export:

Export today's LinkedIn session as structured notes:
- Date
- Each prospect: name, company, title, LinkedIn URL, fit score,
  pain points, message sent, status, next action, notes
Format as a table I can paste into Baserow or Google Sheets.

After the Session

Copy Claude’s CRM export into your tracking sheet
Review tomorrow’s follow-up queue
Note any patterns: which connection notes got accepted? Which follow-up messages got replies?

6) When to Use Which Channel (Decision Matrix)

Scenario	Channel	Why
MSP partners in Colorado	Both — LinkedIn first, email second	MSP owners are on LinkedIn. Connect first, then email creates multi-touch.
SMB executives you can find on LinkedIn	LinkedIn primary, email backup	Higher conversion, more personal, builds relationship
SMB executives NOT active on LinkedIn	Cold email only	Many SMB owners (especially smaller ones) aren’t on LinkedIn or don’t check it
Nonprofit EDs	LinkedIn primary	Nonprofits respond better to personal outreach than cold email
PE operating partners	LinkedIn InMail primary	Too senior for cold email; InMail cuts through
IT directors	Cold email primary	IT people check email; many are passive on LinkedIn
Adjacent consultants	LinkedIn primary	Relationship-building; not a cold sale
Scaling beyond Colorado	Cold email primary	Can’t do 500 LinkedIn connections/month nationally; email scales
Reddit warm leads	LinkedIn DM or email	Reference their post; either channel works because it’s warm

7) The Multi-Channel Compound Effect

The research is clear: prospects who see you on MULTIPLE channels are 2-3x more likely to respond to any single channel. Here’s the play:

The “Surround Sound” Sequence

DAY 1: Claude engages with their LinkedIn post (thoughtful comment)
DAY 2: Send LinkedIn connection request with short note
DAY 3: Cold email #1 arrives from solanasis.co
DAY 5: They accept LinkedIn connection → Claude drafts follow-up message
DAY 7: Cold email #2 arrives (automated follow-up)
DAY 8: Send LinkedIn follow-up message (you send, Claude drafted)
DAY 12: Cold email #3 arrives (final touch)

The prospect has now seen your name 5-6 times across 2 channels in 12 days. Each touch reinforces the others. The LinkedIn connection makes the cold email feel less cold. The cold email makes the LinkedIn message feel more serious.

Pro Tip: This compound effect is the REAL reason to run both channels. It’s not about “which one is better” — it’s about the multiplication effect of showing up consistently in multiple places. This is the Smartcuts “platform surfing” play applied to outreach: each channel amplifies the others.

8) The Gmail MCP Connector — How to Set It Up

This is the piece that closes the loop between cold email replies and Claude’s ability to help manage conversations.

What to Connect

The Gmail MCP connector gives Claude these tools:

create_draft — Claude writes a reply, it appears in your Drafts
search_messages — Claude finds specific emails/threads
read_message / read_thread — Claude reads full conversations
list_drafts — Claude sees what’s queued
get_profile — Claude knows which Gmail account it’s working with

The Reply Management Workflow

1. Positive reply arrives in your cold email inbox (solanasis.co)
   OR in your primary Gmail (solanasis.com) if they looked you up

2. You forward the reply to Claude (or Claude searches Gmail via MCP)

3. Claude reads the full thread and drafts a reply:
   - In your voice
   - Acknowledges what they said
   - Suggests 2-3 specific times for a call
   - Keeps it short and warm

4. The draft appears in your Gmail Drafts folder

5. You open the draft, review in 30 seconds, hit Send

6. Claude logs the interaction in your tracking sheet

When to Connect Gmail

Don’t connect yet if you’re still in the warmup/validation phase (Weeks 1-3)
Connect when you start getting positive replies that need timely responses (Week 4+)
The value is speed — a prospect who replies to a cold email and gets a thoughtful response within 1-2 hours is 3x more likely to book a call than one who waits 24 hours

9) Revised Timeline — What to Do When

Week 1 (March 10-14): LinkedIn Active + Cold Email Infrastructure

Day	LinkedIn (Active NOW)	Cold Email (Setup)
Mon	Set up Sales Navigator lists (if not done). Run first Claude in Chrome triage session.	Buy sending domain. Set up Google Workspace.
Tue	Send 10 connection requests (Claude-drafted notes).	Configure SPF, DKIM, DMARC. Start manual warmup.
Wed	Send 10 more requests. Follow up with any acceptances.	Sign up Apollo.io (free). Run CO MSP search. Export CSV.
Thu	Send 10 more requests. Engage with 5 target posts.	Upload Apollo CSV to Claude. Claude cleans, segments, generates personalization.
Fri	Send 10 more requests. Weekly review.	Run Outscraper Google Maps scrape. Claude merges with Apollo data.

LinkedIn reach this week: 40-50 connection requests sent Cold email progress: Infrastructure live, domain warming, list built

Week 2 (March 17-21): LinkedIn Ramping + Cold Email Warmup

Day	LinkedIn	Cold Email
Daily	10 connection requests + 5-10 follow-ups + 3-5 post engagements	Continue manual warmup (10-15 emails/day to friends)
Mid-week	First LinkedIn responses arriving — Claude drafts replies	Start sending 5-10 manual cold emails/day (hand-sent from Claude drafts)
Friday	Review acceptance rates, adjust notes if needed	Track manual cold email opens/replies

Week 3-4: Both Channels Active

Activity	LinkedIn	Cold Email
Daily volume	10 connection requests + 10 follow-ups + engagement	15-30 automated emails/day (GMass or manual)
Claude’s role	Chrome: triage, briefs, draft messages	Cowork: process lists, write sequences, analyze results
Your role	Send messages, take calls, log results	Review drafts, manage replies, take calls
Decision point		Sign up for GMass/Instantly if manual sending validated

Month 2+: Full System Running

Both channels on autopilot with Claude handling 60%+ of the work:

Cold email: 30-50/day automated, Claude managing reply drafts via Gmail MCP
LinkedIn: 10-15 touches/day, Claude doing all research and drafting in Chrome
Reddit: Scheduled task flagging warm leads daily
CRM: Baserow or HubSpot free, with Claude formatting entries

10) What This Proves About Being AI-Native

This is the “AI-native agency” proof of concept. Here’s what you’re demonstrating:

Traditional SDR Team (What This Would Normally Cost)

Role	Monthly Cost	Hours/Week	What They Do
SDR (Sales Development Rep) #1	$4,000-6,000	40	Cold email list building, sending, follow-ups
SDR #2	$4,000-6,000	40	LinkedIn outreach, research, message sending
Sales Ops / Admin	$2,000-3,000	20	CRM management, data entry, analytics
Total	$10,000-15,000/mo	100 hrs/week

Solanasis AI-Native Approach

Role	Monthly Cost	Hours/Week	What They Do
Dmitri (founder)	Your time	6-9	Final review, sending LinkedIn messages, taking calls
Claude Cowork	Existing subscription	N/A	List processing, email drafting, analytics, reply drafting
Claude in Chrome	Existing subscription	N/A	LinkedIn research, account briefs, message drafting
Gmail MCP	$0	N/A	Reply management, draft creation
Tools (GMass + domains + Sales Nav)	~$170/mo	N/A	Sending infrastructure
Total	~$170/mo + your time	6-9 hrs/week	Same output as 2-3 SDRs

That’s a 98% cost reduction and a 90% time reduction. That’s the story you tell future clients about what AI-native operations look like.

Pro Tip: The Meta-Play

Every time you run this system for Solanasis, you’re also building a CASE STUDY for your “Responsible AI Implementation” offering. You can walk into a client meeting and say: “Here’s how I replaced a $15, 000/ m o n t h S D Rt e am w i t h$ 170/month in tools and 7 hours/week of my time. Want me to help your team do something similar?”

That’s not just a growth hack for Solanasis — it’s a wedge offering. You’re eating your own cooking.

Sources

LinkedIn Automation Safety:

Cold Email Infrastructure:

Google Maps / List Building:

Enrichment:

Email Hosting:

Companion Playbooks:

LinkedIn_Cold_Outreach_Playbook.md — Full message library for every segment
MSP_Cold_Email_Outreach_Playbook.md — MSP-specific email sequences + infrastructure
solanasis-claude-in-chrome-gtm-playbook.md — Chrome prompt blocks and SOPs
Solanasis_LinkedIn_SalesNavigator_ORB_Playbook_v1.md — Sales Navigator setup and targeting
2026-03-10-cold-email-deep-dive-v2.md — Tool comparisons, Zoho assessment, enrichment workflow

Solanasis Docs

Explorer

AI_Native_Outreach_Playbook_v1