Question 1

What is Exenai Connect?

Accepted Answer

Connect is one governed gateway between AI and the systems your firm already runs — Bullhorn and Invenias as the system of record, and everything around them: timesheets and pay, accounting and finance, productivity in 365 and Google, project management and more. Through it, your team can ask questions, build apps and dashboards, and run agents on your live data, with every request allow-listed, approved and logged. Connect is also the app host: everything you build runs on Connect, standalone or embedded inside Bullhorn. Nothing is copied, nothing is stored — it reads and writes your systems in real time.

Question 2

What's the difference between this and Bullhorn Amplify?

Accepted Answer

Amplify is AI in Bullhorn. Connect is the AI gateway for everything else. Amplify is brilliant at everything you do inside Bullhorn — its digital workers enrich and update your records from every interaction, transcribe and summarise calls and meetings, match and screen candidates, run outreach and much more, with Amplify Chat putting a recruitment-built AI to work without ever leaving Bullhorn. Connect makes external AI safe to use on your firm's data, and puts it to work building the solutions that extend and complement the Bullhorn products — without buying another marketplace app for every need.

Question 3

How do we connect third-party AI tools to Bullhorn or Invenias?

Accepted Answer

Through an MCP connector — and be careful which one. MCP is the open standard AI tools like Claude, ChatGPT and Microsoft Copilot use to reach other systems, so connecting AI to your ATS means putting an MCP connector in front of it. Bullhorn may well launch official MCP connectors for Bullhorn and Invenias in time — nothing is confirmed today — and in the meantime a wave of unofficial connectors has appeared on the market, many built on the wrong authentication methods and operating outside Bullhorn's guidelines for secure, auditable API access. Wiring one of those into the system that holds your candidates' personal data deserves real scrutiny: ask how it authenticates, what it logs, and what governs each request. Which is exactly where Connect comes in — the next question explains.

Question 4

Is Connect an MCP for Bullhorn and Invenias?

Accepted Answer

Yes and no — and the difference is the whole point. We haven't built an MCP connector for Bullhorn or Invenias, and we wouldn't: that would wire AI straight into your system of record. Connect talks to Bullhorn and Invenias the official way — through their REST APIs, with the authentication, permissions and audit logging that come with working with those platforms properly. Where Connect is an MCP connector is on the AI side: Claude, ChatGPT, Microsoft Copilot and any other MCP-capable tool or agent connect to Connect, and everything they ask for passes through the governed gateway — allow-listed, intercepted where risky, approved where needed, and logged — before a single field is read or written. Your AI speaks MCP; your ATS only ever speaks to Connect. One deliberate boundary stays in place: large-scale search and match isn't exposed over the API, so it isn't reachable through Connect — that stays with Amplify, whose AI is trained on the largest recruitment dataset in the industry. Complementary by design — and the next question spells out how.

Question 5

How do Connect and Amplify work together?

Accepted Answer

Hand in hand — and Connect actively steers people to Amplify. Prompt interception reads every request at the gateway — so when someone asks Connect for something Amplify already does well, search and match included, they're redirected to Amplify inside Bullhorn: the right AI in the right place, with candidate data kept where it belongs. Connect's job starts where Amplify's ends: everything that needs to reach beyond Bullhorn, and every solution you'd otherwise be shopping the marketplace for.

Question 6

Our team is already using AI to build its own tools and scripts on Bullhorn. Should we worry?

Accepted Answer

Their instinct is right — the route is the problem. AI has made building cheap: anyone with Claude, ChatGPT or Cursor can now knock together a script or app against your ATS in an afternoon, and your most capable people are already doing it. But look at what those builds actually are: API credentials pasted into code, candidate data flowing through unreviewed AI-written scripts, no audit trail, no access control, and API usage outside Bullhorn's guidelines — invisible to leadership until something breaks or leaks. The answer isn't to ban building; it's to give it a sanctioned home. Connect delivers the same speed — describe it, and it's built — but every app runs behind the gateway: official API access, scoped permissions, a review pipeline before anything publishes, and every read and write in the audit log. Your builders keep building. Your data stays governed.

Question 7

We keep buying marketplace apps for every gap. How is this different?

Accepted Answer

That's the model Connect replaces. Instead of a separate app, contract and integration for each need, your team describes what they need and Connect builds it — on your live data, governed, in minutes. One subscription, unlimited solutions, and everything it builds lives in your control rather than a third party's.

Question 8

Do you take a copy of our data?

Accepted Answer

No — and this is the question to press every AI vendor on. Most AI products sold into the Bullhorn ecosystem need a copy of your database somewhere outside Bullhorn — synced to their cloud, indexed on their servers — and every copy is another set of the same candidate PII to secure, reconcile and explain. Connect's unique pass-through model was designed specifically to avoid that: one system of record, with Bullhorn and Invenias read and written in real time through the gateway, and nothing exported, synced or stored along the way. The only data Connect ever holds is the additional data your systems were never built for — commission schemes, checklists, your own rules — which lives in your Exenai tables, in your control, alongside the record. Never a copy of it.

Question 9

