A qualification standard that turns "they're hiring" into something dated, sourced and checkable

Recruiting outbound has an unusual problem: the qualifying signal is public, abundant and almost entirely noise. Job boards, careers pages and hiring posts will tell you that nearly every company in a target market is hiring something, which means a list built on 'is hiring' is a list built on nothing. The standard exists to make the difference between a company that is hiring and a company in a hiring wave into a field on a row rather than a judgement in somebody's head.

'They're hiring' is true of almost every company and useful for none of them.

1. 01

   A signal without a date is a guess

   Every signal on a row carries the date it was observed and a link to where it was observed. A funding announcement from fourteen months ago and one from last week are the same fact and completely different leads, and without a date field the list cannot tell them apart three weeks later when somebody works it.

2. 02

   Evergreen listings are the trap the whole standard is built around

   A permanently open 'Sales — always hiring' page produces the same data signature as a genuine hiring wave: multiple open roles, recent posting dates, an active careers page. The standard requires recurrence evidence that is distinct from the listing itself, which is what separates a company that is growing from a company that has high turnover.

3. 03

   The disqualifier list does more work than the qualifier list

   One open role, no evidence of recurrence, and an undated signal each remove a row outright. Removing rows is unpopular with anyone measured on list size, which is precisely why the removal rules are written down rather than left to the person building the list.

4. 04

   Segmentation is a promise about what you can say later

   The signal type recorded on the row is what the first message can reference. If the row says only 'hiring', the message can only say 'I saw you're hiring', which is the message everyone else sends.

Recruiting is the **best-performing vertical on LinkedIn** (36.5% acceptance, 18.9% reply — 1.8× average; Expandi 2026), which is exactly why it's the hardest to sound different in. When everyone gets replies, the differentiation has to be in list quality and the offer, not the outreach.

Each row carries: company, employee band, open-role count with the date observed, signal type from a closed list of five, signal date, source link, recurrence evidence, disqualifier check, segment tag and owner. The five signal types are funding, a new office or market, an explicit multi-team hiring statement, a stated headcount number, and a single-function push. The list is closed on purpose: an open taxonomy fills up with 'growth' and 'expansion' within a fortnight. The disqualifier check is a single column with a fixed set of reasons, so removals can be counted and the reasons compared across list builds rather than argued about.

1. 1

   Week 1

   Signal taxonomy

   Five signal types agreed and closed; disqualifier reasons written as a fixed list

   Owner: OmniFlow

2. 2

   Week 1

   Row schema

   Column schema including date observed, source link and recurrence evidence

   Owner: OmniFlow

3. 3

   Weeks 2–3

   Build and check

   Rows built to schema; disqualifier column completed on every row, including the ones that pass

   Owner: OmniFlow

4. 4

   Monthly

   Re-qualification rhythm

   Rows older than the signal window re-checked against the source link rather than rebuilt

   Owner: OmniFlow

This entry makes no performance claim. It documents a qualification standard and the specific failure it was written to prevent: a list of companies that are permanently hiring being mistaken for a list of companies in a hiring wave.

These are the surfaces this engagement is run and measured from, shown with representative figures built around the benchmarks cited on this page. Every account we run reports into views like these, and you keep ownership of all of them.

The first version of the schema had a free-text signal column. Within two list builds it contained nineteen different phrasings of the same four ideas and could not be grouped, counted or compared. The taxonomy is closed now, and adding a sixth signal type is a deliberate decision rather than something that happens quietly while someone builds a list at speed.

Real client work that shipped. No performance figures are published, because none have been verified and approved for release. See all our work