Claude for Recruiters: A Configured Setup Guide

Short answer: set up Claude Cowork for recruiters by writing a CLAUDE.md file that encodes your pipeline stages and outreach voice, organizing job descriptions and resumes so the workspace can reference them, then wiring screening, outreach, and pipeline tracking into repeatable Claude Cowork workflows on top of that foundation.

I run a solo desk, and this is the exact configuration I use every week to move requisitions from intake to placement without losing context between candidates and clients. If you already know what Claude Cowork is and you want a working setup instead of a tour of the interface, this is that setup, section by section.

Claude Cowork is built on Claude Code, but for recruiting the value is not the underlying model. It is how you configure the workspace around your pipeline, your clients, and your voice. If you want the plain-English rundown first, I already covered what Claude Cowork actually is; this post assumes you know it and walks through configuration. Everything below is what I actually configured, not a hypothetical.

Writing a Starter CLAUDE.md for Your Claude Cowork for Recruiters Setup

Your CLAUDE.md file is the context document that Claude Cowork reads before it does anything else for you. For a recruiting desk, I treat mine as the single source of truth for three things: my pipeline stages, my active client and requisition context, and the tone I want in outreach.

Before you set anything up, read through these AI use cases for recruiters and mark the jobs you would hand off first.

I did not write mine from a blank page. I started with the Claude Cowork Foundation Plugin intake, which asks structured questions about your business and turns your answers into a first draft of the file. From there I edited it by hand until it matched how I actually talk to candidates and clients.

Here is a stripped down version of the CLAUDE.md I use, with placeholders instead of real client or candidate data:

# CLAUDE.md - Recruiting Desk Context

## Who I am
- Role: [Independent recruiter / solo talent acquisition founder]
- Specialty: [e.g., mid-market SaaS sales hires]

## Pipeline stages
1. [Sourced]
2. [Screened]
3. [Submitted to client]
4. [Client interview]
5. [Offer]
6. [Placed / Closed]

## Active requisitions
- [Client Name] - [Req Title] - [Priority: High/Medium/Low] - [Target close date]

## Outreach tone
- Voice: [Direct, warm, no fluff]
- Never use: [phrases to avoid]
- Always include: [clear call to action]

## Boundaries
- Never send a final rejection to a candidate without my review.
- Never make a bias-sensitive judgment call on its own.

Once that file exists, Claude Cowork stops guessing at your context on every single request. I also use this file to define custom Claude Cowork skills, small named routines like “screen against req” or “draft client update” that reference the pipeline stages I already defined, so I am not re-explaining my process every time I open a new session.

Organizing Candidate Files and Job Descriptions So Claude Cowork Can Actually Use Them

Four-step setup flow diagram for configuring a Claude Cowork recruiting workspace: CLAUDE.md, organize files, connect tools, run workflows.
Four-step setup flow diagram for configuring a Claude Cowork recruiting workspace: CLAUDE.md, organize files, connect tools, run workflows.

A CLAUDE.md file only helps if the workspace can actually get to your documents. I keep three folders inside my workspace:

  • Job descriptions, one per open req.
  • Active candidates, resumes named with the candidate’s last name and the req code.
  • Client intake notes, so context from the client conversation stays with the req.

Naming every resume file consistently is what keeps nothing from getting misfiled.

This is where the how it works walkthrough is worth reading once, because it explains how the workspace indexes files instead of just storing them. Once your folders are organized, you are not re-uploading a resume every time you want it screened, the workspace already knows where to look.

I also connected my inbox and calendar through Claude Cowork connectors, so scheduling and email threads related to a req show up in the same context as the resume itself. If you use an ATS or a scheduling tool, Claude Cowork connectors built on the open Model Context Protocol are what let the workspace read and write into those tools instead of treating them as separate systems you have to bridge manually.

For anything that lives behind a login and does not have a direct connector, Claude Cowork computer use lets the workspace open a browser and pull information the way you would, which matters for recruiting because plenty of client portals and job boards do not offer a clean integration. Check the full features overview for what is currently supported before you build a workflow around it.

