What about the Python or Node scripts I already wrote?

Most map cleanly to Vitae workflows in a few clicks. For anything custom, we have a complete API and native MCP. Your existing code can call Vitae directly.

Can my AI still drive Vitae the same way it drives my custom MCP?

Yes, that's the design. Vitae has a native MCP server. Every action a recruiter can take, your AI can take too. Same API surface, just no longer brittle.

What happens to my Apollo, ContactOut, and Exa keys?

Drop them in as integrations. Your AI can use them inside Vitae. No more juggling .env files or pasting keys into Cowork sessions.

Do I need to migrate everything at once?

No. Most teams keep their current setup running for a month while they move workflows over one at a time. Common pattern: scoring first, then sourcing, then outreach. ATS migration usually lands last.

Will my custom workflows still feel like mine?

Yes. Vitae is built so you can shape pipelines, fields, and workflows to fit your business. The difference is they don't break, and a new recruiter can read them.

Use caseFor recruiters running their own AI

Replace your Claude duct tape.

If you've stitched Claude or ChatGPT into your recruiting with scripts, Sheets, Zapier, MCP servers, and 14 tabs, this is for you. Vitae is the ATS and CRM your AI talks to natively.

Start for free Book a demo

01The current setup/ what most recruiters run today

The setup most recruiters actually have.

None of this is wrong. It works. It just shouldn’t take nine tools, three browsers, and a custom MCP server to hire someone.

Claude Code in your terminal

Boolean strings, batch CV processing, JD drafts

Claude Cowork or browser scripts

LinkedIn scraping, profile lookups, light enrichment

A custom MCP server

Glue between Claude and your ATS, brittle and undocumented

Apollo, ContactOut, Exa keys

Sitting in .env files or pasted into Cowork sessions

Google Sheets

The real candidate database your team actually trusts

Zapier or Make.com

The duct tape between Claude, Sheets, and your ATS

Slack threads

Where decisions get made and lost

Bullhorn, Greenhouse, or Workable

The system of record that has no idea any of this happened

14 tabs open at any time

Plus a stickies note with passwords

“I built this. It works. I’m also tired.”

02What breaks/ five failure modes

Why duct tape cracks under load.

Data drift between five places

The candidate in your Sheet is stale. The one in Bullhorn is missing notes. Claude scored them in a chat you can't find. Three people on your team have three different views of the same candidate.

Brittle integrations that break on every update

Claude updates an API. LinkedIn changes a CSS class. Bullhorn pushes a new field. Your custom MCP server breaks at 11pm on a Friday and your Monday pipeline is gone.

AI scores stuck in chat history

Claude told you the candidate is a 9/10 fit. That score is now in a chat you closed last week. The hiring manager wants to know why. You guess.

Re-onboarding every new recruiter

The setup lives in your head. New hires take a month to learn it. Half of them give up and go back to the old way.

44 hours a year, per recruiter

Recent industry research puts the cost of poor tool integration at 44 hours per recruiter, per year. That's a full work-week burned on duct tape.

03How Vitae consolidates/ same work, no glue

What Vitae replaces, line by line.

Every script, every workflow, every brittle integration. Mapped onto a single platform that your AI can drive natively.

What you do nowIn Vitae

Boolean string generation in Claude Code, copy into LinkedIn RecruiterPlain-English search across 400M+ profiles. Your AI builds the query for you.

Batch CV screening via a Python script that calls ClaudeAI screening as a workflow step. Scores live with the candidate, not in chat history.

LinkedIn scraping via Cowork in a browser sessionNative LinkedIn enrichment. Updates flow to the candidate record automatically.

Custom MCP server you wrote to talk to your ATSVitae IS the ATS, with a built-in MCP server. Your Claude or ChatGPT plugs in directly.

Google Sheet as the real candidate databaseCustom objects, custom fields, custom pipelines. Built around how your team actually works.

Zapier or Make.com workflow that breaks when an API changesNative workflows with triggers, conditions, and actions. We maintain the integrations.

Slack threads where context gets lostComments and decisions live on the candidate record. Slack notifies, Vitae remembers.

Re-onboarding pain when a new recruiter joinsOne platform to learn. New hires productive in a day, not a month.

04What you get back/ five wins

What changes when the duct tape comes off.

One source of truth

Every candidate, score, note, and decision lives on one record.

Workflows that don't break

We maintain the integrations. You maintain the workflows that matter.

AI runs in context

Your Claude or ChatGPT sees every candidate, every conversation, every stage.

Faster onboarding

New recruiters productive in a day. No bespoke setup to memorise.

Hours back

The 44 hours/year that went to glue code go back to candidate conversations.

05FAQ/ six questions

Questions about moving off duct tape.

Short answers to the questions we get most often. Need more detail? Talk to sales.

Yes. Drop your prompts into Vitae as workflow steps. Your Claude or ChatGPT runs them inside the platform with full access to candidate data. No copy-paste.

Stop maintaining your own ATS.

Vitae is the platform you would have built, if you had a year and a team.