RevOps does not need another place to look. It needs the same rules to hold in every place Rudy shows up: the browser, Slack, the CRM and Claude.
Every reply Rudy posts to a signal has the caps, gates and opt-outs applied before anyone is tagged. Nobody can tag their way around policy.
ClayAPP11:20 AM
Datadog flagged in market, tier 2.
1 reply
RudyAPPin thread
Alan Boyd knows the buyer, but Datadog is on his no-go list. Tagging the team route instead.
Paths, hops, asks and outcomes are written back to Salesforce, HubSpot or Attio, so reporting runs where it already runs.
Rudy · asks on this deal
Every rep’s plan runs on the same objects, so plan completion is a number you can report, not a vibe.
Rudy drafts. A person sends. Every ask goes out from someone the recipient knows, and anyone along the way can say no.
Warm score, strongest path and rule eligibility arrive as fields on your own account object, in your own schema. A custom field in Salesforce, a property in HubSpot, an attribute in Attio. Reps never learn a new console because there is not one to learn.
Rudy · Boomerang fields, native
The policy engine sits between every rep and every connector. Per-pillar thresholds, per-connector preferences, routing rules, escalation gates. Configured once. The rep is not asked to remember anything, because out-of-policy paths never render.
RudyAPP10:41 AM
Three asks were stopped this week before anyone saw them. Worth reviewing whether the gate is set where you want it.
POLICY ENGINE, LAST 7 DAYS
Two-hop asks are where programmes go wrong: a rep asks a CSM, who asks a champion, and nobody can see it. Rudy drafts every step, logs who approved each hop and what happened, and writes it to the opportunity. You set who may start a two-hop ask and who approves.
Jon, AE to Maria, CSMSlack DM
Logged 10:02. Maria approved 10:40.
Maria to Lena, championEmail
Logged 10:41. Lena replied, forwarding.
Lena to Nadia, VP FinanceEmail
Forwarded 14:15. Meeting booked Thursday.
Every hop is written to the opportunity with its approver and outcome. The champion never sees Rudy.
A board member who will take two asks a quarter and only above a certain size. A customer champion who will answer anything but not in renewal month. Those preferences ride with the person across every interaction rather than living in somebody's head.
what are Alan Boyd’s connector preferences and how close are we to them
Alan has a self-set cap of two asks per quarter and a floor of $500K ACV. He has taken one this quarter and answered it in a day. His no-go list has two accounts on it:
One ask left this quarter, and his response rate is 100 percent across seven asks this year. This is a connector worth protecting, not one worth maximising.
By month six you have per-seat usage data on the tools the relationship layer overlaps, which is the only argument that survives a renewal conversation. Boomerang ships alongside what you have, then you decide what is still earning its licence.
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 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 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.
YESACV thresholds, qualification thresholds and frequency caps, set differently for each persona: SDR, AE, CSM, marketing.
NEVEROne global rule for everyone. That is how you get a board burned out by SDRs.
YESEach board member, champion and partner sets their own quarterly cap, deal-size floor and no-go list. It rides with them everywhere.
NEVERPreferences that live in one person’s memory.
YESCustomer asks via the CSM, partner asks via the Partner Manager, CEO asks via the Chief of Staff. Configured once, enforced everywhere.
NEVERReps deciding routing case by case under quarter-end pressure.
YESEvery ask, every approval, every outcome, exportable. Comp design and programme governance both get easier.
NEVERNothing. This one is never optional.
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.
What share of asks fell inside the configured rules. It should be close to all of them, because out-of-policy paths do not render.
Reps actively using it each week, which is the number that predicts whether any of this survives.
Seats you can defend at renewal, with the usage data to defend them.
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.
