The accountable headhunter for European tech startups.Every candidate comes with a reason.So does every rejection.

Paste your job description into Claude. Talent Master pressure-tests your brief, hunts tech profiles across the web and GitHub, and writes to candidates from your Gmail once you approve.

See an annotated shortlist ↓

Talk to us for 15 minutes

01Nothing goes out without your approval
02No commission, cost shown before every hunt
03400 trial credits valid 60 days, no card needed

01 · The reasons

A shortlist you can stand behind.

An agency sends you names. Talent Master tells you why each one is there, what it rests on, and why the others are not. You keep, reject or rescue: the decision stays yours.

Example · kept · 1/25 · Senior Rust back-end engineerInès Marchal

Maintains an open-source Modbus library in Rust, 7 years of back-end, 4 of them with Rust in production. Based in Lyon, fits 2 days on site.

Found by · a GitHub search and a web search

The rejects register

A headhunter is also judged by who it turns away.

Example · Moraine · 381 rejected by the agent, 1 by you
github · Java back-end, no Rust in productionrejected by the agent
web · Rust in side projects only, nothing in productionrejected by the agent
github · React front-end, no back-endrejected by the agent
web · based in Montreal, not looking for a role in Francerejected by the agent
web · data engineer, no application back-endrejected by the agent
Julien Mercier · little web back-end, a core part of the role at Morainerejected by you
… and 376 more, each with its reason.

Reasons tied to the role.
The stack, production experience, location, the scope of the role. Never age, origin or gender: those criteria are refused, and the agent tells you why.
A rejected profile can be rescued.
Disagree with a reason? Rescue the profile: it joins the shortlist, and you contact them like the others.

02 · Example

Example: one full search, from brief to interview.

A typical conversation, reconstructed step by step. The company and candidates are made up; the steps are the product’s.

Talent Master

Example · reconstructed conversation, made-up company and candidates

Here’s our job description and my call notes with Hugo, my co-founder. We’re looking for a senior Rust back-end engineer.

Job description - Senior Rust back-end.pdfCall notes Hugo 10-08.txt

Role createdcreate_mission

2 sources read · Rust, PostgreSQL, Modbus · Lyon · permanent · team of 5 engineers

I have the role, the stack, the contract and the team. Before we start anything, two things.

A contradiction: the job description says “100% remote”; your notes with Hugo say “two days a week at the Lyon office”. Which one should I go with? It changes the whole search area.

What’s missing: the salary range, and what’s a must-have versus a plus. Modbus, for instance?

get_mission_conflicts

1 contradiction to settle

Two days in Lyon, Hugo’s right. €60–70k. Production Rust is a must, Modbus a plus. And ideally someone who graduated after 2015, so they fit the team.

Got it for location and salary. But I won’t filter on graduation year: it’s an indirect way of filtering on age, which the law doesn’t allow. I suggest “at least 5 years of back-end, 2 of them with Rust in production” instead.

The brief: Rust in production (2+ yrs) · 5+ yrs back-end · Modbus a plus · Lyon, 2 days on site · €60–70k · permanent

If this brief works for you, here’s the estimate:

Estimateestimate_auto_source

about 400 profiles to screen · 2 credits per profile · ≈ 800 credits · balance: 2,400 credits

I suggest: target 25 kept candidates, standard strictness, cap at 900 credits.

Brief approved. Go ahead, cap at 900.

11 minutes later

How’s it going?

Hunt finishedget_auto_source

web and GitHub · 406 profiles screened · 25 kept · 381 rejected, each with its reason · 11 min · 812 credits, within the 900 cap · balance 1,588

Here are the first three of 25, with the reason for each. Each name opens their record on your Talent Master page.

Inès Marchal · 7 years of back-end, 4 of them with Rust in production. Maintains an open-source Modbus library in Rust on GitHub. Based in Lyon.

Awa Konaté · Rust back-end at an EV charging operator. Led the migration of a service from Go to Rust. Based in Lyon.

Julien Mercier · 6 years in embedded systems (C, then Rust), industrial protocols. To check: little web back-end experience. Based in Grenoble, on-site presence to confirm.

The other 22 follow if you want them.

