Two AI-native recruitment CRMs. One puts the AI inside the product.

Spott and Kepler are chasing the same idea from opposite ends. Spott has built roughly twenty separate AI features, each with its own switch. Kepler has built one assistant that works across the whole database, and a matching engine we measure.

The short answer

Spott is the broader product today and Kepler is the deeper one. Spott ships more modules — outbound campaigns, a BD pipeline, interview scorecards, a client portal, telephony — and pushes cross-record AI work out to ChatGPT or Claude through an MCP server. Kepler keeps the agent inside the app, where it can search across every candidate, email and call transcript you own and then act on what it finds, and it publishes one price with every feature switched on.

Choose Kepler if
You want one assistant that can answer a real question about your whole database and then do something about it, you want matching whose reasoning you can read and audit, and you would rather pay one price than assemble a plan out of seats and credits.
Choose Spott if
You need outbound sequences, an opportunities pipeline, interview scorecards, a client-facing shortlist portal, a dialler or a mobile app in the next quarter. Spott ships all of those today and Kepler ships none of them — that is a real reason to buy Spott and we would rather you heard it here.

Last checked 6 Sep 2026 · Written from Spott's own public documentation and pricing pages. Tell us if we have something wrong and we will correct it.

01

The agent is in the product

Spott’s Ask AI is scoped to the record you have open; cross-record work goes out to an external chat app through their MCP server. Kepler’s assistant sits in a sidebar on every page, reads the whole workspace, and can create and update records once you approve.

02

Matching you can audit

Both products score candidates against natural-language criteria. Kepler shows a verdict and the evidence behind every single requirement, so a consultant can see why someone ranked where they did rather than trusting a number.

03

One price, everything on

Kepler is USD 119 per user per month billed annually, with every feature included and unlimited records. There is no edition above it, and AI usage draws on an included monthly allowance.

Side by side

Where the two differ.

Dimensions where Kepler is the stronger product. Spott is ahead of us on several others — campaigns, opportunities, scorecards, the client portal, telephony and mobile — and the blog post covers those in full.

Kepler compared with Spott
Kepler Spott
The assistant
Scope of the AI assistantWhether it can answer a question that spans records. App-wide sidebar that reads the whole workspace and acts across records Ask AI panel scoped to the open record; cross-record work goes to ChatGPT or Claude via MCP
Acting on an answerReading is half the job. Creates and updates records, builds shortlists, saves a result as a list — behind an approval step Answers questions about the record in view
What search readsThe corpus, not the ranking. Candidates, CVs, notes, emails and call transcripts, semantic and keyword together AI-ranked search over notes and attachments labelled as CVs
Matching
Evidence per requirementCan a consultant see the reasoning? A verdict and the supporting evidence for every criterion, expandable under the row A 0–100 score with a thumb per criterion
Measured qualityWhether anyone checks the ranker. A standing evaluation programme with recall and precision gates and a cost ceiling per job No published evaluation; docs note matching degrades above roughly 2,000 candidates in the filter pool
Trusting the record
Field-level historyWhat changed, who changed it, and from what. Per-cell history with the source of every AI-suggested change, and undo Activity panel shows the change and its source; no per-cell history or undo
Two people, one recordThe quiet data-loss bug in most CRMs. Optimistic concurrency across resources, so a stale edit is refused rather than silently applied Not described in their documentation
Automatic profile updatesApplied, or proposed for review? Emails, calls and messages become proposed field updates you approve or reject Scheduled profile refresh; no review surface is documented and history reports only Updated or Profile not found
Your careers page
Custom domainWhether the jobs rank for your brand. Your own domain, server-rendered and indexable, with structured data per role Branded pages hosted at app.spott.io/careers/
Getting in and paying
MigrationWho does the unglamorous half. Done for you on every plan — extraction, mapping, de-duplication, a sample of your own records to check Import tooling and onboarding documentation
EditionsHow many decisions before you can buy. One edition. Every feature included, unlimited records and storage CORE and PRO seat plans, plus a separate credit balance for AI and enrichment
AI cost modelWhat happens when the team uses it. An allowance is included; additional capacity is available on request Metered credits per action — work email 1, personal email 3, phone 10, profile refresh 5
The difference in practice

Ask the database a question, not the record.

Spott’s Ask AI answers about the candidate you are looking at, and their documentation is explicit that cross-record agentic work belongs in ChatGPT or Claude over MCP. Kepler’s assistant is a sidebar on every page: it searches everything you own, shows the records it used, and can act on them once you approve.

