Recruitment Proposal

What a recruitment proposal is

A recruitment proposal is the document a recruitment agency or RPO provider gives a hiring company to win a search. It sets out which roles you will fill, how you will source and screen candidates, the timeline and service levels you commit to, what the engagement costs, and the guarantee you stand behind if a hire doesn't work out.

Unlike a generic sales pitch, a recruitment proposal lives or dies on specifics: the roles and volumes, the fee model, the replacement guarantee, and a time-to-hire commitment the client can hold you to. The clients who say "yes" fastest are the ones who can see exactly what they're paying for and what protects them if a placement falls through.

When to use one

Use a recruitment proposal after a briefing call, once you understand the client's open roles, target start dates, salary bands, and how they currently hire. Send it when you're asking for the search — whether that's a single contingency role, a multi-role retained campaign, or a full RPO arrangement. For an ongoing relationship, the accepted proposal is usually followed by a service agreement and, for project-based delivery, a statement of work per campaign.

Who uses it

Recruitment agencies, executive search firms, staffing companies, and RPO providers use these to win mandates. In-house talent teams sometimes adapt the format to scope an external partner. The structure holds across industries; what changes is the role detail, the sourcing channels, and the fee model that fits the seniority and volume of the hire.

Sections a recruitment proposal should include

Required

• Overview — the client's hiring goal in one short paragraph: how many roles, by when, and the headline commitment (e.g., "12 hires across two quarters, average 35 days to offer").
• Roles in scope — a table of each role, seniority, location/work model, target salary band, and volume. Vague briefs produce vague shortlists; this section forces precision.
• Sourcing approach — where the candidates will come from: active outreach, talent pools, referrals, job boards, niche communities. Show you'll reach passive candidates, not just inbound applicants.
• Screening process — the stages a candidate passes before you submit them: CV review, structured screen, skills/technical assessment, references, right-to-work checks.
• Timeline & SLAs — when the first shortlist lands, how many qualified candidates per role, response times, and a target time-to-hire. SLAs turn promises into commitments.
• Fee structure & terms — the model (contingency, retained, or RPO), the percentage or fixed fee, what triggers payment, and any retainer or monthly charge.
• Guarantee / replacement policy — the rebate or free-replacement terms if a hire leaves within a set window. This is the single biggest trust-builder in the document.
• Next steps — one clear action to start the search (countersign, pay a retainer, share the role briefs).

Optional but persuasive

• Track record — relevant placements, fill rates, or time-to-hire data for similar roles.
• Account team — the consultants who will run the search and their domain reach.
• Reporting cadence — weekly pipeline updates, dashboards, and a named point of contact.
• Exclusivity & engagement terms — whether the search is exclusive, candidate-ownership rules, and how duplicate submissions are handled.

Choosing a fee model

The fee model signals how much risk each side carries.

• Contingency — you're paid only when the client hires your candidate, typically a percentage of first-year salary (commonly 15–25%). Low client risk, but you're competing and may not get exclusivity.
• Retained — the client pays in instalments across the search (often a third up front, a third on shortlist, a third on placement). Best for senior, hard-to-fill, or confidential roles where you need committed effort.
• RPO (recruitment process outsourcing) — you embed as the client's hiring function for volume or ongoing needs, usually a monthly management fee plus a smaller per-hire fee. Best when hiring is constant and the client wants predictable cost.

Match the model to the role: contingency for steady mid-level demand, retained for senior or scarce talent, RPO for sustained volume.

Common mistakes to avoid

• No volume or salary bands. "Several engineering roles" can't be sourced or priced. Pin down counts, seniority, and ranges in the roles table.
• Burying the guarantee. The replacement window and rebate terms are reassurance — state them plainly, not in fine print.
• SLAs you can't keep. A promised first shortlist in five days you can't deliver costs you the account. Commit to numbers you can hit.
• Ignoring candidate ownership. Spell out how duplicate submissions and prior-applicant conflicts are resolved before they become a fee dispute.
• One fee model for every role. Pricing a niche senior search like a high-volume junior one undersells the effort and erodes margin.