Reject Julien, web back-end is central for us. Find emails for the first nine.

Julien is rejected, with your reason (reject_candidate). That leaves 8 emails to look up: 24 credits at most, charged only if found. Suppression list checked: no one excluded. Shall I go ahead?

Yes.

Emails foundenrich_candidates

6 of 8 · 18 credits · balance 1,570

Personalised emails

6 candidates · 6 credits · balance 1,564

I’ve drafted a three-email sequence on Moraine’s behalf, with a personalised first email for each candidate. Here’s Inès’s:

Subject: A Rust role in Lyon, at Moraine

“Hi Inès, I’m Camille, CTO at Moraine. I came across your Rust Modbus library on GitHub. We write the software that runs batteries on industrial sites, in Rust, and we’re looking for a senior back-end engineer…”

Candidate notice: included, cannot be removed

To launch it: Confirm the launch on your Talent Master page

3 days later

Who replied?

2 replies out of 6, and their sequences have stopped. Inès is interested and asks whether the role is open to a four-day week: I don’t have that information. Awa would rather talk again in January.

Yes to the four-day week. Offer her some slots.

Here’s the draft:

“Thanks, Inès. Yes, a four-day week works for us. Pick the slot that suits you: [booking link]”

To send it: Approve the reply on your Talent Master page

Sent from your Gmail, in Inès’s threadsend_reply

Next day

Any interviews booked?

Inès booked Thursday, 2:00 to 2:45 p.m., with a Meet link; it’s in your calendar. She hasn’t heard from us yet. Shall I confirm it to her?

Yes.

Interview confirmedconfirm_booking

Inès Marchal · Thursday 2:00 – 2:45 p.m. · Google Meet

1 · Collect · the brief

Job description - Senior Rust back-end.pdf

Senior Rust back-end engineer

Moraine · Lyon · permanent · team of 5Rust, PostgreSQL, Modbus100% remote100% remote Lyon, 2 days on siteSalary: —€60–70kRust in production, 2+ yrs · 5+ yrs back-end · Modbus a plus

Contradiction. Job description: 100% remote. Hugo’s notes: 2 days in Lyon.

Missing the salary range. Modbus: must-have or plus?

Refused: “graduated after 2015”, an indirect filter on age.

≈ 400 profiles · ≈ 800 credits · cap 900

brief approved by you

2 · Contact · the hunt and the sequence

14:02hunt started · 900-credit cap

14:13406 profiles screened · web and GitHub

14:1325 kept · 381 rejected, each with its reason

14:13812 credits · balance 1,588

14:166 of 8 emails found · 18 credits · balance 1,570

14:176 personalised emails · 6 credits · balance 1,564

kept · 1/25Inès MarchalMaintains an open-source Modbus library in Rust, 7 years of back-end, 4 with Rust in production. Lyon.

kept · 2/25Awa KonatéLed a service’s migration from Go to Rust, at an EV charging operator. Lyon.

kept · 3/25rejected by youJulien Mercier6 years in embedded systems (C, then Rust). To check: little web back-end. Grenoble.your reason: web back-end is central at Moraine

your Talent Master page · confirmation

Launch the sequence · Senior Rust back-end engineer

6 candidates · 3 emails

Sender: camille@moraine.io (Gmail)

A reply stops the sequence for that candidate.

Candidate notice: included in the first email, cannot be removed

Sequence launched · 6 candidates · 150 emails a day at most, weekdays 9 a.m. to 6 p.m.

3 · Organize · the reply and the interview

your Talent Master page · reply to approve

To: Inès Marchal · in her thread · from camille@moraine.io

“Thanks, Inès. Yes, a four-day week works for us. Pick the slot that suits you: [booking link]”

sent from your Gmail · in Inès’s thread

Thu2:00 p.m.Interview · Inès Marchal · 2:00 – 2:45 p.m. · Google Meet · in your Google Calendarwaiting for your confirmationconfirmed to Inès

It hunts. You approve.

Collect · A brief that holds up.

Paste your job description, your call notes or the link to the posting. Talent Master spots what is missing and asks only the questions that change the results: salary, must-have or nice-to-have, remote, seniority, companies to target or avoid. It catches contradictions, like “100% remote” in the job description and “two days in the office” in your notes.

