From file archaeology in SharePoint to one current profile per person.
CV database software for consulting and professional-services teams: import every CV once, keep one live profile per consultant, and generate any format on demand.
The problem today
Right now the "CV database" is a SharePoint folder, three inboxes, and a handful of laptops. The same consultant exists as CV_2022.pdf, final_v3_JS_edit.docx, and a LinkedIn profile nobody exported - and none of them is clearly current. That isn't cv data management; it's file archaeology. It bites hardest at the worst moment: a bid manager needing 8 CVs inside a 48-hour tender window, or an account lead promising a client "profiles by tomorrow" and then spending the evening chasing consultants who are busy billing. MagicCV replaces the folder with a database. You import the CVs you already have - Word, PDF, whatever format they accumulated in - and MagicCV parses each into a structured profile, one per person. Updates happen once, on the profile. Every output after that - tailored bid CV, anonymized tender version, translated copy - is generated fresh from the current data, so "which file is the latest?" stops being a question anyone asks.
How MagicCV does it
Import the mess you have, not the data you wish you had
Drop in your existing CV files in any format - Word, PDF, exports from old systems. MagicCV parses each into a structured profile with experience, skills, certifications, and languages as data, not paragraphs. Duplicate files for the same person merge into one profile.
Keep one profile per person - and keep it current without chasing
Each consultant has exactly one profile. When a project ends or a certification lands, it's added once, there - not patched into five documents. AI-assisted updates make the edit a two-minute job instead of a document rewrite.
Search the team like a database, because it is one
The skills matrix makes the whole bench searchable: filter by skill, sector, language, or certification and get people, not filenames. "Who has AWS certification and speaks German?" becomes a five-second query instead of a Friday-afternoon email thread.
Generate any output from the same source of truth
Tailored bid CV, blind CV for a tender, French version for a cross-border proposal - all generated on demand from the current profile, all in your brand template. The output is disposable; the profile is the asset.
Outcome
Before: 20 minutes of folder-diving per CV, multiplied by every bid, with a real chance of sending a client something two years stale. After: one query, one current profile, any format in minutes. The database quietly compounds - every bid gets faster because the last one kept the data clean.
“We used to lose a full afternoon per bid just assembling CVs. Now the pack is ready before the kickoff call — and it actually reads like one firm.”
Elke Bakker
Bid Manager · Nordhaus Advisory
Frequently asked questions
What happens to the hundreds of CVs we already have in SharePoint?
You import them. MagicCV parses Word and PDF files into structured profiles - one per person, even if you have four versions of the same consultant's CV. The old files can stay in SharePoint as an archive; they just stop being the working copy.
How do we keep 200 consultant CVs current without chasing people every quarter?
By making the update small and singular. Each person has one profile, updates are AI-assisted edits rather than document rewrites, and there's nothing to reformat afterward - the templates handle presentation. Most teams fold profile updates into project close-out instead of running a chase campaign.
How is CV database software different from our ATS or HRIS?
An ATS tracks job applicants; an HRIS holds employment records like contracts and payroll data. Neither is built to produce a tailored, on-brand CV for a bid. MagicCV is the layer for your delivery team's experience data - structured, searchable, and instantly exportable as client-facing documents.
Do you integrate with our HRIS?
HRIS integrations (Personio, BambooHR, HiBob) are on the roadmap. Today, file import covers the initial load, and because profiles only need updating in one place, day-to-day upkeep is light even without a sync.
Is a central CV database a GDPR problem or a GDPR improvement?
Done properly, an improvement. MagicCV is GDPR-first with EU data residency, so consultant data sits in one governed system instead of scattered across inboxes and laptops - which makes access control, deletion requests, and audits tractable. Enterprise adds SSO, audit logs, and a DPA.
How many profiles do the plans cover?
Free covers 10 profiles and 30 generated CVs - enough to prove the workflow on one team. Pro ($50/month) covers 200 profiles and 600 CVs, which fits most consultancies up to a couple hundred billable staff. Enterprise is unlimited, with SSO and a DPA for larger firms.
Who maintains the profiles - a central owner or the consultants themselves?
Either model works. Some firms have an ops or resourcing lead own the database; others have consultants update their own profile at project close-out with ops reviewing. Because there's one profile per person and the template controls formatting, contributors can't fork versions or break the layout.
What formats can we generate once the CVs are centralized?
Pixel-consistent PDF and Word exports in your brand templates, plus tailored versions for a specific RFP, anonymized blind CVs for tenders, and translations - all generated from the same profile. Centralizing is the setup; the generated outputs are the payoff.
From scattered CVs to a polished, on-brand pack in minutes.
See it on your own consultants, or start free today - no credit card.
GDPR by design · EU data residency · Free plan, no credit card