Time-to-hire: being in the first five packs is still a brutal edge

Why the first five profiles win: the cognitive mechanics

This is not a gut feeling from the field: it is primacy bias, documented in cognitive psychology. The first pieces of information received in an evaluation decision anchor the frame of reference. Everything that comes after is compared to the first elements, unconsciously.

An excellent candidate presented in tenth position is judged against those who came before, not on absolute merit. The human brain works this way: it builds a yardstick from the earliest available data, then measures what follows against that yardstick.

The effect amplified in an ESN context

In ESN recruitment, this bias is reinforced by three cumulative factors:

• The buyer’s cognitive load: a technical lead or project manager who receives fifteen packs for an open role will not run fifteen full evaluations. They form a mental shortlist after the first four or five profiles that tick the minimum boxes.
• Schedule pressure: the need exists because a project is starting or a departure has left a gap. Every day of delay has a cost. The buyer has a rational interest in closing quickly, not in waiting for the perfect candidate.
• Contrast effect: when the first profiles are good enough, the sixth must be clearly better to justify reopening the comparison. The bar rises without anyone having formally decided it.

The numbers that frame reality

Figures vary by source and sector, but the pattern repeats:

These numbers do not say talent does not matter. They say talent needs to arrive on time to be seen.

---

What slows you down without being measured

Most ESNs do not measure their actual delay between “CV received or identified” and “profile sent to client.” If you do it on ten recent cases, you will likely find two things: a longer average than expected, and a large standard deviation between consultants.

The seven invisible frictions

Here are the slowdowns you see almost everywhere, none is serious on its own, but stacked on a busy day, they push you out of the favorable window.

1. Hunt for the logo or brand guidelines: the salesperson knows the client wants a “clean” pack, but the source file lives in a poorly organized shared folder, or the latest version of the guidelines was not distributed.

2. Copy-paste from old packs: the classic reflex. You take an old Word pack for the same consultant, change dates, update assignments. Except you leave in an outdated reference, a job title that has changed, or a confidential project that should not still be there.

3. Waiting for internal sign-off: the template is not locked, or the manager wants to review before send. On paper, that is quality control. In practice, it is 24 to 48 hours of latency when the manager is in meetings or on something else.

4. Chasing the candidate for missing information: the database did not hold the certification, the real availability date, or the updated day rate. One follow-up email, a reply the next day, and the pack slips a day.

5. Manual reformatting: moving from one format to another (Word to PDF, adaptation for a client who wants a specific layout). That takes between 20 minutes and 2 hours depending on complexity.

6. Hesitation on what to highlight: which project to mention first? Should you detail that 2019 assignment or summarize? Without clear guidelines, each salesperson decides differently, and thinking time adds up.

7. Versioning issues: the consultant emailed an updated CV three weeks ago, but nobody imported it into the tool. The salesperson works from an obsolete version without knowing it.

The real cumulative cost

Take a concrete case. An ESN with 80 consultants and 5 salespeople, each handling 3 to 4 requests per week.

Twenty-two hours a week of work that creates no commercial value. Roughly half a headcount spent only on document friction.

---

Speed does not oppose quality: if the foundation is sound

The classic mistake is to treat speed and rigor as a trade-off. “We go fast, so we make mistakes” or “we are rigorous, so we are slow.” That only holds if your document base is a construction site.

The real speed factor: the state of your data

A pack sent in two hours from a profile that is clean, structured, and up to date is objectively better than a pack sent in ten hours with the same information pulled by hand from five different sources. Speed does not come from cutting corners, it comes from not having to rebuild.

In practice, the difference rests on three conditions:

• Consultant data is current: availability, day rate, latest assignments, certifications. No need to chase.
• Format is already defined: approved template, brand applied, consistent layout. No need to reformat.
• History is usable: past missions documented with the right keywords, tech stack, contexts. No need to dig through email.

When these three are in place, the salesperson’s work focuses on what actually matters: framing the mission. Why this profile for this specific need. Which differentiator to lead with. Which risk to anticipate and how to present it.

What faster teams do differently

Watching ESNs that regularly place among the first profiles sent, you see common patterns:

• A single source of truth per consultant: no CVs in email, no Word version on the salesperson’s desktop, no Excel sheet on the side. One maintained source.
• Locked templates: the salesperson does not choose layout. They choose content. Format is standardized, which removes variability and formatting time.
• A structured import process: when a new CV arrives (LinkedIn, PDF, Word), it is integrated into the base in a usable form, not just stored as an attachment.
• Adaptation by mission, not by client: instead of rebuilding a full pack for every send, you adapt the existing pack to the mission context: emphasize a given skill, reorder experience, tweak the summary.

