360 vs 180 recruiter workflows in Wiggli
360 and 180 describe how a recruiter’s job splits. Wiggli supports both models without forcing a workflow.
PUBLIC · Concept Explainer
If you’ve ever had to bend your tool stack around how your team is structured, this article is the answer to why Wiggli doesn’t make you do that.
The terms
Section titled “The terms”- 360 recruiter owns the full cycle: business development with clients AND candidate sourcing and placement.
- 180 recruiter owns one half, usually candidate-side, while another team owns client-side BD.
Why it matters
Section titled “Why it matters”Agencies structure teams differently, and the wrong tool stack forces a structure. Wiggli’s unified database, search, and outreach flex either way, so you choose the model that fits your business, not the one your tools dictate.
How 360 recruiters use Wiggli
Section titled “How 360 recruiters use Wiggli”Two parallel motions in one workspace.
BD motion
Section titled “BD motion”Find decision-makers at target clients, save to a BD project, reveal contacts, run a BD campaign, qualify with Company Insights, pipeline replies into your CRM.
Candidate motion
Section titled “Candidate motion”Search for candidates, save to vacancy projects, qualify with the Co-pilot, run outreach, push qualified candidates to the ATS.
Same balance, same workspace, two distinct project and campaign sets. Naming conventions (BD - ACME vs Search - Senior FE Dev) keep them visually separate.
How 180 recruiters use Wiggli
Section titled “How 180 recruiters use Wiggli”A candidate-side 180 recruiter focuses on sourcing and placement: receive vacancies (often as ATS records), build vacancy projects, source, qualify, outreach, push to the ATS. The BD team uses Wiggli for prospecting or a separate CRM, depending on the agency’s tooling philosophy.
[GAP: confirm whether Wiggli has a native “team-level” project concept separating BD from candidate work, or whether this is naming convention only.]
Common misconceptions
Section titled “Common misconceptions”BD and candidate sourcing don’t need separate platforms if the platform supports both data sets. Wiggli does.
Outreach limits are shared. They’re per connected sender, not per campaign type. A 360 recruiter’s daily email limit covers both motions combined.
Switching models doesn’t mean a new tool. Reassign projects and campaigns to the relevant person; the data stays.
Related articles
Section titled “Related articles”Still stuck?
Your customer success manager reads faster than any search bar.