It tells you what will make the hunt hard, and won’t filter on age, graduation year, name, photo or address, explaining why.

Contact · The hunt, then your emails.

You set the target (10, 25 or 50 kept candidates), the strictness and a credit cap. Talent Master hunts across the web and GitHub, then hands back a shortlist where each kept candidate comes with its reason. You keep, reject or rescue. For the ones you keep, it looks up their personal email, charged only if found, and drafts the sequence in your company’s voice. It goes out from your Gmail once you have launched it.

Organize · Interviews, in your calendar.

When a candidate is interested, you approve a reply that offers them three slots, taken from your working hours and clear of your meetings. They pick one on a page with your name and logo, and the interview lands in your Google Calendar with a Meet link. They get a confirmation only once you have given it.

03 · Control

It’s ready. You send it.

Talent Master prepares the sequence. You read the email as it will go out, and your click, on the web page, launches it. Every reply to a candidate is approved on your Talent Master page too. Nothing goes out without your approval.

your Talent Master page · example

Launch the sequence · Senior Rust back-end engineer

Send: 6 candidates · 3 emails
Sender: camille@moraine.io (Gmail)
Pace: 150 emails a day at most, 2 to 5 minutes apart, weekdays 9 a.m. to 6 p.m.
Replies: A reply stops the sequence for that candidate.
Notice: Candidate notice: included in the first email, cannot be removed

Launching a sequence: only by your click, on the web page
Reply to a candidate: approved by you on your Talent Master page
Automatic replies: don’t exist
Sending mailbox: yours
Cap per hunt: the one you set
Candidate notice: always
Your decisions train a shared model: no, unless you tick the box

Every reply is approved on your Talent Master page: a single-use link, valid for 24 hours, that opens only once you are signed in. The model cannot send it on its own.

01
Your click launches the sequence. Your replies go through you.
Your click, on the web page, launches the sequence. Every reply to a candidate is shown to you as it will go out, and you approve it on your Talent Master page, through a single-use link valid for 24 hours: the model cannot send it on its own.
02
Your address, your voice.
Emails go out from your Gmail, signed with your name, at a measured pace: 150 a day at most, 2 to 5 minutes apart. Never from a no-reply address.
03
The cost, up front.
Before every hunt and every email lookup, you see the estimated cost and your balance. You set a cap, and it holds.
04
People who said no are not contacted again.
Before any email lookup and any contact, Talent Master checks your suppression list. An unsubscribe counts as a refusal.

The agent’s rules

It puts every send to you: the sequence waits for your click on the web page, each reply waits for your approval on your Talent Master page.
It announces the cost before every hunt and every email lookup, and respects the cap.
It refuses protected criteria and their proxies (age, graduation year, name, photo, address), and says why.
It gives a reason for every candidate it keeps or rejects.
It checks the suppression list before any email lookup and any contact.
It invents no fact, no time slot and nothing about your company.
It writes on your company’s behalf, and says “we”.

04 · The candidate

Your reputation travels with every email.

In a small tech scene, a bad message gets passed around. Here is what the person you contact receives.

From: camille@moraine.io · Subject: A Rust role in Lyon, at Moraine

An email from your address, approved by you.

It comes from your address, in your company’s voice, about a specific role. If they reply, the sequence stops.

A clear notice, from the first message.

It says who is writing, why, and where their profile was found. It states that an AI helped screen it, sets out their rights and gives a separate link to stop being contacted. You can’t remove it.

A booking page with your name on it.

Your logo, your name, your privacy policy. The candidate picks a slot, and can move or cancel it.

05 · Compare

What you are really comparing.

For a startup hiring two or three engineers a year, here are the options and what each one means.

	An agency	An AI recruiter paid on hire	An agent that acts on its own	Doing it yourself	Talent Master
