The account graph, wherever your team already works.
Kairo is not trying to become the screen your reps live in. It is trying to make the screen they already live in correct.
HubSpot
Two-way. Scores, stages and top contributing touches written to the company record; deals and amounts read back for attribution. Available from Starter.
Salesforce
Two-way on Account and Opportunity, with a managed package and field-level mapping you control. Growth and above.
Attio
Two-way sync to any object you nominate, for teams whose CRM is not shaped like a 2011 CRM. Pro and above.
Clay
Threshold crossings and account context pushed into a Clay table so enrichment and outbound fire off a real signal.
Outreach & Salesloft
An account entering In market can start a sequence without waiting for someone to notice on a Monday.
Webhooks
Signed, retried, with a replay window. Every stage transition and threshold crossing, in a payload you can read.
REST API
The whole graph: accounts, lists, exposures, scores, stage history, opportunities. Cursor-paginated, sensible rate limits.
MCP server
Point Claude or your own agent at the same data Kai queries. Read-only by default; write scopes are opt-in per key.
Slack & email digests
A weekly account-movement digest, or an alert the moment a Tier 1 account crosses into market.
Designed to be read by something that is not a person
Every object in the interface has an endpoint, and the field names are the same in both places. No undocumented internal shapes, no CSV-shaped API.
- Bearer-token auth, scoped keys, per-key audit log
- Cursor pagination, updated_since on every collection
- Sandbox workspace with generated data for building against
- OpenAPI schema, so a client generates itself
{
"data": [
{
"id": "acc_8Fq2xR",
"name": "Ravensbourne Group",
"domain": "ravensbourne.example",
"list": "dach-ent",
"stage": "in_market",
"score": 94,
"score_changed_at": "2026-09-04T06:12:09Z",
"functions_engaged": 7,
"impressions_30d": 31,
"top_creative": "SI-04",
"crm_account_id": "0018e00000K1x2Z"
}
],
"next_cursor": "eyJvIjoxfQ"
}
The boring commitments, stated plainly
Your data is not training data
Target lists, CRM records and campaign data are never used to train models and are never pooled across customers. Benchmarks are opt-in and computed on anonymised minimum cohorts.
Regional storage
EU and US data residency, chosen at workspace creation. Sub-processors are listed publicly and changes are announced 30 days ahead.
Deletion means deletion
Workspace deletion removes derived records too, not just the rows you uploaded. Confirmation is issued within 30 days.
Put the account graph where your team already is.
Connect a CRM in the trial and the first sync runs within the hour.