ATS integration layer for AI interview and hiring tools

An HR or talent acquisition team buys an AI interviewing tool expecting it to slot into their existing hiring stack. Then they discover there are no ATS integrations — one complaint states this plainly: 'the platform only supports Slack and WhatsApp, with no ATS integrations available yet.' So candidate data captured during AI interviews has to be manually re-entered into Greenhouse, Lever, Workday, or whatever ATS the company already runs. The AI tool saved time on the interview itself and created new work on either side of it.

This gap persists because AI interviewing tools are young companies with small engineering teams racing to make the core interview experience work. ATS integrations are expensive to build and maintain — each ATS has its own API, its own authentication quirks, its own data model for candidates and stages. For a seed-stage AI hiring startup, building even three ATS integrations properly is months of work. So they ship Slack webhooks and call it 'integrated.'

The buyer — a TA director or HR ops lead — often doesn't discover the ATS gap until after purchase, because the sales demo shows the interview experience, not the handoff. By then they're committed, and they absorb the manual work rather than churn. This means the AI tool vendor hears little complaint loudly enough to reprioritize — the pain is borne quietly by a coordinator.

A standalone ATS integration layer that sits between AI interview tools and the major ATS systems — handling candidate record creation, stage updates, and scorecard sync — is a business because every new AI hiring tool that comes to market needs this solved, and every ATS adds maintenance burden when it updates its API. The vendor selling this doesn't compete with the AI interview tool; they make it stickier.

What to build

Build a middleware service that accepts candidate data webhooks from AI interviewing tools and maps them to create or update candidate records in Greenhouse, Lever, and Workday — handling field mapping, deduplication, and stage progression — with a setup UI that a non-technical HR ops person can configure without filing an IT ticket.

Where to start

Get traction through AI interview tool vendors themselves — pitch it as a white-labeled integration they can offer customers, giving the vendor a sales advantage ('yes, we integrate with your ATS') without them having to build it. Revenue split makes it self-distributing.

The hard part

ATS vendors like Greenhouse control API access and can restrict or rate-limit third-party integrations for competitive reasons, meaning your core product dependency is in the hands of vendors who may not want you to exist.

How it makes money

Charged to the AI interview tool vendor as a white-label integration fee ($200-500/month per their customer who activates it), so the HR ops buyer never sees a separate bill — the interview tool bundles it as a feature add-on.