Candidates
Your CV database is a lead list you already paid for.
Drop in a CV. OutputX reads it, works out what kind of role that person fits, and matches them against every live vacancy and hiring signal on their patch. Then it writes the spec-out. No forms, no manual tagging.
A name and a file. That's the whole input.
Shared skills shown on every match. The "why" is never hidden behind a score.
The stuff you do daily. In one click.
- Match
- A CV becomes a ranked list of live vacancies and pre-advert signals that fit, with the shared skills shown as the reason. Works the other way too: paste a role, find the people in your pool who fit it.
- Sell in
- One click blends the candidate into an outreach draft for any opportunity. The best fits are suggested for each lead before you've even opened the picker.
- Anonymise, or don't
- Built in, on by default. The candidate is described, never named, and their name is scrubbed before drafting so it can't leak through. Naming them is a deliberate untick, made when the client bites.
- Spec-out written for you
- The classic play, automated: the pitch leads with the person, in your voice, to a named decision maker.
- Dead ends become searches
- Nothing matching? It proposes three concrete searches to run for that candidate, each one click from running.
Compliance is built in, not bolted on
Consent is a gate
A CV can't be uploaded until you confirm your lawful basis as controller, and the confirmation is timestamped as audit evidence. OutputX acts solely as your processor.
Deleting means deleting
One click destroys the file and the record. Right to erasure, actually implemented.
Pools are private
Each consultant's candidates are isolated, enforced in the data layer, not just hidden in the interface.