Kepler vs Invenias: which should an executive search firm choose?

What Kepler and Invenias each are

Invenias by Bullhorn is executive search software. Bullhorn describes it on its product page as “a leading boutique executive search platform” with eighteen years in market, 700+ global customers and 10,000 users. Bullhorn acquired Invenias in July 2018 and sells it today alongside a second, larger product: Bullhorn’s executive-search page offers “Invenias by Bullhorn for boutique firms” and “Bullhorn Recruitment Cloud for enterprise firms”, and invenias.com now redirects to Bullhorn’s Invenias product page. Anyone quoted for “Bullhorn for executive search” in 2026 should establish which of the two the quote covers, because they are different systems.

Invenias is organised around the assignment. Its documented feature set covers longlist building against target companies, off-limits policies, candidate summaries produced as branded deliverables, bulk GDPR consent requests carrying a purpose and a lawful basis, a business-development pipeline, a client portal, and analytics through Invenias Analytics or Power BI. It has always been Outlook-anchored and still is: Bullhorn’s system requirements list a Windows 11 desktop application working with Microsoft Office 2016, 2019 or 2021, alongside a browser-based web app and iOS and Android apps.

Kepler is a recruitment CRM built around a single assistant and a searchable database. One agent sits in a sidebar on every page, reads the whole workspace — candidates, CVs, notes, email threads and call transcripts — and can create and update records once a person approves the change. Around it sit the ordinary parts of a desk: pipelines, jobs, tasks, email and calendar sync, a notetaker, CV parsing and formatting, a branded job board, reporting, campaigns and automations. Kepler is not built for retained executive search, and the section below says exactly what that costs a search firm.

The real difference: an Outlook desktop application and a browser database

Invenias’ centre of gravity is the Windows desktop application. Bullhorn’s own Web Application FAQ is direct about it: the Essentials web app lets users “perform the most important actions in a search process” from any device, but “Essentials is not an alternative to the Professional Desktop Application”, and research teams and power users “will likely continue to leverage the power of the existing desktop application”. Full parity is stated as a long-term goal; as of September 2026 Bullhorn does not claim it has arrived.

That has consequences a buyer feels in the first week. The Invenias desktop application requires Windows 11 64-bit, a stack of .NET runtimes, and an Invenias Control Panel process kept running in the system tray. Bullhorn’s FAQ notes that a licence covers up to five registered devices and that the Outlook application requires a user to be logged into one PC at a time. Mac users are directed to the Essentials web app plus the Office 365 add-in — that is, to the version Bullhorn itself says is not a replacement for the full one.

Kepler is one responsive web application. There is no installer, no desktop client, no per-device registration, no Windows requirement and no reduced edition: the browser app is the product. The trade is real and worth naming — Kepler has no native mobile app at all, while Invenias ships iOS and Android, and Kepler has no Outlook add-in for filing an email from inside Outlook. Kepler syncs Gmail and Outlook mailboxes two-way and links threads to the right record, which is a different workflow from working inside the inbox. A search firm whose partners genuinely live in Outlook should weigh that seriously.

What each product’s AI does today, and what is still on the roadmap

Bullhorn published an Invenias AI roadmap on 16 June 2026, and it is unusually clear about what is shipped and what is not. Stage one is available now: natural language search, AI-powered candidate matching that “surfaces relevant ranked and contextualized profiles”, document search across CVs, proposals and assessments, and relationship intelligence that maps connections across a firm’s network. Stage two, “coming next”, is where AI “analyzes call transcripts or notes and automatically updates records”, together with a conversational action execution engine. Stage three, later, is proactive agents — a pipeline monitor and a sector intelligence agent that drafts a pre-ranked longlist.

Separately, the Invenias AI Assistant — formerly Copilot — is documented as an optional feature on Person and Assignment records in the Invenias web application, enabled by request through an Account Manager. It uses a “bring your own model” design: an administrator chooses OpenAI or Azure OpenAI and enters the firm’s own credentials, so Bullhorn does not host or control the model. That is a defensible architecture, and it also means part of the AI bill is the customer’s cloud bill and the assistant is scoped to a record rather than the database.

