The market answer, before the plan is signed
A landscape is the layer above a candidate list: how many people, at what price, against how much competition, and how long it will really take.
$100 of credits on us. No card required.
Four things that decide whether the plan holds
Supply at your bar
Not the total population. The people who would pass your loop, which is usually a fraction of what a job board suggests.
Comp reality
What the same brief is advertised and closed at in that market, so the budget conversation happens before the offer stage.
Competition
Who else is chasing these people, how aggressively, and what they are offering that you are not.
Honest time to hire
Weeks, from the shape of the pool and your own historical loop speed. Not a benchmark from someone else's company.
Roles rarely fail because the sourcing was lazy. They fail because the brief, the budget and the timeline never agreed with each other.
One job, learned properly
I do recruiting and nothing else. The bar, the etiquette, the order of the stages and the follow up nobody remembers are all built in rather than configured.
Most tools query the same three databases. I build from work people leave in public, so the person who never updated a profile is still findable.
Nobody lists that they carried a migration or ran the on call rotation. I infer it from the work and then check it.
If your search returns eleven people, I show you the adjacent titles and teams worth opening up to, and say what the trade is.
Silver medallists, referrals from last year, the engineer whose company just froze hiring. I keep watching so you do not restart from zero.
What people ask about market intelligence
Where does the comp data come from?
Advertised ranges for the same brief in the same market, plus what candidates in your own pipelines said they were on. I show the spread rather than one confident number.
Is the time to hire a benchmark from other companies?
No. It combines the shape of the pool with how fast your own loop has moved historically, which is the part generic benchmarks always get wrong.
Can I use this to defend a headcount request?
That is one of the most common uses. You get the pool count, the comp reality and the competition in a paragraph you can paste into the doc.
Ask me what your budget actually buys
Supply, comp and a realistic number of weeks.