CV parsing & ranking
Very high volume · fixed schema · repetitive
Pull structured fields off an inbound CV and score it against the live brief for a consultant to review.
One approved place for the AI work your consultants do.
Candidate CVs and client hiring plans are one paste away from a tool nobody approved, and nothing in that tool tells you it happened. Banning it costs you the speed. One approved workspace at your own address, run for you and inside your perimeter, does not.
AI arrived before the policy did.
A consultant with a desk full of live roles reaches for whatever gets the next shortlist out faster. If nobody signed that off, nobody can say which candidate records went where. A policy that only bans public tools tends to move the usage somewhere less visible rather than stop it. The problem is not adoption; it is control.
- No way to tell which candidate records went into an unapproved tool
- Individual AI subscriptions arriving one by one on expenses
- An AI policy that restricts public tools, with nothing offered instead
- Clients asking what your AI and data policy actually says
Both halves of the bill.
ai.yourcompany.com
Your consultants are almost certainly using AI already. Candidate CVs, client briefs and interview notes go into whatever tool is open in a browser tab, and the subscriptions turn up on expenses. A workspace at your own address gives them a sanctioned place to do the same work: unlimited use at one flat price per person, 60% less than a premium per-seat licence, and the work on infrastructure you control.
- Recruitment consultants
- Resourcers and researchers
- Client account managers
- Compliance and payroll
- Bids and marketing
api.ai.yourcompany.com
This half is the smaller one in a recruitment group. It is your own systems calling one endpoint: the applicant tracking system, the CRM, the payroll and compliance stack, and the jobs below that repeat all day. Runvo operates it under a UK entity with data residency in the region you name, so your firm never becomes an AI infrastructure team.
Both addresses run on one deployment and one bill: the workspace flat per person, endpoint volume on real usage.
The jobs worth running as volume.
These are not the things a consultant does once in a chat window. They repeat all day, in the same shape every time, which is what makes them worth moving in recruitment and staffing.
Candidate submission notes
High volume · short output · reviewed
Draft the client-facing summary from the CV, the interview notes and the brief.
Job spec & advert drafting
High volume · templated · batch
Write the job spec and the adverts from the intake call.
Interview & call notes
Very high volume · batch · non-interactive
Turn the raw notes and the transcript into a structured record on the candidate file.
Right-to-work documents
High volume · fixed schema · reviewed
Read the uploaded document, pull the fields onto the candidate record, and flag what is close to expiry.
The same AI, bought two ways.
Where the work happens
Whatever tab was already open
One workspace on your own domain
Candidate and client data
Leaves the perimeter
Stays inside your perimeter
Cost per person
Per seat, licence by licence
One flat price, unlimited use
Who runs it
Nobody in particular
Runvo, under a UK contract
When a consultant leaves
The account goes with them
You disable one login
Repetitive volume jobs
Done by hand, one at a time
Run through your own endpoint
Illustrative. Which of these matter to you depends on how many people you have, what they are using today and which jobs actually repeat. That is what the assessment establishes.
One
Approved workspace
One address on your domain to point people at.
0
CVs exported for inference
The workspace runs inside your own boundary.
Fixed
Cost per person, per month
Unlimited use inside that price.
What we treat as non-negotiable.
A person still decides
The workspace drafts, extracts and ranks; it does not decide. No candidate is put forward or rejected on a model’s output alone, and the right-to-work check itself stays with your compliance team.
Not every job moves
Volume and repetition are the test. Work that happens once, or that genuinely needs a frontier model, is better left where it is, and Runvo says so before you sign anything.
An alternative, not enforcement
Runvo gives your people a sanctioned place to do this work. It does not block websites, monitor laptops or police browsers, and it cannot stop someone opening a public tool. What changes is that the approved route is now the faster one.
Tell us what you run in recruitment.
We start from your real traffic (volumes, prompt shapes, quality bars and latency targets) and tell you which workloads are worth moving. If none of them are, we say so.
Talk to Runvo
Tell us the size of the firm and what your client contracts require.