The published band and the closed offer are two different numbers
One is written by people not running mandates. The other is what the candidate actually signs. Only one of them should set your budget.
Draft. Figures marked like this are illustrative and pending verification against Recruise placement data & Sachith sign-off before publication.
Key takeaways
- The published band and the closed offer diverge because they are written by different people, for different purposes — one describes a market, the other closes a person.
- Survey bands lag the mandates that move them; by the time a figure is published, the roles that set it have already re-priced.
- Budget against what candidates in your segment are actually signing, not the aggregate — the aggregate is a rear-view mirror wearing a lab coat.
A band is a description of the market. An offer is a decision about a person.
The published band is assembled by people who are not, at that moment, trying to close anyone. It smooths thousands of data points into a range that is true on average and precise about no one. The closed offer is the opposite: it is the single number that moved one specific candidate, with one specific alternative in hand, on one specific Tuesday. The two are not versions of the same fact. They answer different questions, and only one of them signs.
This matters most in the senior AI, data and IT roles where the interesting hires live above the median by definition. When a committee anchors its budget to a published midpoint, it is budgeting for a candidate who, almost by construction, isn’t the one they want. The person worth chasing is already being quoted numbers the survey hasn’t seen.
“The band tells you where the market was. The offer tells you what it costs to move the person in front of you. Confuse the two and you lose slowly, one great candidate at a time.”
Sachith Rai · MD & Founder, Recruise
The lag is structural, and it always favours the roles that are moving.
By the time a range is compiled, checked and published, the mandates that pushed it have already closed at numbers the compilation never captured. In a steady segment that lag is harmless. In a segment that is re-pricing — which is most of the ones a GCC actually competes in — the lag runs in exactly the direction that hurts you. Roughly a quarter or two of drift, all of it on the roles you can least afford to under-price.
The fix is not to abandon benchmarks. It is to read them as a floor and a starting point, then correct upward with live signal from the offers your own mandates are producing. The band sets the conversation; the closed offer ends it. Only one of them should set your budget.
One pattern worth knowing, every week.
The Signal is our weekly read on the senior GCC talent market — one chart, one pattern, no noise. Written from live placement data.
More from Recruise Insights.
The AI/ML salary band just snapped in two
The top of band hasn't moved — it has split. Two markets now operate side by side, and most benchmarks still price them as one.
The hidden cost of paying at the 75th percentile
It sounds defensible. It’s also why your offer-accept rate is slipping. The real benchmark isn’t where you think.
The AI/ML band didn’t shift — it split in two
Traditional ML sits where it was a year ago. The GenAI end has pulled away. Price them as one band and you lose the top while over-paying the bottom.