Guides

Job-Posting Velocity as a Standalone BD Signal: Reading Volume Spikes Before They Become RFPs

A sudden spike in a company's job-posting volume is its own BD signal, distinct from funding, layoffs or exec moves. Learn how to read velocity spikes and win the desk before the formal search forms.

TB Team Boilr

· July 13, 2026 · 15 min read

Abstract dark liquid-metal texture representing a rising volume signal

TL;DR

Most recruitment BD teams treat a single job ad as the signal. It isn't. The signal is the rate of change in how many roles a company is posting - its job-posting velocity. Companies that increase postings by 30%+ in a quarter are 2.4x more likely to make a new purchase decision the following quarter [2], and 73% of job openings go live within 30 days of budget approval [2]. That means a velocity spike is visible on the desk before the hiring manager has briefed a preferred supplier list, let alone issued an RFP - the formal buying process for recruitment services typically takes 4-8 weeks from planning to signed contract [6]. Agencies that track 7/30/90-day posting deltas instead of individual ads reach the account whilst the campaign is still forming. boilr.ai tracks hiring velocity as a distinct signal type alongside funding, exec moves and expansions, scoring it against your ICP and surfacing the account before the job boards fill up with competing agency outreach.

Why a Single Job Ad Is the Wrong Unit of Signal

Most BD workflows are still built around the individual job ad: a recruiter sees one posting, checks if it matches a desk, and reaches out. That approach misses the actual signal, which sits one level up.

One ad is noise; a cluster is intent. A single posting could be a backfill, a re-post, or a role that's been open for months. A company posting five roles in the same function within two weeks signals compressed urgency and real headcount commitment, not routine replacement [1].
Volume without velocity is misleading. Raw posting counts rise and fall with seasonality and market noise. Velocity - the percentage change in postings over a defined window - strips that out and shows whether a company's hiring is actually accelerating [7].
By the time you see one ad, others already have. A posting on a major job board is visible to every agency and every in-house recruiter simultaneously. There is no first-mover advantage left in reacting to a single listing.
Budget moves before the req goes live. 73% of job openings are posted within 30 days of a company approving new budget allocation [2]. The posting is a lagging confirmation of a decision, not the decision itself - which is exactly why the pattern across postings (the velocity) carries more information than any one of them.
High volume can mean a hard-to-fill market, not a healthy one. London job postings rose from 583,000 in Q4 2025 to 748,000 in Q1 2026 [4]. Reading that jump correctly - plenty of open roles, not enough of the right candidates - is a different BD conversation than "they're growing fast," and it changes the pitch you lead with.

This is not the same signal as a funding round, a layoff, an executive hire, an office expansion or a PE acquisition. Those are event-based triggers tied to a single, discrete announcement. Job-posting velocity is a continuous, self-reported behavioural signal - it comes directly from the company's own hiring activity, updates weekly, and often moves before any of those other events are publicly known at all.

What Job-Posting Velocity Actually Measures

Velocity is not "how many roles are open." It is the rate of change in open roles over a rolling window, usually tracked across 7, 30 and 90-day periods across large company datasets [7]. The framework has three layers:

Layer 1: The Delta

The core number is a percentage change: postings this period vs. the prior comparable period. A company moving from 4 open roles to 11 in 30 days is a +175% delta - a very different signal from a company holding steady at 40 open roles, even though the second company has more total postings.

Layer 2: The Cluster

Velocity means more when the new postings share a function, level or location. Five engineering roles opening in two weeks signals a product or platform investment; five roles split across sales, CS and marketing signals a go-to-market push [5]. A scattered mix of one-off roles across unrelated departments is weaker evidence of a coordinated campaign than a tight cluster.

Layer 3: The Duration and Repost Pattern

