Betterfolio
Betterfolio team
A shortlist of 3 profiles at an ESN: structure, order and what the buyer reads in 30 seconds
A strong consultant can lose because the shortlist is poorly put together. How to choose, order and present 2 to 3 competency dossiers so they hold up to a reading of a few dozen seconds.
In short
A shortlist of three profiles is read as a single document. The buyer does not judge each dossier on its own. They skim the whole set, retain an order, a logic and a consistency of format, then decide who to call. Relevant profiles presented in the wrong order or in different formats lose to a more modest but readable shortlist.
- IT recruitment players put the first screening of a dossier between 20 and 45 seconds. These are orders of magnitude taken from vendor content, not Betterfolio measurements: check them with your own buyers.
- What the buyer reads in that time: the summary at the top, the requested skills, the first mission, a certification if any. The rest is read only if the opening has convinced them.
- A shortlist of three is ordered like this: the must-fit profile first, the alternative second, the differentiating profile third, with a sentence from the Business Manager explaining the choice.
- When the client compares several ESNs, consistency (same template, same structure) and relevance (few, well-targeted profiles) weigh more than volume.
- Pushing, meaning sending unqualified generic dossiers, tires the buyer and damages the ESN's credibility on later requests.
Why you lose even when the profile is good
Many lost missions are not lost on the consultant's skills. They are lost on what the buyer saw in the first seconds, and on how the three dossiers answer one another.
Three situations Business Managers recognise
- The right profile is buried. The consultant matches the need, but the dossier opens on a generic career summary and the missions are listed from most recent to oldest. The mission that is actually relevant appears on page 2.
- The three dossiers do not look alike. A different template, job titles that change from one profile to the next, an uneven level of detail. The buyer concludes that the industrialisation work is only partial, and extrapolates to the service itself.
- The shortlist does not say why these three. Three dossiers arrive as attachments with no explanation. The buyer has to rebuild the logic alone, or does not try.
The cost of pushing
Pushing means sending large volumes of unqualified dossiers in the hope that one will land. Turnover-IT, in an article on the competency dossier, lists it among the practices that destroy an ESN's credibility: three profiles pushed of which only one is vaguely relevant, or a dossier arriving minutes after a tender is published, signal that no qualification took place. Conversely, sector players advise buyers to judge the quality of the first send: a few well-targeted profiles are worth more than a pile of approximate dossiers.
The consequence is measured at account level, not mission level. A buyer who receives off-target dossiers twice in a row reads the next ones faster and with less goodwill.
What the buyer really reads in 30 seconds
A time frame to handle with care
Two vendor sources give an order of magnitude. Turnover-IT writes that the buyer knows within 20 seconds whether to keep reading or move on to the next dossier. Cobalt mentions 45 seconds to decide whether a profile goes to interview. These figures are business angles, not study results. The "30 seconds" in this article is a working benchmark between the two. The most useful thing is to test it: ask two buyers or two business units to skim one of your dossiers for 30 seconds, then say what they retained.
What is read, and in what order
| Dossier zone | What the buyer looks for | What moves them forward | What makes them drop off |
|---|---|---|---|
| Title and headline | The right job, the right level | A title aligned with the tender | A generic title ("senior consultant") |
| Summary (3 to 5 lines) | An answer to their need, not a biography | Specialty, comparable context, result | A sentence of years of experience with no object |
| Skills | Their keywords, at the top | 6 to 8 skills ranked by relevance | A list of 25 technologies with no hierarchy |
| First visible mission | A situation close to theirs | Context, role, result | A recent mission with no connection |
| Certifications and rare assets | Verifiable risk reduction | Visible at the top of the page | Buried on the last page |
| Soft skills | Evidence of working in a team | One situation illustrated in a sentence | Adjectives with no facts |
| Overall form | A polished document | Same template and structure across all three dossiers | Two fonts, an approximate header |
The buyer does not read less because they are in a hurry. They read by zones, and each zone must answer a precise question.
Anatomy of a dossier that passes the scan
- A summary of 3 to 5 lines focused on project value. Turnover-IT recommends replacing "senior consultant with 12 years of Java experience" with a sentence that names the type of project delivered, the specialty and the team scale.
- Ranked skills: those from the tender first, in the tender's words, then complementary skills.
- Missions written in STAR (situation, task, action, result), the most relevant mission first rather than the most recent.
- Certifications useful to the need, not every certification.
- Soft skills illustrated by a fact: "led architecture reviews with three vendor teams" rather than "good communicator".
Building the shortlist of three
How many dossiers to send
Two to three. A single dossier leaves the buyer with nothing to compare, which prompts them to ask for other profiles. More than three shifts the sorting work onto them, which is exactly what the ESN should do in their place. Some ESNs even state that they propose the right person rather than five CVs between which the client must decide alone. When the need is very precise, a shortlist of two solid dossiers is better than three of which one is weak.
The three roles
| Rank | Role | Question it answers | Selection criterion |
|---|---|---|---|
| #1 | Must-fit | "This one does exactly what I asked" | Maximum coverage of the knockout criteria, recent comparable mission, confirmed availability |
| #2 | Alternative | "What if the first one does not suit?" | Good coverage with a different background (other sector, other seniority), at the same level of reliability |
| #3 | Differentiating | "What had I not considered?" | An asset the first two lack (regulated domain, language, rare certification, team leadership experience) |
The third profile is not filler. If it brings nothing distinct, a shortlist of two is better.
An example of composition
Fictional need: a Java back-end developer for an insurer, with a migration to an event-driven architecture.
- #1 Must-fit: a consultant who led a comparable migration at an insurer, identical stack, available on the requested date.
- #2 Alternative: a consultant from banking, same stack, shorter migration experience but strong autonomy on architecture.
- #3 Differentiating: a consultant less close on the sector, but holding a cloud certification requested as an option and used to supervising a team of junior developers.
Each profile answers a different question. The buyer can arbitrate between three logics, not between three variants of the same CV.
Order and packaging
Order is a message
The buyer reads the first dossier with the most attention, then compares the next ones to it. The first dossier therefore sets the reference. Placing the strongest profile third, out of caution or habit, means it faces the test after two readings that are already tiring.
One template for all three dossiers
On a shortlist that circulates between several ESNs, visual and structural consistency counts for more than people think, as Turnover-IT points out. An approximate header or two fonts signal an industrialisation flaw that the buyer may apply to the rest of the service. In practice:
- same template, same blocks, same section order from one dossier to the next
- same level of detail for missions
- harmonised job titles
- availability and mobility in the same place, in the same form
Adapt without rewriting
Standardisation applies to the structure. The content changes with every send: summary rephrased, skills reordered according to the tender, the mission closest to the need placed first. It is the same logic as for a tender response: industrialise the process, do not make the profiles uniform.
Checklist before sending
On each dossier
- The summary fits in 3 to 5 lines and names a context comparable to the need
- The tender's skills appear at the top, in its own terms
- The most relevant mission comes first, written in STAR
- Certifications and rare assets are visible without turning the page
- Soft skills are backed by a fact
- Availability is confirmed with the consultant
On the shortlist
- Each profile plays a distinct role (must-fit, alternative, differentiating)
- The must-fit comes first
- The three dossiers share the same template, structure and job titles
- No dossier contradicts another (availability, format, vocabulary)
- The three dossiers have been proofread by someone who did not write them
Supporting the send: the Business Manager note
Three dossiers with no comment leave the buyer alone with an interpretation task. A short BM note in the body of the email replaces an oral explanation that nobody will have time to ask for.
The content of a good note
- One sentence per profile, saying how it answers the need
- The overall logic: why these three and not others
- A concrete invitation: availability for a call, a proposed slot
Example note (fictional need)
Hello [First name],
Here are three profiles for the event-driven migration of your claims platform.
1. [First name L.]: led a comparable migration at an insurer, available from the 1st of the month. This is the profile that covers the most of your criteria.
2. [First name L.]: banking background, same stack, very autonomous on architecture. An alternative if you want a perspective from outside the sector.
3. [First name L.]: less close on the sector, but cloud-certified and used to leading a team. To consider if you want a technical lead as well as delivery.
We remain available for a call with any of the consultants this week.
The note stays short. It does not argue the price, does not repeat the dossiers and contains no superlatives. Its only purpose is to make the logic visible.
What to avoid in the note
- Summarising the dossiers instead of explaining the choice
- Ranking without saying so (the order must stay consistent with the text)
- Promising availability that is not confirmed, a risk that ESN proposal guides also point out
Common mistakes
| Mistake | What the buyer infers | Fix |
|---|---|---|
| Generic competency dossier | The ESN has not read the need | Reorder summary, skills and missions from the tender |
| Empty summary ("motivated consultant, 10 years of experience") | Nothing to retain in 20 seconds | 3 to 5 lines: specialty, context, result, target role |
| Missions in chronological order | The relevant mission is hidden | Rank by relevance, the one closest to the need first |
| Tender skills missing from the top of the page | The profile does not match, or was not prepared | Reuse the tender's terms in the first lines |
| Three profiles that look alike | No choice to make, so no reason to select | Give each profile a distinct role |
| Three dossiers in different formats | An industrialisation flaw | One template for the whole shortlist |
| Shortlist sent without a note | The logic has to be rebuilt | A BM note of a few lines |
| Push: unqualified or immediate send | No qualification upstream | Few, targeted dossiers, sent after reading the need |
Frequently asked questions
How many profiles should an ESN shortlist contain?
Two to three dossiers are enough in most cases. A single dossier allows no comparison, and more than three shifts the sorting work onto the buyer. If the need is very precise and the third available profile is weak, two solid dossiers are better than three.
In what order should three competency dossiers be presented?
The profile that best covers the need's criteria goes first, because it serves as the reference for the others. Second place goes to a credible alternative with a different background. Third place hosts a differentiating profile that brings an asset absent from the other two. A sentence from the Business Manager explains this logic.
How much time does a buyer spend on a competency dossier?
There is no universal figure. IT recruitment players put a first screening at around 20 seconds (Turnover-IT) to 45 seconds (Cobalt), but these are orders of magnitude from vendor content, not validated measurements. The most reliable approach is to test your dossiers with a few buyers or business units and note what they retain after a timed reading.
What should come first in a competency dossier?
A summary of 3 to 5 lines focused on project value, followed by the skills requested in the tender, ranked by relevance. The mission closest to the need comes next, written as situation, task, action, result. Certifications useful to the need appear at the top of the page rather than in an appendix.
What should be done when the client compares several ESNs?
Take care over the consistency between dossiers (template, structure, vocabulary) and the relevance of the profiles chosen. A client receiving several shortlists compares both the profiles and the seriousness of the preparation. A dossier poorly aligned with the template, or an obviously unqualified send, weighs on the credibility of the whole ESN.
Should a note be sent with the shortlist?
Yes. A few lines from the Business Manager are enough: one sentence per profile, the overall logic, a proposal for a call. This note spares the buyer from rebuilding the reasoning, and lets the ESN guide the reading without pleading.
Key takeaways
A shortlist is won before the interview, in the first few dozen seconds of reading. The buyer compares dossiers with one another, not with an ideal grid. They retain the one whose logic is readable.
Four reflexes for building a shortlist that passes the scan:
- Reorder each dossier from the need: summary, tender skills at the top, most relevant mission first.
- Give each profile a role: must-fit, alternative, differentiating. Two solid dossiers are better than three of which one is filler.
- Unify the form: same template, same structure, same job titles across all dossiers.
- Accompany the send with a BM note of a few lines explaining why these profiles, in this order.
Adapting three dossiers to a need takes time, and that is often the time missing when the tender arrives. Betterfolio is there to narrow that gap: a stable dossier base per consultant, versions adapted to each need, and a history of sent dossiers to keep a shortlist consistent from one account to the next. Choosing the three profiles and writing the accompanying note remain the Business Manager's work.
Sources
- Turnover-IT, Dossier de compétences : l'arme commerciale qui décide vos missions ESN, May 2026
- Cobalt, Dossier de compétences : 7 erreurs qui font perdre des missions
- HumanCraft, Comment évaluer rapidement une ESN
- Offry, Proposition commerciale ESN : exemple 2026
- Voxalia, Appel d'offres ESN : les attentes des DSI en 2026
- Négosphère, Dossier de compétences : structure, modèle et conseils pour convaincre
Read next
GEO and AEO for IT services firms: appearing in ChatGPT, Perplexity and Copilot answers
Definitions, AI crawlers, page and competency dossier structure, a 30-day measurement plan. What an IT services firm can control, and what no provider can promise.
Betterfolio vs Showcase (DoYouBuzz) vs Middleman: which tool for your IT services firm in 2026?
A comparison of the three French competency portfolio tools. BoondManager integration, real day-to-day adoption by managers, candidate qualification and pricing models: what actually matters when you choose.
The first 30 days on mission: securing the placement after the signature
A signed contract isn't the end of the sales cycle. Most missions that end early are decided in the first month. An onboarding protocol that protects margin and the client relationship.
