Connecting Loxo

#Sourcing-led search has a CV problem

Loxo tends to sit with teams who build a shortlist outwards rather than wait for one to arrive. Names are researched, approached and talked round; applications are the exception. That changes the raw material. Somebody who applied for a job sends a document tidied up for the occasion. Somebody you found and persuaded sends whatever exists — a file last touched three roles ago, or a PDF exported from a professional profile.

None of that reflects on the candidate, but all of it lands on whoever prepares the submission, and it lands late, when the client is already waiting. Turning four documents of four different provenances into one comparable set is the least interesting hour in a search. It is the hour this connection is aimed at.

#What changes day to day

Your researchers and consultants stay in Loxo. When a candidate is ready to go out, the CV held against them is rebuilt in your firm's design and filed back where it came from, so the record becomes what you submit from. Adding information that was not on the original CV earns more here than on an inbound desk — availability, package, what would actually move them — because that came out of your conversation and was never going to be in the file they sent.

The middle of it is ordinary RemakeCV: see uploading a CV and reviewing and editing.

#Setting it up

1. 1

   Tell us Loxo is where your search runs

   Email support@remakecv.com with your firm's name and a short picture of the current path — who prepares candidate documents today, and what a client receives at the end of it.

2. 2

   Arrange API access on your Loxo account

   Loxo decides what credentials can be issued to you and on what terms. Their answer draws the boundary of what we are able to build against, so it is worth asking early.

3. 3

   Get the credentials to us on a secure channel

   We will point you at one. Anything reaching candidate data deserves the handling you would give a production secret: not plain email, and not left in a shared inbox.

4. 4

   We build it, then switch it on

   Our team implements the connection and enables it for your company. The controls appear in your RemakeCV dashboard, so there is nothing for a researcher or consultant to install.

#Formatting is identical either way

A connection governs how a file travels and nothing beyond that. Your template, the editor, anonymisation, summaries and downloads all work as they do when someone drags a CV into the browser, so adopting one never reopens a decision about your output.

Two features earn their keep on sourced candidates in particular. Neutralising first-person language evens out CVs written in wildly different voices, which is the usual state of a researched shortlist. And checking what was extracted is worth the glance on profile exports and scans, where the source was never meant to be read by anything but a human. If your firm's design has not been built with us yet, our team builds it from your own document — see requesting a custom template.

#If you would rather build it yourself

The platforms with pages here are the ones we are asked about most, not the limit of what we will connect to; if your firm runs something else, including an in-house system, our team builds against whatever credentials that provider issues. Where you have engineers of your own, the public REST API exposes the processing, retrieval and template endpoints directly — see connecting RemakeCV to any ATS or internal system.

#Plans, and where to start

There are two plans, Business and Enterprise, and integration work is included on both — plans and pricing sets out how they differ otherwise. To begin, email support@remakecv.com with Loxo and your firm's name. We will come back with what the connection can do on your account, what we need from you, and how a consultant will use it.