Revenue Workflow
Influencer Audience Capture
This workflow monitors engagement and connections around industry influencers, enriches and qualifies the audience, then routes high-fit accounts into tiered outbound motion.
OperationalTime to value · 3 to 4 weeks7 tools
The outcome
Converts passive social signals into qualified pipeline by capturing intent before competitors see it.
How it flows
How it flows.
Build it, step by step
Build it, step by step.
01
Select influencers to monitor
Pick 5 to 15 industry creators, operators, or thought leaders whose audience overlaps with your ICP. You want people your buyers already follow and engage with.
- List influencers by LinkedIn profile URL
- Confirm their audience includes your target titles and industries
- Track both personal profiles and company pages if relevant
02
Capture engagement on influencer posts
Use Trigify to monitor every like, comment, and repost on influencer content. Each engagement event includes the engager's LinkedIn profile, post URL, and engagement type.
- Trigify watches influencer posts automatically
- Captures likes, comments, and reposts as separate records
- Returns LinkedIn profile URL and post URL for each event
- Streams data into Clay via webhook or API
03
Scrape influencer connection lists
Pull the full connection list from each influencer using LinkedIn Sales Navigator and Findymail. This gives you a broader net of profiles who already know the influencer.
- Export connections via Sales Navigator search
- Send profile URLs through Findymail to normalize company data
- Tag each record with the influencer source
- Route into Clay alongside engagement data
04
Enrich companies and contacts
Inside Clay, run waterfall enrichment on every profile and company. You need firmographics and job data to filter and score downstream.
- Company: industry, size, geography, funding stage
- Contact: title, seniority, department, tenure
- Store engagement type and influencer source as signal fields
- Deduplicate by LinkedIn profile URL
05
Run AI qualification
Use a Clay AI step to filter out non-buyers. Check company fit, role relevance, and whether the account is already a customer or closed-lost.
- Pass enriched fields plus ICP criteria into the AI prompt
- Output: Qualified or Disqualified
- Disqualified records stop here
- Qualified records move to scoring
06
Score qualified leads into tiers
Assign a tier based on engagement type, influencer relevance, and company fit. Tier 1 gets high-touch outreach, Tier 2 and 3 get automated sequences.
- Tier 1: Commented or reposted, high-fit company, decision-maker title
- Tier 2: Liked or connected, medium-fit company, relevant role
- Tier 3: Everything else that passed qualification
- Store tier in a Clay column for routing
07
Route Tier 1 to high-touch outbound
Send Tier 1 leads into sequences from C-level profiles and alert the team in Slack. These are your highest-intent accounts and deserve immediate attention.
- Trigger LinkedIn connection request from founder or executive via HeyReach
- Trigger email sequence from C-level via Instantly
- Send Slack alert with profile, company, and signal context
- Optionally send follow-up connection requests from supporting AEs
08
Route Tier 2 and Tier 3 to automated sequences
Enroll mid and low-tier leads into standard email and LinkedIn sequences. No manual touch, but still personalized by signal and enrichment data.
- Push to Instantly email sequence (generic rep sender)
- Push to HeyReach LinkedIn sequence (SDR or rep profile)
- Use signal and enrichment tokens in message copy
- Track reply and meeting rates by tier in your CRM
The stack
The stack.
- Trigify Monitors post engagement in real time
- LinkedIn Sales Navigator Scrapes influencer connection lists
- Findymail Finds email addresses from profiles
- Clay Enriches, qualifies, and scores records
- HeyReach Sends LinkedIn connection requests
- Instantly Sends email sequences
- Slack Alerts team on Tier 1 leads
Related workflows
Related workflows.
Want a pod to run this for you?
Phi pods plug this workflow into your existing stack as Revenue Infrastructure, then operate it.

