Field marketers build lists and run them in Slack. Rudy answers the list question nobody else can (who do our champions know in this city?) and reacts when the right person registers.
City, seniority, target account and which network the path runs through, in one question. The answer is a guest list with a sender for every name.
23 people
A target-account registration lands in the events channel. Rudy names who knows them, so a personal note goes out before the event instead of a reminder email.
HubSpotAPP4:31 PM
New registration, Boston dinner: Dana Ortiz, CIO, Toast.
1 reply
RudyAPPin thread
Jordan Pace at Armis knows Dana well.
Seats, senders and follow-ups agreed on Friday, with every invitation tied to the person who should send it.
Rudy drafts. A person sends. Every ask goes out from someone the recipient knows, and anyone along the way can say no.
A roadshow lands in a city where you have no customers, so the invite list gets bought and the room fills with whoever had a free evening. But relationships do not stop at the city line. Rudy works your whole customer, team and investor network against the geography of the event, which is how a Boston room gets filled by people who have never heard of you and have heard of someone you know.
An invite from the CSM who ran their onboarding reads nothing like an invite from your events address, and neither reads like one from your CEO. Rudy assigns every target guest to whoever actually knows them, then drafts each note in that person’s voice. Which is most of why warm invitations get answered and bulk ones do not.
who should send each invitation for the Boston dinner
Nine of the twelve you want have someone here who knows them, and it is not the same person each time. Three go from Dana, two from your CEO, one through the investor and three from the AEs who already have the relationship:
I am doing a small dinner in Boston on the 14th, about twelve people, talking about how we rebuilt our onboarding. Thought you would find the room useful. No pitch, and I will be there the whole evening.
A booth is usually treated as a volume exercise: scan the badge, sort it later. Rudy takes the attendee list before the event, finds which of those accounts already have a route through your networks, and books the meetings while there is still calendar left. What is left on the day is the genuine cold walk-up, which is a much smaller and more honest job.
Rudy · attending, route found
Field marketing has more latitude than sales because the ask is join us rather than buy from us. It is not unlimited. Rudy checks the health of the relationship before a co-host ask is ever surfaced, and caps how many people any one customer is asked to invite.
RudyAPP10:41 AM
Dana is clean to ask. Erin is not, and it is worth knowing why before someone asks her anyway.
CO-HOST CHECK
An event produces relationships, not just meetings: your CRO met the CIO, your customer talked to a buyer for an hour. Rudy turns who met whom into intro requests within the week, sent by the person each guest actually spent time with. The full seven-day plan is in after the event.
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.
YESAlways. Your own people know more of the guest list than you expect, including in cities you have never sold into.
NEVERNothing. Never skipped.
YESWhen the relationship is healthy: NPS 7 or above, no open criticals, no renewal risk. Capped at 50 invitees per co-host.
NEVERWhen they are unhappy or mid-renewal. Come to our dinner is the wrong sentence that week.
YESCo-hosted events and shared booths, routed through the Partner Manager.
NEVERDirect outreach into partner marketing.
YESExecutive briefings and curated invitations, where a name on the invite genuinely changes who comes.
NEVERVolume events. A board member is not a registration 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.
Attended against invited. The number that separates a room from a list, and the one a bought list never moves.
What share of the room came from a city or an account where you had no relationship before. This is the network doing work a list cannot.
Sourced from people who were actually in the room, not from everyone who registered.
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.
