Claude Project: Build a Persistent Full-Desk Recruiting Assistant

What This Builds

A Claude Project configured specifically for your agency, your market, and your desk — so every conversation you have with Claude starts from complete context about your firm, your clients, your typical req types, and your preferred output formats. Instead of re-explaining your situation every session, your Claude assistant already knows it.

Prerequisites

• Claude Pro account ($20/month — claude.ai)
• 30 minutes to write your setup instructions
• Optional: past candidate submittals or client emails to use as style examples

The Concept

A Claude Project is like having a new coworker who read your entire onboarding packet before their first day. You set up the project once by writing a configuration document (called System Instructions) that tells Claude about you, your firm, and your work. After that, every conversation in the project inherits that context automatically — no re-explaining required.

Without a project, you'd write: "I'm a recruiter at a staffing firm specializing in finance and accounting placements in the Chicago market. Write me a candidate submittal for..." With a project, you just write: "Write me a candidate submittal for..." and Claude already knows the rest.

Build It Step by Step

Part 1: Create the Project

1. Log into claude.ai with your Pro account
2. Click Projects in the left sidebar
3. Click New Project and name it something like "Agency Recruiting — [Your Name]" or "[Your Firm Name] Desk"
4. You'll see a configuration area where you can add Project Instructions — this is where you write the setup document below

Part 2: Write Your Project Instructions

This is the most important step. Copy the template below and customize every bracket:

You are a recruiting assistant for [Your Name], an agency recruiter at [Firm Name], a [describe your agency: boutique staffing firm / national staffing firm / executive search firm] specializing in [your niche: finance & accounting / IT & engineering / healthcare / light industrial] placements in the [market: Chicago metro / Southeast / Pacific Northwest] market.

## About My Practice
- Service types: [contingency search / retained search / temp-to-perm / contract staffing]
- Typical fee: [15–25% of salary for direct hire / $X/hour spread for contract]
- Active client sectors: [list 3–5: manufacturing, financial services, healthcare systems, etc.]
- Typical req types: [Controller, Finance Director, Operations Manager, etc. — your most common roles]
- Typical candidate profiles: [senior accounting professionals / mid-level manufacturing managers / etc.]

## My Clients
[Add brief descriptions of your key client accounts here — just enough for context]
- [Client A]: [Industry, type of roles they hire, anything notable about their culture or process]
- [Client B]: [etc.]

## Communication Style Preferences
- Candidate submittals: 3 paragraphs, lead with strongest qualification, close with comp and availability, professional and confident tone — no hedging language
- BD emails: under 100 words, reference something specific about the company, end with a soft ask for a 10-minute call
- Client pipeline updates: structured paragraphs (not bullets), open with progress, be direct about bottlenecks, close with a specific ask
- InMails: 3 sentences max, reference candidate's specific background, direct about opportunity, conversational not formal

## What I Do in This Workspace
- Draft candidate submittals from screen notes I paste in
- Write BD cold emails for specific target companies
- Generate personalized InMails for passive candidates
- Write weekly client pipeline updates
- Draft interview prep documents for candidates
- Generate Boolean search strings for LinkedIn and Bullhorn
- Draft offer letters and rejection emails
- Prepare counter-offer coaching scripts

Always write from my first-person perspective (as me, not about me). Match the communication style described above. When I paste screen notes or context, use all the details I've provided — don't make up information.

Paste this into the Project Instructions field in Claude. Save it.

Part 3: Add Knowledge Files (Optional but Powerful)

Claude Projects lets you upload files that Claude can reference in every conversation. Upload:

1. One or two past submittals you're proud of — Claude will match the writing style and structure
2. A sample BD cold email that got a response — Claude will learn what works for your market
3. Your standard pipeline update template — if your firm has a preferred format
4. A list of your active clients and their current open reqs — Claude can reference this when suggesting candidates or drafting targeted outreach

To upload: In your Project, click Add Content or the attachment icon and upload PDF or text files.

Part 4: Test and Refine

Start a new conversation in your project and test the most common use cases:

Test 1 — Candidate submittal: Type: "Write a submittal. Candidate: [paste 5-bullet screen notes]. Role: [Job Title] at [Client Name]." Good result: A 3-paragraph submittal in your preferred style, using the details you provided, with no invented information.

Test 2 — BD email: Type: "Write a BD email to the CFO at [Company Name]. They're currently hiring a [Role]." Good result: A concise, referenced email under 100 words with a soft close.

Test 3 — InMail: Type: "Write an InMail to a passive candidate. Current: [Title] at [Company], [X] years, notable: [1 fact]. Role: [Title]." Good result: A 3-sentence, conversational InMail that references the specific fact you provided.

If any output misses the mark, add a clarifying line to your Project Instructions and test again. It usually takes 2–3 refinements to dial in the style.

Real Example: A Monday Morning on the Desk

Setup in project: Firm: regional executive search firm; niche: healthcare administration; market: Southeast US; fee structure: 20% retained; clients include 3 regional hospital systems.

Monday morning session — 8 tasks in 25 minutes:

Inputs you type: Nothing but brief prompts with pasted context — no re-explaining who you are or what you do.

1. "Submittal — Role: VP Revenue Cycle, [Hospital Client]. Candidate notes: [pastes 6 bullets from Carv summary]" → 3-paragraph submittal ready in 30 seconds
2. "BD email — target: [Health System Name], currently hiring a Director of Patient Access on LinkedIn" → 4-sentence referenced email ready in 30 seconds
3. "InMail — VP Nursing candidate, 12 yrs, Magnet-designated hospitals, current: [System], looking for COO path" → 3-sentence InMail ready in 30 seconds
4. "Pipeline update — [Client Name]. Status: [pastes 5-bullet status]" → Professional update email ready in 30 seconds

Time saved: 25 minutes of Claude output vs. 90+ minutes of manual drafting. The output is consistent, professional, and calibrated to your market and clients — not generic.

Time saved: Each of the 8 tasks takes 30–60 seconds instead of 5–20 minutes. Total session: 25 minutes vs. 90+ minutes manually.

What to Do When It Breaks

• Claude ignores my communication style preferences → Check that your Project Instructions are saved (not just typed in the chat). Go back to the Project settings and confirm the instructions appear in the configuration panel.
• Output is generic and doesn't reference my market or clients → Add more specific examples to your instructions. Instead of "Southeast healthcare market," write "Atlanta, Charlotte, and Nashville hospital systems."
• Output invents candidate details I didn't provide → Add to your instructions: "Never invent facts about candidates. Only use the information I provide in my prompt. If something is unclear, say so."
• Claude forgets my style after a long conversation → Start a new conversation in the project. Each conversation inherits your Project Instructions fresh.

Variations

• Simpler version: Skip the knowledge file uploads and just use the Project Instructions template — you'll get 80% of the value with half the setup time
• Extended version: Create separate Projects for different practice areas or client verticals (e.g., one project for healthcare, one for finance) with tailored instructions for each

What to Do Next

• This week: Create the project, write your instructions, and test with 3 real use cases from your current desk
• This month: Refine the instructions based on what's missing; add 2–3 knowledge files (past submittals, BD emails that worked)
• Advanced: Create a second project configured specifically for a single key client account — loaded with their culture, their hiring history, and their communication preferences

Advanced guide for agency recruiter professionals. These techniques use more sophisticated AI features that may require paid subscriptions.