Video summary

UPDATED 2026: LinkedIn Sales Navigator Lead Gen with AI & Apollo (Step-by-Step)

Main summary

Key takeaways

Business

Business-focused Summary (Sales Pipeline Lead Gen Workflow)

Core Problem the Video Addresses

Most teams treat Sales Navigator as a manual “phone book” instead of a repeatable pipeline-generation system, which leads to poor execution and missed quota.

The Playbook: A 5-Step Weekly Pipeline Engine

Step 1) Build the Outbound Sequence First (Foundation)

  • Create a multi-channel (omnichannel) outreach sequence in an outreach tool.
    • Example tools: Apollo (other tools acceptable, e.g., Outreach/Instantly)
  • The example sequence is a 21-day sequence.
  • Purpose: ensure you have a structured, organized way to execute touches across channels (email, call, LinkedIn, etc.) with timing control.

Deliverable

  • A ready-to-run 21-day sequence template you can load prospects into.

Step 2) Set Up Trigger-Based Sales Navigator Saved Searches (Mostly One-Time)

Build saved searches using:

  • ICP-defining filters
  • Buying-trigger logic

Key filter categories mentioned

  • Company headcount (example ranges used: 5,001–10,000)
  • Tenure / years in current company (example triggers: < 1 year, or “X months/years in a row”)
  • Industry / geography (suggested as additional dimensions)
  • Following your company (buying interest trigger)
  • Viewing your profile
  • Connections / “best path in” (first-degree vs second/third-degree; potential referral leverage)
  • Posted on LinkedIn (engagement / activeness signal)
  • “Change jobs” was mentioned as hit-or-miss, with tenure-based triggers preferred

Important Operational Rule

Saved searches should be niche (fewer leads, higher targeting) rather than overly broad. Configure searches so that when prospects are viewed or messaged/added, they drop off the candidate list—so teams always see “new” opportunities.

Examples of Search Setups

  • Example A: First-degree connections + headcount range + job titles (e.g., sales VPs) + posted on LinkedIn
  • Example B: Second/third-degree execs + tenure filter (e.g., < 1 year) + industries + posted on LinkedIn + avoid duplicates from past lead lists
  • Example C: A broader version with more results (example shown: 761 results and “65 new results”)

Step 3) Do “Deep Research” Before Adding Prospects (Signal Harvesting)

Goal: uncover strategic buy signals so outreach is relevant and personalized.

Process described

  1. Open prospect/company pages to verify data accuracy (example: Sales Navigator fields like company attribution can be inaccurate).
  2. Check company signals using Sales Nav Growth Insights (video uses job openings as a key trigger).
  3. Pre-qualify for fit (example: verifying company size by employee count / AES—terminology may vary, intent is “right org size”).
  4. Use ChatGPT (or other research tools like Perplexity/Google/manual review) to synthesize strategy + likely pain.
  5. Produce outreach notes that link:
    • the observable trigger (e.g., job openings, tenure, profile activity)
    • the hypothesis about the business situation
    • evidence/metrics to reference in messaging

Concrete Buying-Trigger Examples Used

  • Job openings growth
    • Example hypotheses: “sales job openings increased 35%” and later “sales job opening growth 250%”
    • Used as a proxy for performance gaps, turnover, or expansion requiring ramp/training
  • Function/team growth
    • Example concept: engineering/CTO org growth percentage (used similarly to infer expansion, funding, new product, or go-to-market changes)
  • Executive-level strategy priorities extracted via AI prompts (includes strategic initiatives and acquisitions)
  • Performance attainment concerns referenced from AI-synthesized stats
    • Video cites figures (formatting unclear), but the takeaway is “performance underachievement”

Research-to-Sequence Integration

After research, add the prospect to the outreach sequence (via Apollo extension/manual add).

Create “trigger notes” inside the outreach tool/task record:

  • Bullet the trigger (e.g., “35% sales job openings growth”)
  • Paste AI research outputs verbatim or summarized (video prefers copying full notes)

