proof of concept
Recruitment Consultancy
Bespoke extensions for CV work, built on Corey for one consultancy's pipeline.
We do not publish the names of businesses we build for. This entry is described by what the business does.
- Status
- proof of concept
- Ownership
- The consultancy
- Operated by
- The consultancy
- Stage
- Built and unpaid. A Corey engagement, anonymised by choice.
What it is
A recruitment team spent most of its week on the mechanical half of the job: reformatting CVs into a house template, and pulling candidate detail out of documents that were never structured for it.
Two bespoke extensions on top of Corey. One builds CVs into the consultancy's own house format; one reads candidate documents and turns them into structured records. Reusable parts stayed in the shared engine; the specialised work is theirs.
True today
- Two bespoke extensions were built and handed over.
- The specialised work belongs to the consultancy.
- Reusable parts stayed in the shared engine.
Not true yet
- It is unpaid. This was a proof of concept, not an engagement.
- We have not asked to name them, so we do not.
Image placeholder
A CV rebuilt into the house format. Left empty until a real screen earns it, and until it can be shown without identifying anyone.
What this demonstrates
What a bespoke build on Corey looks like: the customer keeps what was built for them, and the reusable half stays in the engine. The work was Corey's, which is the distinction this entry exists to keep straight.