What you pay	Usually 18 to 25% of annual salary, per hire	A percentage of salary, on hire	A subscription, often by quote	Nothing but your evenings	A subscription with credits, no commission
Who writes to the candidate	The agency, in its own name	The platform, on your behalf	The agent, depending on its settings	You	You: it drafts, you approve every sequence and every reply
Where messages come from	The agency’s address	The platform	Depends on the tool	Your address	Your Gmail
What you know before spending	The rate, not the outcome	The rate	The plan price	Nothing	The estimated cost of each hunt, under your cap
Why this candidate	A presentation, rarely the reasons for rejections	An introduction, without the rejected profiles	A score, sometimes an explanation	Your notes, if you take any	A reason for every kept and every rejected profile, which you can dispute
When it’s the right call	Rare searches, very senior roles	You’d rather pay on results	You want to hand off sending	One role, and time to spare	A few tech hires a year, keeping control

An agency

What you pay: Usually 18 to 25% of annual salary, per hire
Who writes to the candidate: The agency, in its own name
Why this candidate: A presentation, rarely the reasons for rejections
When it’s the right call: Rare searches, very senior roles

An AI recruiter paid on hire

What you pay: A percentage of salary, on hire
Who writes to the candidate: The platform, on your behalf
Why this candidate: An introduction, without the rejected profiles
When it’s the right call: You’d rather pay on results

An agent that acts on its own

What you pay: A subscription, often by quote
Who writes to the candidate: The agent, depending on its settings
Why this candidate: A score, sometimes an explanation
When it’s the right call: You want to hand off sending

Doing it yourself

What you pay: Nothing but your evenings
Who writes to the candidate: You
Why this candidate: Your notes, if you take any
When it’s the right call: One role, and time to spare

Talent Master

What you pay: A subscription with credits, no commission
Who writes to the candidate: You: it drafts, you approve every sequence and every reply
Why this candidate: A reason for every kept and every rejected profile, which you can dispute
When it’s the right call: A few tech hires a year, keeping control

The publisher

Talent Master is published by GetPro, a headhunting firm specialised in tech and AI. Talent Master is the search you run yourself. For a rare, very senior or confidential search, GetPro runs it for you, made to measure.

Talk to GetPro

06 · Limits

What Talent Master doesn’t do yet.

01No LinkedIn, no InMails, no SMS: email only, from your own mailbox. Your LinkedIn account is never at stake.
02No ATS sync. Candidate records stay on your Talent Master page.
03Tech and AI roles first.
04Gmail for now.

07 · Pricing

You pay for the hunt. Not the hire.

A subscription that includes credits. Every paid action has a fixed unit price, and its estimated cost is shown before it starts. Never a percentage of salary.

Letter of engagementTalent Master

Agency fee, 20% of gross annual salary

Talent Master subscription, credits included

The prices in force, per action and for the subscription, are shown in the Credits section of your Talent Master page.

Try it on a first hunt. 400 trial credits, valid for 60 days, no card needed: enough for a small hunt (about 180 profiles screened) and about ten emails found. One trial per company.

The brief is free. Reading your documents, asking the questions and catching contradictions costs no credits, and the conversation itself runs in your own Claude.

Your cap. Before every hunt, you set a credit maximum. It holds, and with no credits left, nothing starts.

A search is one role, from job description to interviews. It often takes one or two hunts.

Credits are bought on your Talent Master page, never inside the conversation.

Agreed and acceptedno commission on hire

08 · Connect

Three steps, then your job description.

1
Add Talent Master to your assistant.
2
Sign in with Google: your mailbox and calendar connect at the same time.
3
Paste your job description.

At first sign-in, you give your name and your company’s name, accept the terms, and your trial credits are added.

Before the first send, on your Talent Master page: the calendars to check, your interview hours and your logo. Without them, all your working hours look free.

Add it from my computerConnector URL

https://api.thestaffing.app/mcp

In Claude, open Customize → Connectors, click “+ Add” then “Add custom connector”, paste the URL above and confirm. Then click “Connect” and sign in with Google. In a conversation, turn Talent Master on from the “+” menu → Connectors and paste your job description.

Custom connectors work on every Claude plan, one on the Free plan. On a Team or Enterprise plan, an admin adds the connector for the team, then each member connects.

claude mcp add --transport http talent-master https://api.thestaffing.app/mcp

Then run /mcp to sign in.

What you authorize.

GmailRead and send email. Talent Master uses it to send what you approved and to spot candidates’ replies.
CalendarRead your availability and create events.
Google DriveRequested only if you paste a Drive link.

