Every sales and marketing team has lived this week. The restaurant is booked, the private room is paid for, and four days out there are six RSVPs for sixteen seats. Sales thought marketing would fill the room. Marketing thought sales would. Everyone starts sending cold invites to anyone with "VP" in their title.
Meghan Gill, who spent 15 years building go-to-market at MongoDB, described exactly this standoff in a recent post on AI outbound. Her fix at Oso was to stop treating the dinner as a mass invite and start treating it as a few carefully chosen asks, each with a real reason, reviewed by a human before it went out.
This playbook takes that idea one step further. The best invite to an executive dinner is not a well-researched cold message from you. It is a short note from someone the guest already trusts.
Why executive dinners fail at the guest list
The venue, the menu and the topic are the easy parts. The hard part is getting ten senior people to give up an evening, and three things work against you:
- Senior buyers ignore cold invites. They get several a week. A dinner invite from a vendor they have never heard of reads like a pitch with dessert.
- Nobody owns the list. When sales and marketing share the goal, each assumes the other is filling seats.
- The list is built from a filter, not a relationship. "VPs of Engineering in the Bay Area at Series B and above" produces 400 names and no reason for any of them to come.
Fix the list and the rest of the dinner mostly takes care of itself.
Why a dinner is the easiest warm ask you will ever make
Compare the two things you could ask a connector to pass on.
"Would you take a meeting to evaluate our software?" is a heavy ask. The guest has to give up time, sit through a pitch and, in a small way, put their judgment on the line. The connector knows that, so they hesitate to send it.
"Want to join a few of us for dinner at a great place in Boston next month?" is a light one. The guest gets a good meal, interesting people and an evening off from their inbox. Nobody has to evaluate anything.
That difference changes who will help you:
- Customers who would never pitch you to a peer will happily invite that peer to dinner. It costs them nothing and makes them look well connected.
- Investors and board members like introducing their network to good rooms. It is part of how they add value.
- Advisors get to play host without doing any selling.
Because the ask is lighter, connectors say yes more often, and they can do more than forward a note. Your anchor guest or a friendly investor can post about the dinner on LinkedIn ("hosting a small dinner for engineering leaders in Boston, a couple of seats left"), which reaches the right people with their name attached rather than yours.
The meeting still happens. It just happens after the guest has had a good evening with you, which is a much better place to start.
The playbook, six weeks out
Week 6: pick the anchor guest
Every good dinner has a reason to attend that is not you. Meghan's team built theirs around a "main attraction": an executive at a customer or a friendly investor that the other guests would want to meet.
Good anchors:
- A customer executive with a story worth hearing (and permission to tell it)
- An operator investor or board member known in the space
- An advisor who has run the job your guests now have
The anchor also becomes your first connector. They know people, and their name on the invite does more than your logo ever will.
Week 5: build the list from paths, not filters
Start with your target accounts, not a title search. For each account, ask one question: who do we already know who knows someone here?
- Your team: executives, sellers and CSMs with past overlaps
- Your customers: champions who would vouch for you
- Your investors, board and advisors: often the strongest paths into senior buyers
- Your partners: people who already sell alongside you
Keep only the guests where a real path exists: a real working relationship, not a shared employer ten years ago. A list of 30 names with real paths beats 400 names from a filter.
Week 4: decide who asks each guest
For every name on the list, pick the one person whose ask is most likely to land. Usually that is the connector with the closest relationship and the most senior title, but not always. A happy customer's ask often beats an investor's for a practitioner audience.
Two rules keep this from burning goodwill:
- One ask per connector per dinner. If your advisor knows five people on the list, ask them to invite their two best fits, not all five.
- Respect the cadence. If you asked the same investor for an intro last month, pick someone else this time.
Week 4: write the invite in the connector's voice
The connector should be able to forward the invite in ten seconds without editing it. Keep it to three lines:
"Hi [Name], a few of us are getting together for dinner on [date] with [anchor guest], who [one line on why they're worth meeting]. Small table, no pitch. I think you'd enjoy the conversation. Want me to save you a seat?"
Notice what is missing: your product, your company pitch, a calendar link. The ask is about the anchor and the connector's judgment, which is exactly why it gets a yes.
Weeks 3 to 2: send in small batches and track every ask
Send asks in batches of five to ten, not all at once, so you can see what is landing and adjust the list. Track each one: who asked, who they asked, when, and the reply.
Alongside the one-to-one asks, ask your anchor guest or one friendly investor to post about the dinner on LinkedIn: who it is for, where, and that seats are limited. Give them a two-line draft they can edit. Replies to their post are warm by default, because people are answering someone they already follow.
A useful rule of thumb from event teams: plan to confirm more guests than you have seats, because senior calendars move. How many more depends on your audience, so track your own no-show rate from one dinner to the next and use that number.
Week 1: confirm, brief and seat
- Confirm every guest 48 hours out, from the person who invited them.
- Send your host team a one-page brief on each guest: who invited them, why they came, what they care about.
- Seat each guest next to someone they will want to talk to, not next to your AE.
After the dinner: thank the connector first
The guest gets a thank-you note. The connector who got them there gets one too, with a line on how the evening went. Connectors who hear back say yes again. Connectors who never hear back quietly stop helping.
Cold invites vs warm invites
- Who sends it: cold, your SDR or marketing. Warm, someone the guest already trusts.
- Why the guest says yes: cold, the topic, maybe. Warm, the person asking, and the anchor guest.
- List size you need: cold, hundreds of names. Warm, tens of names with real paths.
- What it costs you: cold, your brand, if it feels like spam. Warm, one ask of a connector's goodwill.
- What you learn: cold, open and reply rates. Warm, which relationships actually convert.
Where AI helps, and where it should not
Meghan's point about AI outbound applies here too: the tools are good at research and pattern matching, and bad at judgment. Use AI to find the paths, rank them and draft the ask. Keep a human deciding who gets invited and who sends each note.
That is how we built Rudy, the agent inside Boomerang. For a dinner, Rudy finds who in your team, customer base, investors, advisors and partners knows each person on your target list, scores which paths are real, and drafts the invite in each connector's voice. Rudy never sends anything. The connector reads the draft and sends it from their own account, and every ask is tracked, so you can see who replied and which intros turned into meetings.
Keep going
- Event-led sales: the wider motion dinners sit inside.
- Field marketing playbook: running warm-intro programs around events.
- Executive engagement at sponsored events: the same idea at conference scale.
- What a warm intro strategy is, and why it matters.
- 100 Warm Meetings in 90 Days: the free ebook with the ask scripts and the 90-day plan.
Frequently asked questions
How many people should I invite to an executive dinner?
Plan the table first (8 to 16 seats is typical for a conversation-driven dinner), then invite enough to fill it after declines and late cancellations. Track your own acceptance and no-show rates across dinners and size future invite lists from those numbers.
Who should host an executive dinner?
Your most senior executive plus an anchor guest who is not from your company, such as a customer executive, investor or advisor. The anchor is the reason most guests come.
How far in advance should I send executive dinner invites?
Four to six weeks for senior guests. Build the list in weeks six and five, send asks from week four, and confirm 48 hours out.
Why do connectors say yes to dinner invites more easily than to meeting intros?
Because the ask is lighter. Inviting a peer to a good dinner costs the connector nothing and makes them look well connected, while asking a peer to evaluate software puts their judgment on the line. Customers, investors and advisors who would hesitate over a sales intro will usually pass on a dinner invite.
Should the dinner include a product pitch?
No. Guests who came through a trusted connector came for the conversation. Follow up after the dinner, one to one, if there is a real fit.
What should an executive dinner invite say?
Three lines: the date, the anchor guest and why they are worth meeting, and a clear "want a seat?" Sent by someone the guest knows, not by your company.
.png)
