Update the CRM by talking.
Nobody opens it anymore.
The conversation is the interface.
You already type the update in Slack. Ari — named after Ari Gold — reads the plain message, picks the right deal, drafts the clean note, and asks before it writes to HubSpot or Salesforce. The CRM is the system of record behind the conversation, not a tab you switch to.
Slack
Where you already type — the interface.
HubSpot
Where the note lands — the system of record.
Salesforce
Same flow, the other system of record.
Proof from the channel.
A real exchange: a one-line update typed the way you'd say it out loud, and Ari's confirmation that the clean note landed on the right deal — with the stage held, not moved.
Exchange in #deals · names blurred, figures kept
The update in the sentence you were already typing.
We run this on ourselves.
The real test: our own team stopped opening the CRM. Updates happen in Slack, through Ari; the record stays current without anyone administering it. The conversation was always where the truth was — now the system of record reflects it without the data-entry tax that used to make it late and half-true.
That's the honest proof. Not a productivity stat we can't show you — the qualitative fact that the CRM UI went quiet because nobody needed to open it anymore.
Input: a plain Slack message, no form, no tab-switch. Control: Ari asks before it writes; the record changes only on your say-so. Result: the team no longer opens the CRM UI.
Questions a sales team asks.
Only on your confirmation. It drafts the note and asks; the record changes when you say so. Nothing lands unseen, and nothing lands without you.
Both supported. The note lands wherever your pipeline lives. The Slack side is identical; only the system of record behind it differs.
It shows you the deal before it writes — you confirm or correct in one line. Nothing lands unseen. If the match is wrong, you say which deal and Ari re-points the note before it commits.
It acts on the messages directed at it, in the channels you connect — not a silent crawl of every conversation. You decide which channels are in scope.
HKR runs it inside your Slack and CRM; you don't administer it. Managed, not another integration to maintain. HKR is a services company — you get the working flow, not a config screen.
It operates inside your tenant with your permissions; it doesn't move data out of your stack. The note is written where your pipeline already lives, under the access controls you already have.
It doesn't invent updates, doesn't move deals on its own, and doesn't message your customers. It records what you tell it, cleanly.
See it run.
A 30-minute walkthrough on a real Slack workspace. A spoken-style update typed in, the deal matched, the clean note drafted, and the confirm-before-write gate — end to end.