Naming the Corpus

A commercial-naming study for the CareerVector job-postings corpus product 2026-05-08

Executive summary

The product is a continuously-scraped, deduplicated, normalized, embedded corpus of job postings, exposed as a search API. Its direct named competitor is Textkernel's Jobfeed; its category neighbour is Coresignal; its archetype-leader is Lightcast. The naming task is harder than a generic SaaS naming exercise because the HR-tech and recruitment-staffing namespace is one of the most saturated commercial verticals on the open web. Most "obvious" {job,talent,hire,career}+{wire,pulse,signal,feed,pool,nest,scout,forge,mint,prism,lens,source,vault,trove,depot,harbor,hive,nexus,atlas,compass,index,reef} compounds are already a live ATS, staffing firm, or scraped-data startup.

Across the ~200 candidates triaged, only a narrow corridor of names survives clean. They cluster into two strategic options:

1. The "labor-market intelligence" lane. Names with the labor- (or labour-) prefix are almost universally clean because the HR-tech ATS herd avoids the word. This positions the product against Lightcast, JobsEQ/Chmura, Indeed Hiring Lab, BLS — a more lucrative buyer (workforce-planning consultancies, governments, sovereign-wealth labor funds) than the recruiter-ATS plumbing buyer.
2. The "obscure-word corpus" lane. Words like granary, gazetteer, trove, foundry, almanac, codex paired with job- are clean because compound-noun saturation hasn't yet reached words people don't use. They tell a "comprehensive collection" story.

Top finalists (ranked):

1. Laborwire / Labourwire — clean, .com plausibly available, LMI-buyer positioning, evokes wire-service heritage (Reuters, AP).
2. Laborcompass — clean, strong LMI metaphor, decision-tool positioning.
3. Jobgranary — clean, "comprehensive corpus" story, no collisions.
4. Laborpulse — clean, "live signal" story, LMI-aligned.
5. Jobfoundry — clean, "we forge curated jobs" story, recruiter-friendly.
6. Joblighthouse — clean, "we surface what matters" story, longer.
7. Jobgazetteer — most-distinctive corpus story; reads literary; obscure but unique.
8. Vocari — clean Latin invented mark; trademark-friendly; abstract.
9. Jobtrove — clean (note: TalentTrove is dead, JobTrove appears free).
10. Laboratlas — clean and LMI-positioned; risks confusion with MongoDB Atlas.

Methodology

Candidates were generated combinatorially: a list of 24 prefixes (job, career, role, talent, hire, gig, work, labor, labour, vacancy, posting, opportunity, recruit, staff, people, position, offer, listing, search, find, match, source, scout, market) was crossed with a list of 60+ second-half semantic families (pool/well/vault, cache/store/depot, wire/feed/stream/signal/pulse, map/atlas/grid/mesh/index, forge/foundry/mint, harbor/dock, nest/hive, watch/lookout/observatory/lighthouse, grove/reef, single descriptors). Roughly 30 single-word standalones (foundry, granary, almanac, codex, opus, fons, locus, agora, bazaar, beacon, atlas, compass, …) and 10 invented marks (vocari, talentum, joborium, careerly, …) were added.

Each candidate received a fast first-pass web-search triage looking for: (a) live HR-tech / ATS / staffing / labor-market brand using the same name, (b) trademark-active company in adjacent sectors, (c) SEO crowding from generic content. Tiers: CLEAN (no major collision), DEFENSIBLE (minor collision, workable), CONTAMINATED (close-but-not-exact, long-list only), DEAD (live competitor or major brand). This is a commercial triage, not legal clearance — finalists still require formal trademark and domain availability checks.

Combinatorial space mapped

• 24 prefixes × 30 representative second-halves = ~720 theoretical compounds.
• ~200 of those triaged on a first pass (clusters of similar suffixes were sampled rather than exhaustively searched once a herd-pattern emerged — e.g. once talent+pool/scout/forge/mint/prism/lens all came back DEAD, full enumeration of talent+* was deprioritized).
• Plus 30 single-word standalones, 10 invented marks, and 5 reverse-form *-labor compounds.
• Full structured data in candidates.json.

Triage results

CLEAN survivors

These are the candidates with no major collision found. Domain availability and trademark search are still required; this is the corridor worth investigating.

Notable DEAD verdicts (with sources)