Kepler’s assistant is on every page, with roughly fifteen tools, @-mentions of specific records, and an approval step before anything is written. It searches the whole workspace semantically and by keyword, returns results as record sets you can save as a list, and can create and update records once approved. Kepler’s matching gives a pass-or-gap verdict per criterion with the evidence behind each one, and criteria are per job and editable. Kepler’s notetaker joins a call and files the summary, next steps and full transcript against the record, and emails, calls and messages become proposed field updates a person accepts or rejects.

The honest summary is that Invenias and Kepler are converging on the same features from different starting points, and that as of September 2026 Kepler has shipped the conversation-to-record half Bullhorn’s own roadmap places in stage two. That is a lead measured in quarters, not in architecture, and a buyer signing a three-year agreement should treat it as such.

Where Invenias is the better product

This is the honest half, and for an executive search firm it is the longer one. Invenias models the retained search process; Kepler models a recruitment desk. Six differences follow, and every one is a capability Invenias has and Kepler does not.

• Off-limits. Invenias supports off-limits policies on companies, inherited automatically by everyone holding a current position there, and on individual people, including as a step in the placement wizard. Adding or progressing an off-limits person on an assignment either warns the consultant or blocks them outright, and policies expire on a date unless you prevent it. Kepler has no off-limits object at all. For a retained firm this is not a nicety; it is the control that stops a consultant approaching someone the firm placed last year.
• A client-facing portal. Bullhorn documents Invenias Client as a premium feature letting Invenias users and client users work together in real time, sharing candidate lists, profiles and assessment data through a secure portal where the client gives feedback and scoring. Kepler publishes a branded job board on your own domain, which is a different thing: there is no portal in Kepler where a client sponsor reviews, comments on and rates a shortlist.
• Consent and GDPR as a data model. Invenias’ product page describes mass-sending notifications and consent requests, with emails auto-generated carrying the purpose and legal basis for holding the data. Kepler has a privacy posture but no consent object — no purpose, lawful basis or expiry stored as data you can filter on. For a European search firm with a compliance function, that gap is decisive on its own.
• Client-ready documents. Invenias ships a document editor and a candidate assignment report pulling background, stage progress, notes and evaluations into one branded document with merge tags, edited in Word. Kepler formats a candidate onto your agency’s own template as DOCX or PDF, which covers the CV but not the assignment narrative a retained client expects.
• Relationship and company structure. Invenias’ relationship intelligence maps connections across a firm’s network to surface warm introductions. Kepler has no company hierarchy — no parent and child group trees — and no network mapping.
• Business development as an object, and a mobile app. Invenias’ product page describes visibility into open pipeline, cross-sell identification and BD campaigns, and Bullhorn ships Invenias apps for iOS and Android. Kepler has no opportunities or BD pipeline object, no weighted deal value, and no native mobile app — its web app is responsive and that is all.

Two more, outside the search workflow. Invenias sits inside Bullhorn, an obvious path to a wider ecosystem and back office as a firm grows; Kepler has no timesheets, invoicing or payroll, and offers a public REST API and outbound webhooks instead. And Kepler holds no security certification — no ISO 27001, no SOC 2. If a client’s vendor security review requires one, that is a straightforward reason not to choose Kepler today.

Where Kepler is the better product

Four areas, and they cluster around finding things in a firm’s own records and being able to trust what is on them.

• What search reads. Invenias’ documented advanced search in the web app is Boolean keyword search over primary text fields — names, emails, addresses, titles, headlines, internal notes — plus current and previous positions and the document set as the default CV. Its newer AI document search covers keywords in CVs, proposals and assessments. Kepler’s search is a hybrid of semantic and keyword retrieval across candidates, CVs, notes and conversations, including the email threads and call transcripts attached to a record. For a search firm whose institutional memory is fifteen years of email and a folder of recordings, that difference is the whole product.
• The assistant’s reach, and who pays for it. The Invenias AI Assistant is documented on Person and Assignment records in the web application, enabled by request, and run on the firm’s own OpenAI or Azure OpenAI credentials. Kepler’s assistant is on every page, reads the whole workspace, can act across records after approval, and its usage is inside the seat price, with an additional AI capacity available on request if a team wants the limits off. Neither model is wrong, but they are budgeted very differently.
• Provenance and reversibility. Invenias keeps a journal of calls, emails, interviews, notes, documents and tasks against each record, plus a global journal of all users’ actions; journal items can be unlinked or deleted. Bullhorn’s documentation does not describe per-field change history or undo. Kepler keeps history at the level of the individual field, records the source of every AI-suggested change, and supports undo. It also uses optimistic concurrency, so when two consultants edit the same record the stale write is refused rather than silently applied.
• Proposed rather than applied, today. Kepler turns emails, calls and messages into proposed field updates and tasks that a person accepts or rejects, with the conversation that produced them attached. Bullhorn’s June 2026 roadmap places the equivalent Invenias capability in stage two, coming next. For a firm that has hand-corrected its database for a decade, the review step matters as much as the extraction.

