Sales navigator prospecting skill

Run LinkedIn Sales Navigator prospecting using Morgan J.

by LeadMagic·MIT license·★ 62 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
# Sales Navigator Prospecting

## Overview

Most teams treat Sales Navigator as a $99/month contact export — find prospects,
paste the same message 4,000 times, wonder why LinkedIn "doesn't work."
**Morgan J. Ingram** (Founder, **AMP Social**; 4x LinkedIn Top Sales Voice) treats
Sales Nav as an **intent engine**: stack behavioral filters (posted recently,
following your company, viewed your profile, tenure windows), pair **each filter
with its own message**, and run a **15-minute daily** saved-search alert workflow.

This skill is the tactical Sales Nav layer. Load `social-selling` for profile
optimization, SSI, and general DM sequencing; load `linkedin-algorithm` when
reps also publish content and need feed reach mechanics.

## When to Use

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Sales navigator prospecting

LeadMagic/main1 file shown
SKILL.md
Show the full text179 lines

Sales Navigator Prospecting

Overview

Most teams treat Sales Navigator as a $99/month contact export — find prospects, paste the same message 4,000 times, wonder why LinkedIn "doesn't work." Morgan J. Ingram (Founder, AMP Social; 4x LinkedIn Top Sales Voice) treats Sales Nav as an intent engine: stack behavioral filters (posted recently, following your company, viewed your profile, tenure windows), pair each filter with its own message, and run a 15-minute daily saved-search alert workflow.

This skill is the tactical Sales Nav layer. Load social-selling for profile optimization, SSI, and general DM sequencing; load linkedin-algorithm when reps also publish content and need feed reach mechanics.

When to Use

  • "How do I actually use Sales Navigator?"
  • "Sales Nav isn't generating meetings"
  • "Morgan Ingram Sales Navigator playbook"
  • "Filter-specific LinkedIn messages"
  • "Get executives to respond on LinkedIn"
  • "10-minute Sales Nav saved search"
  • "Posted in last 30 days filter"
  • "Build a Sales Nav workflow for my SDR team"

Authoritative Foundations

Morgan J. Ingram (AMP Social) — filter-specific prospecting. Public thesis: each Sales Navigator filter is a signal that deserves its own message — not one recycled script. Core motions: high-intent filter stacks, insight + question comments on recent posts, 24–48 hour wait before connect, saved-search weekly alerts, and multi-thread plays per account. Trained teams at Zoom, HubSpot, Snowflake (public positioning). Full filter tables, message library, and weekly workflow → references/morgan-ingram-sales-navigator.md.

LinkedIn SSI Methodology — professional brand, finding people, engaging with insights, building relationships. Use SSI as a diagnostic; Ingram's motion is the operational layer on top.

Richard van der Blom (Just Connecting) — when reps also post content, apply feed mechanics (dwell time, golden hour, no external links in posts) so profile traffic from Sales Nav outreach converts. → linkedin-algorithm.

Prerequisites

  • Sales Navigator Core or Advanced seat
  • ICP defined: titles, seniority, company size, geography
  • Optimized personal profile (social-selling Phase 1)
  • CRM or spreadsheet to log filter variant → response rate

Step-by-Step Process

Phase 1: Audit the Current Motion
  1. Export last 30 days of LinkedIn outreach: message text, filter used (if any), sends, accepts, replies, meetings.
  2. Flag one-template abuse — same body copy across unlike filters.
  3. Baseline response rate by message variant; set improvement target per filter.
Phase 2: Build High-Intent Saved Searches

Create one saved search per motion (enable weekly alert):

  1. Active executives — Posted last 30 days + VP/C-suite + ICP geo/industry.
  2. Warm to brand — Following your company + target titles.
  3. Profile viewers — Viewed your profile in last 90 days.
  4. New in role — Years in company < 1 year + buyer titles.
  5. Buying window — Years in company 6–12 months + buyer titles.

Document each search in a playbook table: filter stack, message variant ID, owner.

Phase 3: Write Filter-Specific Messages

Build 12+ variants minimum (see template table in reference). Rules:

  • Open with the filter signal ("Noticed your post on…", "Saw you're [N] months into…", "Thanks for following [company]…").
  • No product pitch in connection request or first DM.
  • One clear question per touch; invite conversation.
