Start with the job
Why this workflow exists
Sourcers repeat the same research and first-message drafting for every candidate.
Response rates suffer when outreach is generic or lacks role context.
A recruiter selects a candidate for an active role.
Evidence and assumptions
What this playbook assumes
Sourcers repeat the same research and first-message drafting for every candidate.
The recruiter already has access to the source system and can approve the output.
AI does not make the final customer, candidate, property, campaign, or client-facing decision.
Last reviewed: 2026-08-05
AI workflow
Where AI helps, and where a person decides
The workflow is useful because each automation step ends at a named human checkpoint.
Assemble context
Collect only the facts needed for a relevant message.
- Input
- Role brief and approved candidate notes
- AI action
- Extract role hook, candidate signal, and constraints.
- Human checkpoint
- Recruiter confirms the context is appropriate to use.
- Output
- Outreach context
Draft message
Write a short, relevant first message.
- Input
- Outreach context and channel rules
- AI action
- Draft one message and a transparent call to action.
- Human checkpoint
- Recruiter edits and approves before sending.
- Output
- Approved outreach draft
Log next action
Keep the ATS record current.
- Input
- Approved message and candidate record
- AI action
- Prepare a note and follow-up date.
- Human checkpoint
- Recruiter confirms the action.
- Output
- Logged outreach
Choose with context
What should your team do next?
Answer three questions to find the most practical next step for your current system, capability, and strategic need.
Answer the questions to choose a path for this workflow.
Strengthen team capability
You want to improve message quality without automating sending.
Trade-off: The team still approves and sends every message.
Open the capability routeUse an existing tool
Your sourcing platform already supports controlled personalization.
Trade-off: Less control over context and logging details.
Check your current systemCreate a custom workflow
You need consistent, auditable drafting across many recruiters.
Trade-off: Needs stronger privacy, permissions, and evaluation work.
Review the custom workflow routeRecommended next move
Start with the capability map below. It connects the selected workflow step to a focused resource and a concrete deliverable.
Open the capability routeKeep your current system if it can preserve source context, expose missing data, allow human editing, and keep observed facts separate from generated interpretation.
Bullhorn · Recruitment operations platform
Compare Bullhorn for this workflow
- Best when
- Your current system cannot preserve the required workflow inputs, controls, or review states.
- Avoid when
- Your existing system already satisfies the workflow requirements and keeps the data in one place.
- Why it fits
- Compare Bullhorn when the current system fails one of the workflow requirements.
- Limitation
- Provider defaults may not match your fields, permissions, or review policy.
- Trade-off
- Faster setup with less control over vendor-specific workflow behavior.
Related template or use case: Open provider guidance
Alternative: Use the automation feature in your current platform · Last checked 2026-08-05
Create a custom workflow when the process is differentiated, integration-heavy, or sensitive enough to require ownership of data boundaries, approvals, and maintenance.
Make · Automation layer
Create this workflow with Make
- Best when
- The workflow repeats often enough to justify visible automation and an owned handoff.
- Avoid when
- The workflow is still changing or the team has not agreed on source ownership and human approval.
- Why it fits
- Make can support the workflow's explicit handoffs before a custom backend is justified.
- Limitation
- The team still owns configuration, monitoring, and the final human checkpoint.
- Trade-off
- More control than a fixed product, with more setup and maintenance responsibility.
Related template or use case: Open provider guidance
We may earn a commission if you sign up through this link.Alternative: Use the automation feature in your current platform · Last checked 2026-08-05
Railway · Application and infrastructure layer
Create this workflow with Railway
- Best when
- The workflow repeats often enough to justify visible automation and an owned handoff.
- Avoid when
- The workflow is still changing or the team has not agreed on source ownership and human approval.
- Why it fits
- Railway can support the workflow's explicit handoffs before a custom backend is justified.
- Limitation
- The team still owns configuration, monitoring, and the final human checkpoint.
- Trade-off
- More control than a fixed product, with more setup and maintenance responsibility.
Alternative: Use the automation feature in your current platform · Last checked 2026-08-05
Capability map
What does your team need to operate this workflow?
Choose a step and your current level to see the shortest route to a useful deliverable.
AI drafting
The message should be relevant without inventing candidate facts.
Recommended learning route
Using AI in Make
The course covers the mechanics; keep sending and personal-data decisions with the recruiter.
Ready-to-use artifact
Outreach context
This is the complete operating template for the workflow: input contract, runbook, automation handoff, human review, escalation, and a test case.
Workflow template
Open the complete operating runbook
The full Markdown stays out of the page until you ask for it. Open it when you are ready to adapt this workflow to your team.
What happens next
- Assemble contextExtract role hook, candidate signal, and constraints.
- Draft messageDraft one message and a transparent call to action.
- Log next actionPrepare a note and follow-up date.
Check before action
- Assemble contextRecruiter confirms the context is appropriate to use.
- Draft messageRecruiter edits and approves before sending.
- Log next actionRecruiter confirms the action.
Logged outreach
Test the filled template on one real but non-sensitive example. Keep the source context and approval decision with the team that owns this workflow.
Implementation stack
What the workflow needs
Automation and AI usage
Sourcing platform · Recruiter time
Explore the product angle
Ideas connected to this workflow
Use this workflow inside an agency, or explore product ideas built around the same operational problem.
SaaS WorkflowSales & Marketing
Partnership Outreach Tracker for B2B Solo Founders
A single-workspace outreach tracker that lets a solo B2B founder run a 30-partner campaign, log email replies, schedule follow-ups, and close co-marketing or integration deals without juggling spreadsheets and Gmail.
AI ToolSales & Marketing
AI Sales CRM Dashboard for Small Business Teams
A focused sales pipeline that explains lead priority, flags stalled deals, drafts the next follow-up, and rolls qualified opportunities into a transparent forecast.
Next workflows
Related playbooks
RecruitmentRecruitment agencies
Client candidate update reporting
Turn ATS activity into a concise client update with progress, blockers, and next actions made explicit.
RecruitmentRecruitment agencies
Candidate intake and shortlist preparation
Turn candidate materials into a structured, reviewable shortlist while keeping hiring decisions with recruiters.