Case studies
Taleva

Case study · Designed with Taleva

Agent-to-agent hiring: a negotiation layer for the talent market

Candidate agents and employer agents negotiate fit, salary and conditions privately. The first human meeting starts from an agreed term sheet.

Built with
Taleva · taleva.io
Sector
Recruitment software / AI talent sourcing
Scope
An agent-to-agent negotiation layer on the Taleva platform
Status
Joint research, in development

In short

Taleva's Talent Compass turns a plain-language brief into a ranked, contactable shortlist drawn from 900 million profiles across twenty-plus sources. This study is about the step after the shortlist: how first contact happens. Together we designed an agent-to-agent hiring layer. A candidate agent and an employer agent each carry a mandate their human signed. The agents prove their constraints overlap without revealing them, negotiate terms inside those mandates, and hand both humans a finished term sheet.

Below: the design, the bench we ran it on, and what has to be true before a market like this works.

Agent-to-agent hiring was one line on a long list of ideas. We now have a much clearer picture of where Taleva goes next.
Marcos Juncá · Co-founder, Taleva
11,000/min
applications hitting LinkedIn, up 45% year on year
8%
of job seekers who believe AI screening made hiring fairer
14%
of deal value lost by the side with the weaker agent
0
terms revealed to either side before the ranges provably overlap

01

Application volume is breaking hiring for both sides

Candidates apply more and hear back less. Employers receive more and trust less. The volume itself is the problem.

LinkedIn processes eleven thousand job applications a minute, up forty-five percent in a year. Three quarters of candidates use AI on their applications; two thirds of hiring managers say they have caught deceptive AI use; four in ten candidates admit to planting prompt injections aimed at the screening software. Greenhouse's CEO calls it the AI doom loop. His own data says only eight percent of job seekers believe any of this made hiring fairer.