Screening Resumes with Claude Cowork for Recruiters

Decision diagram showing how Claude Cowork routes a resume screening result to submit to client or log the gap and keep sourcing - a guide.
Decision diagram showing how Claude Cowork routes a resume screening result to submit to client or log the gap and keep sourcing.

Once your files are organized, screening is where the setup starts paying you back. I built a simple workflow: drop a job description into the req folder, point Claude Cowork at the batch of resumes for that req, and ask for a summary that scores each candidate against the must haves and nice to haves I listed in the job description.

This is a Claude Cowork agents style workflow, meaning it runs the same steps every time instead of me re-describing the task. I ask for three things per candidate: a fit summary, the gaps, and one open question I should ask on the first call. Claude Cowork automation handles the repetitive read through of ten or twenty resumes, I handle the judgment calls.

A human reviews every screening output before it affects a candidate. I never configured this workspace to make a final rejection decision or any bias-sensitive judgment call on its own, and I would not recommend anyone else set it up that way either.

If you want a guided walkthrough of building this exact screening configuration, the free Learn Claude guides cover it in more depth than I can in one section here.

Drafting Outreach Messages and Follow Ups with Claude Cowork Agents and Workflows

Outreach is where your CLAUDE.md tone settings actually show up. Because I defined my voice once in that file, every draft Claude Cowork writes for me, whether it is a first touch to a candidate or a status update to a client, sounds like something I would actually send.

I set up three standing sequences, each a Claude Cowork workflows entry that pulls the req details and candidate stage automatically, so I am editing a draft instead of writing from nothing:

  • Candidate first outreach, sent the day a fit summary clears review.
  • Candidate follow up after silence, flagged once a candidate sits in a stage too long.
  • Client weekly update, drafted from the current pipeline tracker.

For follow ups specifically, I use Claude Cowork automation to flag any candidate who has been sitting in a stage for more than a set number of days, then draft the nudge for me to review. I still send every message myself, the workspace just removes the blank page problem.

If you recruit for a specific niche, it is worth looking at the Claude Cowork persona packs available for other roles, since they show what a role specific plugin actually looks like once configured. Recruiters comparing the best Claude Cowork plugins for their desk should think about it the same way agencies and consultants do, the plugin should match your actual workflow, not just your job title.

Tracking Your Recruiting Pipeline Inside the Claude Cowork Workspace

Hub diagram of a recruiting pipeline tracker in Claude Cowork with six stages: sourced, screened, submitted, interview, offer, placed - a.
Hub diagram of a recruiting pipeline tracker in Claude Cowork with six stages: sourced, screened, submitted, interview, offer, placed.

Screening and outreach only matter if you can see the whole pipeline at once. I keep a single tracking document inside the workspace with every open req, every candidate tied to it, their current stage, and the next action for each one.

Claude Cowork updates this tracker as a side effect of the other workflows, when a screening summary is generated or an outreach message goes out, the stage and next action get logged automatically. Claude Cowork connectors to my calendar mean interview dates land in the same view without me copying anything over by hand.

For anything synced from an external ATS or spreadsheet, the Claude Cowork MCP layer is what keeps the tracker current without me manually reconciling two systems. I was part of the early group testing this setup through the Foundation Plugin download, and pipeline tracking was the piece that took the most iteration to get right.

What You Configure, What Claude Cowork Does, and What You Review

It helps to be explicit about where the workspace is doing labor and where you are still the decision maker. Here is how I break it down on my own desk. There’s more in the CoworkStack Foundation Plugin walkthrough.

Setup Step What Claude Cowork Does What You Review or Approve
CLAUDE.md context file Applies your pipeline stages, tone, and boundaries to every task The wording of the file itself, updated as your process changes
File and job description organization Indexes resumes and job descriptions so they can be referenced Folder naming and which reqs are marked active
Resume screening Generates fit summaries and gap notes against the job description Every summary before it influences a candidate decision
Outreach drafting Writes candidate and client messages in your configured voice The final send, every time, no exceptions
Pipeline tracking Logs stage changes and next actions as workflows run Weekly accuracy check against actual client conversations

