Lead Generation Using Claude: 7 Signal-Based MCP Workflows (2026)
By Kushal Magar · September 28, 2026 · 16 min read
Key Takeaway
Lead generation using Claude becomes signal-based when you connect it to the SyncGTM MCP. Each play starts with a real business trigger — a job posting, a promotion, a LinkedIn like — and ends with an enriched, personalized outreach list. Seven plays, exact prompts, credit math per 100 leads, and first-line templates are all in this guide.
Most lead generation advice treats Claude like a copywriting tool — paste a company name, get a cold email. That is the wrong model. Lead generation using Claude becomes genuinely powerful when Claude is connected to real-time business signals and can execute the full workflow: detect the trigger, pull the accounts, enrich the contacts, and draft the first line — without you touching a spreadsheet.
This guide covers seven signal-based plays you can run inside Claude today using the SyncGTM MCP. For each play you will get the trigger logic, the exact numbered prompt, the MCP tool chain, a sample output table, credit math per 100 leads, and the first-line personalization the signal unlocks.
Teams running signal-based outreach consistently see 3–5× higher reply rates than cold lists because the outreach is timed to a moment the prospect is already in motion.
TL;DR
- Signal-based lead gen uses real business events as outreach triggers — hiring, promotion, job change, growth, engagement, tech stack changes.
- Claude + SyncGTM MCP runs the full workflow: signal detection → account pull → contact enrichment → personalized first line.
- 7 plays covered: hiring signals, job changes, promotions, newly hired executives, headcount growth, LinkedIn post engagers, and tech-stack fit / Google Maps.
- Each play includes the exact numbered prompt, MCP tool chain, output table, credit math per 100 leads, and first-line personalization template.
- Setup: Connect the SyncGTM MCP to Claude once. All plays run from natural-language prompts — no code required.
What Is Signal-Based Lead Generation with Claude?
Definition
Lead generation using Claude is the practice of connecting Claude AI to real-time business signal data — via the SyncGTM Model Context Protocol (MCP) — so that Claude can detect purchase-intent triggers, pull matched accounts, enrich contact details, and draft personalized outreach in a single workflow session, without manual spreadsheet work.
A signal is any observable business event that increases the probability a company or person needs what you sell. A company hiring six SDRs is a signal they are scaling outbound. A VP of Sales moving to a new company is a signal the new company is about to change its sales stack. A founder liking three posts about pipeline automation is a signal they are researching the problem you solve.
Traditional lead generation ignores timing. You build a list of companies in a vertical, blast them with an email, and hope some are in-market. Signal-based lead generation inverts this: you identify companies that are demonstrably in-market right now and reach out with a message that references exactly why.
Claude makes this scalable because it can call signal-detection APIs, cross-reference enrichment data, apply qualification logic, and write personalized outreach — all in the same session. The SyncGTM MCP is the data layer: one authenticated connection gives Claude access to LinkedIn job postings, job change databases, promotion trackers, headcount growth metrics, tech stack detectors, LinkedIn engagement data, and contact enrichment waterfalls.
Read our overview of Claude Code for sales prospecting if you want more background on how MCP integrations work before diving into the plays.
Play 1: Hiring Signals
Trigger: A company has posted a role that indicates budget, headcount growth, or a pain point you solve. A SaaS company posting "BDR Manager" signals they are investing in outbound. A logistics firm posting "Revenue Operations Analyst" signals they are formalizing their sales process.
MCP tools
search_linkedin_job_openings— search by keyword, location, and company sizecompany_job_openings— pull all active openings for a specific companyfind_people— find the right decision-maker at each companyfind_work_email— enrich with verified work email
Exact prompt
1. Use search_linkedin_job_openings to find US-based SaaS companies with 50–300 employees that posted a "Head of Sales" or "VP of Sales" role in the last 14 days. 2. For each company returned, use find_people to identify the CEO or founder (title contains "CEO" or "Founder", seniority = C-level). 3. Use find_work_email for each person found. Skip rows where email confidence is below 70%. 4. Output a table: Company | LinkedIn URL | CEO Name | Email | Job Posted | Signal Summary.
Sample output
| Company | CEO Name | Role Posted | |
|---|---|---|---|
| Acme Corp | Sarah Chen | sarah@acmecorp.io | VP of Sales · 3 days ago |
| Growthly | Marcus Bell | marcus@growthly.com | Head of Sales · 9 days ago |
Credit math (per 100 leads)
search_linkedin_job_openings: ~1 credit per company pulled · find_people: ~1 credit per person · find_work_email: 1 credit per email. Total: ~300–500 credits for 100 enriched contacts (accounting for ~30% drop-off at each step).
First-line personalization
"Saw you're hiring a VP of Sales at [Company] — congrats on the growth. Teams at that stage usually run into [problem SyncGTM solves]. Happy to show you how we've helped similar companies get their first outbound motion off the ground."
Play 2: Job Changes
Trigger: A contact you know — an existing customer, a warm prospect, or a champion at a churned account — has moved to a new company. The first 90 days in a new role are when buyers have the most budget flexibility and the strongest motivation to prove themselves.
MCP tools
check_job_change— detect recent role changes for a list of LinkedIn URLsfind_work_email— get new work email at the new companyenrich_organization— pull firmographic context on the new employer
Exact prompt
1. I have a list of LinkedIn profile URLs from past customers and warm prospects (paste list). Use check_job_change for each URL to identify anyone who changed employer in the last 90 days. 2. For each person who changed jobs, use find_work_email to get their new work email. Flag as "no email" if confidence is below 65%. 3. Use enrich_organization on each new employer to get industry, headcount, and estimated revenue. 4. Output: Name | Old Company | New Company | New Title | New Email | New Company Size | Days Since Change.
Credit math (per 100 leads)
check_job_change: ~1 credit per check · find_work_email: 1 credit each · enrich_organization: 1 credit each. Checking 300 contacts to find 100 job changers: ~400–600 credits total.
First-line personalization
"Congrats on the move to [New Company], [First Name] — exciting step. Given what you built at [Old Company], I suspect [New Company] is about to run into the same data enrichment bottleneck. Would love to show you how we solve it."
Play 3: Promotions
Trigger: A contact has been promoted — usually from individual contributor to manager, or from manager to director/VP. Newly promoted leaders inherit budget decisions and immediately start evaluating the tools they will own going forward.
MCP tools
check_promotions— detect promotion events for a list of LinkedIn URLslinkedin_profile_enrich— pull full profile context including new responsibilitiesfind_work_email— confirm their current email is still valid
Exact prompt
1. Use check_promotions on this list of LinkedIn URLs to find contacts promoted in the last 60 days (same company, higher title). 2. Filter to promotions that moved someone into a Director, VP, or C-level title — these have budget authority. 3. Use linkedin_profile_enrich on each to get their new title, company headcount, and any listed responsibilities. 4. Use find_work_email to verify their email is still active. 5. Output: Name | Company | Old Title | New Title | Promotion Date | Email | Company Size.
Credit math (per 100 leads)
check_promotions: ~1 credit per check · enrichment + email: ~3 credits per qualified lead. Checking 400 to find 100 promoted decision-makers: ~500–700 credits.
First-line personalization
"Congrats on the step up to [New Title] at [Company], [First Name]. Most revenue leaders in your position spend the first 60 days auditing what's in the stack — happy to show you what SyncGTM replaces."
Play 4: Newly Hired Executives
Trigger: A company has brought in a new VP of Sales, CRO, Head of RevOps, or CMO from outside. External executive hires typically carry a 90-day mandate to audit and replace tools — and they arrive without loyalty to the existing stack.
MCP tools
newly_hired_executives— pull companies that hired into executive roles in the last 30–90 dayslinkedin_profile_enrich— get the executive's background and prior companiesfind_work_email— find their new work email
Exact prompt
1. Use newly_hired_executives to find US-based B2B SaaS companies (50–500 employees) that hired a VP of Sales, CRO, VP of Revenue Operations, or CMO in the last 45 days. 2. For each executive found, use linkedin_profile_enrich to get their previous company, years of experience, and any linked posts from the last 30 days. 3. Use find_work_email to get their new work email. 4. Output: Executive Name | Title | Company | Hire Date | Previous Company | Email | Company Headcount.
Credit math (per 100 leads)
newly_hired_executives: signal pull cost is low (batch) · enrichment: ~2 credits per exec · email: 1 credit each. Total for 100 newly hired execs: ~300–450 credits.
First-line personalization
"As you settle into your first 90 days at [Company], the data quality question usually surfaces fast — especially if the previous team was running [common tool in their vertical]. Happy to show you how SyncGTM gives you a clean signal layer on day one."
Play 5: Headcount Growth
Trigger: A company has grown its headcount by 20%+ in the last six months. Fast-growing teams almost always hit data and tooling gaps at the inflection point — their current stack does not scale with them.
MCP tools
head_count_growth_rate— pull companies with a defined growth % over a time windowheadcount_by_department— see which departments are growing fastestfind_people— identify the RevOps or Sales Ops leadfind_work_email— enrich with verified email
Exact prompt
1. Use head_count_growth_rate to find US-based SaaS companies with 100–1000 employees that grew headcount by at least 25% in the last 6 months. 2. For each company, use headcount_by_department to identify whether the Sales or Revenue department is growing faster than the company average. Keep only companies where it is. 3. Use find_people to identify the VP/Director of Revenue Operations or Sales Operations (or Head of Sales if RevOps doesn't exist). 4. Use find_work_email to enrich each contact. 5. Output: Company | Headcount Growth % | Sales Dept Growth % | Contact Name | Title | Email.
Credit math (per 100 leads)
head_count_growth_rate: ~1 credit per company · headcount_by_department: ~1 credit · person + email: ~2 credits. Total for 100 enriched leads: ~400–600 credits.
First-line personalization
"Saw [Company] grew headcount by [X]% over the last six months — that's a meaningful signal that your sales motion is scaling fast. That's also exactly when enrichment quality becomes the bottleneck. Happy to show you how teams at your stage use SyncGTM to keep data quality ahead of headcount."
Play 6: LinkedIn Post Engagers
Trigger: Someone liked, commented on, or shared a post from your company page, a competitor, or a relevant thought leader. Engagement with specific content signals topic interest — and it is timestamped, making it one of the highest-intent signals available without asking someone to fill out a form.
MCP tools
linkedin_post_engagers— pull everyone who liked or commented on a specific post URLlinkedin_profile_enrich— get title, company, seniority for each engagerfind_work_email— enrich ICP-matching engagers with email
Exact prompt
1. Use linkedin_post_engagers on this post URL: [paste competitor or thought-leader post URL]. Pull all engagers (likes + comments). 2. Use linkedin_profile_enrich on each engager. Filter to people whose title contains "Sales", "Revenue", "GTM", "Operations", or "Marketing" AND seniority is Manager or above. 3. Filter to companies with 50–500 employees. 4. Use find_work_email for the remaining contacts. 5. Output: Name | Title | Company | Engagement Type | Company Size | Email | Post Topic.
Credit math (per 100 leads)
linkedin_post_engagers: low cost (batch pull) · linkedin_profile_enrich: ~1 credit per profile · email: 1 credit each. This is the cheapest play: ~200–400 credits per 100 enriched leads because the contact list is already scoped by the post.
First-line personalization
"Saw you engaged with [Author]'s post about [topic] — that's exactly the problem SyncGTM was built to solve. Happy to show you how we approach it differently."
Play 7: Tech-Stack Fit & Local Businesses
Trigger (tech-stack): A company is running a tool that is complementary to yours, or a tool that your product replaces. Tech-stack fit is one of the most reliable predictors of a fast sales cycle — the prospect already understands the category.
Trigger (Google Maps): For plays targeting local businesses — agencies, consultancies, clinics, law firms — Google Maps is the richest structured directory of business type, size, location, and contact info.
MCP tools
find_company_techstack— detect the tools a company is running by domainfind_companies— search for companies by tech stack keywordgoogle_maps_listings— pull local business listings by type and geographyfind_people— find the right contact at each companyfind_work_email— enrich with verified email
Exact prompt (tech-stack variant)
1. Use find_companies to find US-based B2B companies with 50–300 employees that use HubSpot CRM (our complement) but do NOT use Apollo, Zoominfo, or Lusha (our category competitors). 2. For each company, use find_company_techstack to confirm the stack and note any enrichment or prospecting tools present. 3. Use find_people to identify the Head of Sales Ops or RevOps. 4. Use find_work_email for each contact. 5. Output: Company | Domain | Tech Stack (relevant) | Contact | Title | Email.
Exact prompt (Google Maps variant)
1. Use google_maps_listings to find marketing agencies in Austin, TX with a Google rating of 4.0+ and at least 10 reviews. 2. For each business, extract: name, website, phone, address. 3. Use find_people on each website domain to find the owner or managing director. 4. Use find_work_email for each contact found. 5. Output: Agency Name | Website | Owner Name | Email | Rating | Reviews.
Credit math (per 100 leads)
Tech-stack: find_companies + find_company_techstack ~2 credits per company · person + email ~2 credits. Total: ~400–700 credits per 100. Google Maps: lower — google_maps_listings is very cost-efficient, mainly paying for email enrichment: ~150–300 credits per 100.
First-line personalization
"Noticed [Company] is running HubSpot — teams using HubSpot without a dedicated enrichment layer usually end up with stale contact data inside 6 months. SyncGTM keeps it clean automatically. Happy to show you the setup."
Credit Math Summary
Every SyncGTM credit call is transparent — Claude shows you the tool call and the cost before executing. Here is the consolidated cost estimate for 100 fully enriched leads across all seven plays:
| Play | Signal Source | Credits / 100 leads | Best For |
|---|---|---|---|
| 1 — Hiring signals | LinkedIn Jobs | 300–500 | Sales tool vendors |
| 2 — Job changes | Job change DB | 400–600 | Any category |
| 3 — Promotions | LinkedIn profiles | 500–700 | Enterprise / mid-market |
| 4 — New executives | Executive hire DB | 300–450 | New budget holders |
| 5 — Headcount growth | LinkedIn headcount | 400–600 | Scaling teams |
| 6 — LinkedIn engagers | LinkedIn posts | 200–400 | Cheapest / highest intent |
| 7 — Tech-stack fit | Tech stack API | 400–700 | Competitive displacement |
| 7 — Google Maps | Maps listings | 150–300 | Local / SMB plays |
Check your current balance before running a large batch: mcp__syncgtm__check_credits returns your live balance. Claude will call this automatically if you include "check credits first" in your prompt.
How SyncGTM Connects Everything
All seven plays run through the same MCP connection. You configure the SyncGTM MCP server once in your Claude environment, and every tool call in this guide becomes available in every session — no separate API keys, no CSV exports, no switching tabs.
The MCP layer handles: waterfall enrichment routing (Claude calls find_work_email once; SyncGTM tries Apollo → RocketReach → LeadMagic → Datagma in order), signal normalization (job change data from multiple providers merged into one schema), and deduplication against your existing outbound history.
Once Claude has built your enriched list, you can instruct it to push directly to your CRM or export to CSV for your sequencing tool. Teams typically pipe the output to automated email sequences or CRM integrations built in Claude Code.
According to Gartner's 2025 B2B Sales report, teams using intent and signal data in their prospecting see 2–4× improvement in pipeline quality compared to static list outreach. Signal-based lead generation using Claude and SyncGTM is how teams implement this without a data engineering team.
Conclusion
Lead generation using Claude stops being a copywriting exercise the moment you connect it to real business signals. Each of the seven plays in this guide follows the same pattern: detect a trigger, pull matched accounts, enrich the right contact, write a personalized first line. Claude handles all of it from a single prompt.
Start with the play that matches your current pipeline gap. If you are selling to growing companies, Play 5 (headcount growth) or Play 4 (newly hired executives) will give the fastest return. If you are targeting companies already in your category, Play 7 (tech-stack fit) is the tightest signal. If you want the cheapest cost-per-lead with highest intent, Play 6 (LinkedIn engagers) is the play.
Connect the SyncGTM MCP, paste the prompt, and run your first list today. The full B2B sales workflow guide covers how to take that list through enrichment, outreach drafting, and CRM logging in the same Claude session.
