Integrations

Every source, and what it is worth.

A CRM tells you what your team wrote down. The sources below tell you what actually happened. Kaypo needs one CRM to be useful and gets sharper with each thing you add.

HubSpotAvailable

Deals, companies, contacts and the activity on them. Optional write-back of the score to a property you name.

How it works

SalesforceAvailable

Opportunities, accounts, contacts and their history. Optional write-back to a field you name.

How it works

AttioIn development

Companies, people, deals, and whichever custom attributes your team actually uses.

How it works

SlackAvailable

Where the digest and alerts arrive. Kaypo posts to a channel you choose and reads nothing.

How it works

GongAvailable

Calls and transcripts. Only what the buyer said is read, and no transcript is kept.

How it works

Conversation intelligenceIn development

Whether next steps were agreed, whether a second stakeholder joined, whether someone stopped attending. Kaypo stores no calls, recordings or transcripts.

Third-party intentIn development

Who is researching the problem before they contact you. Bring your own credentials; Kaypo never holds the contract.

The website tagAvailable

A 2KB script on your own site that tells you when a company in your pipeline is reading your pricing page.

Two rules that apply to all of them

Kaypo is read-only everywhere except your CRM, and write-back to your CRM stays off until you switch it on. Disconnecting a source stops the sync immediately and removes the stored credential.

Kaypo keeps the signal, not the source material. It records that a security review started on a given deal on a given day and what that was worth to the score. It does not keep the call, the email, or the transcript that told it so.