Job Posts to Buyer Emails

Turn public job posts into B2B buyer leads. A company hiring for a role is a company spending money on that area, so a live job opening is one of the cleanest buying signals you can get. This actor reads those openings and works out the buyer persona for each one. Where the company exposes its people publicly, it also finds the named decision maker and a work email, labelled as published on the company site or guessed from the name pattern. Every row is a CRM ready lead built on a real hiring signal. No cookies, no logins.

Why a job post is a buying signal

A company hiring a Salesforce admin is a Salesforce buyer. A company hiring a RevOps lead is investing in revenue tooling. A company hiring three SDRs is scaling outbound and needs everything that supports outbound. The job opening tells you what they are buying and when. Most lead lists sell you a name and an email with no reason to reach out. This one sells you the reason first, then the person, then the way to contact them.

How it works

flowchart LR
    A[Company domains + role keywords] --> B[Scan public ATS job boards]
    B --> C{Matching live opening?}
    C -- no --> X[Skip company]
    C -- yes --> D[Job signal: proof of intent]
    D --> E[Map the buyer persona for that role]
    E --> F[Find the named decision maker]
    F --> G[Generate work email candidates]
    G --> H[Label the email: published or pattern guessed]
    H --> I[CRM ready lead row]

What each lead row contains

• companyDomain and the job trigger (the exact opening that proves intent)
• buyerPersona (the function that owns the purchase: revenue, marketing, recruiting, engineering, operations)
• contactName and contactTitle (the named decision maker)
• email and emailStatus (mx-valid-domain when the address is published on the company site, pattern-guessed when it is built from the name)
• confidence score and the jobUrl so every row is auditable

Input

• companies: company domains to inspect, such as acme.com.
• roleKeywords: the job triggers that prove buying intent, such as hubspot, revops, sdr, salesforce, or data engineer.
• location: optional location filter.
• freshnessDays: only keep openings posted within this window, so signals are current.
• buyerPersonaMode: auto map the buyer, or force a function.

Output example

{
  "companyDomain": "acme.com",
  "jobTitle": "Senior RevOps Manager",
  "buyerPersona": "revenue",
  "contactName": "Dana Ruiz",
  "contactTitle": "VP Revenue Operations",
  "email": "dana.ruiz@acme.com",
  "emailStatus": "pattern-guessed",
  "confidence": 0.86,
  "jobUrl": "https://boards.greenhouse.io/acme/jobs/123"
}

Pricing

This is buyer intent data, not a generic email dump, so it is priced for the outcome. You pay for what the pipeline actually delivers, and only for the good stuff.

Event	Price	What you get
Run started	$0.00005	Charged once when valid input is accepted
Qualified job signal	$0.02	A live opening proving hiring intent
Decision maker contact	$0.05	A named buyer matched to the signal
Candidate work email	$0.04	A work email candidate or MX valid business email
Verified work email	$0.15	A work email with positive SMTP verification

A buyer email tied to a live hiring signal is worth many times a scraped address with no context, which is why it sits well above generic email finders. A clean run only bills the signals and contacts it truly finds.

Use cases

1. Timed outbound: reach a buyer in the same week they start hiring for the thing you sell.
2. Account based marketing: feed intent qualified accounts and named contacts into your ABM lists.
3. Competitive selling: a company hiring for a rival tool is a company you can win.

What makes it different

• Intent first: every row comes with the job opening that justifies the outreach.
• No cookies or logins: it reads public ATS boards and company pages.
• Honest email status: an address published on the company site and one guessed from the name pattern are labelled differently, so you know exactly what you are sending to.

FAQ

Where do the job posts come from? Public applicant tracking boards and company career pages, the same pages anyone can open in a browser.

Do you guarantee every email? No. An email published on the company site is labelled mx-valid-domain and one built from the name is labelled pattern-guessed. The actor does not run SMTP mailbox checks, so no email is billed at the verified rate.

Can I filter by buyer function? Yes, set buyerPersonaMode to revenue, marketing, recruiting, engineering, or operations.