Kara Cold Outbound

Kara Cold Outbound

Write and fix LinkedIn cold outbound that gets replies. Core doctrine comes from Kara McMaster (https://www.karamcmaster.com/) and her own description of her playbook; gaps (exact message-by-message structure, timing, objection handling) are filled from Kellen Casebeer / GTM Cafe teachings and high-engagement practitioner sources. Every rule below is tagged with its origin: [Kara] = from Kara directly, [Casebeer] = GTM Cafe / Kellen Casebeer, [Research] = consensus across practitioner videos/threads. When Kara and research conflict, Kara wins.

The Five Laws

1. Optimize for the reply, not the call. [Kara] This is where everyone goes wrong. The first touches exist to start a conversation. The ask for time comes only after engagement.
2. Don't be a dick. Personalize. Show effort. Bring personality. [Kara] Her entire messaging framework in one line. A message that could be sent unchanged to 1,000 people is not personalized [Research].
3. Never pitch in the connection request. [Kara][Casebeer][Research - strongest consensus] The request's only job is acceptance. Any pitch smell kills it.
4. Signals are for targeting, not for messaging. [Casebeer] Commodity triggers (hiring, funding, job change) tell you WHO to message; the message itself should talk about the underlying problem, not congratulate them on the trigger. Kara goes further and calls most signal-based copy marketing BS [Kara].
5. No trust, no offer. [Kara] Track what they open and watch. If they haven't engaged with anything, don't make an offer. If someone shows up to a call asking "who are you?", end it.

The Sequence

Step 0: Connection request - no note [Kara]

Send blank. Kara's rule, and it matches Casebeer's default ("a connection request is not a pitch... treat acceptance as access, not conversion") and Reddit A/B data (26% blank vs 13% with a salesy note).

Exception [Casebeer][Research]: a note is fine ONLY if it is genuinely non-salesy and segment-specific (mutual group, mutual connections, shared space). Test blank vs note per audience; never pitch in the note either way. If you can't write a note that couldn't go to 1,000 other people, go blank.

Before requesting [Research]: like or comment on one of their posts 1 day before sending the request (+18% acceptance reported).

Steps 1-4: The icebreaker sequence (4-5 messages) [Kara]

Kara sends 4-5 messages. Her non-negotiable design rule: the last message is what shows as the inbox preview, so it must be the most human, personal one - it's what makes them open the thread at all [Kara].

Her last-message formula: geo/personal personalization with zero business content. Examples she gave verbatim:

• NYC prospect: "I was in New York last year, took my kids - safe to say the Lego store was the highlight of the trip haha"
• Dallas prospect: "Terry's Barbecue, best barbecue spot on the planet"

What messages 1-4 do (Kara defines the arc, research fills the slots):

• Message 1 - Observation + one easy question. [Kara][Research] Reference something real (their post, role, company situation) and ask ONE low-friction question. Formula: "{looks like / sounds like / I noticed} + {have you tried / are you happy with / how are you handling?}". No case studies, no pitch, no links. Screening-question variant: "are you running {service category} for {company}?" - even a "no" opens the conversation ("why not?").
• Message 2 (+2-5 days) - New value, zero reference to the no-reply. [Research] Never say "just checking in" or "circling back." Bring something new: an industry pattern, a resource, a result from a similar client. Casebeer's "agitational bump": a context-free jolt that makes them scroll up and re-read message 1.
• Message 3 (+2-5 days) - Social proof or a new medium. [Kara][Research] Case study, client result, or a 30-second voice note / video ("context on why I reached out" -> observation -> what peers tell you -> "worth chatting about? keep it real").
• Message 4 (+2-5 days) - The human closer / takeaway. [Kara][Research] This is Kara's preview-text slot: the personal, geo-based, kids-and-Lego-store message. It doubles as the soft breakup - low commitment, no pitch, gives them a graceful reason to reply. Casebeer's "softened breakup" variant: give the genuine reason you reached out, soften the ask, state it's the last message "as an act of respect."

Timing note: Kara didn't publish exact day-gaps; the 2-5 day spacing above is the practitioner consensus [Research]. Wait 24-48h after they accept before message 1 - instant DM on accept is the most common killer [Research].

Step 5: Long-funnel revive (optional) [Research]

+2-3 months: "Yo, it's been a while. How are things going at {company}?" Non-response is "life happened," not rejection. Park them, stay visible via content engagement, re-open later.

After the Reply [Kara]

1. Back and forth. Show you know their world: name their main challenge before they do ("you're probably stuck dealing with only referrals coming in the door").
2. Then the fit-framed ask: "I'm looking for a couple more revenue share partners, wondering if this would even be a fit." Frame as mutual selection, not a favor.
3. Prime before the call: send the engineered environment - a folder of video assets, workflows, and video case studies. Prospects should show up pre-sold.
4. Track engagement. Watched nothing -> no offer. Offer only after trust signals.

Objection & Reply Handling

• "No" to a screening question -> "Why not?" - turns a dead end into a conversation [Research].
• Correction replies are wins. Use uncertainty language ("it seems like you're...") - people reply to correct you, and a correction is a conversation [Casebeer].
• "Not interested" -> treat as qualification, thank them, move on. A fast no saves a pitch [Research].
• Interested but ghosting after the ask -> up to 4 follow-ups, vary the medium (voice note, email). Propose two specific times instead of a calendar link [Research].
• Brush-offs -> future-pace: "Down the line, do you think you'll want to solve this, or is it a later problem?" [Research]
• Cap LinkedIn follow-ups at 2-3 total touches after the opener, then park for ~3 months. Pest control matters - reports kill sender accounts [Research].

Anti-Patterns (buyers pattern-match these to spam instantly) [Research]

• "This might be random / out of the blue..."
• Fake flattery: "seriously impressive", "really cool", "loved your post"
• "Curious" as an opener, "just checking in", "circling back", "bumping this"
• "Not trying to sell you anything" (means you are)
• Stacked value props - one idea per message. "People accept or reject ideas, not sentence structures" [Casebeer]
• Token personalization ("I see you like pizza"). If it's a mail-merge variable, it doesn't count [Casebeer]

Volume & Account Safety [Research]

• ~20-25 connection requests/day manual; withdraw pending requests after 10-14 days.
• Benchmarks for calibration (self-reported, treat as directional): 35-50% acceptance, 15-25% reply rate on messages is strong; Kara-tier operators claim higher on warm lists.

Critique Rubric

When reviewing a draft message or sequence, score it against:

1. Reply-first: does this touch ask for a reply, or prematurely for time? (Premature time-ask = fail.)
2. Preview test: for the final message - would the inbox preview line make a stranger curious enough to open? Is it the most human message in the sequence?
3. 1-of-1000 test: could this exact message be sent unchanged to 1,000 people? If yes, it's not personalized.
4. One idea: does the message carry exactly one idea?
5. Effort signal: does it look like a human spent 60 seconds on this specific person?
6. Anti-pattern scan: none of the spam-tell phrases above.
7. Trust gate: if an offer is being made, is there tracked engagement justifying it?
8. Punctuation tell: zero colons, zero em/en dashes, no hyphen used as a pause. If any message trips this, rewrite it into plain sentences before it ships (see House Style).

House Style

Cold outbound has to read like a human typing in the DM box, not like formatted marketing copy. Punctuation is the biggest tell, so these rules are hard:

• No colons in message copy. A colon reads as a header, a label, or a pitch setup ("Quick question:", "Here's the thing:", "One idea for you:"). Rewrite it as two short sentences or just delete it. Colons are fine in this doc and in internal notes, never in a message a prospect receives.
• No em dashes or en dashes, ever. Use plain sentences.
• Do not use a hyphen as a dramatic pause or clause separator. A hyphen standing in for an em dash ("I was in town last week - figured I'd reach out") is still the banned pattern wearing a disguise. Split it into two sentences instead. Real hyphens inside compound words (revenue-share, 30-second, follow-up) are fine and don't count.
• One or zero pieces of "clever" punctuation per message. If a draft has multiple hyphens or any colon, it looks auto-generated, the exact thing that gets ignored. Prefer periods. Short, plain sentences beat punctuation gymnastics.

Note: some examples elsewhere in this doc use hyphens as separators for readability in the doc itself. Do not copy that punctuation into actual messages, convert to plain sentences.

Sources

• Kara McMaster (https://www.karamcmaster.com/) - core doctrine from her LinkedIn outbound playbook walkthrough on the Agent J AI Prompting Masterclass, 2026-07-23
• Kellen Casebeer message templates: heyreach.io/blog/linkedin-message-templates; signals doctrine: blog.syftdata.com/p/linkedin-signals-are-a-commodity; GTM Cafe: gtmcafe.com
• YouTube research (14 top-engagement practitioner videos, all transcripts read): Alex Berman 6-touch sequence; Matthew Lakajev LVQ; Will Aitken one-sentence opener; Ben Hemingway 3-message flow; lemlist acceptance data; Lead Gen Jay 48h rule; Patrick Dang 3-step DM
• Reddit research (23 top threads read): incl. r/sales "95% of meetings from LinkedIn", "200 LinkedIn Bookings in 5 Months", r/salesdevelopment "3377 connection requests" funnel
• Known gap: Kara's exact message 1-4 copy and day-gaps were never shared verbatim. Message slot contents above are the best-evidence synthesis, marked [Research].

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: jpeslar1
• Source: jpeslar1/john-peslar-ai-skills
• License: MIT

Install and usage instructions live in the source repository linked above.