The team problem is coordination, not effort
Most recruiting tools are built for one recruiter at a time. They help a single person find, contact, and track candidates — and they break the moment a second recruiter is added to the same search. Two people end up sourcing the same names. A finalist gets emailed twice with two different pitches. A hiring-manager note lives in one recruiter’s inbox and never reaches the colleague who picks up the req on Friday. The desk is working hard, but it is working in parallel instead of together, and the duplicated effort is invisible until a candidate replies “your colleague already reached out.”
For a search firm, the same problem compounds across every client engagement. Each consultant runs their own searches, keeps their own shortlists, and reports their own progress, and the principal has no single place to see the state of the whole book. When a candidate from one search would be perfect for another partner’s role, nobody knows, because that candidate only exists in one consultant’s head and one consultant’s spreadsheet. The firm’s most valuable asset — its accumulated knowledge of who is out there and who is open — leaks out the door every time someone moves on.
MentionFox is built the other way around. The unit of work is the shared talent pipeline, not the individual recruiter. Sourcing feeds a common pool. Evaluation happens in bulk against the same criteria. Candidate dossiers are saved where the whole team can read them. Outreach runs from sequences the team authors once and reuses everywhere. The recruiter is a participant in a shared system, not an island maintaining a private one. That single shift — from many private workflows to one shared pipeline — is what turns a group of recruiters into a desk.
Team candidate sourcing, into one pool
Sourcing for a team has to land somewhere everyone can see, or it is just more private lists. MentionFox gives the desk three sourcing surfaces that all feed the same shared pipeline.
Find People & Companies at /dashboard/find is the team’s open-ended search surface: describe the kind of person you need — the role, the seniority, the company background, the market — and pull back matching people the desk can act on together. Anyone on the team can run it, and what they find drops into the same pool the rest of the team is working, so a name one recruiter surfaces on Monday is visible to the colleague staffing the same req on Tuesday.
The Talent Finder at /dashboard/hr-tools/talent-finder is the recruiting-specific surface: a sourcing tool tuned for how a desk actually fills roles, so the team is not bending a generic search to fit a hiring search. It is where a team turns a role brief into a starting slate of candidates without each recruiter reinventing the query.
And Scans at /dashboard/scans let the team run repeatable searches across the surfaces where candidates actually talk — the conversations, posts, and threads where people signal what they are working on and whether they are open. Scans turn passive listening into sourcing: instead of a recruiter manually checking the same places every week, the desk runs a scan and reviews what comes back, together. Every recruiter draws from the same sourcing engine, so the team builds one pool of candidates rather than five overlapping ones.
Bulk candidate evaluation, on the same criteria
Sourcing produces a long list. The team’s real work is turning that long list into a defensible shortlist — fast, and on criteria everyone agrees on. MentionFox is built to evaluate candidates at the scale a team operates at, not one at a time.
Bulk Compare at /dashboard/hr-tools/bulk-compare is the workhorse for a desk filling a slate. Line up a whole group of candidates and rank them against the same dimensions in a single pass, so the team is comparing like for like instead of each recruiter forming a private opinion of a private subset. When a hiring manager asks “why these five and not those fifteen?”, the answer is a structured, side-by-side comparison the whole team can stand behind — not five recruiters’ gut feel stitched together in a meeting.
For head-to-head work on a smaller set, the Compare tab on /dashboard/find puts two or a few candidates next to each other across every dimension that matters, which is exactly the view a hiring committee wants when it is down to the final names. Bulk Compare ranks the field; Compare settles the finalists.
When a shortlisted candidate needs to be understood in depth, the team turns to the Vetting Suite at /investor-vetter. It produces a point-in-time candidate dossier — a complete, sourced picture of a person as of the moment it is generated, with every claim sourced and cited so the team and the client can trust it. The Suite works in two tiers: the Snapshot row gives the team a fast read on a candidate, and when a finalist warrants a deeper look, the team chooses Order Full Report to go further. The Full Report row is already the complete picture — there is no upsell waiting at the end of it. Because every dossier is point-in-time and sourced, two recruiters reading the same candidate see the same facts, and the firm can hand a client a dossier that holds up to scrutiny.
One shared talent pipeline, not five spreadsheets
This is the heart of running a team on MentionFox. A shortlist that lives in one recruiter’s spreadsheet is invisible to the rest of the desk, and it dies when that recruiter is out, busy, or gone. MentionFox replaces the private spreadsheet with a pipeline the whole team works from.
The Talent CRM at /dashboard/hr-tools/talent-crm is the desk’s shared candidate database. Every candidate the team sources, evaluates, and contacts lives here, with ownership, stage, and history attached, so a recruiter picking up a req can see exactly where each candidate stands without a handoff meeting. The candidate one consultant surfaced for a closed search is still in the CRM when a different consultant opens a role that fits — the firm’s knowledge of the market stays inside the firm instead of walking out with whoever sourced it.
The dashboard CRM at /dashboard/pipeline-crm is the shared pipeline view of the work in motion: who is in which stage, what is moving, what is stalled, and where the team needs to push. For a principal running a book of searches, this is the single place to see the state of the whole desk rather than chasing five status updates. For a team filling a high-volume req, it is the board everyone moves candidates across together, so stage never drifts out of sync between recruiters. A shortlist nobody else can see is a liability; a shared pipeline everybody can see is the asset that lets a team scale past what any one recruiter can hold in their head.
Outreach the whole team runs from one playbook
When five recruiters each write their own outreach, the firm has five voices, five quality levels, and no way to know what works. MentionFox makes outreach a team capability. Sequences at /dashboard/sequences let the desk author multi-step candidate outreach once and run it across the team, so a strong approach written by your best recruiter becomes the approach the whole desk uses. New recruiters inherit the playbook instead of inventing one. The firm’s outreach reads like one consistent, professional voice to candidates, because it is. And because outreach runs from the shared pipeline, the team always knows who has already been contacted and at what step — no candidate gets two cold notes from two recruiters, the failure mode that quietly burns a firm’s reputation with the talent market it depends on.