Senior Data EngineerNorthwind Capital · London · Open
Criteria · 4 Re-run
Example matches for a Senior Data Engineer brief. Select a row to read its evidence.
CandidateMatchRole titleCurrent employerSkills
Sophia Bennett92StrongSenior Data EngineerMonarch AnalyticsPython, Spark, AWS, Terraform, dbt
Amir Hassan81GoodData EngineerNorthwind CapitalPython, Spark, EMR, SQL, Airflow
James Okafor74GoodSenior Data EngineerJuniper SystemsSpark, Azure, Databricks, Kafka, Scala
Mei Tan68WeakEngineering Manager, DataAtlas CloudAWS, Leadership, Python, Snowflake
Elena Rossi55WeakAnalytics EngineerFormadbt, SQL, Python, Looker
Oliver Chen49Off specPlatform EngineerNorthwind CapitalAWS, Kubernetes, Terraform, Go

Sophia Bennett

1 of 6

Assessment

A strong fit for the brief. Sophia has run a production Spark platform on AWS and has managed a team through a migration. Financial services exposure is via a payments client rather than a bank.

EmployerMonarch AnalyticsLocationLondonStatusScreeningLatest degreeMSc Computer ScienceEmailsophia.bennett@monarch.exampleProfile

Criteria · 3 of 4

  • Financial services“Two years on a payments client; no bank or fund experience stated.”
  • Python & Spark in productionmust“Built the ingestion platform in Python and Spark, processing 40 TB a day.”
  • AWS data platform“Ran the platform on AWS: Glue, Redshift and S3, with Terraform.”
  • Led a team“Managed four engineers across two squads through the warehouse migration.”

Decision

↑ ↓ next candidate · Esc close

Proposed, not applied

A conversation changes a record. You still get the last word.

Both products mine conversations for profile changes. The difference is what happens next. Spott’s scheduled refresh documents no review step and reports only whether a profile was updated. Kepler routes every change through a proposal you accept or reject, with the email, call or message it came from attached.

Three candidates · this week

Sophia Bennettto me
Today, 09:12

Re: Senior Data Engineer at Northwind

Thanks for sending the details over. The role sounds great, and I can start on 3 October if the timing works for them.

Amir Hassanonline
WhatsApp

Are you still keeping half an eye out?

10:41

I handed my notice in this morning, so I am actively looking now.

10:46
Catch-up call · 14 minJames Okafor · Today, 11:20
Zoom

James · 11:26For my next move I am looking for £105,000. I would want a step up for a move.

ListsData engineers · London Assistant
All candidates Search candidates... Filter Sort Import / Export
Example candidate records. Three cells carry an AI suggested update from the conversations beside them.
CandidateAvailable fromStatusExpected salaryNotice periodCompanyOwnerSkills
Sophia BennettNot setPassive£90,0001 monthMonarch AnalyticsPriya NairPythonSparkAWS+1
Amir Hassan14 Oct 2026Passive£85,0002 weeksNorthwind CapitalPriya NairPythonEMRSQL
James OkaforImmediateNew£100,0003 monthsJuniper SystemsTom ReillySparkAzureKafka+1
Mei TanNot setPassiveS$160,0002 monthsAtlas CloudTom ReillyAWSLeadership
Elena RossiNot setActive€78,0001 monthFormaTom ReillydbtSQLPython+1
Oliver ChenImmediateNew£88,000NoneNorthwind CapitalPriya NairAWSKubernetesTerraform+1
Rahul Menon2 Nov 2026Active£92,0001 monthJuniper SystemsPriya NairPythonAirflowSnowflake
Yuki TanakaNot setPassive¥14,000,0003 monthsAtlas CloudTom ReillyScalaKafkaGCP
Hafiz Rahman20 Oct 2026ActiveS$145,0002 weeksMeridian PartnersPriya NairSQLdbtLooker
Clara NowakNot setNew€84,0001 monthFormaTom ReillyPythonDatabricksSpark+1
Daniel OkonkwoImmediateActive£78,000NoneNorthwind CapitalPriya NairSQLFivetran
Ana Ferreira8 Dec 2026Passive€96,0003 monthsJuniper SystemsTom ReillySparkAWSTerraform
Tomas NovakNot setActive€71,0001 monthMonarch AnalyticsPriya NairPythonSQLAirflow
Grace Adeyemi27 Oct 2026Active£105,0002 weeksAtlas CloudTom ReillyLeadershipAWSKafka+1
Ivan PetrovNot setPassive€88,0002 monthsFormaPriya NairGoKubernetesGCP
Leila HaddadImmediateNew£82,000NoneMeridian PartnersTom ReillyPythondbtBigQuery
Marcus Reid16 Nov 2026Active£98,0001 monthMonarch AnalyticsPriya NairSparkDatabricksAzure
Nadia KaurNot setPassiveS$172,0003 monthsNorthwind CapitalTom ReillyLeadershipPythonSQL
Where the engine comes from

