Someone who already bought from you is about to land somewhere that has never heard of you. Rudy sees it first: the Slack channel you share says they left, usually weeks before LinkedIn. He rebuilds the last deal and drafts the ask before a competitor notices.
Try for free Book a demoAnika RoyHalcyon
was added to #halcyon-boomerang by laura. Also, Marcus Webb left.
Rudy reads it. Only your team sees what he does with it.
RudyAPP2 min later
Marcus has left Halcyon. His LinkedIn still says Halcyon and will for a while. Anika looks like his replacement. I will follow Marcus to his next company.
When a champion leaves, their Slack account is removed and your shared channel says they left, usually weeks before LinkedIn. New people show up when someone adds them.
Ranked by what people do in your channels, not by the title on the contact record.
A note that references what they actually cared about last time, not a template with their new company pasted in.
Rudy watches every past advocate, in your shared Slack channels and on LinkedIn, and tells you the day one turns up somewhere worth selling to.
Rudy sits in the channels you already share with customers. When someone leaves, the channel says so the day their account is removed, weeks before a profile changes. And because he has been in the room the whole time, he knows who that person actually worked with and how the account read when they left. A calendar cannot tell you that.
The contact marked champion in your CRM is often whoever signed. The real champion answers other users’ questions in your shared channel, asks for features and defends you in their own meetings. Rudy ranks people by what they do, so the person you track is the one worth following.
New executives reassess the stack in their first ninety days. Rudy spots them from both sides, being added to your shared channel and the job change on LinkedIn, and finds who on your side already knows them.
What they bought, what they pushed for internally, what the deal turned on. Pulled from your CRM and call history, then written into the ask.
Saw you landed at Siemens Healthineers. Congratulations.
When we worked together at Halcyon, the thing you cared about was cutting security review from six weeks to two. I suspect that problem followed you.
Halcyon closed Q2 last year. Marcus scored the rollout 9 at close. Two call recordings flag security review time as the blocker he personally owned.
Old contact flagged as moved and kept for history. New contact created at the new account, enriched with seniority, function, location and time in role. The owner hears about it the same day.
Rudy shows up where the work already happens.
Chrome, on LinkedIn and company websites Your team’s upcoming meetings, with Inside track Slack, including shared customer channels On the CRM record Claude and ChatGPT, over MCP HTTP API and webhooksRudy drafts. A person sends. Every ask goes out from someone the recipient knows, and anyone along the way can say no.
"In two weeks, two meetings and a 12 percent reply rate."
Nalin Senthamil · Founder · Storylane
Watch the Storylane story →Read-only on ingest, connected once, then kept current on its own. Writes go back through your own schema, into your own objects and fields.
Salesforce
HubSpot
Slack
Google Calendar
Gong
Outreach
Reach the person who signs, through someone they trust. One hop or two, every step drafted.
See the play →A champion is one voice. The decision needs six. See them all on the company page.
See the play →Connect your stack and see the graph you already own. Live in about 30 minutes.
Try for free Book a demo →
Rudy, our AI referral agent, finds the warm path, drafts the ask for the right person to send, and tracks it to the meeting.
