Kenny Damian's LinkedIn Strategy, Head of GTM…

I've spent 600+ hours inside Claude Code. Here's the complete cheat sheet I wish I had before starting. Saving this will save you dozens of hours of trial and error. 1️⃣ INSTALL IN 30 SECONDS M…

LinkedIn post image: I've spent 600+ hours inside Claude Code.

1.0K8994100 viral

AI Developer Tools5 months ago

View on LinkedIn

Everything you need to know about what version of Claude you should be using. Claude Desktop → You need to think → Research, brainstorm, write, analyze → Upload a PDF and ask questions → Draft em…

LinkedIn post image: Everything you need to know about what version of Claude you should be using.

14378438 viral

AI Tools & Productivity5 months ago

View on LinkedIn

Most teams spend $50k on SDRs before spending $5000 on demand. Here's why that's backwards I see this all the time-teams go straight to cold outreach and paid ads, then ask why conversion rates are…

LinkedIn post image: Most teams spend $50k on SDRs before spending $5000 on demand.

13269535 viral

B2B Demand Generation5 months ago

View on LinkedIn

This outbound system printed $250,000 in pipeline in 30 days. Here’s the 7-stage playbook behind it. 1️⃣ ICP FOUNDATION We start with proof, not guesses. → Deep intake form → Reverse-engineer th…

LinkedIn post image: This outbound system printed $250,000 in pipeline in 30 days.

12765332 viral

Outbound Sales5 months ago

View on LinkedIn

I now run my entire GTM stack from Claude Code. Here are the 10 MCPs every GTM team should connect: (MCP = Model Context Protocol. One connection = Claude controls the entire tool.) 1. Notion - s…

14551631 viral

AI GTM Automation5 months ago

View on LinkedIn

We’ve sent millions of cold emails this year. The tool you choose matters less than you think. A founder asked me which platform to pick. My answer: it depends on your motion, not your taste. Here…

LinkedIn post image: We’ve sent millions of cold emails this year.

9558629 viral

Cold Email Outreach5 months ago

View on LinkedIn

Topics & Content Focus

Primary Topics

Agentic AI for GTM operations (where agents fit, how they trigger, and what they automate across Sales/Marketing/RevOps/CS)Outbound as infrastructure (deliverability-first systems, data waterfalls, sequencing mechanics)Signal-driven pipeline generation (intent, timing, enrichment/validation, and routing orchestration)

Secondary Themes

Tooling frameworks for AI adoption (when to use chat vs code vs background delegation)GTM strategy sequencing (demand creation before demand capture; foundation before scaling SDR spend)Operational stack design (connected systems, automation layers, and failure points at scale)

Industry Focus

B2B SaaS GTM (Sales/Marketing/RevOps) teamsOutbound agencies and outbound-led growth teamsTechnical founders building revenue systems with AI automation

Content Categories

Operator playbooksFrameworks and diagnosticsTech stack breakdownsImplementation checklistsContrarian GTM strategy

Performance Insights

278.6%

Avg Engagement Rate

STABLE

Performance Trend

Best Performing Topics

AI tool decision frameworks (thinking vs building vs delegating)GTM sequencing and contrarian strategy (foundation/demand creation before outbound)Systemization playbooks (infrastructure-first outbound and connected stacks)

Virality Signals

Specific numbers and outcomes (pipeline/ARR) to earn attention fastCopy/paste-ready frameworks (phases/layers/agent types) that audiences share internallyTool-and-process specificity (names, constraints, timelines) that signals real operator experienceDebate-inviting endings (questions) that lift comment volume

Structure & Quality

360

Avg Length (Words)

HIGH

Depth Level

ADVANCED

Expertise Level

0.83/10

Uniqueness Score

Common Hooks

Credibility hook ("I built X for Y teams/clients")Contrarian correction ("Most teams think..." / "Here’s why that’s backwards")Outcome/number hook (pipeline/ARR figures, concrete results)Promise of a framework (diagnostic, phases, layers, rule-of-thumb)

Common Endings

Open loop + offer (cheat sheet, mapped builds, exact stack)Direct question to invite contributions ("Anything I’m missing?")Actionable next step ("Start with one" / "Follow this order")

Value Delivery Methods

Decision frameworks (what to do first, what to build next, where AI belongs)Operational checklists (deliverability setup, enrichment/verification steps, sequencing rules)Diagnostics and heuristics (team-size rules, bottleneck identification, trigger-based automation slots)Stack architecture thinking (how tools connect, not just what tools exist)

Formatting Style

Skimmable bullets with arrows (→) and short linesNamed frameworks (Phases, Layers, Agent types)Rule-based heuristics (team-size rules, do/don’t constraints)Tool lists grouped by workflow stage

Audience & Tone

YES

Question Usage

0.35%

Response Rate

Detected Tone

Smart-casual operatorDirect and systems-mindedTactically opinionated (clear do/don’t stances)Builder/implementer credibilitysemi-formalfirst-person

Interaction Style

Practitioner-to-practitioner problem solving (people respond with tools, edge cases, and workflow questions)Preference polling via frameworks (audience debates “what’s missing” or “what works for me”)Implementation validation (readers ask whether their stack/process matches the described standard)

Community Building Signals

Invites collaboration (asks for missing distinctions, encourages additions)Creates shared language (agents, phases, layers) that followers can reusePositions assets as community artifacts (cheat sheets, mapped builds) rather than pure promotion

Writing Style Patterns

Content Strategy

Hook: Credibility hook ("I built X for Y teams/clients")Tone: semi-formalCTA: Low-friction discussion CTA (ask for feedback, mis

Writing style breakdown

I've spent 1,000+ hours building GTM systems that actually scale.

The biggest mistake I see?

Teams buy the tools before they define the logic.

Here is the 5-step architecture I use to build a $1M pipeline engine from scratch.

1️⃣ THE DATA WATERFALL

Don't rely on one source. One source is a single point of failure.

We stack

→ Apollo for the broad TAM

→ Clay for the deep research

→ Prospeo for the email find

→ BounceBan to protect the domains

2️⃣ THE SIGNAL LAYER

Stop blasting everyone. Reach out when they are 'warm'.

Track these

→ New VP of Sales hired

→ Company just raised Series B

→ They just installed a competitor's tech

→ 3+ people from the same account visited your site

3️⃣ THE INFRASTRUCTURE

If you send from your main domain, you are playing with fire.

→ 15 secondary domains

→ 2 mailboxes per domain

→ 3 weeks of slow warmup

→ SPF/DKIM/DMARC locked down

4️⃣ THE MESSAGE FRAMEWORK

No one cares about your 'end-to-end solution'.

They care about

→ The specific pain they felt this morning

→ How you solve it in 30 seconds

→ The proof that you've done it for someone exactly like them

Keep it under 100 words. Plain text only.

5️⃣ THE AUTOMATION LOOP

Use n8n or Make to tie it all together.

→ Lead hits signal -> Auto-enrich -> Add to sequence -> Alert rep on Slack

Anything I missed on the technical setup for 2025?

Kenny Damian

Warm Analysis

Performance Overview

Top Posts by Engagement

Posting Patterns & Frequency

Best Performing Days

Best Performing Times To Post