How long a role stays live, and whether it gets reposted or re-worded, tells you whether the company is struggling to fill it (a "hard to fill" signal, often meaning they'll consider outside help) or simply working through a planned pipeline of approvals (a "fast-moving campaign" signal, meaning speed matters more than search depth to them right now). Both are BD-relevant, but they call for a different pitch.

Where the Underlying Data Comes From

You don't need a single perfect source - velocity is more reliable when it's corroborated across several:

Major job boards (Indeed, LinkedIn Jobs, Otta) - broadest coverage, but posting delays vary by board
Company careers pages - often the first place a role appears, before it syndicates elsewhere
ATS-embedded feeds (Greenhouse, Lever, Workday career sites) - structured, timestamped, easy to diff over time
Aggregators and job-data APIs - useful for tracking volume at scale across thousands of companies at once
Signal platforms with recruitment context (boilr.ai) - combine posting data with ICP scoring and other signal types so velocity isn't read in isolation

The Velocity-to-RFP Timeline

The reason velocity is worth tracking as its own signal is timing. A formal, budgeted, multi-role hiring campaign does not appear instantly - it moves through a predictable sequence, and job-posting velocity is visible earlier in that sequence than almost anything else an outside recruiter can observe.

Stage	What's happening internally	Externally visible?	Typical window
Budget approved	Headcount signed off, often tied to a funding event, quarter plan or expansion decision	Rarely	Day 0
First reqs open internally	ATS records created, hiring managers briefed, internal sourcing starts	No	Days 1-14
Postings go live (velocity spike)	Roles publish to job boards and careers page in a cluster	Yes - this is the signal	Within 30 days of budget approval [2]
Internal + inbound pipeline runs dry	Company realises internal sourcing and inbound won't cover the volume or seniority	Indirectly (postings stay open, get reposted)	Weeks 3-8
PSL brief / RFP forms	Preferred supplier list gets briefed, or a formal RFP is drafted for agency support	Only once issued	4-8 weeks from planning to signed contract [6]

Hiring signals in general reveal buying intent 60-90 days before a company begins formal vendor research [3]. A velocity spike sits right at the start of that window - it is the earliest externally visible checkpoint in the whole chain, well before the account has organised a formal search.

Manual Tracking vs Signal-Led Velocity Detection

Most agencies either watch job boards manually or don't watch volume at all - they wait for a single relevant ad to land in a saved search. Neither approach surfaces velocity.

Approach	What it catches	What it misses	Time cost
Saved job-board search / alert	Individual ads matching keywords	Rate of change, clustering, repost patterns, cross-board volume	Ongoing manual checking, 20-30 min/day
Manual spreadsheet tracking per account	Trend for a small hand-picked account list	Scale - can't track more than a handful of companies well	2-3 hrs/week per 10-15 accounts
Generic sales intent tools	Broad hiring surge as a "buying signal" for software	Recruitment-specific context: seniority mix, desk fit, department relevance	Subscription cost + manual interpretation
Signal-led BD layer (boilr.ai)	7/30/90-day velocity deltas across your ICP, scored and matched to desk fit	Nothing structural - still needs a human to make the call and send the outreach	Review time only, 5-20 min/day

Building a BD Play Around Velocity Spikes

Once you can see velocity, the play is different from a standard cold approach. You're not selling "we heard you're hiring" - you're selling early access to a campaign the company hasn't fully organised yet.

Set your ICP thresholds first. Decide what counts as a meaningful spike for your desk - e.g. +30% postings in 30 days, or 3+ roles in one function within 14 days. Thresholds should vary by company size; a spike of 3 roles means something very different at a 20-person startup than a 2,000-person enterprise.
Read the cluster before you write the email. Confirm the function, seniority mix and location pattern. "I noticed you've opened four backend engineering roles in the last two weeks" lands very differently to a generic "saw you're hiring."
Check duration and repost status. A role live for 45+ days or reposted with a wider title is a hard-to-fill signal - lead with search capability, not just speed.
Move before the RFP forms, not after. The whole value of catching velocity is reaching the hiring manager or Talent lead before a PSL brief or RFP formalises the process and adds procurement friction.
Corroborate, don't over-fit to one signal. Velocity is strongest combined with other context - does the cluster line up with a known funding round, a new office, or an executive hire? Signals that agree with each other are worth more than any single one [1].
Log the outcome back into your ICP. Which velocity thresholds actually converted to meetings? Feed that back so the next spike gets prioritised more accurately.

The 6 KPIs That Show a Velocity Play Is Working

Metric	Why it matters	Target
Spike-to-outreach time	How fast you reach the account after the velocity threshold triggers	<48 hours
Spike-to-first-reply rate	Response rate on velocity-triggered outreach vs cold outreach	8-12% (vs 2-3% cold)
False-positive rate	% of spikes that turn out to be re-posts, seasonal noise, or one-off backfills	<20%
Pre-RFP win rate	% of engaged accounts where you're talking to the hiring manager before a PSL/RFP forms	Track and grow quarter over quarter
Signal-to-brief conversion	% of velocity-flagged accounts that become an active mandate	10-15%
Cluster accuracy	% of flagged clusters that match your desk's specialism	>80%

How boilr Powers Velocity-Led BD

boilr.ai tracks hiring velocity as one of its core signal types - the platform's own examples include flagging companies with double-digit month-on-month velocity swings - alongside funding rounds, executive moves, expansions and other triggers, so a velocity spike is never read in isolation:

Signals - detects posting-volume changes across 10,000+ sources and flags the delta, not just the individual ad, corroborating it against other signal types on the same account where they overlap.
ICP scoring - your AI employee learns which industries, sizes, geographies and desk types matter to you, so it only surfaces the velocity spikes that fit your specialism, not every company hiring anywhere.
Companies - enriches the flagged account with firmographic and hiring-manager context so the cluster (function, seniority, location) is visible before you write anything.
Candidates - starts building a shortlist against the emerging role cluster, so you can speak to pipeline depth, not just intent, when you reach out.
Tasks - drafts outreach referencing the specific cluster and timing, ready for you to review, personalise and send within 5-20 minutes.
Company Brain - keeps a record of which velocity thresholds and cluster types actually convert for your agency, so the pattern survives even if the consultant who spotted it moves desks.

What stays human:

Deciding which spikes are worth a call versus noise for your specific desk
Writing the actual outreach voice and tone
The discovery call, qualifying the brief, and negotiating terms
Judging whether a hard-to-fill signal means "they need search help" or "the role is badly scoped"

5 Mistakes That Waste a Velocity Signal

Mistake #1: Treating Every Spike as a Hot Lead

Why it fails: Not every increase in postings is a coordinated campaign - seasonal hiring, batch reposting, and data noise all inflate raw counts.

Fix: Set a minimum threshold (e.g. 30%+ delta or 3+ roles in one function) and check the cluster before you reach out, not just the headline number.

Mistake #2: Ignoring Company Size in Your Thresholds

Why it fails: A flat percentage threshold overweights small companies (where 2 roles can look like a 100% jump) and underweights large ones (where a real campaign might only move the percentage a little).

Fix: Use size-adjusted thresholds - a minimum absolute number of roles alongside the percentage delta.

Mistake #3: Reaching Out Before Reading the Cluster

Why it fails: A generic "I see you're hiring" email on a velocity spike wastes the one advantage the signal gives you - specificity.

Fix: Reference the actual function, level and timing of the cluster in the first line.

Mistake #4: Waiting for the RFP to Respond

Why it fails: By the time a PSL brief or RFP is issued, procurement is involved, terms are set, and every competing agency on the list gets the same brief at the same time.

Fix: Move on the velocity spike itself, days or weeks before the formal process starts, when you can still shape the conversation directly with the hiring manager.

Mistake #5: Not Distinguishing Velocity From Other Signal Types

Why it fails: Folding velocity into a generic "hiring signal" bucket alongside funding news or exec moves means you lose the specific, timing-sensitive angle it offers.

Fix: Track velocity as its own signal category with its own thresholds and its own outreach template, then corroborate it with other signals when they line up.

Set Up a Velocity Play in 7 Days

Day 1-2: Define Thresholds

Set your velocity thresholds by company size (percentage delta + minimum role count) and decide which functions matter most to your desk.

Day 3: Choose Your Tracking Method

Option A: Manual job-board monitoring across your target accounts (time-intensive, hard to scale past 10-15 accounts). Option B: Automated velocity tracking (boilr.ai) across your full ICP.

Day 4: Build the Outreach Template

Draft a velocity-specific email and LinkedIn message referencing the cluster, not a generic "hiring" mention. Include a version for the "fast campaign" read and a version for the "hard to fill" read.

Day 5: Set Review Cadence

Decide how often you review flagged spikes (daily is standard for a live desk) and who on the team actions them.

Day 6: Run It on 10 Flagged Accounts

Send velocity-triggered outreach to 10 accounts. Track reply rate and note which cluster types respond best.

Day 7: Review and Refine Thresholds

Check which spikes converted to a conversation and which were false positives. Tighten your thresholds and template accordingly, then scale to your full target list.

Want to see velocity spikes on your own target accounts before the job boards fill up with competing agency outreach? Try boilr.ai free and let your AI sales employee flag the campaigns forming right now.

Frequently Asked Questions

What is job-posting velocity?

Job-posting velocity is the rate of change in a company's open roles over a defined window, usually measured across 7, 30 and 90-day periods [7]. It's a percentage delta, not a raw count - it tells you whether a company's hiring is accelerating, holding steady, or slowing down, which is more useful for BD timing than the total number of jobs live at any given moment.

How is job-posting velocity different from a hiring signal like funding or exec moves?

Funding rounds, layoffs, executive moves, office expansions and PE acquisitions are event-based signals tied to a single, discrete, usually publicly-announced event. Job-posting velocity is a continuous, self-reported behavioural signal that comes directly from the company's own recruiting activity and updates on a rolling basis. It often moves before any of those other events are publicly confirmed, and it can occur with no other trigger event at all.

How early does a velocity spike appear before a formal RFP?

Hiring signals broadly reveal buying intent 60-90 days before a company begins formal vendor research [3], and postings themselves typically go live within 30 days of budget being approved [2]. A recruitment RFP process then runs a further 4-8 weeks from planning to signed contract [6]. That puts a velocity spike weeks, sometimes months, ahead of any formal PSL brief or RFP.

What counts as a meaningful velocity spike?

There's no universal number, but useful starting thresholds are a 30%+ increase in postings within a 30-day window, or three or more roles opening in the same function within two weeks [1][2]. Thresholds should be adjusted for company size, since a small percentage jump at a large company can represent more real hiring than a large percentage jump at a five-person team.

Does a high volume of job postings always mean a company is growing?

No. Rising volume combined with roles that stay open a long time or get reposted often signals the opposite - a company that has plenty of budget and open roles but is struggling to find the right candidates [4]. That's still a strong BD opportunity, but the pitch should lead with search capability and candidate pipeline, not just speed.

Can I track job-posting velocity manually?

Yes for a small hand-picked account list, using saved job-board searches and a tracking spreadsheet, but it takes roughly 2-3 hours per week to maintain per 10-15 accounts and won't reliably catch clustering or repost patterns. Beyond a small target list, manual tracking cannot scale to a full ICP without an automated signal layer.

What should my outreach say when I spot a velocity spike?

Reference the specific cluster you've identified - function, approximate number of roles, and the time window - rather than a generic "I see you're hiring" line. If roles have stayed open a long time or been reposted, lead with your search and candidate-pipeline capability. If the cluster is fresh and moving fast, lead with speed and availability to start immediately.

How does boilr.ai detect job-posting velocity?

boilr.ai monitors hiring activity as one of its core signal types across 10,000+ sources, flagging companies where posting velocity accelerates and scoring the account against your ICP - industries, company sizes, geographies and desk specialisms - before enriching it with company and candidate context and drafting outreach for you to review and send.

Sources

Information sourced from public industry reports and vendor research as of July 2026.

Back to all articles