Market telemetry
Taleva
0
applications submitted since you opened this page (at LinkedIn's published rate)
Interviews per 50 auto-applications1
Postings that are ghost jobs~1 in 5
Candidates who trust the screen8%

Applying got easier and getting hired got harder, and those are the same fact.

These problems have one cause: both sides broadcast at each other. Candidates mass-apply, employers mass-post, and most of the contact that results was never going to go anywhere. Better filters do not fix a broadcast problem. The fix is to check fit on both sides before contact happens.

02

Taleva already runs the half of this that exists

An agent market needs somebody who can stand behind both sides. A sourcing platform that a hundred recruitment firms already trust is the natural party.

Describe the hire in natural language, and Talent Compass searches twenty-plus sources, ranks every candidate against the brief with the reasoning attached, enriches contact details, and syncs the pipeline into the ATS. GDPR-native, built in Europe for Europe. The step after the shortlist is the one nobody in the market has built yet. First contact, on any platform, is still a message into a crowded inbox.

The pipeline today
Talevasearch.taleva.io
1Search

Semantic search over 900M+ profiles across 20+ sources. Meaning, not keywords.

2Review

Talent Compass ranks every candidate against the brief, reasoning attached.

3Contact

Verified emails and phones. Personalised multi-channel outreach.

4Pipeline

Synced into eight ATS / CRM systems the firm already runs.

Next act

Today: outreach by message.
Next: agent-to-agent negotiation. Contact once fit is proven.

The most sophisticated sourcing in the market still ends in a cold message, because there is nothing on the other side to talk to.

03

We put the mandate before the agent

The first thing we designed was not the agent. It was the instrument that limits what the agent is allowed to do, because the recorded failure of autonomous negotiators is that they exceed their instructions.

Stanford's benchmark of agent-against-agent commerce found agents committing their principals to terms outside the limits they were given. In one recorded case an agent closed a purchase at nearly double the user's budget. So the unit of this design is the mandate: a signed, machine-verifiable envelope of band, non-negotiables and expiry, following the pattern Google's AP2 protocol established for agent payments. A commitment without a covering mandate is invalid by construction, not by policy.

Two signed mandates
TalevaMandate service
LR
Candidate mandate
Backend engineer · Barcelona
✓ Signed · principal verified
Reservation band€58,000 – €72,000
Remote≥ 3 days / week · hard
Earliest start2026-10-01
Do not contactCurrent employer + 2 firms
Expires30 days
did:tal:cand:8f3a…c1 · sig 0x4e91…7b · KYA credential chain valid
NV
Employer mandate
Series B fintech · role #2214
✓ Signed · role approved
Approved band€60,000 – €78,000
Hard requirementsEU work rights · Python · on-call
Hiring managerCounter-signature required
Budget authorityVP Eng · verified
Expires45 days
did:tal:org:2214…9d · sig 0xa07f…33 · ghost-check: role has a signer
counter-offer €82,000: rejected by mandate service. Outside the signed envelope; the agent cannot say yes to this, and neither can a prompt injection.

An agent that can exceed its mandate is not an agent. It is an unsecured signature.

04

Fit is proven before anything is revealed

Neither side states its real number first, because whoever does gives ground. The match check removes that problem. If there is no match, nothing is revealed to either side.

Each agent submits its constraints to a private-set-intersection check. The only thing either side learns is whether the two envelopes overlap. If they do not, the negotiation never opens, and neither side finds out the other's band or how close it came. Drag either band below to see it work.

The overlap check · interactive
TalevaPrivate match

C Candidate agent

Own band (private)
58k – €72k
Employer's band, as seen from here
0
No overlap
Neither side has learned anything.

E Employer agent

Own band (private)
40k – €54k
Candidate's band, as seen from here
Envelopes overlap. Only now do terms surface, and only inside the negotiation.

05

The negotiator is a solver; the language model is its voice

Language models on their own are poor negotiators, and the research is consistent about it. The design gives the negotiation to a solver and keeps the model for the language.

Model-against-model negotiations resolve near whoever anchored first. So in this design the language model never chooses a number: offers, counters and concession schedules come from a bargaining solver, computed from the mandate envelope, the disclosed band, and the compensation comparables Taleva already holds. Every exchange is signed, logged and replayable. The audit trail the EU AI Act requires is also the debugging tool, the bias-audit substrate and the dispute record.

A negotiation, replayed
TalevaNegotiation #0491 · replay
Candidate agent
Opening within mandate: €70,500 base, 3 remote days, start Oct 1. Comparables attached: p60 for the role band in Barcelona.
solver: open @ p60 · envelope €58–72k · sig ✓
Employer agent
Counter €63,000, 2 remote days. Role budget verified; band midpoint p45 on the same comparables.
solver: counter @ p45 · envelope €60–78k · sig ✓
Candidate agent
€67,500 with remote ≥3 held. Remote is a hard term, so €1,500 of base is traded to keep it.
solver: concede 42% of gap · hold hard term · sig ✓
Employer agent
Accept remote 3 days. €66,000 base, review at 6 months written in. Converging.
solver: accept hard term · concede 50% · sig ✓
Candidate agent
Agreed at €66,500, remote 3 days, Oct 1, 6-month review. Escalating to principals for counter-signature.
solver: settle @ 0.51 of ZOPA · both envelopes satisfied · sig ✓
Concession curve · computed, not improvised
€72k · candidate ceiling€60k · employer floor€66.5k
Solver state
ZOPA (private, proven)€60k – €72k
Settlement point0.51 of zone
Hard terms heldremote ≥ 3d ✓
Anchoring exposuresolver-capped
Audit spine
Messages signed5 / 5
Mandate violations0
Replayableend-to-end

06

The humans come in at the term sheet

The output of an agent negotiation is a draft term sheet. The humans decide whether it becomes a hire.

When a negotiation converges, both sides receive the agreed terms, the evidence behind them, and the full signed transcript. The interview goes ahead as normal, with the terms already settled.

The term sheet
Taleva
Term sheet · draft for counter-signatureNEG-0491 · 2026-08-06
Base salary€66,500
Remote3 days / week
Start date1 October 2026
Compensation reviewAt 6 months, written
Negotiated byTaleva agents, within signed mandates
Verified in negotiation: EU work rights · 5 years of Python, checked against public code · role approved and budgeted
Candidate
Hiring manager

07

Symmetry is the product

Everyone else in this market builds for one side. A two-sided platform can give both sides equally capable agents, so the outcome depends on the fit rather than on who has the better software.

Employer-side agents are well funded and widely deployed. Candidates have little beyond auto-apply tools and interview coaching. Stanford's benchmark says what that gap does: in agent-to-agent bargaining the weaker agent's principal pays, up to fourteen percent of deal value. On this platform both sides run the same negotiator. Same solver, same mandate protection, same audit trail; what differs is only what each principal authorises.

What asymmetry costs
Taleva
Employer agent capability →
0%
4%
7%
11%
14%
4%
0%
4%
7%
11%
7%
4%
0%
4%
7%
11%
7%
4%
0%
4%
14%
11%
7%
4%
0%
↓ Candidate agent capability · cell = surplus transferred to stronger side
Balanced: surplus follows fit, not firepower.
Asymmetric: the weaker side's principal pays, every time.
The platform's job is to keep every negotiation on the diagonal, where both agents are equally capable.

If one side has the better agent, the other side pays for it.

08

The pilot starts inside Taleva's network

We worked this design through with the Taleva team, down to how a first deployment would run. It does not need a new market to exist; it runs on the network Taleva already has.

Taleva's recruitment firms bring both sides of the pilot: the roles they are filling, and the candidates they already represent. A candidate's band and non-negotiables, collected at registration the way agencies already collect them, become the first signed mandates. From there the build is five components.

Mandate service
Signing, verification and expiry for both envelope types; the AP2-pattern credential chain.
Overlap check
The private-set-intersection match on band and hard constraints; one bit out.
Offer engine
Solver-computed positions from envelope, comparables and disclosed band; model-carried language.
Audit spine
Signed, replayable transcripts feeding the bias audit and the AI-Act file.
Handoff surface
The term sheet lands in the recruiter's existing Taleva pipeline view. The tool people already open is the only place a new artifact survives.

Nobody has shipped this market yet. The party that already owns one side of it goes first.

Which market do you own one side of?

If your product owns one side of a market, the negotiation layer is your next act. A call with us is enough to see what it looks like.