What should we ask any AI vendor before giving them access to our ATS?

Accepted Answer

Four questions, and be suspicious of soft answers. How do you authenticate — through Bullhorn's official APIs and guidelines, or a workaround? Do you copy our data — and if so, where does it live, who secures it, and how do we get it deleted? What does the AI actually do with candidate personal data — and can it act without a human? And can we see an audit trail of every action your product takes? These questions have hard answers for any vendor doing it properly. For the record, Connect's are: official REST APIs only; no copies, ever — real-time pass-through; every AI action governed by allow-lists, guardrails and approvals; and a complete audit log you can query yourself.

Question 10

How does authentication and security work?

Accepted Answer

Connect handles both sides of it. On the system side, Connect holds the authenticated connections to Bullhorn, Invenias and the rest of your stack — your credentials never spread across tools, and no third-party app ever holds its own key to your ATS. On the user side, Connect manages who can do what: role-based access, rights and privileges applied to every app you publish, every chat and every AI process that runs — so a consultant, a team lead and finance each see exactly what their role allows, in the apps and in the underlying data. One place to grant access, one place to revoke it, and every permission decision enforced at the gateway and logged. And when apps face outward, candidates and clients sign in with their own identity — Microsoft, Google, Apple, LinkedIn or a one-time passcode — with data scopes enforced by the host, so an outside user can only ever see, and only ever write to, their own data.

Question 11

What does “governed” actually mean?

Accepted Answer

Four things, all enforced at the gateway before anything touches your systems: an allow-list of what each user and agent may do, prompt interception for risky requests, human approval steps for actions that need them, and rate and cost caps. Every request from every actor — human or agent — lands in the audit log, and anything denied, held for approval or out of the ordinary raises an alert — email, Slack or SMS — the moment it happens.

Question 12

What is prompt interception?

Accepted Answer

Every request — from a person or an agent — is read at the gateway before anything runs. Interception applies one of four effects: deny for what should never happen — bulk exports, personal data heading somewhere it shouldn't; redirect to steer work to the right tool — a prompt Amplify does better is sent to Amplify, inside Bullhorn; and warn or advise where a nudge is enough. Whatever happens, the person is told in their chat, in the moment. And every deny raises a real-time alert — email, Slack or SMS — so leadership sees issues as they happen, not in a report afterwards.

Question 13

Can we see how AI is being used across the firm?

Accepted Answer

Yes — and for most firms it's the first time AI becomes visible at all. Every request from every person and every agent lands in one audit log, and that log is data like any other: ask it questions in plain English — how is AI being used across the business this month, which teams get the most value from it, was there any risky activity I should know about, what did that agent do yesterday — or build dashboards and alerts on top of it. Adoption, value and risk, measured from what actually happened rather than what people say. It's how AI spend stops being an act of faith.

Question 14

Our people are already pasting company data into public AI tools. How does this help?

Accepted Answer

That's exactly the problem Connect exists to close. External AI is coming into your business either way — Connect is how it arrives safely. It gives your team a sanctioned place to use AI on live company data, so the spreadsheet export into an ungoverned tool stops being the path of least resistance, and it gives leadership visibility of every AI action for the first time.

Question 15

Do we need developers to build with it?

Accepted Answer

No — that's the point. You describe what you need in plain English — “build me a commissions dashboard for my users, visible in placements and jobs” — and Connect builds it from your live data. Finished apps publish to the Exenai app host, standalone or embedded directly inside your Bullhorn records. Building stops being something you buy and becomes something anyone in the firm can do.

Question 16

What kinds of things can we build?

Accepted Answer

Everything from simple data jobs to full interactive applications. At one end, data-oriented processes: checking relationships, updating statuses across a whole desk in one governed action. In the middle, analytical dashboards that join live data from across your stack — placements against invoicing and payments, pipeline-health boards that show time-in-stage and flag stale candidates. At the far end, fully interactive read-and-write applications — kanban boards, commission calculators — published standalone or embedded in your records, plus agents that run processes 24/7. And client-ready deliverables that used to be documents: a search report that's a live app in every assignment, editable in line, writing back to the system of record, shared as a link that's never out of date. Never a stale PDF again. None of it is limited to Bullhorn and Invenias — anything you build can talk to any system in your connected stack, and where your systems don't hold the data a workflow needs, Connect creates flexible custom tables alongside them.

Question 17

Can we get reporting, dashboards and analytics across our systems — without the data leaving them?

Accepted Answer

Yes — that's exactly what Connect is for. Every other route to cross-system reporting starts by moving your data: a BI platform, a warehouse, a sync out of each system before you can chart a single number — and every copy is more cost, more risk, and another dataset to reconcile. Connect inverts it. Dashboards, reports and analytics are built on live reads through the gateway — placements from Bullhorn against invoices and payments from finance, pipeline health, commissions, whatever the question is — joined in real time while the data stays exactly where it lives. Nothing exported, nothing warehoused, nothing to reconcile. What you build publishes standalone or embedded in your records, permission-aware and always current. The expensive part of BI was never the charts — it was moving the data. Connect doesn't move it.

Question 18

Where do the apps we build actually run?