Not a first attempt at parsing CVs.

Kepler's CV parsing and formatting are ported from RemakeCV, our own product, which 300+ recruitment agencies use. The migration that fills your database on day one runs on an engine that has been reading real agency CVs for years, not on something written for this launch.

RemakeCV is a Kepler product. It is the same team and the same code, which is why we are willing to point at it — and it is the only outside evidence on this page, because Kepler itself is new and has no customer stories yet.

Migration

Get migrated in days.
We handle the whole move.

  1. 1. Send us the export

    Whatever your current system gives you, plus any loose CVs and spreadsheets sitting in folders. If you are not sure how to get the export out, we will walk you through it.

  2. 2. We build the migration

    Extraction, mapping, de-duplication and validation — the unglamorous half most vendors leave on your desk. Your custom fields are recreated rather than flattened into notes.

  3. 3. You look at a sample

    Fifty of your own records, fully parsed — your people, not a demo set. Tell us what we got wrong and we fix it and re-run, as many times as it takes.

  4. 4. Everything loads

    The full database goes in, mailboxes and calendars connect, and history backfills onto the right records. We stay on it until your team is working in Kepler.

Pricing

What each one costs.

Kepler

£89 per user / month, billed annually

  • Every feature included — there is no edition above this one
  • Unlimited records and storage
  • Migration done for you, on every plan
  • Monthly AI allowance included; more capacity available on request

Spott

Two seat plans, CORE and PRO, plus credits

Spott does not publish per-seat pricing on its website; the plan names and the credit model come from their documentation. AI and enrichment are metered separately from seats, with published per-action costs — a work email is 1 credit, a personal email 3, a phone number 10, a profile refresh 5 — pooled per workspace, carried over, and expiring after a year.

That model is a genuine strength for them: it lets expensive AI ship without eroding margin. It is also a second budget to forecast. Kepler puts the same class of work inside the seat price, with a flat add-on if a team wants to stop thinking about it entirely.

Questions, answered.

Is Kepler or Spott better for a recruitment agency?

It depends on which half of the product you need first. Spott is broader — outbound campaigns, an opportunities pipeline, interview scorecards, a client portal, telephony integrations and a mobile app are all live, and Kepler has none of them. Kepler is deeper on the AI itself: one assistant that works across your whole database rather than a panel per record, matching with readable evidence behind every requirement, and per-field history with undo. An agency that runs on outbound sequences should look hard at Spott. An agency whose value is in a large database it cannot currently search should look hard at Kepler.

Does Spott have an AI assistant?

Yes. Spott’s Ask AI is available on candidate, job, application, opportunity and call records, and answers questions about the record you have open. For work that spans many records, Spott’s own documentation points you at their MCP server, which lets ChatGPT or Claude query your Spott data from outside the product. Kepler takes the other approach: the assistant is a sidebar inside the app, it reads the whole workspace, and it can write changes back once you approve them.

How much does Spott cost compared to Kepler?

Kepler is USD 119 per user per month billed annually, which is USD 1,428 per seat per year, with every feature included, unlimited records, and free migration. Additional AI capacity is available on request. Spott does not publish per-seat pricing; their documentation describes CORE and PRO plans with a separate pooled credit balance for AI and enrichment actions, priced per action. You would need a quote from Spott to compare the totals.

Can Kepler do outbound campaigns like Spott?

Kepler has campaigns — multi-step email sequences with audiences, delivery windows, exit criteria and reply classification. Spott’s sequencing is more developed: they also ship manual steps that become assignable tasks, per-mailbox daily caps with send jitter, automatic mailbox warm-up, delegated sending and campaign templates. If sequencing is the centre of how your desk works, Spott is ahead of us on it today.

What does Kepler have that Spott does not?

An assistant that works across the whole database from inside the product rather than one scoped to a single record; search that reads emails and call transcripts as well as CVs and notes; matching with readable per-criterion evidence, held to internal recall and precision gates before a ranker change ships; per-cell field history with undo and the source of every AI suggestion; optimistic concurrency so two people editing one record cannot silently overwrite each other; a careers site on your own domain rather than a subpath of the vendor’s; and one edition at one price with migration included.

How hard is it to move from Spott to Kepler?

Kepler runs the migration for you on every plan. You send an export from Spott plus any loose CVs and spreadsheets; we handle extraction, mapping, de-duplication and validation, rebuild your custom fields as fields rather than flattening them into notes, and show you fifty of your own records fully parsed before the full load. Activity, stages and history come across, not just names and email addresses.

See it run on your own database.

Bring your hardest search to a 15-minute call. We will run it live, on real records, and talk through what a migration would look like.