---

Anatomy of a pack that arrives on time, and converts

Being in the first five is not enough if the pack is hollow. The goal is to be both fast and relevant. Here is what a pack that makes the shortlist contains.

The structure that works

What makes the content stand out

The summary is not a bio. It is a pitch tailored to the need. “Java/Spring developer, 7 years’ experience including 4 in banking, focused on legacy IS modernization” speaks to the reader. “Passionate about new technologies with solid experience” says nothing.

Assignments are contextualized. Not just “Developer at X for 18 months.” But: “Pricing engine overhaul, team of 6, Spring Boot 2 to 3 migration, batch processing time cut from 4h to 45 min.” The reader sees context, role, and impact.

Skills are prioritized. The client wants Kubernetes? Kubernetes comes first, not buried between “Microsoft Office” and “Agile methods.”

---

The “perfect profile” trap: why waiting costs more than sending

A common reflex among ESN salespeople is to hold a profile back because one detail is missing. The certification is not up to date. Experience on a given framework is 2 years instead of 3. The day rate was not reconfirmed this week.

The rational calculation

Two scenarios:

• Scenario A: you send a 90% fit profile within 24h. A minor detail is missing. You flag it in the send email (“AWS certification renewal in progress, expected date: June”).
• Scenario B: you wait 72h for the “complete” profile. In the meantime, three other ESNs have sent their candidates. The client already has a shortlist.

In scenario A, you are still in the race. The missing detail is rarely disqualifying if the rest of the profile is strong. In scenario B, you have a perfect pack nobody will read because the decision is already forming.

The 80/20 rule applied to staffing

• 80% of pack content can stay ready at all times if your base is maintained
• The remaining 20% is mission-context adaptation: that is the only work that should take time
• If the 80% takes you as long as the 20%, your problem is structural, not situational

---

Building a systematic responsiveness process

Lasting speed is not a one-off heroic push. It is a system. Here is how to build it step by step.

Step 1: Measure the current state

Take your last ten profile sends. For each, note:

• Date the need was received / identified
• Date the pack was sent to the client
• Who handled it
• Outcome (shortlist, interview, placement, rejection)

Compute average delay and the gap between fastest and slowest. If that gap exceeds a factor of two on comparable missions, the problem is not individual, it is systemic.

Step 2: Identify bottlenecks

Rank delay causes by frequency:

Step 3: Standardize the foundation

• Define one single template approved by sales leadership. One. Not three variants.
• Create a standard consultant sheet with mandatory fields: stack, seniority, sectors, availability, day rate, 3 key missions.
• Run a quarterly review of sheets, the consultant validates their info, the salesperson checks consistency.

Step 4: Automate what can be automated

Importing data from a CV (PDF, Word, LinkedIn) into a structured format does not have to be manual. Tools like Betterfolio can parse a CV, structure the data, and generate a pack aligned with your brand in minutes instead of hours.

What stays human, and should, is profile choice, positioning angle, and client relationship.

Step 5: Track metrics over time

Two indicators are enough to steer:

• Median delay CV→send (the median is more telling than the mean; it resists outliers)
• Shortlist rate by delay band (sent within 24h vs 48h vs 72h+)

If you see a correlation between speed and shortlist rate, and you will, you have your case to invest in the process.

---

Classic objections, and why they do not hold

“Our clients are not in a hurry; they take their time”

Maybe. But even a client who “takes their time” forms a first impression from the first packs received. Primacy bias works regardless of the official timeline. And when the client suddenly accelerates, which happens often, those who sent early are already in play.

“We prefer to send fewer but better”

False opposition. Sending fast and well is possible when the base is clean. Slowness is not a guarantee of quality: it is often the symptom of a disorganized process that burns time on low-value tasks.

“Our salespeople know their consultants; they do not need a tool”

Individual knowledge does not scale. When a salesperson is away, ill, or overloaded, their knowledge goes with them. A shared repository ensures any team member can send a quality pack for any consultant in the pool.

“The client cares about price, not speed”

Price matters, obviously. But at comparable day rates (and among similar-sized ESNs, rates often sit in the same band) pack quality and response speed make the difference. The first relevant profile received has a structural edge over the fifth, even at the same price.

---

The metric to put in place this week

You do not need a transformation program. Start with one concrete action: measure your CV→send delay over the last thirty days.

Build a simple table:

Run the numbers. Look at the correlation between delay and outcome. If the pattern holds, and it will, you have the factual basis to prioritize reducing your time-to-hire.

The lever is not hiring better. It is presenting faster what you already have. Most ESNs already have the right profiles in their pool. The problem is the time between identified need and sent pack. Shrink that time, and your shortlist rates will follow.