Skip to content
CynestiaCynestia
03Capabilities

Three more ways to get value from the database you already have.

Candidate Database Reactivation is the core engagement. These modules run on the same cleaned records and the same operating layer, for the desks where the database needs to move faster than a reactivation cycle allows.

Three operated modulesOne cleaned databaseScoped and priced separatelyRun on the same layer
Fig. 01 — the three modules at a glanceOperated flows
01Speed-to-Submission
NEW REQYOUR DBMATCHEDSUBMIT
02Contractor Redeployment
END DATERE-ENGAGECONFIRMDEPLOY
03Compliance & Operational Visibility
LOGGEDREVIEWEDREPORTED
01Module 1 of 3

Speed-to-Submission

When a new order lands, surface the candidates you already have — before anyone opens a sourcing tool.

The moment it matters

A new contract React order lands at 10:14 on a Tuesday.

Without this workflow

The requisition enters the sourcing queue. The first recruiter with capacity opens a job board and starts from zero — while three competitors do exactly the same thing.

With this workflow

Ranked candidates from your own database arrive against the requisition while it is still fresh: people you already know, each with the reason they surfaced.

Workflow schematicOperated flow
NEW REQYOUR DBMATCHEDSUBMIT

Runs continuously alongside reactivation. Most valuable where requisition volume is high and time-to-first-submission is the constraint.

How it runs
  1. 01A new requisition enters your ATS and is picked up by the workflow.
  2. 02The existing database is searched against it while the req is still fresh.
  3. 03Known candidates — placements, past submissions, prior conversations — are ranked with reasons.
  4. 04Your recruiter works from a list of people they already own, not an empty sourcing tab.
What your team receives
  • Ranked existing candidates against each new requisition
  • A recorded match reason attached to every name
  • A submission-ready pool drawn from records you already paid for
Where it stops

It does not source externally or contact candidates you have never worked with. This module draws exclusively on your own history.

02Module 2 of 3

Contractor Redeployment

Track upcoming availability across your contractor book and redeploy known talent into new orders.

The moment it matters

A consultant’s assignment ends in twelve working days.

Without this workflow

The end date sits in a spreadsheet or in one recruiter’s head. Nobody spots it, and the consultant signs something else before your desk makes the call.

With this workflow

The window is tracked, the consultant is re-engaged with what is currently open, and availability and rate are confirmed before anyone is put forward.

Workflow schematicOperated flow
END DATERE-ENGAGECONFIRMDEPLOY

For desks with a meaningful contract book where redeployment is a recurring revenue line rather than an occasional win.

How it runs
  1. 01Assignment end dates and availability windows are tracked per consultant.
  2. 02As an end date approaches, the consultant is re-engaged with what is currently open.
  3. 03Availability, rate, and interest are confirmed before anyone is put forward.
  4. 04Confirmed consultants are matched against open contract orders.
What your team receives
  • A forward view of upcoming consultant availability
  • Confirmed-availability contractor lists against open orders
  • A re-engagement history for every consultant on the book
Where it stops

It does not manage contracts, payroll, or compliance for your contractors. It keeps the redeployment conversation from being missed.

03Module 3 of 3

Compliance & Operational Visibility

Interaction records, human oversight, and reporting around every AI-assisted workflow we operate.

The moment it matters

An operations leader asks what the AI-assisted workflow actually did last month.

Without this workflow

The honest answer is a black box: a ranking nobody can audit, a handful of exports, and a lot of trust placed in the vendor.

With this workflow

Every match, message and response is logged against the record it belongs to — with the human review points visible, dated, and reported.

Workflow schematicOperated flow
LOGGEDREVIEWEDREPORTED

Not an add-on. It is how every engagement we run is instrumented, in place from the first day of the pilot.

How it runs
  1. 01Every match, message, and response is logged against the record it belongs to.
  2. 02Shortlists pass human review before they reach your recruiters.
  3. 03Oversight points — what the system may do, and what requires a person — are agreed up front.
  4. 04Activity and outcomes are reported on a cadence you set.
What your team receives
  • A full interaction log per candidate and per requisition
  • Oversight rules your team sets and can change
  • Regular reporting on matches, responses, confirmations, and shortlists
Where it stops

It does not certify legal compliance or replace your policies. It makes your own controls visible, enforced, and auditable.

The model
A module is not a product you license. It is a workflow someone operates for you, on your data, to your rules.
01Processed onceYour records are cleaned and structured a single time, then shared across every module.
02Scoped separatelyEach module is priced and run on its own terms — add one without reopening the rest.
03Instrumented the sameEvery module logs matches, messages and reviews against the record they belong to.
02How they compose

One operating layer. One cleaned database. One set of records.

The reason adding a second module does not double the cost: the expensive part — cleaning and structuring a decade of candidate history — happens once, and everything above it shares the result.

Fig. 02 — three modules, one layer
SPEED-TO-SUBMISSIONtrigger: a new orderCONTRACTOR REDEPLOYMENTtrigger: an assignment end dateCOMPLIANCE & VISIBILITYtrigger: every workflow runONE CYNESTIA OPERATING LAYERmatch · re-engage · confirm · log · reportONE CLEANED CANDIDATE DATABASEprocessed once · shared across every module · yours throughout

Swipe horizontally to read the full diagram →

03Choosing between them

Which module answers which question — before you decide.

Most agencies arrive with one of these problems uppermost. The table below is the shortest honest route to knowing which module is worth running first.

Comparison of the three Cynestia modules across trigger, output, audience, deliverable, cadence and limits.
Dimension01Speed-to-Submission02Contractor Redeployment03Compliance & Visibility
What triggers itA new requisitionAn approaching assignment end dateEvery workflow run
What it surfacesRanked candidates from your own databaseConsultants about to become availableMatch, message and review records
Who it servesRecruiters racing to submitDesk leads running the contract bookOperations and compliance leads
What you receiveA submission-ready pool, each with its match reasonA confirmed-availability list per open orderA full interaction log and recurring reporting
CadenceContinuously, alongside reactivationIn step with your contract bookFrom the first day of the pilot
Not designed forExternal sourcing or cold listsContract, payroll or compliance administrationCertifying legal compliance

All three run against the same cleaned database and the same operating layer — so adding a second module never means paying to process your records again.

Swipe horizontally to read the full table →

Next step

Tell us which of these is actually your problem.

One conversation about your requisitions, your contractor book, and the state of your database. If none of it applies, we will say so — and you will have a clearer read on your own operation either way.

Assessment first · modules scoped to your desk, never bundled