You can revoke this access at any time from your Google account.

To start

09 · Questions

Frequently asked questions

Does Talent Master send emails on its own?

No. A sequence goes out only after you click on the confirmation page, where you read the email and see the number of candidates and the sending pace. Every reply to a candidate is approved on your Talent Master page, through a single-use link valid for 24 hours: the model cannot send it on its own. Automatic replies don’t exist.

Which tools does it work with?

Claude, or another tool that supports remote MCP servers with OAuth sign-in (not tested by us). For email and calendar: Gmail and Google Calendar, for now.

What do I need to set up before the first send?

Three things, on your Talent Master page: the calendars to check for your availability, your interview hours, and your logo and privacy-policy URL, shown on the booking page.

How much does a search cost?

Every action has a fixed price in credits: a profile screened by the hunt, an email found (nothing if it isn’t found), a personalised first email. The prices in force, and the subscription’s, are shown in the Credits section of your Talent Master page. The brief is free. Before every hunt, you see the estimate and your balance, and you set a cap.

Will it really find good profiles in Europe?

Judge it on your own role. The hunt covers the web and GitHub, and every kept candidate comes with its reason. The 400 trial credits, valid for 60 days with no card needed, cover a small first hunt of about 180 profiles: run it on a real role before you pay anything.

Why not another sourcing tool plugged into Claude, or Claude with a contact database?

Finding profiles has become easy: plenty of tools do it, in Claude or elsewhere. What is rare is a shortlist you can stand behind. Talent Master gives a reason for every candidate kept and every candidate rejected, pressure-tests your brief before anything is spent, writes from your mailbox once you approve, and takes interviews all the way to your calendar.

How does it pick candidates? Can it filter on age or graduation year?

It filters on what the role needs: skills, experience, seniority, location, language. It refuses protected criteria and their proxies (age, graduation year, name, photo, address), and tells you why. Every kept or rejected candidate has its reason, and you can rescue a rejected profile.

What does the candidate see?

An email from your address, in your company’s voice. The first one carries a notice you can’t remove: who is writing, why, where their profile came from, the AI-assisted screening, their rights and a link to stop being contacted. If they reply, the sequence stops.

Where does my data go, and who sees my conversation?

The conversation stays in your Claude account. Talent Master receives only what your assistant sends when it calls one of its tools: the job description, your answers, your choices. Your decisions train no shared model unless you tick the box at sign-up, which is unticked by default.

What access do you ask for on my mailbox and calendar?

Gmail: read and send email. Talent Master uses it to send what you approved and to spot candidates’ replies. Calendar: read your availability and create events. Google Drive: requested only if you paste a Drive link. You can revoke this access at any time from your Google account.

Are interviews recorded?

Not yet. Recording and transcription come right after launch, with notice to the candidate and the right to refuse.

Your next hire starts with a job description.

Add Talent Master, paste the job description, and see what it asks you before anything is spent: the brief is free.

You approve every sequence and every reply · 400 trial credits valid 60 days, no card needed

The accountable headhunter for European tech startups.Every candidate comes with a reason.So does every rejection.

A shortlist you can stand behind.

A headhunter is also judged by who it turns away.

Reasons tied to the role.

A rejected profile can be rescued.

Example: one full search, from brief to interview.

Senior Rust back-end engineer

Launch the sequence · Senior Rust back-end engineer

Collect · A brief that holds up.

Contact · The hunt, then your emails.

Organize · Interviews, in your calendar.

It’s ready. You send it.

Launch the sequence · Senior Rust back-end engineer

Your click launches the sequence. Your replies go through you.

Your address, your voice.

The cost, up front.

People who said no are not contacted again.

Your reputation travels with every email.

An email from your address, approved by you.

A clear notice, from the first message.

A booking page with your name on it.

What you are really comparing.

An agency

An AI recruiter paid on hire

An agent that acts on its own

Doing it yourself

Talent Master

What Talent Master doesn’t do yet.

You pay for the hunt. Not the hire.

Three steps, then your job description.

What you authorize.

To start

Frequently asked questions

Your next hire starts with a job description.