A Repeatable Weekly Routine for Running Your Desk on Claude Cowork

Weekly routine flow diagram for running a recruiting desk on Claude Cowork: Monday review, screen resumes, midweek check, Friday update - a.
Weekly routine flow diagram for running a recruiting desk on Claude Cowork: Monday review, screen resumes, midweek check, Friday update.

Configuration only pays off if you actually run it the same way every week. Mine looks like this. Monday morning, I review the req list and update anything that changed with a client over the weekend. Then I run screening on any new resumes that came in, and I send the outreach drafts for follow up before lunch.

Midweek, I check the pipeline tracker against what is actually happening on calls, since the workspace only knows what it has been told. Friday, I do a short client update pass using the standing sequence I set up earlier.

This routine is really just the Cowork Strategy Stack applied to one specific desk, guided intake, file organization, connectors, then playbooks, run on a weekly cadence instead of set up once and forgotten. The same logic that applies to Claude Cowork for founders running a lean team applies here too, you are both the operator and the client facing person, and the workspace exists to remove the repetitive parts of that job. If you want more on how this approach was put together, the about page covers the background.

Conclusion: Configure the Workspace That Actually Runs Your Desk

You can read recruiting advice indefinitely and never change how your Monday actually starts. It comes down to skimming recruiting tips versus configuring the one workspace that runs your pipeline for you. Configuring Claude Cowork for recruiters is different, because the CLAUDE.md file, the folder structure, the screening workflow, and the outreach sequences either exist in your workspace or they do not.

I would rather spend a few hours setting this up once than spend every week re-explaining my process to a blank chat window. If you want more configuration walkthroughs like this one, the blog has others worth reading, but reading is not the same as having the pipeline actually run for you. Claude Cowork for recruiters only works once you build it.

Ready to configure your own desk?Get the free Foundation Plugin and build this setup inside your own Claude Cowork workspace.

Frequently Asked Questions

How do you set up Claude Cowork for recruiting?

Write a CLAUDE.md with your pipeline stages and tone, organize resumes and job descriptions by req, then build screening, outreach, and tracking workflows on top of that file.

Can Claude Cowork replace an ATS?

No. Claude Cowork works alongside your ATS through connectors, it organizes context and drafts work, it does not replace the system of record for compliance and reporting.

Is it safe to put candidate resumes into Claude Cowork?

Recruiters handle sensitive candidate data, so keep files organized, limit access, and always have a human review screening output before it affects any candidate.

Does Claude Cowork automate final rejection decisions?

It should not be configured to. I set explicit boundaries in my CLAUDE.md so the workspace never makes a final rejection or bias sensitive call without my review.

Is Claude Cowork only useful for recruiters?

No. The same foundation plugin and workflow logic works for Claude Cowork for founders, consultants, and agencies, recruiters just configure it around candidate pipelines instead of deals or campaigns.

For an individual or a small business, Claude AI setup for recruiters and staffing firms is the shortest path from a half-working setup to one that runs.

Michael Robichaud

Written by

Michael Robichaud

Founder of Strategized.ai, home of the free Foundation Plugin and twelve role-specific Claude plugins. Michael designs Claude plugins and skills for business owners and leads the custom plugin builds his developers ship.

 ·  Connect on LinkedIn →

The free Foundation Plugin is where the Strategy Stack starts.

A Guided Intake, your Business Blueprint, and a workspace that knows your business. Free, instant download, no account.

Free download. No card.

Keep Exploring

More from the blog

Guides, use cases, and plugin reviews.

Browse the Blog →

See everything inside the Stack

Every deliverable, layer by layer.

Explore Features →

Need it built for you?

Hands-on AI strategy and expert-led configuration.

Visit Strategized.ai →

The Foundation Plugin: free for business owners and professionals Get it free → Instant download. No account.