# Turn target accounts' job postings into buying signals

> Every weekday at 7am, we read your watchlist companies' job boards, flag the openings that mean a budget just opened, and post only what changed to Slack.

- Workflow type: agent
- Services: Hyperbrowser, HubSpot, Slack Bot
- Categories: Sales
- Published: 2026-08-14

## What it does

- Works through your watchlist of target companies every weekday morning and finds each one's careers page and job board listings on its own, so you never have to store a careers link on every account first.
- Reads the live postings and turns them into clean records: role title, function, seniority, location, posted date, and the tools named in the requirements.
- Judges which openings actually mean something. A first hire of its kind, a sudden surge of roles in one team, a role in a country they have never hired in, a wave of director and VP hires, or a shift in the tools they are asking for.
- Files the evidence on the company's HubSpot record, quoting the exact postings with a one line reason to reach out now, then posts only the strongest signals to your sales channel, grouped by signal type, and stays quiet when nothing has changed.

## What you'll need

- A list of the companies you want watched. Names or website addresses are enough, and they do not need to be in your CRM yet.
- A HubSpot login that can view companies, create new ones, and add notes.
- A Slack workspace and the channel where your sales team wants the alerts.
- A Hyperbrowser account for reading careers pages and job boards. The free plan is enough to get started.

## Prompt

Every weekday at 7am in my timezone, turn job postings at my target accounts into sales-ready buying signals. Use a cron trigger, Monday through Friday.

This must be an agent workflow. Deciding whether an opening is a genuine buying signal, comparing this run against what we saw before, and writing the outreach angle all need judgement that a fixed script cannot do.

Start from a watchlist of companies I maintain on the prompt page: a simple list of company names, with website domains where I have them. Do not require a careers page URL to be stored anywhere in advance, and do not require the company to already exist in my CRM.

Step 1: for each company on the watchlist, use Hyperbrowser's Search Web operation to locate that company's live careers page and any job board listings they use, such as Greenhouse, Lever, Ashby, or Workday. Prefer the company's own careers page and its job board subdomain over third party aggregators, which go stale and mix in dead postings.

Step 2: call Hyperbrowser's Start Scrape Job on the careers and job board URLs you found, returning markdown. These job endpoints are asynchronous: the start call returns a job id, so poll Get Scrape Job Result until the status is completed before using the content. If a job comes back failed or stopped, record that company as unreadable for this run and carry on instead of failing the whole workflow.

Step 3: turn the scraped pages into structured records with Hyperbrowser's Start Extract Job, passing a schema with these fields per posting: role title, function (engineering, sales, marketing, finance, operations, product, data, security, other), seniority (individual contributor, manager, director, VP, C-level), location including city and country, whether the role is remote, the posted date when shown, the tools and technologies named in the requirements, and the direct link to the posting. Poll Get Extract Job Result until it completes.

Step 4: judge which openings are genuine buying signals against my ICP rules. Flag a company when any of the following hold.

First of type. The company is hiring its first role of a given kind, for example a first Head of DevOps, a first Enterprise Account Executive, a first Security Engineer. A first infrastructure or security leader usually means they are about to invest in tooling for that area.

Volume acceleration. A sudden surge of openings concentrated in one function, for example going from a handful of engineering roles to dozens in a quarter. That points to a product push, significant attrition, or fresh funding.

Geographic expansion. A role in a city or country the company has not hired in before, which points to a new office or a new market.

Seniority shift. A wave of director, VP, and principal level hires, which often precedes a strategic repositioning.

Tech stack change. The tools named in the requirements have shifted, for example moving from Java and Oracle toward Python, Kubernetes, and cloud native tooling, which implies a platform modernization and a buying window for anything adjacent.

Only companies that clear at least one of these rules move forward. Ignore routine backfills, high volume retail, warehouse and support hiring, and roles unrelated to what we sell. When in doubt, leave it out, because a quiet channel is the goal.

Step 5: for each company that clears the bar, look it up in HubSpot with the Search Companies operation, matching on domain first and falling back to company name. If the record exists, attach the finding to it. If it does not exist, create it with the Create Company operation, setting at least name and domain, then attach the finding to the new record.

Step 6: write the evidence up with HubSpot's Create Note operation, associated with the company record. The note should name the signal type, quote the specific postings with their titles, locations, and posted dates, link to each posting, and end with a one line why now angle a rep can open a conversation with. Title the note so it is scannable on the timeline, for example "Hiring signal: first Head of DevOps, 14 Aug".

Step 7: keep a per company record across runs of the signals already reported, including the signal type and the postings behind it. At the start of each run, compare against it. Skip any company whose signal has not changed since the previous run, so the channel stays quiet on slow days. Treat a signal as changed when the signal type is new for that company, or when new postings have appeared that strengthen an existing signal.

Step 8: finish by sending a Slack message with the Slack Bot Send a Message operation to my sales channel, which I set during setup. Include only the strongest signals from that run, capped at a configurable number that defaults to the top five. Group them by signal type with a heading per group. Under each company, give the signal in one line, the roles behind it as links to the live postings, and the why now angle. Format with Slack mrkdwn, which uses single asterisks for bold and angle bracket links like <url|text>. If nothing cleared the bar and nothing changed, post nothing at all rather than an empty digest.

Keep these configurable on the prompt page: the watchlist of companies, the schedule, the ICP signal rules and any role or function filters, the Slack channel, and how many signals make the cut per run. Keep the watchlist bounded, since each company costs a web search plus a scrape and an extraction on every run.

## How to customize

- Change the schedule. Weekday mornings at 7am is the default, but daily, twice a week, or Monday only all work the same way.
- Tune the bar for what counts as a signal. Add your own rules, like only flagging roles above a certain seniority or in the functions that map to what you sell.
- Cap how many signals make the cut each run, and point the digest at a different channel or split it so each rep only sees the accounts they own.

## FAQ

### Do I need to add a careers page link for every company first?

No. You give it company names or website addresses and it finds the live careers page and job board for each one itself. That is usually the part that stops people from building this by hand.

### Will this fill my Slack channel with noise every morning?

No. It remembers what it reported for each company and skips anything that has not changed since the last run. On a slow day it posts nothing at all, so a message in the channel always means something actually moved.

### What happens if a company is not in HubSpot yet?

It creates the company record for you and attaches the finding there. That means your watchlist can include accounts you have not started working yet, which is usually where the best net-new signals come from.

### Will this work on HubSpot Free?

Yes. It only needs companies and notes, which are part of the free CRM. You do not need Sales Hub or a paid tier.

### How is this different from buying hiring intent data from a vendor?

It reads the same job postings straight from the source the day they go up, and it judges them against your rules about who is a good fit rather than a generic score. You also get the exact quoted posting on the CRM record, so a rep can see why the account surfaced.

Use this prompt in General Input: https://www.generalinput.com/prompts/turn-target-accounts-job-postings-into-buying-signals