Integrations
Connecting a tool
What each source contributes, the permissions it asks for, and what happens when you disconnect it.
Slack
The morning digest
What Kaypo posts, the permissions it asks Slack for, and how to remove it.
API and CLI
Your scores in your own tools
Seven read endpoints with a workspace key: scores, deals, why a deal scores what it does, Discover, past champions, account research and what you sell. And the kaypo command line that calls them.
For mid-market teams
Research, routing and agents
Account families from your CRM, past champions who moved, job postings that came before your wins, inbound lead routing, Knowledge, and the account and goal agents.
Legal
Terms and privacy
The agreement covering a Kaypo subscription, and what Kaypo does with the data you connect to it.
The product
See it running
The fastest way to understand the scoring model is to watch it read a pipeline. There is no card and no call.
In short
Kaypo reads your pipeline and the activity around it, and turns that into a score out of 100 on every open deal. Every score lists what produced it and what each part was worth. You set the weights, and Kaypo runs Hindsight over your own closed deals so you can see whether they separate your wins from your losses.
Kaypo is read-only on every source except your CRM. It writes to your CRM only when somebody chooses to: the score once write-back is on, an edit made in Kaypo, or work an agent prepared after somebody presses Approve. Lead routing writes once an admin says yes to it. For new inbound HubSpot contacts nobody owns: the company owner (when HubSpot granted Kaypo permission to edit companies), the owner on an unowned open deal and a task with the fit. For new Salesforce Leads from a form waiting in a queue: the rep as the Lead owner and a task on the Lead. It stores the signals it derives, not the conversations they came from. Nothing Kaypo holds is shared with another customer, sold, or used to train a model.
