Day 1Your roles, your criteria
Add the roles you’re already hiring for
Write each open requirement once, with its terms and what partners must include.
For employers and recruitment teams
Your recruitment network.Your rules.One command center.
Run a more controlled, accountable and scalable recruitment operation, without replacing the partners you already trust.
- Private
- partner networks
- Tracked
- partner commitments
- Recorded
- every submission
02Operational visibility
Know what’s happening across every requirement.
Late roles, partners who owe you an answer, candidates waiting on a decision and the interviews ahead, ranked by what needs you first.
Needs you today
Company A · 8 open
- LateData Engineer · 0 of 4 profilesCommitment from Partner 3 was due yesterday1 day late
- PartnerPartner 2 hasn’t accepted QA LeadShared 2 days ago · response window closes todayDue 17:00
- Review3 new profiles for Senior Java DeveloperFrom Partner 1 and Partner 2 · consent confirmedSince 09:40
- InterviewNeha S. · technical roundSenior Java Developer · Priya and Ravi on the panelToday 15:00
- LateProduct Designer · fill date passed2 of 3 openings filled · 12 days over plan12 days late
- PartnerPartner 4 asked about notice termsQuestion on Backend Engineer, waiting on youSince 11:15
Illustrative workspace with example data. Pick a type to filter, or act on an item.
03Private sourcing network
Your partners stay yours.
The agencies and recruiters you invite join your network, never a shared pool. Change the viewer to see who can see, invite or reach each partner.
View as
Companies
Partners
Company A
Private network
Requirements
- Senior Java Developer
- Data Engineer
- QA Lead
Sourcing partners
Partner 1
Partner 2
Partner 3
Company B
Private network
Requirements
- Product Designer
- Backend Engineer
Sourcing partners
Hidden partner
Hidden partner
No access
Company A recruiter can
- Can: See Company A’s partner list
- Can: Invite or remove partners
- Cannot: See Company B’s partners or roles
Partners you invite join your network only. Another company can’t see them, and the open marketplace is never forced on you.
04Sourcing capacity
Scale your reach when you need it.
Your own network goes first. When a role needs more hands, add verified partners to that role, and only that role.
- Your existing partners stay first in line
- Verified partners by specialty and record
- You choose who joins each role
- Extra reach switches off when the role is covered
Data Engineer · 4 openings
Your 3 partners working on it
Partner 13 profilesPartner 21 profilePartner 3AcceptedYour network first
Turn on more reach only when a role needs it.
05Requirement execution
Every open role has an owner, a deadline and a plan.
Partners accept, commit to what they’ll deliver and acknowledge every change. Nothing runs on memory.
- Partner acceptance within a response window
- Delivery commitments you can track
- Changes every partner must acknowledge
- A named owner for every requirement
Requirement
Senior Java Developer
Pune · 2 openings
Owner
Priya Sharma
Fill by
30 May · 18 days left
Partner commitments
Partner 1
5 profiles by Fri
acceptedDelivered4/5Partner 2
3 profiles by Fri
acceptedDelivered1/3- Waiting
Partner 3
Awaiting acceptance
Change: notice period now 30 days or less
Sent to every partner on this role · 11 May
06Candidate decision workspace
Less resume noise. Better hiring decisions.
Partner submissions and direct applicants arrive in one queue, each with its evidence and consent attached. Your reviewers make the call.
Review queue · all requirements4 waiting · 0 decided
Profiles · 4
Neha S.
Senior Java Developer
- Source
- Partner 1
- Received
- Today, 09:40
Led the payments migration at her current company.
Match92%
- Java, Spring Boot in production
- 30-day notice
- Payments domain, like the brief
- !No cloud deployment
Partner submissions and direct applicants in one queue; your reviewers decide. Illustrative profiles with example data.
07Recruitment governance
Every submission has a record.
Consent, source, duplicates, history and access live on the submission itself, so a dispute is settled by the record, not an email thread.
- Consent captured before a profile is shared
- First valid submission owns the candidate
- Every stage change keeps who and when
- Access limited to the people on the role
SUB-1042 · Neha S. → Senior Java DeveloperOn record
Source attribution
Submitted
Who introduced the candidate, and exactly when.
- Submitted by
- Partner 1
- Requirement
- Senior Java Developer
- Timestamp
- 10 May, 10:05:12
Recorded 10:05 · Partner 1
08Business intelligence
Know which partners actually deliver.
Rank partners by submissions, interviews, joins and the commitments they keep, then see exactly where each one’s candidates fall away.
Partner performance · last 6 months
Partner 1
From submission to join
- Submitted42
- Screened31
- Interviewed14
- Joined5
Biggest drop: Interviewed → joined. 9 of 14 stop here (64%).
Illustrative figures. Rank by any measure, then pick a partner.
09Adoption
Bring your current recruitment process with you.
Start with the roles and the partners you already have. Nothing about those relationships has to be rebuilt.
- 1
- 2Week 1Your partners, your terms
Invite the partners you already use
They join your private network on your terms. Nobody changes who they work with.
- 3Week 2Your team decides
Run a role from brief to hire
Submissions, reviews and interviews come into one place, alongside how you hire today.
Questions & answers
Good questions. Clear answers.
See your recruitment operations in one workspace.
Your roles, your partners and every candidate decision, with the control your team has been missing.