• Jobfeed — Textkernel (textkernel.com/jobfeed) — the direct competitor.
• Talentpulse — TalentPulse360, Accendo, dMACQ, Retensa, talentpulse.group (talentpulse360.com).
• Talentpool — TalentPools.io, thetalentpool.ai, talentpoolapp.com.
• Talentmesh / Talentgrid / Talentforge / Talentmint / Talentprism / Talentlens / Talentnest / Talentvault / Talenttrove / Talentsource / Talentwell / Talentyard / Talentharbor — all live recruiting/ATS products.
• Jobhive (.ai/.io/.com) — three competing products.
• Hirewire / Hirestream / Hirescout / Hirewell / Hirehive / Hireharbor — all live.
• Jobcompass — JobCompass.net, JobCompass.ai, JobCompass.pro.
• Jobindex — Jobindex A/S, the largest Danish job portal since 1996.
• Jobatlas — JobAtlas.de career-guidance platform.
• Jobsignal — JobSignal.work and thejobsignal.com.
• Talentscout — Indeed's flagship AI recruitment agent.
• Talentum — multiple active recruiters.
• Opus — Opus Recruitment Solutions, Opus Advisors.
• Jobspring — now Motion Recruitment.

Positioning archetypes

Each surviving name tells one of five stories. The archetype matters more than the specific word: it determines which buyer you fight for.

Corpus story — "we have the comprehensive collection"

Granary, gazetteer, trove, codex, almanac, compendium, chronicle, foundry. Buyer hears: "everything is in there, including the long tail." Best for buyers who pay for coverage breadth — labor-market consultancies, sovereign workforce planners, academic researchers.

• Best in class: Jobgranary, Jobgazetteer, Jobfoundry, Talentchronicle.

Feed story — "we have the live stream"

Wire, feed, stream, signal, pulse. Buyer hears: "we deliver hiring intent the moment it appears." Best for sales-intelligence buyers (Crustdata, Autobound), B2B prospect-trigger buyers, real-time analytics.

• Best in class: Laborwire, Laborpulse, Hirefeed, Rolewire.

Cache story — "we have the queryable index"

Cache, base, ledger, registry, depot, store. Buyer hears: "data API, you write SQL." Best for engineering-led buyers (HR-tech vendors building ATS features, devtools).

• Best in class: Jobcache, Jobledger, Laborbase, Talentregistry.

Market story — "we are labor-market intelligence"

labor- prefix family — labormap, laborcompass, laboratlas, laborindex. Buyer hears: "Lightcast competitor." Best for the highest-margin enterprise buyers — McKinsey/BCG workforce practices, sovereign funds, OECD/EU stat agencies, large HR-strategy consulting.

• Best in class: Laborwire, Laborcompass, Laborpulse, Labormap, Laborindex.

Discovery story — "we surface the good ones"

Scout, lookout, observatory, lighthouse. Buyer hears: "we find what matters in the noise." Best for downstream curated-jobs buyers, talent-marketplace builders.

• Best in class: Joblighthouse, Joblookout, Talentobservatory.

Special section: the labor-market positioning angle

This is the single highest-leverage strategic decision in the naming exercise.

The recruiter/ATS buyer is what Jobfeed targets. Average ACV is in the €1–10k range. Sales is bottom-up SaaS. Buyer cares about: deduplication quality, posting freshness, ATS integrations, search relevance. The competitive set is Coresignal, JobsPikr, TheirStack, Techmap, Crustdata, Bright Data — well-funded and aggressively priced.

The labor-market-intelligence buyer is what Lightcast (formerly Burning Glass + Emsi), JobsEQ/Chmura, Indeed Hiring Lab, and the Chinese/EU stat-bureau commercial wings target. Average ACV is €25–250k+. Sales is enterprise/government RFP. Buyer cares about: longitudinal coverage, occupation taxonomy alignment (ESCO, O*NET, ISCO-08), wage-data triangulation, geographic granularity, methodological transparency. Margins are dramatically better. The competitive set is much smaller and slower-moving.

The same scraped-and-normalized job corpus serves both buyers — but the name pre-commits you to one. A name like Laborcompass or Laborwire immediately tells a procurement officer at a labor ministry, a workforce-strategy partner at a Big Four consultancy, or a Lightcast competitor scout: "this is in the LMI category." A name like Jobfoundry or Hirefeed tells the same officer: "this is HR-tech plumbing, talk to our IT department."

