Where does the evidence come from?

Only from previous Hiring signals for that company. Velocity is recomputed after Hiring is processed, in the same chain that refreshes Tool adoption.

When does Velocity not write a row?

When there is no recent AI hiring, or no meaningful acceleration — for example a lift ratio under 1.1× when a prior baseline exists, or a weak new surge with only one recent hire.

How does lift map to confidence?

Lift at or above 2× scores 85, at or above 1.5× scores 75, at or above 1.1× scores 65, and other cases that still write score 55.

How is Velocity different from Hiring?

Hiring is the BASE fact that seats opened. Velocity is the COMPUTED story that those AI-qualifying seats are accelerating versus the prior window.

Hiring velocity

COMPUTED

AI hiring acceleration, last 30 days vs the prior 30.

As Hiring accumulates, VeilStrat computes whether AI-qualifying hiring is speeding up — one live Velocity row per company, refreshed as the windows move, skipped when lift is weak or empty.

Computed only from previous Hiring signals
Compares recent 30d AI hiring vs prior 30d
Lift bands map to confidence (1.1× → 2×+)
Weak or empty acceleration does not ship a row

Get this week's buyer list Read the API docs

Sample signalCOMPUTED

Velocity · 2.5× AI hiring lift

Last 30d vs prior 30d · sample

Prior 30d

AI hiring rows

Last 30d

AI hiring rows

Lift · confidence2.5× · 85

Weak or empty acceleration does not ship a row

COMPUTED

Role

30d vs 30d

Compare

≥1.1×

Lift gate

At a glance

How this signal shows up in the store

COMPUTED

Built only from prior Hiring signals

2×30d

Recent window vs prior window

1 row

One live Velocity row per company

55–85

Confidence from lift ratio bands

What it is

Pace of AI hiring — not just headcount

Hiring velocity is a COMPUTED signal asking whether AI-qualifying hiring is accelerating for the company. It is built from prior Hiring rows over two adjacent 30-day windows — the same COMPUTED pattern as Tools, but measuring lift instead of catalog tools.

After Hiring is processed, Velocity recomputes. If there is no recent AI hiring, or no meaningful acceleration (for example ratio under 1.1× when a prior baseline exists, or a weak new surge with only one recent hire), no row ships. Otherwise one live company row is created or refreshed as windows move.

AI-qualifying Hiring uses role-family / confidence gates
Confidence follows lift: ≥2× → 85, ≥1.5× → 75, ≥1.1× → 65, else 55 when still written
Complementary to raw Hiring counts — explicitly about ramp

Signature story

Acceleration, not static headcount

Velocity compares AI-qualifying Hiring in the last 30 days to the prior 30 — one live company row when lift clears the gate.

Last 30 vs prior 30

Dual windows

Prior 30d

AI hiring rows

Last 30d

AI hiring rows

Lift · confidence2.5× · 85

Lift → confidence bands

≥ 2×85
≥ 1.5×75
≥ 1.1×65
Otherwise (if written)55

Skip when there is no recent AI hiring or meaningful acceleration.

How it forms

Same post-Hiring recompute as Tools

After Hiring is processed, Velocity recomputes from existing Hiring for the company — previous signals in, acceleration signal out.

1
Read two windows
Count AI-qualifying Hiring in the recent 30 days versus the prior 30 days using the same role-family and confidence gates that define AI-qualifying seats.
2
Gate weak cases
Skip if there is no recent AI hiring, or no meaningful acceleration — for example ratio under 1.1× when a baseline exists, or a weak new surge with only one recent hire.
3
Create or refresh
One live Velocity row per company — created if missing, refreshed as the dual windows slide forward.
4
Score from lift
Confidence follows lift ratio bands from 55 up through 85 so stronger ramps read as stronger timeline facts.

Confidence

Based on lift ratio

Stronger acceleration versus the prior window earns higher write-time confidence.

BandConfidenceNote

≥ 2× lift85—
≥ 1.5× lift75—
≥ 1.1× lift65—
Otherwise (when still written)55e.g. new surge cases that clear the gate

