5 Things I Use Claude and Kolvera For Every Day as a Recruiter

I get asked constantly in the RU community: "What do you actually use Claude for?" Not the pitch deck version. The real, daily version. So here are five things I do with Claude and Kolvera every single day. Not hypotheticals -- actual workflows I run before my first coffee gets cold.

The key thing to understand first: Kolvera uses something called MCP (Model Context Protocol) to connect Claude directly to your recruitment data. That means Claude isn't guessing or working off whatever you paste into a chat window. It can read your pipeline, search your contacts, run enrichment, and trigger campaigns -- all from a conversation. The MCP connection runs server-side, so there's no browser extension slowing down your LinkedIn tabs.

With that context, here's what my mornings actually look like.

1. Morning Pipeline Review

First thing I do every day is ask Claude to check my pipeline. Not "tell me about pipeline management best practices" -- I mean literally: "Show me prospects I haven't contacted in 7 days and suggest who to follow up with today."

Because Claude has MCP access to Kolvera, it pulls my actual prospect list, checks last contact dates, looks at what stage each prospect is in, and comes back with a prioritised list. It'll say things like "Sarah Chen at Canva -- last email was 9 days ago, she opened it twice but didn't reply. Worth a follow-up call." That's not generic advice. That's my data, interpreted in context.

This takes about 30 seconds. The alternative is opening the pipeline, sorting by last contacted, eyeballing each row, and trying to remember context. That's 15 minutes minimum, and I'd miss the email-opened-but-didn't-reply signal because I'd have to cross-reference tracking data manually.

2. Company Research Before Calls

Before I pick up the phone, I need to know who I'm calling. What does the company do, how big are they, are they hiring, who are their competitors, and what's their recent news?

I used to spend 30 minutes per company doing this manually -- checking SEEK for active roles, Googling for news, looking up ASIC data, scanning LinkedIn for headcount changes. Now I run Deep Research in Kolvera. One click, 3 credits, about 2 minutes. It pulls ASIC registration data, current SEEK job postings, recent news mentions, competitor landscape, and employee growth signals. Everything lands in a structured report attached to the company record.

The difference isn't just speed. It's coverage. I consistently find hiring signals I would have missed manually -- a company that's not on SEEK but has three roles on their careers page, or a business that just registered a new ABN for an expansion entity. Deep Research catches those because it's checking sources I wouldn't bother with individually.

3. Finding and Enriching Contacts

This is the one that saves the most time. I'll be on a call, hear a name, and need their details immediately. Or I'll finish a Deep Research report and want to find the hiring manager at one of the discovered companies.

I type something like: "Find me the HR Director at Buildkite." Claude searches Kolvera's contact database and enrichment providers, finds the person, enriches them with a verified email and phone number, and adds them to my prospect list. One sentence from me. The enrichment waterfall handles the rest -- it tries cached data first, then works through providers in order of cost, and only charges credits when it finds a verified result.

The old workflow: search LinkedIn, find the person, copy their name, go to an enrichment tool, paste, wait, copy the email, go back to my CRM, create a record, paste. Six tabs, four tools, five minutes per contact. Now it's one sentence and I stay in the same conversation.

4. Writing Personalised Outreach

Here's where the MCP connection really matters. When I ask Claude to write an outreach email, it doesn't produce generic templates. It pulls the prospect's enriched data from Kolvera -- their company, role, recent hiring activity, what I already know about them -- and writes something specific.

The difference between "I noticed your company is growing" and "I saw Buildkite posted three SRE roles on SEEK last week -- I have a platform engineer who built observability tooling at Atlassian" is the difference between delete and reply. The first is a template. The second is a pitch built from real data.

I'll generate a full email sequence -- initial outreach, follow-up, and a final touch -- in one conversation. Claude knows what data was used for the first email, so the follow-ups reference the same signals without repeating them. The sequences go straight into a Kolvera campaign, with staggered send times across working hours.

5. Building ICP Profiles From a Brief

This is the one I show people when they ask what AI recruitment tooling looks like in practice. I'll type something like: "I want to target mid-market SaaS companies in Melbourne hiring DevOps engineers, 50 to 200 employees."

Claude generates a full Ideal Client Profile -- target industries, company size ranges, decision-maker titles, pain points, value proposition. Then it runs Deep Research against that ICP and returns a list of real companies matching the criteria, complete with verified company data, current job postings, and contact details for hiring managers.

In 5 minutes, I go from a vague brief to a list of 15 companies with contacts I can call today. That's not a theoretical capability. That's what I did last Tuesday when a candidate told me they wanted to move into a DevOps role at a product company.

The MCP Difference

Everything I've described above is possible because of MCP. Without it, using Claude for recruitment means copying data out of your tools, pasting it into a chat window, getting a response, and copying it back. It works, but it's slow and error-prone.

With MCP, Claude reads and writes directly to Kolvera. My pipeline data, contact records, research reports, and campaigns are all accessible in the same conversation. I don't context-switch between tools. I describe what I want in plain English and the system handles the rest.

If you're a recruiter who keeps hearing about AI but isn't sure where to start -- start here. Pick one of these five workflows and try it for a week. The morning pipeline review alone will change how your day starts.

Frequently Asked Questions