Leadpuller
CHAPTER 00 · THE OVERVIEW

How Leadpuller pulls revenue.

An operator's field manual for the four-stage machine that runs your LinkedIn pipeline. Inspect every input, tune every output, and let the engine compound while you sleep.

04STAGES
127TUNABLE INPUTS
0BANS IN 12 MONTHS
FIG. 00 · THE MACHINE

The four-stage pipeline, end to end.

Target list in one side, qualified replies out the other — everything between is controllable, measurable, and safe by design.

01
FINDINGSource prospects from LinkedIn search, Sales Navigator, post engagement, or your own CSV.
~1,200 leads/wk
02
QUALIFYINGScore every lead against your ICP. Filter out low-fit contacts before a single message fires.
ICP-scored
03
ENGAGINGRun multi-step sequences across unlimited senders. Connect, follow up, message, voice note.
8-sender rotation
04
CONVERTINGEvery reply lands in MailRoom. Close deals from the unified inbox, push wins to your CRM.
INPUTTarget list + ICP rules
OUTPUTQualified replies in MailRoom
CHAPTER 01

Finding the right prospects.

Leadpuller scrapes four sources your team already uses — LinkedIn search, Sales Navigator exports, post engagers, and CSV uploads — then enriches every record with verified email and phone in a single pass.

  • LinkedIn Search scraper · 10K per session
  • Sales Navigator + post engagement miner
  • Email + phone enrichment, 94% match rate
scrape_job_01.specRUNNING
SOURCELinkedIn Search
QUERYVP Sales · B2B SaaS · 200–500 FTE
ESTIMATED847 results
ENRICHMENTEmail ✓ · Phone ✓
PROGRESS634 / 847
FIG. 01A · A RUNNING SCRAPE JOB SPECIFICATION
CHAPTER 02

Qualifying against your ICP.

Score every prospect against a rule-based Ideal Customer Profile — firmographics, job title, tech stack, intent signals. Your outreach fires only at leads that can actually close.

  • 15+ weighted firmographic filters
  • Real-time scoring as leads enter the pool
  • Threshold branching (If ICP ≥ 80 → fast lane)
icp_rule_seniortech.spec71AVG SCORE
Company size 200–1000 FTEWeight×1
Industry: B2B SaaSWeight×2
Title match: VP / Head of SalesWeight×3
Tech stack: HubSpot or SalesforceWeight×1
QUALIFIED1,284 / 2,109 leads · 61%
FIG. 02A · ICP RULE WITH WEIGHTED FIRMOGRAPHICS
CHAPTER 03

Engaging on autopilot.

Each mission is a directed sequence — connect requests, waits, messages, voice notes — executed across unlimited LinkedIn senders with per-sender rate budgets so no one account carries the full load.

  • 5 step types: connect, wait, DM, follow-up, voice note
  • Conditional branches (If connected / If ICP ≥ 80)
  • Multi-sender rotation with per-account daily budgets
mission_eu_saas_q2.seqRUNNING · 8 SENDERS
1Connect request412 sent
2Wait 2 dayselapsing
3DM: "Saw your post on scaling SDR teams…"287 sent
4Branch: If ICP ≥ 80 → fast lane, else → nurtureactive
5Voice note (fast lane only)scheduled
FIG. 03A · A RUNNING MISSION WITH A CONDITIONAL BRANCH
CHAPTER 04

Converting from one inbox.

MailRoom unifies every LinkedIn conversation across every sender. Reply, snooze, push to CRM — without switching profiles. Each thread carries the prospect's ICP score, mission history, and context.

  • Unified threads across unlimited senders
  • AI-suggested replies, one-click send
  • Auto-push hot replies to HubSpot / Salesforce
mailroom.threads12 UNREAD
MC
Marcus Chen·“Can we hop on a 15-min?”
Hot2m
SP
Sarah Park·Thanks — sending my team's ICP
Qualified1h
DK
David Kline·Quick question — does this integrate with…
New3h
FIG. 04A · THE UNIFIED INBOX ACROSS EIGHT SENDERS
APPENDIX A · SAFETY PROTOCOLS

Built to stay well below LinkedIn's safe-use limits.

Every protocol below is enforced at the worker level — not just documented. 3,412 active senders. Zero platform bans in the last 12 months.

0PLATFORM BANS · 12 MONTHS
A.01
Per-sender rate limitsEvery LinkedIn sender operates on a hard-coded action budget. No single account can exceed daily caps even if a mission tries.
A.02
Human-paced actionsRandomized delay between actions — never in bursts. Mimics the rhythm of a human-operated LinkedIn session.
A.03
Dedicated proxy per senderResidential IP address country-matched to sender profile. Same IP per account across sessions — LinkedIn sees a consistent location.
A.04
Cookie rotation & challenge detectionSession cookies revalidated every 6 hours. Any security challenge auto-pauses the sender and notifies the operator immediately.
A.05
Incident response playbookAnomaly detection monitors every sender for unusual LinkedIn responses. On trigger, immediate pause and manual review within 2 hours.
END OF MANUAL

Ready to run the machine?

Start the trial. Connect your first sender. Launch a mission. The rest is documented above.