These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Recruitment CRM
- Features
- Hiring opportunities
Hiring opportunities
Follow a client hiring request through qualification, proposal, negotiation and outcome.
OverviewMy hiring opportunities×
Recruitment CRM · Hiring opportunities
New
My hiring opportunities
Opportunities
| Record number | Subject | Status | Expected close date | Expected value USD | Counterparty | |
|---|---|---|---|---|---|---|
| OPP-69282 | New opp-763 | New | 22 Oct | 860 | ACC-110 | |
| OPP-85129 | Qualified opp-113 | Qualified | 04 Oct | 200 | ACC-130 | |
| OPP-94924 | Proposal opp-699 | Proposal | 05 Oct | 480 | ACC-130 | |
| OPP-84887 | Negotiation opp-924 | Negotiation | 07 Oct | 170 | ACC-130 | |
| OPP-16936 | Won opp-685 | Won | 10 Oct | 330 | ACC-110 |
6 of 6 records
New opp-763Opportunities · OPP-69282
NewExpected close date22 Oct
Expected value USD860
CounterpartyACC-110
What you can do
Give each hiring request an owner
An opportunity is the working record for a client’s hiring request. It has a record number, subject, client account, owner, expected close date, expected value and revision. The status moves through New, Qualified, Proposal and Negotiation before a Won or Lost outcome. A Relationship Owner can keep the client conversation visible without merging separate requests from the same client.
Consider a client seeking a warehouse supervisor. The owner creates a separate opportunity for that search, even if the client already has another open position. A call can establish the scope; a later meeting can clarify timing. The owner can then mark the opportunity Qualified and keep the next activity with the same parent record. The Sales Manager sees its current stage and examines evidence before a final outcome is recorded.
How the work is organized
- Ownership. Each opportunity points to a team member, giving the Relationship Owner assigned work to follow.
- Stage. Status shows where the discussion stands, while expected close date and value support pipeline review.
- History. Activities, mandates, attachments, decisions and receipts all point back to the opportunity.
What to agree during setup
Define what a qualified hiring request means and what evidence is enough to move from proposal to negotiation. Agree how expected value is entered and when it should be revised. The record stores expected value in US dollars, so teams using another organization currency need a consistent entry policy. Set a cadence for reviewing close dates. A stale date should be corrected by the owner before the Sales Manager uses it in a pipeline meeting.
Choose a convention for the subject and record number that lets people distinguish positions at the same client. The account gives the customer identity; the subject describes the hiring request. Keep the owner current when a request changes hands so activity and review follow the person who can answer the client’s next question.
Check the handoff on an actual case
Open a new opportunity for a client request and assign a Relationship Owner. Log the first call, qualify the request, draft the proposal terms and mark negotiation when the client discussion begins. Add a mandate for the position and attach supporting evidence. Ask another person to inspect the opportunity, linked activity and submitted mandate before recording a win. For a lost request, record the reason so a later account review can distinguish a declined mandate from an accepted one. Check that both outcomes remain visible in the client’s history.
What your team sees
- My hiring opportunities — Assigned requests with stage, expected close date and client account.
- Opportunity stage board — Open requests grouped by current status for a pipeline discussion.
- Opportunities due to close — Requests whose expected close date needs attention.
Follow the work through
Use client intake for the first request, mandate review for position terms, and outcome review for a final decision.
What it keeps track of
Data model- Opportunities
- Client hiring opportunities tracked through the recruitment lifecycle
- Accounts
- Client hiring accounts eligible for recruitment opportunities
- Team members
- Recruitment team members with organization membership and role scope
- Relationship activities
- Calls, meetings, emails and tasks logged against an opportunity
- Hiring mandates
- Client hiring mandates submitted for review and approval
Who uses it
Permissions- Relationship Owner
- Manages assigned opportunities and client conversations.
- Sales Manager
- Reviews pipeline and independent decisions.
- Auditor
- Reads authorized outcomes and evidence.
Set up Recruitment CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.