Marketing runs on signals, and the signals already land in Slack. Rudy reacts to them, keeps campaigns from spending the same connectors twice, and answers list questions wherever you ask them.
Intent, a pricing-page spike, a form fill from a target account. Rudy replies in the thread with who knows them and tags those people, so a hot account gets a warm route the same morning.
HubSpotAPP8:40 AM
Form fill: Head of Data, Rippling. Target account, tier 1.
1 reply
RudyAPPin thread
Two of your customers worked with her.
Campaign asks, held asks and caps in one list, so the programme does not burn the same five connectors every quarter.
Score a target list before you split the budget, from Claude or ChatGPT over MCP.
which of next quarter’s 100 accounts already have a warm path
Thirty-seven clear your threshold. Nine of them are two hops away, through customer champions.
Warm route first on the 37. Cold budget on the 54 with no route at all.
Rudy drafts. A person sends. Every ask goes out from someone the recipient knows, and anyone along the way can say no.
Before the quarter’s budget is committed, Rudy scores the whole target list for warm paths. The accounts with a route get the relationship treatment. The rest get the cold spend, which is now going to the accounts where cold is genuinely the only option rather than being spread evenly over both.
Someone chose your product, used it daily and told their team about it. Then the record reaches a rep with a score on it and nothing else. Before that handoff, Rudy maps the buying group and attaches the route, so the rep opens a record that already knows who can make the introduction.
Rudy · signup, mapped
Warm accounts convert better at every stage, but they stop converting the moment the person who opened the door stops appearing in the thread. Rudy watches the funnel by stage, finds where the drop is, and names who should come back in. It is a different diagnosis from the one a nurture sequence makes.
where in the funnel are we losing accounts that arrived with a warm route
Warm-routed accounts hold up through first meeting and then fall off a cliff. The pattern is the same in nearly every one of them, and it is not about the follow-up copy:
Nineteen accounts stalled after the first meeting. In eleven of them the person who made the introduction has not been in the thread since. That is a one-line check from someone they already trust, not a new pitch from someone they do not.
A target with no direct path often has one through a customer: your CSM knows the champion, and the champion knows the buyer. Rudy drafts all three messages and tracks each step, so two-hop routes can sit in a campaign plan instead of in somebody’s head.
You to Maria, CSM for SiemensSlack DM
Lena at Siemens worked with Rippling’s Head of Data. Would you ask her?
Maria to Lena ParkEmail
Lena, would you introduce our team to Ana at Rippling? Draft below.
Lena to Ana RuizEmail
Ana, this team is worth a short call. Copying them here.
Each person gets a draft in their own voice and can say no. The person at the end hears from someone they know, never from Rudy.
The failure mode here is scale. Forty customers asked to amplify the same launch is forty small withdrawals made on the same afternoon, and the cost does not show up until the quarter you actually need one of them. Rudy applies the health gate and the per-person cap before anything reaches a campaign list.
RudyAPP10:41 AM
Four customers were queued for the launch amplification ask. Two should go, two should not, and it is worth seeing why before the send.
AMPLIFICATION CHECK
The trigger comes from your stack. Rudy does the relationship work.
Salesforce, HubSpot and Attio Clay Common Room and Outreach Your own calendars and call recordingsAnd he shows up where the work already happens.
Chrome, on LinkedIn and company websites Slack, including shared customer channels On the CRM record Claude and ChatGPT, over MCP HTTP API and webhooksEvery pillar has a different cost and a different refill rate. The limits are set per source, and Rudy applies them before anything is surfaced, so the only asks anyone sees are the ones they are allowed to make.
YESAlways. Your own people know more of the target list than the list vendor does, and it costs nothing to ask.
NEVERNothing. This one is never skipped when a path exists.
YESWhen the relationship is healthy: NPS 7 or above, no open criticals, no renewal inside 60 days. Capped at two asks per person per year.
NEVERAt campaign scale. One ask sent to forty customers is forty withdrawals, not one.
YESCo-marketing and shared-account routing, through the Partner Manager.
NEVERDirect outreach into a partner’s list. Ever.
YESNamed portfolio introductions where the fit is real and the account is qualified.
NEVERLaunch amplification. A board member is not a distribution channel.
Every connector agrees to one rule. Someone who ghosts three asks is telling you they would rather not be a connector, and that is a fine answer. Better than silence, because silence is what trains the next person to stop asking. Both sides protected.
Not leads against spend. The count you are actually paid on, measured against the same budget.
Stage-by-stage conversion, split by whether the account arrived with a route. This is the number that either justifies the programme or kills it.
Response rate across your connectors. If this falls, fix the programme before pipeline does.
Champion tracking run as a motion rather than a memory, inside a PLG funnel.
Watch the story →
Product
How Rudy works
The relationship graph underneath all of it, and what gets written back into your own CRM objects and fields.
Product overview →
See what Rudy would put in your first weekly plan. Connect your stack and the graph you already own shows up in about thirty minutes.
Try for free Book a demo →Seven day free trial on Starter · No card to start · See pricing
Rudy, our AI referral agent, finds the warm path, drafts the ask for the right person to send, and tracks it to the meeting.