Stock vs flow

Velocity vs static headcount growth charts

Headcount charts lag and blur AI seats into total hiring. Velocity isolates AI-qualifying Hiring and asks whether the pace is up.

Layer

Traditional

VeilStrat

Metric

What you measure

Total headcount delta

AI seats get lost in the average

AI-qualifying Hiring lift

Recent 30d vs prior 30d

Source

Evidence

HRIS export months later

Too late for outbound timing

Prior Hiring signals

Recomputed after Hiring writes

Gate

What ships

Any upward tick

Noise looks like momentum

Meaningful acceleration only

Weak lift does not ship a row

Unit

Storage

Spreadsheet series

No shared timeline identity

One live company row

Updated as windows move

Metric

What you measure

Traditional

Total headcount delta

AI seats get lost in the average

VeilStrat

AI-qualifying Hiring lift

Recent 30d vs prior 30d

Source

Evidence

Traditional

HRIS export months later

Too late for outbound timing

VeilStrat

Prior Hiring signals

Recomputed after Hiring writes

Gate

What ships

Traditional

Any upward tick

Noise looks like momentum

VeilStrat

Meaningful acceleration only

Weak lift does not ship a row

Unit

Storage

Traditional

Spreadsheet series

No shared timeline identity

VeilStrat

One live company row

Updated as windows move

Example snapshots

What a Velocity row looks like

Illustrative lift — real rows carry window counts, ratio, and confidence.

Strong ramp

Velocity · 2.5× AI hiring lift

Five AI-qualifying Hiring rows in the last 30 days versus two in the prior 30.

Lift ≥2× · Confidence 85 · One live company row

Moderate ramp

Velocity · 1.4× lift

Clear acceleration that clears the 1.1× gate without reaching 1.5×.

Lift ≥1.1× · Confidence 65

No ship

Flat AI hiring — no Velocity row

Recent window exists but lift stays under the meaningful acceleration gate.

Skipped · No timeline write

GTM moments

Who is ramping AI seats now

Use Velocity when acceleration matters more than raw opening count.

Prioritize

Rank accounts by ramp, not headcount

Put teams accelerating AI hiring above accounts with flat but large opening volume.

Timing

Enter while the team is still expanding

Live rows refresh as windows move — closer to the ramp than annual surveys.

Qualify

Separate surge from noise

Weak lift never ships, so lists stay focused on meaningful acceleration.

Pair

One live company row

Velocity is not a new vendor event — it is derived from Hiring over time. One row per company stays live and updates as the dual windows slide forward. If acceleration is missing or weak, VeilStrat simply does not write the row.

Related signals

How this connects on the timeline

Who is ramping AI seats now — explore the signals that feed or follow this type.

FAQ

Hiring velocity, answered

How dual windows, lift gates, and confidence bands work.

It is a COMPUTED timeline row that measures whether AI-qualifying Hiring is accelerating by comparing the last 30 days to the prior 30 days — one live row per company when the gate clears.

Find teams that areaccelerating AI hiring.

Velocity signals compare the last 30 days to the prior 30 — so you chase ramp, not static headcount.

Get this week's velocity signals Read the API docs

AI hiring acceleration, last 30 days vs the prior 30.

How this signal shows up in the store

Pace of AI hiring — not just headcount

Acceleration, not static headcount

Same post-Hiring recompute as Tools

Based on lift ratio

Velocity vs static headcount growth charts

What a Velocity row looks like

Velocity · 2.5× AI hiring lift

Velocity · 1.4× lift

Flat AI hiring — no Velocity row

Who is ramping AI seats now

Rank accounts by ramp, not headcount

Enter while the team is still expanding

Separate surge from noise

Read next to Hiring and Tools

One live company row

How this connects on the timeline

What is a Hiring velocity signal?

Where does the evidence come from?

When does Velocity not write a row?

How does lift map to confidence?

How is Velocity different from Hiring?

Find teams that areaccelerating AI hiring.