How much do Kepler and Invenias cost?

Kepler publishes one price: USD 119 per user per month billed annually, which is USD 1,428 per seat per year. There is one edition and every feature is included — no tier above it and no feature gating. Records and storage are unlimited, with no per-record charge, and migration is free on every plan. Additional AI capacity is available on request; an allowance is included without it. Firms with 50+ seats can ask for volume pricing.

Bullhorn does not publish pricing for Invenias. The Invenias product page and Bullhorn’s executive-search page both route to a demo request. What the documentation describes is a shape rather than a number: an Essentials web application, a Professional desktop application, and an Executive Edition subscription that bundles premium products — Invenias Client, the collaborative client portal, is documented as one of them. The AI Assistant is a further optional feature requested through an Account Manager, and because it runs on the customer’s own OpenAI or Azure OpenAI credentials, part of the AI cost lands on the firm’s cloud bill rather than the software invoice.

One trap worth flagging. Bullhorn does publish per-seat pricing on its small-agency staffing software page — Bullhorn Starter at USD 99 per user per month and Bullhorn Core at USD 165 per user per month, with Bullhorn Pro and Bullhorn Max quoted on request, checked 6 September 2026. Those are plans for a different product. Invenias and executive search do not appear on that page, and nothing on it should be read as an Invenias price.

Which one is right for your firm?

Choose Invenias by Bullhorn if you run retained executive search and the assignment is your unit of work: if you need off-limits policies that a company passes down to its employees and that block or warn a consultant mid-assignment; if your clients expect a portal where they review, comment on and score a longlist; if you send consent requests in bulk with a purpose and a lawful basis attached; if a merge-tag candidate report in your own branding is a deliverable rather than a convenience; if you map a network for warm introductions; if your partners work from inside Outlook on Windows; or if your clients’ security reviews require a certification. Invenias does all of that today and Kepler does none of it.

Choose Kepler if what holds your firm back is not the search process but the records underneath it: if you have fifteen years of CVs, candidate reports, notes, email threads and call recordings that no keyword search reaches; if you want one assistant that answers a real question across all of it and can then act on the answer with your approval; if you need to see why a candidate ranked where they did, criterion by criterion; or if you want a published price with one edition and the migration done for you.

A blunter version: Invenias is the better choice for a firm buying the executive-search workflow, and Kepler is the better choice for a firm that already knows its workflow and cannot find anything in its own database. For most retained practices with a compliance obligation and a client who expects a portal, that is Invenias.

Can you migrate from Invenias to Kepler?

Yes, and Kepler runs the migration for you on every plan rather than handing it over as a spreadsheet and a login. You send an export from Invenias, plus the loose material a search firm always has outside the system: candidate reports in Word, scanned references, market maps in spreadsheets, shared-inbox archives. Kepler handles extraction, mapping, de-duplication and validation, and rebuilds your custom fields as real fields rather than flattening them into notes. Before the full load you review fifty of your own records fully parsed — your people, not a demo set — and anything wrong is corrected and re-run. Activity, stages and history come across alongside the records.

The CV parsing behind that migration is the engine from RemakeCV, our own product, which 300+ recruitment agencies use; it is the same team and the same code, which is why it is not a first attempt at reading a badly formatted CV. Kepler exports the whole workspace on request at any time, with no exit fee.

Two things will not come across, and it is better to know now. Kepler has no off-limits object, so off-limits policies cannot be migrated as policies — they would arrive as data on a record with no enforcement behind them. And Kepler has no consent records with a purpose and a lawful basis, so a GDPR consent register maintained in Invenias has nowhere equivalent to land. Those are the two migration items most likely to stop a retained firm from moving, and they are gaps rather than roadmap items.