Accepted Answer

On Exenai's secure app hosts — build once, deliver to three audiences. The consultant host runs every app you build, standalone or embedded inside Bullhorn, with Connect handling the authentication, roles and governance underneath. Around it sit our candidate and client experience platforms — deliberately separate, because candidates and clients sign in from outside your firm with their own identity (Microsoft, Google, Apple, LinkedIn, or a one-time passcode), and their access is hard-scoped by the host: a candidate sees their own record and nothing else, a client sees their shortlist and workforce and nothing else. One build — a shift app, a candidate briefing, a client portal — delivered to any of the three, or all of them at once.

Question 19

What stops someone publishing a bad app?

Accepted Answer

Nothing publishes unreviewed. Every artifact goes through the publish pipeline: scanned for anything unsafe, reviewed by a separate AI that reports exactly what the app does, reads and writes, and held for human approval where it matters. And even a published app can only reach your data through the gateway — the same scopes, caps and audit log as every other actor. Everything is versioned with one-click rollback, so nothing is ever irreversible.

Question 20

Are agents subject to the same rules as people?

Accepted Answer

Exactly the same rules. Agents run processes and workflows for you 24/7 — working through the night, chasing what's overdue, watching for the things humans miss — and they go through the same allow-list, the same approvals and the same caps as your people. Every action an agent takes is logged with the agent named as the actor, and if one tries to read outside its scope, it's intercepted before it happens.

Question 21

Who is Connect for?

Accepted Answer

Recruitment and executive search firms running Bullhorn or Invenias. If that's you, it was built for you.

Question 22

When can we get it, and what does it cost?

Accepted Answer

Connect opens in September to a limited number of firms on fixed-price subscriptions, first come, first served. Registering early costs nothing, holds your place in the queue, and we'll show you the whole thing before you decide anything.

Question 23

What happens when we register?

Accepted Answer

You're added to the founding list and you'll be among the first to see Connect in full — a proper walkthrough on your kind of data, before launch. No commitment, no card, no obligation. When doors open, the queue order is the order we onboard.

Your AI, through one
governed gateway

Safe AI · Governed AI · AUDITED AI · Measured AI

Build apps from a prompt.
In plain English.

Applications · Dashboards · Reports · Read & Write

A live database. From a prompt.

Context, rules and memory for everything you build.

One build. Three audiences.
Consultant. Candidate. Client.

Ask your audit logs anything

visibility of AI · measured roi · business intelligence

Be part of our journey

Real ROI.
In Minutes.

Register your interest

Frequently asked questions

What is Exenai Connect?

What's the difference between this and Bullhorn Amplify?

How do we connect third-party AI tools to Bullhorn or Invenias?

Is Connect an MCP for Bullhorn and Invenias?

How do Connect and Amplify work together?

Our team is already using AI to build its own tools and scripts on Bullhorn. Should we worry?

We keep buying marketplace apps for every gap. How is this different?

Do you take a copy of our data?

What should we ask any AI vendor before giving them access to our ATS?

How does authentication and security work?

What does “governed” actually mean?

What is prompt interception?

Can we see how AI is being used across the firm?

Our people are already pasting company data into public AI tools. How does this help?

Do we need developers to build with it?

What kinds of things can we build?

Can we get reporting, dashboards and analytics across our systems — without the data leaving them?

Where do the apps we build actually run?

What stops someone publishing a bad app?

Are agents subject to the same rules as people?

Who is Connect for?

When can we get it, and what does it cost?

What happens when we register?

Your AI, through one governed gateway

Safe AI · Governed AI · AUDITED AI · Measured AI

Build apps from a prompt. In plain English.

Applications · Dashboards · Reports · Read & Write

A live database. From a prompt.

Context, rules and memory for everything you build.

One build. Three audiences. Consultant. Candidate. Client.

Ask your audit logs anything

visibility of AI · measured roi · business intelligence

Be part of our journey

Real ROI.In Minutes.

Register your interest

Frequently asked questions

What is Exenai Connect?

What's the difference between this and Bullhorn Amplify?

How do we connect third-party AI tools to Bullhorn or Invenias?

Is Connect an MCP for Bullhorn and Invenias?

How do Connect and Amplify work together?

Our team is already using AI to build its own tools and scripts on Bullhorn. Should we worry?

We keep buying marketplace apps for every gap. How is this different?

Do you take a copy of our data?

What should we ask any AI vendor before giving them access to our ATS?

How does authentication and security work?

What does “governed” actually mean?

What is prompt interception?

Can we see how AI is being used across the firm?

Our people are already pasting company data into public AI tools. How does this help?

Do we need developers to build with it?

What kinds of things can we build?

Can we get reporting, dashboards and analytics across our systems — without the data leaving them?

Where do the apps we build actually run?

What stops someone publishing a bad app?

Are agents subject to the same rules as people?

Who is Connect for?

When can we get it, and what does it cost?

What happens when we register?

Your AI, through one
governed gateway

Build apps from a prompt.
In plain English.

One build. Three audiences.
Consultant. Candidate. Client.

Real ROI.
In Minutes.