Automating Outbound With LinkedIn Hiring Signals: How I Built a Job Post Monitoring Campaign in Clay, HubSpot, and Salesloft

Hiring signals are one of the hot new topics in outbound. When a company posts for a role that matches your ICP user, it's a direct indicator that their team is growing, their output is increasing, and their need for your product is building. That's a genuine reason to reach out, grounded in something real the prospect just did.

I built a workflow that monitors those signals across more than 15,000 ICP companies, qualifies contacts automatically, and enrolls them into a personalized email cadence — without any manual steps in between.

How the Workflow Is Structured

The pipeline runs across two Clay tables that operate as a parent-child system.

Table 1 — Job Post Monitor (Company Level)

The first table watches LinkedIn for new job postings at every company in our ICP list. It filters for specific roles and titles that make up most of our SQLs, full-time US positions only, and — critically — job descriptions that mention PM tools we integrate with like Asana, Monday.com, ClickUp, or Jira. A company that references project management tools in a job post is already thinking about workflow and systems, which makes the outreach angle sharper.

Since we've been running outbound for years and have other intent-based campaigns running, there's a chance we're already emailing this company. So before moving forward it looks up the company in HubSpot and makes sure it's not a customer and that there's been no activity for at least 90 days.

Last, Clay uses AI to normalize the job title, fetches recent company news for context, and generates a personalized email snippet tying the specific post to a relevant feature or use case for our software.

Table 2 — People and Enrollment (Contact Level)

Once a post qualifies, Table 2 finds up to 15 contacts per company who match our ICP profile — manager or higher, US-based, right title and role. Each contact's LinkedIn profile, title, and company then goes through a secondary AI analysis step that confirms ICP fit.

We found that relying on basic filters forces a tradeoff: be too specific and you kill volume, or cast too wide a net and you're emailing people who would never buy. So I cast a wide net on the first filter and use AI to spear-fish the best prospects after.

From there, the workflow runs an 11-provider email finder and validation waterfall. An AI prompt then generates a use case sentence that connects a specific product feature to their actual role — not a generic pitch, but something tied to what they do day to day.

Before anyone gets enrolled, the workflow runs a duplicate and recency check against HubSpot: it skips contacts already in an active cadence or with any logged activity in the past 90 days. Contacts that clear every check get created or updated in HubSpot, synced to Salesloft, and enrolled in the cadence automatically.

What's Running Under the Hood

From a qualifying job post to a contact enrolled in Salesloft, the workflow runs through:

• 6 qualification and filtering checks
• 11 email discovery providers in sequence
• 3 AI steps: job title normalization, ICP fit scoring, personalized use case generation
• 2 HubSpot lookups (company level, then contact level)
• 4 system writes: create/update company, create/update contact, Salesloft sync, cadence enrollment

None of that requires manual review. The cadence itself runs 8 emails, 2 calls, and a LinkedIn connection request over 44 days. The first email references the specific job post by title.

Why Job Posts Work as a Signal

A company posting an IC role is adding headcount to a team that's producing more work. That means they're growing, and any efficiency problems they have will grow with the size of the team.

Reaching out with a reference to the job post gives a specific, timely reason to make contact. It's not a fabricated pain point — it's something the company published about itself last week. That specificity changes the response dynamic of cold outreach.

This Structure Works Across Industries

The core logic here — monitor a signal, enrich contacts, qualify with AI, dedupe against your CRM, enroll — isn't specific to our product or industry. It's a template. The signal source, role filters, and messaging angle are the variables. Swap those out and you have a fundamentally different campaign.

A few examples of how it translates:

• Fintech and financial services — pair funding announcement data with compliance or ops hiring signals. A company that just closed a Series B and is posting for a Head of Finance Operations has a new budget and a process problem at the same time. That's the window.
• HealthTech and medical devices — companies hiring clinical coordinators or quality engineers are scaling regulated workflows. Target ops and quality leaders with tools that manage documentation, version control, and approval chains.
• E-commerce and retail SaaS — brands posting for paid media, CX, or creative ops roles are growing their storefront output. The hiring signal tells you they're scaling before their stack has caught up.
• Construction and real estate tech — building permit filings and new commercial project listings surface GCs and developers at the start of a project cycle, before vendor decisions are made.

The pattern is the same in each case: find a public signal that indicates a company is in motion, get to the right person before they've already solved the problem, and give them a specific reason why you're reaching out now rather than six months ago.

If you're running outbound and want to move beyond static lists, I'm happy to talk through whether a signal-based approach makes sense for your ICP and what it would take to build it for your stack. Reach out here.