Phase 4: Executive Engagement (Posted-in-30-Days)
  1. Find recent post from saved-search lead.
  2. Comment: insight + question (not "great post").
  3. Wait 24–48 hours.
  4. Connection request referencing the exchange.
  5. After accept: DM with value; meeting ask only after rapport.
Phase 5: Weekly 15-Minute Rhythm
  • Monday: triage saved-search alerts; rank by intent (viewed profile > posted > following company).
  • Tue–Thu: comments + connection requests (batch 10–15/day per rep).
  • Friday: DM follow-ups; log meetings; retire underperforming variants.
Phase 6: Multi-Thread Target Accounts

For ABM accounts, assign different filter plays per persona on the same account (exec, champion, technical). Coordinate in CRM to avoid duplicate pitches same week. → multi-thread-orchestration.

Output Format

Sales Navigator prospecting playbook: current-state audit, five saved-search definitions with filter stacks, 12 filter-specific message variants, executive engagement runbook (comment → wait → connect → DM), 15-minute daily/weekly calendar, multi-thread map for top accounts, and measurement dashboard (response rate by filter, meetings per search).

Quality Check

  • Every saved search has a unique message variant (no generic blast)
  • Executive motion uses insight+question, not "great post"
  • 24–48 hour wait between comment and connection request documented
  • Weekly alert enabled on each saved search
  • Profile optimized before outreach scales (social-selling)
  • CRM logs filter type for reply-rate analysis
  • Multi-thread plan exists for tier-1 accounts

Common Pitfalls

  1. One script for every filter. Wastes the strongest Sales Nav signals; Ingram's 5× pipeline lift illustration comes from filter-message matching.

  2. Instant connect after comment. Reads as automation; breaks trust.

  3. Skipping "viewed your profile" and "following company." Highest-intent free signals in the stack.

  4. No tenure-based plays. New leaders (< 1 year) and month-6–12 operators have different pains — same message misses both.

  5. Sales Nav without profile investment. Prospects check your profile; empty activity kills accept rates.

  6. Attribution only in last-touch CRM. LinkedIn pipeline is often dark social — add self-reported source fields.

Execution Artifacts

  • references/framework-notes.md — Framework index and authority routing
  • templates/output-template.md — Deliverable shell
  • scripts/check-output.py — Lightweight deliverable validator
  • references/morgan-ingram-sales-navigator.md — Filters, messages, workflows
  • social-selling: Profile, SSI, general DM sequencing
  • linkedin-algorithm: Organic content reach when pairing with outbound
  • list-building: Multi-source lists; Sales Nav as one source
  • multi-channel-outreach: Email/call steps on same prospects
  • multi-thread-orchestration: ABM persona coordination
