Skip to content
CynestiaCynestia
04How we work

A service your team uses — not a platform your team runs.

We build, deploy, and operate the workflow ourselves. Your team agrees the scope, reviews what arrives, and keeps making the decisions. This page sets out exactly what that involves on both sides.

Four phasesTwo lanes, one mapNo platform to runRecruiters keep every decision
Fig. 01 — the engagement at a glanceFour phases
ASSESSPILOTOPERATEREVIEW
01The journey

Four phases, and exactly whose job is whose.

Every phase shows both lanes side by side: the work we run, and the contribution that has to come from your team. Nothing is agreed in one lane alone.

01

Assessment

First conversation

We look at your database, your open reqs, and your ATS — then tell you plainly what looks recoverable.

Cynestia runs
  • Read the size, age and condition of the database you already have
  • Work through the requisitions you are carrying right now
  • Establish what is genuinely recoverable and what is not
  • Come back with a proposed scope — or a clear explanation of why not
Your side
  • A short conversation
  • A sense of database size and age
  • Two or three live requisitions to look at
You leave this phase with
An honest read on what is recoverableThe scope we would propose — or a clear no
02

Pilot

Scoped first run

A defined first engagement against a set of requisitions, with the criteria agreed before anything starts.

Cynestia runs
  • Connect to your ATS, or take a scheduled export
  • Clean and structure the records inside the agreed scope
  • Match them against the agreed requisitions
  • Run outreach under messaging you have already approved
  • Deliver shortlists carrying their evidence
Your side
  • ATS access or exports
  • Agreed requisitions and shortlist criteria
  • Approved messaging and a point of contact
You leave this phase with
Shortlists against the agreed requisitionsThe activity behind themA clear read on whether to continue
03

Operate

Ongoing

We run the workflow continuously. Your recruiters keep doing the part only recruiters can do.

Cynestia runs
  • Match, contact and confirm continuously against live requisitions
  • Deliver shortlists on the cadence you have agreed
  • Log every interaction against the candidate it belongs to
  • Run and maintain the workflow — there is no platform left for you to manage
Your side
  • Shortlist review time
  • Feedback on what is landing and what is not
  • Updated requisition priorities
You leave this phase with
Continuous matching and reactivationRecruiter-ready shortlistsNo software for your team to maintain
04

Review

Regular cadence

Reporting on what was matched, contacted, and confirmed — and adjustments based on it.

Cynestia runs
  • Report matches, responses, confirmations and shortlists
  • Show plainly what drew a response and what did not
  • Tune matching and messaging against what we learn
  • Escalate anything that needs a decision from your side
Your side
  • A recurring review slot
  • Straight feedback on shortlist quality
You leave this phase with
Activity and outcome reportingTuned matching and messaging each cycle

Terms, scope, and what gets measured are agreed before the pilot starts — so neither side is negotiating after the work has begun.

See who does what
02Who does what

The whole engagement on one page of responsibilities.

Before anyone grants access to a candidate database, it should be obvious where the work sits and where judgement stays. This is that map.

Owns it Contributes– Not involved
Responsibility map: which party owns, contributes to, or sits out each activity in a Cynestia engagement.
What happensCynestiaYour teamTogether
Connect to your ATS, or take exports
Runs the connection
Grants and scopes access
Clean and structure candidate history
Does the work
Match records against live requisitions
Runs continuously
Agree shortlist criteria
Proposes
Confirms
Set together
Approve candidate messaging
Drafts
Approves
Agreed before anything is sent
Run candidate outreach
Operates it
Confirm availability, rate and skills
Runs the conversation
Review each shortlist
Recruiter judgement
Submit, decide and place
Entirely yours
Report on activity and outcomes
Every cycle
Reads it
Tune matching and messaging
Adjusts
Feeds back
Joint call each cycle

The two rows that matter most sit on your side of the line: reviewing each shortlist, and deciding who gets submitted.

Swipe horizontally to read the full map →

The standard
An operated service should be measured by how little it asks of the team it exists to relieve.
01No platform to runThere is nothing for your team to log into, configure, or maintain.
02No decisions movedReviewing shortlists and choosing who gets submitted stays with your recruiters.
03No scope by defaultPhases advance only when the one before has delivered what it promised.
03The footprint

What we need from you — and what we never will.

An operated service should be judged on how little it asks of the team it is meant to relieve. Here is the honest footprint on your side.

Required from you

The full footprint
  • A single point of contactOne person who can agree scope, shortlist criteria, and messaging — and answer questions when the workflow hits an edge case.
  • Scoped ATS access or exportsRead-scoped credentials where the platform supports them, otherwise a scheduled export. Granted by you, revocable by you.
  • Active requisitions to work againstThe workflow needs live roles. The more clearly defined the requisition, the sharper the matching.
  • Agreed shortlist criteriaWhat a submittable candidate looks like for each role — seniority, stack, location, rate band, contract shape.
  • Approved messaging and review timeOutreach is agreed before it is sent, and your recruiters need time to review what arrives.

Never required

Not part of the deal
  • New software or seatsThere is no product for your team to log into, no license to add, and no vendor to onboard.
  • Recruiter retrainingShortlists arrive in the form your team already reviews candidates in. Nothing about their day changes.
  • A data migrationYour ATS stays where it is. We work against it; you are not moving a decade of records anywhere.
  • Write-back into your system of recordNothing is written into your ATS without explicit agreement. What we produce is delivered to your team.
  • A long implementation projectSetup is scoped access, agreed criteria, and approved messaging — not a quarter-long change programme.
What every reporting cycle contains

Matches surfaced

How many candidates the workflow raised per requisition, and on what basis.

Responses received

Who replied, and what they actually said — logged in full, not summarised away.

Candidates confirmed

Availability, rate, and qualification status for each person put forward.

Shortlists delivered

What reached your recruiters, and what they did with it.

The cycle repeats on the cadence you set. Anything unusual in a candidate response is escalated to your point of contact rather than handled silently — and matching or messaging can be changed at any point in the cycle.

Next step

Start with the assessment, not the contract.

The first conversation exists to establish whether your database has anything worth recovering. If it does, you will see the proposed scope before agreeing to anything. If it does not, you will still leave with a clearer picture of your own operation.

No fees before scope is agreed · no access until your team says so