The labor-market-intelligence framing also has a Switzerland-first home advantage. SECO (State Secretariat for Economic Affairs), KOF Konjunkturforschungsstelle (ETH Zurich), and Bundesamt für Statistik are existing customers of LMI-style products. Coming out of CH with a German-readable name (Labourwire, Labourcompass) is uniquely well-positioned for European public-sector entry.

Recommendation: anchor the name to the labor-market lane. Not because the recruiter-ATS lane can't be served, but because a labor-market-positioned name can sell into recruiter-ATS just fine (Lightcast does), whereas a recruiter-ATS-positioned name struggles to upsell into ministries.

Final recommendations

Top 3 picks ranked

1. Laborwire (or Labourwire) The strongest candidate. The "wire" suffix has a centuries-old commercial pedigree (telegraph wire-services like Reuters and AP) that maps perfectly to "we deliver continuous, deduplicated, normalized signal." It positions the product unambiguously as labor-market intelligence rather than ATS plumbing, which puts CV in the higher-margin enterprise lane. The name is short, English-readable, sounds professional, and carries no major brand collision in the labor or HR space (Marketwire was a defunct press-release service). The UK/CH spelling Labourwire is also clean and gives a localizable second mark for European positioning. Best optionality across both ATS and LMI buyers.

2. Laborcompass The decision-tool framing. "Compass" suggests "we help you orient in the labor market" rather than "we deliver a stream." This lands well with strategy-consulting and workforce-planning buyers, who buy direction more than data. JobCompass cluster is dead, but laborcompass itself is clean. Slightly heavier than Laborwire; carries less ambiguity about what the product does.

3. Jobgranary The strongest pure-corpus story. "Granary" is unusual enough that it's almost certainly trademark-clean and SEO-uncontested. It tells the comprehensive coverage story: "everything's stored here, even the seed-corn." Best pick if you want to fight in the recruiter-ATS lane against Jobfeed/Coresignal directly rather than pivot to LMI. Risks: agricultural connotation may feel quaint to enterprise buyers; English-reading required (German speakers may not recognize it).

Decision matrix — if you optimize for X, pick Y

Required next steps before committing

1. Domain availability check (.com, .io, .ch, .eu) on top 3.
2. EUIPO + USPTO + IPI (Swiss) trademark search on top 3 in classes 9 (software), 35 (employment services), 42 (SaaS).
3. Quick whois on parked domains — often a parked domain is acquirable for $500–5000 and is not a real obstacle.
4. Linguistic check: does Laborwire read well in German, French, Italian? Labourwire may be the safer multilingual variant for European entry given that the German "Labor" means laboratory, not work.

One important caveat about "Labor" in German-speaking markets

In German, Labor means laboratory, not work. Labourwire with the British/CH-French-friendly "u" reads more naturally to a Swiss audience. Arbeitswire / Arbeitscompass would be the literal translation but reads awkward and isn't English-export-friendly. The recommendation stands: use the English mark Laborwire (or Labourwire) but be aware that on-the-ground German marketing will need to gloss it as "Labor (engl.) = Arbeit" the first few times. This is a feature, not a bug — it telegraphs the international/English-first product positioning.

Decision (2026-05-08)

Picked: jobcache — accepting the engineer-buyer-lane positioning from the decision matrix. Initial deploy at jobcache.corbet.ch.

Rationale: technically accurate (the corpus literally is a refreshable cache of upstream postings), short, phonetically clean, no HR-vertical brand collision, and lands well with HR-tech engineering buyers integrating the API. The LMI repositioning (Laborwire/Laborcompass) was tempting but commits to a different sales motion and buyer persona than a one-person operation can serve in the near term.

Rebrand-friendly architecture mandate

The decision is provisional. The codebase must be rebrand-ready so a future move to Laborwire, Jobgranary, or any other finalist costs hours, not days:

• The product name appears only in user-facing surfaces: the dashboard title bar, the <title> tag, marketing copy, the public domain. Centralize these in a single config (config.brand.name, config.brand.domain).
• Folder name jobcache/ is fine — folder renames are a single git mv.
• Do not use the brand name in: database schema (table names, column names), package/module names (@cv/<...>), API path segments, environment variable prefixes, code identifiers, log fields, or class names. Use neutral terms instead — corpus, postings, adapters, ingest, feed.
• HTTP routes are fine being neutral (/api/jobs, /api/adapters/health); the brand only appears in the served HTML and on the public domain.
• Database migrations should never reference the brand name in column comments or seed data.

The cost of a future rebrand should be: edit one config file, change DNS, redeploy. Nothing else.