Hiring signal to outbound
1,000 hiring companies to 2,127 sequenced contacts for $281
POST /v1/jobs/search { "job_title_or": ["SDR", "Sales Development"], "posted_at_max_age_days": 14, "company_country_code_or": ["US", "GB"] } # a company hiring 3 SDRs has already # decided to spend. that is the signal.
Intent data is usually somebody's model guessing at a buying committee's mood. A job posting is a company publishing, in writing, that it has budget approval and a problem it cannot staff its way out of. That is the cheapest honest trigger in B2B, and it is the one you can act on the same week.
This stack turns that posting into a sequenced contact in four steps. TheirStack finds the companies, Apollo finds and enriches the people, Findymail picks up what Apollo missed, and Smartlead sends. The whole thing runs nightly and costs about the price of a team lunch per thousand companies.
The trigger is public, dated and specific, so your first line writes itself without an AI personalization step. "Saw you are hiring three SDRs in Manchester" is not a guess, and the recipient knows it is not a guess. That is the whole advantage, and it disappears if you sit on the signal for a month.
Four steps, 1,000 companies, $280.88
Starting from a job-title filter rather than a company list. Target is a verified, sequenced contact at every company that posted in the last 14 days.
TheirStack · 1,000 company credits
Filter by job title, posting age and country. Returns the companies plus the postings themselves, which is the raw material for your first line. Credits roll over for 12 months.
Apollo people search · 3 per company
Search costs nothing, so filter hard before spending a credit. Take the VP Sales, the Head of RevOps and the hiring manager named on the posting. 3,000 people identified, zero credits spent.
Apollo enrichment, then Findymail on the misses
Apollo resolves roughly 1,650 at 1 credit each. Findymail takes the 1,350 misses and returns about 675 more, already verified. ZeroBounce validates Apollo's output only.
Smartlead · campaign per segment
Create the campaign, push the leads with the posting text as a custom field, and let webhooks push replies back into your CRM. The API and webhooks start on Smartlead's Pro plan, so that is the plan this step needs. Flat monthly cost, so this step does not scale with volume.
Where the $281 goes
The signal is 39% of this bill and sending a third of it, which is the opposite of the waterfall stack where the data was cheap and verification dominated.
That works out at $0.132 per mailable contact and $0.281 per qualified company. Rates are verified from vendor pricing pages. The match rates behind the contact counts are our modeling assumptions and will differ on your segment.
Contacts per company, not cost per contact. At three contacts per company this runs $0.132 each. At one contact per company the $109 signal cost and the $94 sending plan are spread over a third as many people and land nearer $0.32. Going wide on the buying committee is what makes the signal cost disappear into the noise.
When this stack is worth building
Four conditions, and the stack is worth building when all four hold rather than most of them. The first two decide whether the signal means anything for your product, and the last two decide whether the arithmetic works once it is running.
Your product maps to a role somebody hires for
Sales tooling maps to SDR and AE postings. Developer tooling maps to backend and platform roles. Compliance software maps to a first GRC hire. If you cannot name the job title that implies your problem, this stack has no trigger and you should be looking at technographics instead.
You can act inside two weeks
The posting-age filter is doing most of the work. A 14-day window is fresh enough that the problem is still unsolved and the budget is still unspent. At 60 days you are emailing a company that has already hired someone, and the signal is worse than no signal because it makes you look slow.
A qualified company is worth more than $0.20
That is the all-in cost per company here. For almost any B2B motion that clears easily, which is why hiring signal is usually the second thing a team adds after basic enrichment. The step that does not always clear is going to three contacts per company rather than one.
You are willing to run it weekly, not once
Postings are a flow, not a stock. Run this once and you get a backlog of stale triggers. Run it weekly against a 14-day window and you get a steady drip of companies at the exact moment they are receptive. The pipeline is the product here, not the list.
How to wire it
This is a scheduled job, not an agent, and it needs four credentials and a queue. The order below is the one that fails least.
Schedule the signal query, not the enrichment
Run the TheirStack query nightly with a 14-day window and dedupe against companies you have already processed. The credits only burn on new companies, so a nightly job over a stable market costs a fraction of the first run. Never re-enrich a company you already have.
Keep search and enrichment as separate steps
Apollo people search costs nothing and enrichment costs credits. Put a filter between them, even a crude one on seniority and department. Teams that chain search straight into enrichment pay for every marginal person the search returned, which is usually double what they wanted.
Carry the posting text through the whole pipeline
The job title, the location and the posting date are what make the first line work. If they get dropped between the signal step and the sending step, you have built an expensive way to send a generic email. Pass them as custom fields all the way into Smartlead.
Cap the daily credit spend
A bad filter that matches 40,000 companies instead of 1,000 costs $4,360 rather than $109, and it will do it in about four minutes. Set a hard ceiling on the TheirStack balance and alert on it. This is the single most expensive mistake available in this stack.
Build it with an agent
This stack ships as a skill file: the API surface of every tool in the chain, the build order, the limits that break it and how to check it worked. Point an agent at it and it has what it needs without reading 4 sets of vendor docs first.
--- name: hiring-signal-to-outbound description: Turn job postings into sequenced outbound: TheirStack for the signal, Apollo search plus Findymail for the people, Smartlead... --- # Hiring signal to outbound ## What you are building ## Prerequisites → 6 rows ## The tools, and how to call them → TheirStack, Apollo, Findymail, Smartlead ## Build it → 5 steps ## Gotchas → 5 ## How to verify it works → 5 checks ## What this costs to run
mkdir -p .claude/skills/hiring-signal-to-outbound curl -o .claude/skills/hiring-signal-to-outbound/SKILL.md https://frontal.so/gtm-apis/skills/hiring-signal.md
For Codex, Cursor, or anything else that reads a file or fetches a URL, hand it https://frontal.so/gtm-apis/skills/hiring-signal.md directly. It is plain markdown with YAML frontmatter and no tool-specific syntax, so nothing in it depends on which agent is reading it.
Signal is cheap. Acting on it fast is not.
The difference between this stack working and this stack being a spreadsheet is the scheduling, the dedupe and the field mapping. Frontal builds that part, and the credit ceilings that stop a bad filter emptying a balance in four minutes.
Worked with 300+ companies. A senior operator runs your account.
The other three stacks on this site are costed the same way, so the numbers are comparable: waterfall email enrichment at $0.0364 a unit, inbound speed to lead at $0.0587 a lead and agent-driven account research at $0.09 an account. Every provider in them is in the directory.
Questions we get
What decides whether this trigger works for you.
How fresh does a posting need to be?
Fourteen days is the window we run. The role is still open, the budget is still unspent, and the problem is still somebody's problem. At 60 days you are emailing a company that has already hired, and the reference makes you look slow rather than attentive. Filter hard on recency and accept the smaller list.
What if my product does not map to a job title?
Then this stack has no trigger and you should look at technographics instead. The test is whether you can name the role whose existence implies your problem. Sales tooling maps to SDR and AE postings, developer tooling to platform and backend roles, compliance software to a first GRC hire. If you cannot name one, TheirStack also sells technology signal, which is the better fit.
How many contacts should I take per company?
Three is roughly where the economics work. The $109 signal cost is fixed per company, and the run modeled on this page writes to 2,127 mailable contacts across 1,000 companies, which is how $281 lands at $0.132 per contact. Take one contact per company and the same spend reaches about half the conversations. Going wide on the buying committee is what makes the signal price disappear.
Does referencing the job posting feel intrusive?
No, and that is the point of using a public signal rather than modeled intent. The company published the posting deliberately, and the recipient knows it. Saying you saw they are hiring three SDRs in Manchester reads as someone who paid attention. Modeled intent data reads as surveillance, because the recipient cannot verify where it came from.
Can I run this without TheirStack?
Apollo returns job postings at 1 credit for up to 10,000 results, which is the best value endpoint in this directory and covers the basic case for almost nothing. TheirStack earns its $0.109 a company on filter depth and on technology signal alongside the hiring data. Start with Apollo, and add TheirStack when the filtering becomes the constraint.