Prospect list hygiene

  • Once a prospect is worked, they disappear from candidate lists after view/message.

Step 4) Execute Outreach in Scheduled Prospecting Blocks

The system only works if teams actually run the tasks.

Recommended calendar cadence

  • Weekly prospecting block(s) to process new leads and complete outreach tasks
  • Example from the presenter: 8 hours/week minimum for cold outbound (in early territory, more)

Execution workflow inside Apollo

  • Tasks are auto-created when prospects are added
  • After completing a task, Apollo advances the prospect through sequence timing (e.g., 1 day later, 2 days later, etc.)

If a prospect does not match ICP or lacks triggers, do not add to the sequence.

Why This Matters (Pipeline Mechanics) Lead list → qualified triggers → personalized outreach sequence → consistent daily task execution → pipeline generation.

Step 5) Run It as an Ongoing Prospecting Engine (Weekly + Daily Loops)

Sales Navigator isn’t a one-time setup; it’s continuous.

Weekly loop (example schedule)

  • Every Monday:
    • check new results from saved searches
    • verify + research triggers
    • add qualified prospects into outreach sequences

Daily loop

  • During outreach windows:
    • execute tasks for leads already loaded into the sequence

Result Claimed “Endless qualified prospects” over time via:

  • rolling refresh of trigger searches
  • prospect removal after engagement
  • consistent outreach execution

Frameworks / Playbooks Implicit in the Workflow

  • ICP + Trigger-based targeting framework
    • ICP filters (headcount, titles, tenure, geography/industry)
    • Buying triggers (following/viewing, job openings growth, active LinkedIn posting, connection leverage)
  • System-of-systems pipeline machine
    • Sequence template (outreach tool)
    • Saved searches (Sales Nav)
    • Research synthesis (ChatGPT/tools)
    • Task execution (Apollo/Outreach)
  • Batching strategy
    • Batch lead list building + research at set times
    • Batch outreach execution into calendar blocks

Metrics / KPIs Mentioned (Mostly Trigger/Qualification Signals)

The video emphasizes “trigger metrics” more than business KPIs like CAC/LTV, but includes performance-related datapoints for relevance:

  • Employee/headcount range: example filter 5,001–10,000
  • Tenure trigger: e.g., < 1 year in current company; also “X months in a row”
  • Sales job openings growth (examples):
    • 35% increase
    • 250% sales job openings growth
  • Rep performance attainment (synthesized):
    • Video cites small quota attainment fractions (formatting unclear), emphasizing “underperformance”
  • Quota context (contrast example used in messaging):
    • Industry average example: 42%
    • Presenter/prospect performance reference: 30–32%
  • Pipeline outcomes are described qualitatively (“millions of pipeline”) without concrete weekly/monthly pipeline KPI targets in the subtitles.

Actionable Recommendations (What to Do Next)

Implement immediately

  • Set up at least one trigger-based saved search today.
  • Add 10 qualified prospects to your sequence this week.

Establish operating cadence

  • Put weekly time blocks on the calendar to check Sales Nav saved searches (example: Monday).
  • Put daily/weekly outreach time blocks on the calendar to execute tasks
    • Example mentioned: 2–3 hours/day or longer blocks
    • Presenter notes 8 hours/week minimum

Maintain list hygiene

  • Add only prospects who meet ICP and have clear buying triggers.
  • Use viewing/messaging updates so candidates naturally “age out” of the list.

Presenters / Sources

  • Marcus Shan (former #1 Sales Director, CentOS Corporation; sales training coach; presenter/source of the workflow)
  • Tools referenced as workflow components (not presenters):
    • LinkedIn Sales Navigator
    • Apollo
    • ChatGPT
    • Also mentions Perplexity, Outreach, Instantly, and “Rep view/other data sources” in the AI research example.

Original video