1---
2name: sales-navigator-prospecting
3description: >-
4 Run LinkedIn Sales Navigator prospecting using Morgan J. Ingram's AMP playbook —
5 high-intent filters, filter-specific messaging, insight+question executive
6 engagement, saved-search alerts, and a 15-minute daily workflow. Use when Sales
7 Nav underperforms, reps blast one template, or you need executive response on
8 LinkedIn. Triggers on: "Sales Navigator", "Sales Nav", "Morgan Ingram", "AMP Social",
9 "posted in last 30 days", "filter-specific messaging", "LinkedIn prospecting",
10 "book meetings LinkedIn", "saved search Sales Nav", "insight plus question",
11 "social selling prospecting".
12license: MIT
13compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
14metadata:
15 version: "1.0.0"
16 author: LeadMagic
17 category: inbound
18 tags: [linkedin, sales-navigator, prospecting, social-selling, outbound, sdr]
19 related_skills: [social-selling, linkedin-algorithm, multi-channel-outreach, list-building, lead-finding, multi-thread-orchestration]
20 frameworks:
21 - "Morgan J. Ingram (AMP Social) — Sales Navigator filter-specific prospecting"
22 - "LinkedIn SSI Methodology"
23 - "Richard van der Blom (Just Connecting) — LinkedIn Algorithm Insights Report"
24---
25 
26# Sales Navigator Prospecting
27 
28## Overview
29 
30Most teams treat Sales Navigator as a $99/month contact export — find prospects,
31paste the same message 4,000 times, wonder why LinkedIn "doesn't work."
32**Morgan J. Ingram** (Founder, **AMP Social**; 4x LinkedIn Top Sales Voice) treats
33Sales Nav as an **intent engine**: stack behavioral filters (posted recently,
34following your company, viewed your profile, tenure windows), pair **each filter
35with its own message**, and run a **15-minute daily** saved-search alert workflow.
36 
37This skill is the tactical Sales Nav layer. Load `social-selling` for profile
38optimization, SSI, and general DM sequencing; load `linkedin-algorithm` when
39reps also publish content and need feed reach mechanics.
40 
41## When to Use
42 
43- "How do I actually use Sales Navigator?"
44- "Sales Nav isn't generating meetings"
45- "Morgan Ingram Sales Navigator playbook"
46- "Filter-specific LinkedIn messages"
47- "Get executives to respond on LinkedIn"
48- "10-minute Sales Nav saved search"
49- "Posted in last 30 days filter"
50- "Build a Sales Nav workflow for my SDR team"
51 
52## Authoritative Foundations
53 
54**Morgan J. Ingram (AMP Social) — filter-specific prospecting.** Public thesis:
55each Sales Navigator filter is a **signal** that deserves its own message —
56not one recycled script. Core motions: high-intent filter stacks, **insight +
57question** comments on recent posts, 24–48 hour wait before connect, saved-search
58weekly alerts, and multi-thread plays per account. Trained teams at Zoom, HubSpot,
59Snowflake (public positioning). Full filter tables, message library, and weekly
60workflow → `references/morgan-ingram-sales-navigator.md`.
61 
62**LinkedIn SSI Methodology** — professional brand, finding people, engaging with
63insights, building relationships. Use SSI as a diagnostic; Ingram's motion is the
64operational layer on top.
65 
66**Richard van der Blom (Just Connecting)** — when reps also post content, apply
67feed mechanics (dwell time, golden hour, no external links in posts) so profile
68traffic from Sales Nav outreach converts. → `linkedin-algorithm`.
69 
70## Prerequisites
71 
72- Sales Navigator Core or Advanced seat
73- ICP defined: titles, seniority, company size, geography
74- Optimized personal profile (`social-selling` Phase 1)
75- CRM or spreadsheet to log filter variant → response rate
76 
77## Step-by-Step Process
78 
79### Phase 1: Audit the Current Motion
80 
811. Export last 30 days of LinkedIn outreach: message text, filter used (if any),
82 sends, accepts, replies, meetings.
832. Flag **one-template abuse** — same body copy across unlike filters.
843. Baseline response rate by message variant; set improvement target per filter.
85 
86### Phase 2: Build High-Intent Saved Searches
87 
88Create one saved search per motion (enable weekly alert):
89 
901. **Active executives** — Posted last 30 days + VP/C-suite + ICP geo/industry.
912. **Warm to brand** — Following your company + target titles.
923. **Profile viewers** — Viewed your profile in last 90 days.
934. **New in role** — Years in company < 1 year + buyer titles.
945. **Buying window** — Years in company 6–12 months + buyer titles.
95 
96Document each search in a playbook table: filter stack, message variant ID, owner.
97 
98### Phase 3: Write Filter-Specific Messages
99 
100Build **12+ variants minimum** (see template table in reference). Rules:
101 
102- Open with the **filter signal** ("Noticed your post on…", "Saw you're
103 [N] months into…", "Thanks for following [company]…").
104- No product pitch in connection request or first DM.
105- One clear question per touch; invite conversation.
106 
107### Phase 4: Executive Engagement (Posted-in-30-Days)
108 
1091. Find recent post from saved-search lead.
1102. Comment: **insight + question** (not "great post").
1113. Wait **24–48 hours**.
1124. Connection request referencing the exchange.
1135. After accept: DM with value; meeting ask only after rapport.
114 
115### Phase 5: Weekly 15-Minute Rhythm
116 
117- Monday: triage saved-search alerts; rank by intent (viewed profile > posted >
118 following company).
119- Tue–Thu: comments + connection requests (batch 10–15/day per rep).
120- Friday: DM follow-ups; log meetings; retire underperforming variants.
121 
122### Phase 6: Multi-Thread Target Accounts
123 
124For ABM accounts, assign **different filter plays per persona** on the same
125account (exec, champion, technical). Coordinate in CRM to avoid duplicate pitches
126same week. → `multi-thread-orchestration`.
127 
128## Output Format
129 
130Sales Navigator prospecting playbook: current-state audit, five saved-search
131definitions with filter stacks, 12 filter-specific message variants, executive
132engagement runbook (comment → wait → connect → DM), 15-minute daily/weekly
133calendar, multi-thread map for top accounts, and measurement dashboard (response
134rate by filter, meetings per search).
135 
136## Quality Check
137 
138- [ ] Every saved search has a unique message variant (no generic blast)
139- [ ] Executive motion uses insight+question, not "great post"
140- [ ] 24–48 hour wait between comment and connection request documented
141- [ ] Weekly alert enabled on each saved search
142- [ ] Profile optimized before outreach scales (`social-selling`)
143- [ ] CRM logs filter type for reply-rate analysis
144- [ ] Multi-thread plan exists for tier-1 accounts
145 
146## Common Pitfalls
147 
1481. **One script for every filter.** Wastes the strongest Sales Nav signals;
149 Ingram's 5× pipeline lift illustration comes from filter-message matching.
150 
1512. **Instant connect after comment.** Reads as automation; breaks trust.
152 
1533. **Skipping "viewed your profile" and "following company."** Highest-intent
154 free signals in the stack.
155 
1564. **No tenure-based plays.** New leaders (< 1 year) and month-6–12 operators
157 have different pains — same message misses both.
158 
1595. **Sales Nav without profile investment.** Prospects check your profile; empty
160 activity kills accept rates.
161 
1626. **Attribution only in last-touch CRM.** LinkedIn pipeline is often dark
163 social — add self-reported source fields.
164 
165## Execution Artifacts
166 
167- `references/framework-notes.md` — Framework index and authority routing
168- `templates/output-template.md` — Deliverable shell
169- `scripts/check-output.py` — Lightweight deliverable validator
170- `references/morgan-ingram-sales-navigator.md` — Filters, messages, workflows
171 
172## Related Skills
173 
174- **social-selling**: Profile, SSI, general DM sequencing
175- **linkedin-algorithm**: Organic content reach when pairing with outbound
176- **list-building**: Multi-source lists; Sales Nav as one source
177- **multi-channel-outreach**: Email/call steps on same prospects
178- **multi-thread-orchestration**: ABM persona coordination
179 

Discussion

Alternatives

AI Sales Team — Main OrchestratorYou are a comprehensive AI sales intelligence and outreach system for Claude Code. You help founders, sales teams, agency owners, and…Sales & ecommerce · MITAuto research publicAutonomous cold email campaign launcher. Takes one target company domain, scrapes their website, generates an ICP with Claude, pulls matching leads via Prospeo, enriches emails + company descriptions, personalizes each lead with parallel Claude Code Task sub-agents (A/B/C variants), and uploads as a live Smartlead campaign. Uses local JSON files for state (no database required). Use for automated daily campaign launches after you have an initial `client-profile.yaml` from /icp-onboarding. Triggers on "auto-research", "launch an automated campaign", "daily campaign", "run the research loop".Sales & ecommerce · MITABM Campaign — DIY PlaybookABM campaign skill for Claude Code: run a full Account-Based Marketing campaign end-to-end — from ICP definition to live LinkedIn Ads. Builds targeted account lists with Vibe Prospecting, enriches and scores companies with real-time B2B data, generates personalized ad creatives with Claude Code and Figma, pushes matched audiences to LinkedIn Ads, and monitors campaigns daily at scale. The complete GTM skill for AI-driven account-based marketing in Claude Code, Codex, Hermes-Agent, and OpenClaw. No agency needed.Sales & ecommerce · MITAccount contact shortlistContact data skill for Claude Code and Codex: build a ranked shortlist of decision-makers and contacts at a target company for outbound prospecting, deal acceleration, or renewal/expansion plays. Returns verified contact data including email, phone, LinkedIn profile, title, seniority, and department. Provide a company name or domain plus optional seniority focus or use case. Use for contact data enrichment, LinkedIn profile lookup, and building outbound contact lists. Works in Claude Code, Codex, Hermes-Agent, and OpenClaw.Business & ops · MIT