Onboarding complete. NPS promoter score. Renewal signed. Each is a peak satisfaction moment that lasts about 72 hours. Rudy DMs the CSM the second the trigger fires, with the specific name to ask the customer to introduce them to, and the specific script that lands.
No credit card required · Set up in ~30 minutes
✓ Ask sent inside the 72-hour window
Rudy AI
Sarah Whitfield, Director of RevOps at Klarna just submitted NPS 10. She knows 7 buyers at ICP-fit accounts, including the CRO at Siemens. Here's the script, tuned to the trigger. Send?
18 to 25%
of total pipeline from referrals, up from 4 to 8%
72 hours
how long a peak satisfaction moment lasts
30 to 45 min
saved per ask, the script writes itself
The Shift
The intro was always there. The window wasn't.
Before
The CSM knows they should ask for intros at peak satisfaction. Forgets in the moment. By the time they remember a week later, the customer is dealing with a usage dip or a Q-end fire drill. The window closed.
Moment missed →After
Rudy DMs the CSM the second the trigger fires. "Sarah Whitfield just hit NPS 10. She knows 7 buyers at ICP-fit accounts. Here's the script. Send?" The CSM taps approve. The ask lands at the literal peak.
Ask lands at the peak →Where Rudy Lives
Zero new UI. No new console for your CS team. Rudy ships into the surfaces your team already runs renewals in.
Primary Surface · Slack
Rudy DMs the CSM with the trigger, the ask script, and the specific names. The CSM approves in one tap.
CS-Native · Gainsight / ChurnZero / Vitally
Triggers fire from health scores, NPS, and renewal events. Outcomes flow back to your CS platform.
LLM Workflow · Claude / Codex (MCP)
CSMs running account research in Claude pull live relationship data and ask scripts into the workflow.
Open API · REST
One API key plugs Rudy into any CS tool. Pull triggers in, push outcomes back to your system of record.
How Rudy Orchestrates
Customer success runs on timing. Rudy listens to your CS platform, your CRM, and your support tool. When a peak-satisfaction trigger fires, Rudy DMs the CSM with three things: who to ask, what to say, and why right now.
Rudy listens for peak-satisfaction triggers across CS, CRM, and support.
Rudy maps the champion's network for ICP-fit names. Drafts a script tailored to the trigger, the account, and the relationship.
The CSM reviews, edits if needed, sends. The outcome flows back to your CS platform for attribution.
Rudy knows the rules
CS owns the customer relationship. CSMs have direct access where sales doesn't. Rules calibrate.
Rudy enforces this. CSMs see only the triggers that are clean to act on.
Your Day, In 5 Plays
CS being responsible for the customer means more than catching peak-satisfaction moments. It means working with executives, partners, and board members to multi-thread the customer's expansion, and going proactive when retention is at stake. Boomerang surfaces the right move at the right moment, both directions: CS asking customers for intros to new logos, and CS using your team's network to multi-thread the customer's own account.
Trigger: the customer goes live. Onboarding status changes to running in your CS platform.
Rudy does: maps the champion's network. Surfaces 5 to 10 ICP-fit names they actually know.
The script Rudy drafts
"Now that you're live, our sales team is targeting Stripe, Datadog, and Snowflake. I see you likely know people at all three. Anyone you'd be open to introing? I'll brief you on context so you're not going in blind."
The script Rudy drafts
"Saw your NPS, means a lot. Quick ask: our team is in active conversations with Klarna and Siemens. You likely know the VP RevOps at Klarna and the CRO at Siemens. Either one open to a quick intro? I'll send you the talking points so you're not winging it."
Trigger: the customer submits NPS 9 or 10. The highest signal you'll ever get. The 72-hour window opens.
Rudy does: DMs the CSM within the hour. Cross-references the promoter's network with your sales team's active target account list. Surfaces specific names at specific companies.
Trigger: the renewal closes. Or an expansion deal signs. Commitment moment confirmed.
Rudy does: maps the champion's network against your sales team's target list with focus on use-case match. Pulls 3 to 5 specific names.
The script Rudy drafts
"Wrapped your renewal, thanks for the trust. Our team is currently chasing Maersk, Stripe, and Datadog. You came up as the closest connection for all three. Want me to set up briefings so the intros land warm, not cold?"
In the QBR, the CSM closes with
"We see Alan Pierce, COO at Maersk, in your network. Same industry, similar growth stage. Open to making an intro?"
Trigger: QBR scheduled and prep in progress.
Rudy does: surfaces relationship maps for the QBR deck. Suggests 2 to 3 specific people the customer's exec sponsor could intro to.
Trigger: a rep, the VP Sales, or the CEO routes an ask via Rudy to one of your customers. The CSM is in the loop because the customer is theirs.
Rudy does: DMs the CSM with context: who's asking, what deal it's for, what the dollar value is, and what the customer would be asked to do. The CSM sees it before the customer does.
Why it matters: the CSM isn't just a gatekeeper. When they say yes thoughtfully, they're contributing directly to new revenue. Most CS orgs don't yet measure this. They should.
The CSM picks one of four
Yes, send it through. Customer is happy, the ask is reasonable, the CSM endorses.
Yes, but let me re-script. The base ask is good, the CSM tightens the wording before it lands.
Not now. Open ticket, fragile renewal, recent escalation. The CSM delays and Rudy queues it for the next clean window.
Wrong customer for this ask. The relationship is real but the timing or fit is off. Rudy routes the question to a different customer who fits better.
The Pillar Escalation Rules
CSMs own the customer relationship. They have access sales doesn't. The rules calibrate.
Customer (Direct)
Can ask: at a peak satisfaction trigger. Onboarding done, NPS 9 or 10, renewal signed, expansion signed.
Can't: open critical tickets, NPS below 7, renewal risk, recent escalations.
Team Networks
Can ask: always. CSMs use team-network paths to warm up the customer's network themselves.
Can't: never skipped.
Partners
Can ask: customer-partner co-success stories, routed via the Partner Manager.
Can't: direct outreach to partner CS.
Board / Investors
Can ask: strategic customer references only. CSM + CRO + exec sponsor approve.
Can't: quarterly pipeline games. The board is not for CS expansion plays.
The Connector Contract
Every customer who participates as a connector agrees to this one rule. Customers who ghost three asks signal they don't want to be a connector. That's fine. Better than silence. The CSM stops asking that customer and focuses energy on customers who participate. Both sides protected.
Single tap. Same contract across personas.
For the VP CS / Chief Customer Officer
Three shifts your CFO and CRO will see within 90 days.
Referral Pipeline
Goes from 4 to 8% of total pipeline to 18 to 25%. Same CSM headcount, the moments are caught instead of missed.
Net Revenue Retention
Lifts because Boomerang surfaces expansion warm paths the CSM didn't know existed. Same customer base, more expansion ARR.
CSM Time
The script writes itself. CSMs save 30 to 45 minutes per ask. That time goes back into account strategy.
Three KPIs for the CSM Scorecard
For most CS teams today, getting customer-driven intros is a win but not a KPI. Rudy makes the activity measurable per CSM, per account, per quarter. Once it's on the scoreboard, it gets run on purpose.
Referral pipeline
$ of pipeline sourced from CSM-led intros.
Expansion ARR
ARR lift from warm-routed expansion.
Moment-catch rate
% of peak triggers acted on within 48 hours.
CS is sitting on more referral pipeline than the SDR team will ever build cold. The whole game is catching the moment. These plays are how you stop missing them.
No credit card required · Set up in ~30 minutes
