Finding who is ready now
The hiring-signal account check
A list you already trust to the accounts on it that are hiring, and a verified person to call.
By Mike Hurley, founder of WarmUp. We ran this on our own list in September 2026.
Version 1.0. Last updated . About 6 minutes.
- Motion
- Outbound
- Steps
- 8
The hiring-signal account check: the route
In order: the list, the check, Stage 1 (is anything open?), Stage 2 (is it a role we care about?), the verdict. An orange arrow is a yes. Every unknown ends at Needs a look and every no at No signal. Each stage is drawn in full beside its steps under "How to build it". Go to the stages in detail
1The list
A list where fit is settled
What each row carries:
- The company domain
- The date it was last checked
- Its rank on your map
In: A list of domains you already want.
2The check
Three looks, cheapest first
3Stage 1, is anything open?
Postings found?
- Yes: On to Stage 2.
- Unknown: Needs a look.
- No: No signal, date recorded.
4Stage 2, is it a role we care about?
- Match the title list
- Read the posting, not just the title
- A signal orders the queue. It never decides fit.
A role on the list?
- Yes: Signal, moves up the queue.
- Unknown: Needs a look.
- No: No signal, date recorded.
5Verdict
Out: One signal per hiring account, and a verified person to call.
5Verdict
Signal, moves up the queue- Flow
- Pass, yes
- Fail, no
- Unknown
- Never automatic
An unknown never counts as a pass.
- Flow
- Pass, yes
- Fail, no
- Unknown
- Never automatic
- An unknown never counts as a pass.
- The check:
- Asks a job feed first. Only when the feed is empty does it pay a research agent to read the job board, then the careers page. Every look writes its date.
Download the boardOpen it full sizeOne sheet, free to keep and share.
Why it helps
The hiring signal feed starts from job postings and asks whether each company is one we want. This check runs the other way. It starts from a list of companies we already want and asks which of them are hiring. When fit is settled, the only open question is timing, and a job posting is the best public answer to it.
Our list was 802 partner agencies of the CRM we build in. On the first run, 67 of them were hiring for a role on our title list, five of those postings named a tool we work in, and the check ended with 71 verified contacts at 39 agencies in the rep's queue. The other 735 agencies were checked once, and for the next 14 days checking them again costs nothing.
One thing to know before you copy it: a job feed alone misses companies that post only on their own site, and small companies often do. That is why there are three looks and not one.
Why we built it this way
- Start from a list you trust. A signal is worth the most where fit is already decided, and you skip qualifying every company a feed returns.
- Cheapest look first. The job feed reads titles only and is the cheapest thing in the workflow, so every account gets it. The paid research runs only when the feed comes back empty.
- Never pay twice. Every look writes its date and what it cost beside the account, whether or not a role was found. Anything checked inside 14 days is skipped, so you can rerun the whole list as often as you like.
- Read the posting, not just the title. The line that matters, such as a tool the role must know, sits in the description. The order of the three looks came from a design the team at Freckle shared with us. We rebuilt it as our own.
- One title list for every hiring check. This check and the daily feed read the same file, so a title means the same thing in both.
- A signal orders the queue and never decides fit. A hiring account moves up inside its rank. Its rank does not change.
- People only where it pays. Contacts are found only for top-ranked accounts with a live signal, the owner or founder first. Every email is verified before anyone is added, and nobody is messaged automatically.
How to build it
- Pick a list where fit is settled. A partner directory, your top tier, a named-account list. Key it on company domain and add two columns: the date last checked and what the check cost.
A list where fit is settled
Accounts you already know you want: a partner directory, your top tier, a named-account list. Because fit is decided, the only open question is timing.
What each row carries
The company domain
The key for every lookup and every write.
The date it was last checked
Blank the first time. Every check writes it, whether or not a role was found.
Its rank on your map
Read from your own table. A signal moves an account up inside its rank and never changes the rank.
In: A list of domains you already want. - Skip anything checked in the last 14 days. Do this before any look runs.
- Pass
- Not checked. Go on to the looks.
- Fail
- Checked. Stop: the earlier answer stands and nothing is paid twice.
- Unknown
- No date on the row. Treat it as not checked.
- Look one: ask a job feed by company domain, titles only. If postings come back, go straight to the match.
Ask the job feed
Does a feed of career-site listings show open roles at this domain?
Source: A job feed searched by company, titles only. The cheapest look, so every account gets it.
- Pass
- Postings come back. On to the match.
- Unknown
- The feed is empty. Many companies post only on their own site.
- Look two, only when the feed is empty. A research agent finds the company's applicant-tracking board and reads what is open.
- Look three, the last resort. The agent reads the careers page the way a person would. If the pages will not load, the answer is unknown, and a person takes a look.
Read the job board, then the careers page
What does the company itself say is open?
Source: A research agent: first the applicant-tracking board, then the careers page as a last resort
- Pass
- Open roles found, with the posting text.
- Fail
- The pages load and list nothing open.
- Unknown
- The pages will not load, or the agent cannot tell.
- Postings found?
- Yes:On to Stage 2.
- Unknown:Needs a look.
- No:No signal, date recorded.
- Match the postings to your title list. Then read each matching description for your marker words. Two matching roles at one company are one signal.
Match the title list
Is any open role on the title list your daily feed already uses?
Source: One title list, shared with every other hiring check you run
- Pass
- A title on the list. Two matches at one company are one signal.
- Fail
- Open roles, none on the list.
- Unknown
- A title that only counts when the description says so.
Read the posting, not just the title
Does the description name the tool or the job you sell into?
Source: The posting text, read for a short list of marker words
- Pass
- A marker is in the text. The signal is stronger and says why.
- Fail
- No marker. The title match still stands on its own.
- Unknown
- The description is missing or cut short.
A signal orders the queue. It never decides fit.
The account was wanted before the posting and is still wanted after it closes. The signal only says call this one first.
- A role on the list?
- Yes:Signal, moves up the queue.
- Unknown:Needs a look.
- No:No signal, date recorded.
- Write one signal event per hiring account. To the same signals table your other workflows use, with the posting as the reason to call. Let your scoring pick it up from there.
- Find people only for the accounts that earned it. Top-ranked, with a live signal. Owner or founder first, then sales and marketing leaders. Verify the email, then put the contact in the rep's queue for a person to work.
Verdict
Signal, moves up the queue
One event per account lands in the shared signals table, with the posting as the reason to call. The score and the CRM record update on their own.
Needs a look
A page that would not load, or a title that needs its description. A person checks it; it is never counted as hiring.
No signal, date recorded
Nothing open, or nothing on the list. The check date is written so the next 14 days cost nothing.
People only where it pays
Contacts are found only for top-ranked accounts with a live signal: the owner or founder first, then sales and marketing leaders. Every email is verified before anyone is added.
Nothing sends on its own
Never automatic
Contacts land in the rep's queue in the CRM. A person works each one.
Out: One signal per hiring account, and a verified person to call.
One row
- a 40-person agency on the partner list, never checked
- feed empty
- job board shows a RevOps Manager role
- the text names the CRM
- signal written
- the owner's verified email goes to the queue
Why it is built this way
A hiring signal is the strongest public sign that a company is about to need help. The check is ordered so the cheap answer comes first, the paid answer only when it is needed, and nothing is paid for twice.
- AStart from a list you trust
- When fit is already settled, a hiring signal is worth the most, and you skip qualifying every company the feed returns. (Design rule.)
- BCheapest look first
- The feed reads titles only. The paid research runs only when the feed is empty, so most accounts never reach the expensive steps. (Design rule.)
- CNever pay twice
- Every look writes its date beside the account. Anything checked inside 14 days is skipped, so rerunning the whole list costs almost nothing. (Design rule.)
- DRead the posting
- The line that matters, such as a tool the role must know, sits in the description. A title list alone misses it. (Design rule.)
Copy this
The fallback order and the people rule
# account-check.yaml
list: accounts where fit is already decided, keyed on company domain
skip_if: checked_at is within 14 days # never pay twice
looks: # in order; stop at the first one that returns postings
1: job feed by company domain, titles only # cheapest, every account
2: research agent reads the applicant-tracking board # paid, only when 1 is empty
3: research agent reads the careers page # paid, last resort
unreadable: unknown -> a person looks; never counted as hiring
match: the same title list your daily hiring feed reads
read_description_for: [the tools you work in, the job you sell into]
write:
always: checked_at, what each look cost
on_match: one signal event per account (title, posting URL, marker found: yes | no)
people:
only_when: the account is in your top two ranks AND has a live signal
order: [owner or founder, sales leader, marketing leader]
require: a verified email
land_in: the rep's queue, as a contact a person works
never: [a message sent automatically, a rank changed by a signal]The same guide as plain Markdown, for an agent or a notes app: /library/hiring-signal-account-check.md
Words we use
- Signal:
- Something a company or a person did that gives a reason to reach out now: a job posting, a funding round, a visit to your site, a click on an ad, a contract award, a compliance date, an expansion, a comment on a post, a form, a reply.
- Tier:
- The rank a company holds on the map because of its fit. A signal moves a company up inside its tier and never changes the tier.
- Queue:
- The one ordered list a rep works from, with a score and a reason to call beside each name.
- Unknown:
- The answer a check gives when it cannot tell. An unknown is never counted as a pass. It waits for a person or for a missing fact.
Want this run on your named accounts?
We build it in your tools and run it with your team.
30 minutes to scope it. Engagements are contracted through WarmUp, Inc.