The Executive Dinner Playbook

For the purposes of this article, I'm going to use a straightforward example: an executive dinner for roughly 20 people.

The goal could be sales, recruiting, gathering insights, or simply relationship-building. The specific goal changes who you want in the room, but the process is mostly the same.

The core idea is simple: you are not filling seats. You are curating an experience. That means being deliberate about who gets invited, in what order, what the invite says, how people RSVP, how they get confirmed, where they sit, and what happens after. Do it right, and the dinner compounds into something bigger than itself. Do it wrong, and all you've done is hosted an expensive meal.

Who do you actually want in the room?

Not who is easy to invite. Not who happens to be in your CRM. Who do you actually want there if you could start from scratch?

If you're an enterprise SaaS company, maybe that's CMOs of tech companies. If you're selling to security teams, maybe it's CISOs at Fortune 500s. Define the target profile first.

Then figure out the TAM (total addressable market). How many of those people live in the geography you care about? Use whatever tools you have to find out — LinkedIn, Clay, ZoomInfo, RocketReach, Harmonic…whatever will allow you to easily filter down to the titles and location data you’re looking for.

As you build the list make sure to track: company, title, location, customer or prospect status, potential deal value if relevant, warmest path in, and why they belong in this specific room.

This step is critical to do before you even decide that you’re moving ahead with the dinner. Assume your conversion rate will be 1 in 7, you’ll need around 140 people who meet the criteria for an invite. If you have less than that, there’s a real risk you won’t get to your goal of 20 people in-seat.

That might mean planning to do a smaller dinner, doing a dinner in a different city, or selecting a venue that can flex up or down in terms of dinner size once you know what your numbers will look like.

Once you have the list, tier it. Three tiers — that's it.

Tiering is just prioritization. It's not a judgment on anyone as a person — someone's tier depends entirely on the event. A Tier 2 for one dinner could easily be a Tier 1 for another.

What tiering does is tell you who to reach out to first, how much effort to put into personalizing each invite, and when to move on. Be honest about it internally, because it affects everything downstream.

Keep it to three tiers. After that, you're overcomplicating it.

Before you email anyone, build the tracker.

This can live in your CRM, a spreadsheet, Airtable — whatever you actually use. You just need one place where the whole dinner pipeline lives. At minimum, track:

Make sure you’re tracking polite nos. If someone replies and says they can't make it because, for example, they’re out of town, that is not a failed invite. That is an open door.

“So sorry to miss you this time around. Hope you have an amazing trip, and I will let you know when we are planning the next dinner in case it works for you to join!”

The venue matters because it can help sell the dinner, and you should think about it the same way you think about the invite.

You don't need something flashy. You need something with a selling point. Maybe it's an iconic spot. Maybe it's new and hard to book. Maybe it has a great view. Maybe Taylor Swift and Travis Kelce were photographed eating there recently.

For a 20-person dinner, make sure you have a fully private dining room. You need people to be able to hear each other, and you need the dinner to feel intentional and elevated.

"Nice restaurant" is not a reason. Pick a venue with something to sell.

Before you reach out to anyone, get the invite right.

For a small executive dinner, the invite needs to be short. The format should be skimmable. I like a very straightforward email…something like:

—

Hi [Name],

[1 sentence opening/line about the dinner]

I thought you in particular would find this one interesting because [insert reason].

Let me know if you can join us and I’ll get you confirmed.

Take care,

[Name]

—

That last part matters more than you might think. People want to know they weren't just pulled from a campaign list. I like to get ahead of that directly and call out specifically why that person will find the dinner useful/helpful/impactful.

The research here isn't hard. Did they just join a company? Launch a product? Post about the topic you're covering? Use that context. If there's a real reason they belong in the room, say it.

Yes, this does mean you have to send emails individually, but that’s what works.

The invite should be short and personal. It should not feel long or templated.

Once the invite is ready, start with the people who are both Tier 1 and warm.

These are the people most likely to say yes before they know who else is coming — current customers, former colleagues, friends of the company, people your investors know, people who already trust you. Get your first anchors here.

If you can get four, five, or six strong Tier 1s confirmed early, the rest of the outreach gets much easier. You're no longer selling a hypothetical room. You're selling a room that already exists.

Your first RSVPs should come from people who trust you enough to say yes before they know who else is coming.

Once you have a few confirmed names, go to the rest of your Tier 1s.

Now you can say: "We'll be joined by leaders from X, Y, and Z." That matters. Busy people want to know who else will be there, and the confirmed names give the room credibility.

But don't rely only on the logos. You still need the topic and the "why you." The ideal invite for a Tier 1 has three things working together: the dinner itself (what, when, where), the room (who else is coming), and the personal reason (why this person specifically belongs there).

For Tier 1s, you're not blasting an invite. You're making a case.

For every tier, I use three touches max.

Touch 1 is the personal invite.

Touch 2 comes two days later as a reply to the first email. A little more social proof if you have it. Who's confirmed. Why you still think they'd get something out of the room.

Touch 3 is the polite takeaway. Something like: "Assuming this isn't a fit — we're down to the last couple spots, so I'll release the seat if I don't hear from you by tomorrow. Happy to keep you in mind for future events."

That works because it forces a decision without being pushy. Telling someone you're going to give their spot to someone else is surprisingly effective at getting them to respond.

After three touches, move on. More than three and you're just burning the relationship.

After you've worked through your Tier 1s, move to Tier 2s. Run the same playbook — three touches, personal invite, social proof follow-up, polite takeaway.

By this point, your confirmed Tier 1 list is longer, which makes Tier 2 outreach easier. The room has more credibility now.

Tier 2 doesn't mean unimportant. It just means slightly less perfect for this specific dinner.

If you find yourself needing to go deep into Tier 3 to fill a 20-person table, that's a signal something is off. Maybe the topic isn't compelling enough. Maybe the time or the format is wrong — some people will say yes to breakfast who won't say yes to dinner. Maybe everyone you want is at a major conference that week.

If you find yourself dipping into Tier 3, take a step back to diagnose what might be going on before you just invite more people and risk diluting the room.

For a 20-person executive dinner, here's my rough benchmark:

A one-in-four conversion rate means you've nailed the offer, the room composition, and the credibility of who else is coming. One-in-six-or-seven is workable, but I'd start asking why.

If you need to send 150+ invites to get 20 people to an executive dinner, the market is telling you something. More invites won't fix a broken offer.

Your invite volume is feedback. Pay attention to it.

For a 20-person dinner, don't use Luma, Partiful, Splash, or a landing page with a form.

Just use email and calendar invites.

In the invite, say something like: "Just reply 'I'm in' and I'll get you confirmed." That's it. Do not make people fill out a form. Do not make them navigate to a page and enter their title and company and LinkedIn URL. You already have that information, and your guest “experience” should start from the invite, not from the start time of the dinner.

Once they say yes, send the calendar invite.

For an intimate dinner, the RSVP flow is: email reply → calendar invite.

The calendar invite is not a throwaway confirmation. It's part of the experience.

Make sure it has a clear title, the correct date, time, and address, a clean description, a hidden guest list, reminders set, and — importantly — no automatically-added Zoom or Google Meet link.

The description should remind them what the dinner is, why it matters, and where they need to be. And once it's out, be careful about updating it casually. Every time you change the description or the time or the location, people get a notification. Make it right before you send.

Every touchpoint is still selling the dinner, even after someone RSVPs.

There will be drops. I've hosted maybe one dinner in the last year with zero attrition.

For a 20-person dinner, I'd typically get around 24 yeses if I want 18–20 people in seats. Rough math: 24 people say yes, 2–3 drop around the one-week reminder, 1–2 more drop the day before or day of, and 18–20 actually show up. Plan for roughly 20% attrition.

Don't build a plan that only works if every RSVP shows up. That almost never happens.

A week out, email everyone who is confirmed.

This is when people start getting serious about their schedule. You want conflicts to surface now, not two hours before dinner.

The email should include:

Make it clear they're holding a real seat. That last line matters — people will not proactively tell you they're dropping if you don't set that expectation.

The one-week email is not a reminder. It's a RE-confirmation.

The day before, one final short email.

Including your cell number opens the right line of communication. People will text if they're running late, and it signals that this is a real thing being hosted by a real person who cares.

By this point, if someone hasn't dropped yet, your attrition risk is much lower. The week-out and day-before touchpoints are what surface most of it.

If you're three or four days out and people have dropped, you may need to fill seats. But be careful.

If you're going back to Tier 2s or Tier 3s that you hadn't reached out to yet, you can run a version of the same invite. Just acknowledge the timing. People know when they're getting a last-minute invite, and it's worse to pretend otherwise — they'll figure it out when they're sitting next to someone who was invited five weeks ago.

But before you go back to send more invites, ask whether it's better to just run a smaller dinner.

By going back to send more invites, you’re running two risks:

1) You could negatively impact your relationship with someone by sending them a last-minute invite that makes them feel like an afterthought.

2) You could dilute the quality of the room and hurt the overall dinner experience by having lower tier people there.

A 14-person table of exactly the right people is better than a 20-person table with two or three people who dilute the room. When you're panicking about attrition, don't reach for whoever is available. Ask whether this person truly belongs there.

My test: picture your highest-tier guest sitting next to your lowest-tier guest. If that feels like it would make the room feel less serious, don't make the invite. Protect the integrity of the room.

Your weakest invite sets the floor for the room. Be willing to run a smaller dinner.

For a dinner this size, always do assigned seating.

Who someone sits next to and across from at a dinner can determine whether they had a good (or awful) time, so don't leave it to chance.

I usually start with outcomes. Who do I most want to spend time with? Who do I want them to sit next to? If I'm trying to build a relationship with someone, I want them near me, but I also want them next to someone they'll genuinely value meeting; not just someone who happens to be next to an empty seat.

Think through: seniority distribution, gender balance, industry overlap, existing friendships, your own team placement, and who each guest would most want to meet. Avoid clustering your team together.

Also strive to have everyone at one table whenever possible. If the group is big enough to require two tables, balance them carefully. Don't create a “kids'“ table and an “adults'“ table. People notice immediately.

If someone replies to your one-week reminder and mentions they're friends with another attendee, factor that in as well. People appreciate it when the seating reflects that someone actually thought about them.

The seating chart is make or break for the strategy.

You'll need preprinted name tags (name and company), name cards for the seats, a printed seating chart, and a bag check setup.

Arrive early. Make sure the table is right. Put out the name cards. Lay out the name tags. Walk the room. Check the entrance. Make sure the staff knows the plan.

And be extremely nice to the restaurant team. The waitstaff, bartender, host, and maître d' all matter. You want excellent service, and they want you to come back. Treat them that way from the start.

If you can get a couple of friendly people (your team, a customer you're close with) to arrive a little early, do it. It's better if the first real guest walks into a room that already has some energy rather than an empty table.

The room should feel alive before the first important guest walks in.

Once people arrive, greet everyone, get drinks going, and make sure people are comfortable.

When it's time, ask everyone to take their seats.

For 20 people, I don't try to force a single conversation. That can work beautifully at a table of six or eight. At 20, especially around a long table, it usually gets awkward and not everyone gets to participate equally. Let people have their own conversations.

Once appetizers are out and people have had a drink, I'll stand up, clink a glass, and say a few words. Keep it under a minute. Welcome everyone. Say why you brought the group together. Be honest about the selfish reason if there is one — people appreciate directness. Make one light joke if you can. Then sit down and let people enjoy the evening.

Note: someone from your team should stay until the very end. Your guests should not be the last people standing in the room alone.

Design the room, kick off the dinner, then get out of the way.

I'll be honest — I don't love taking photos at dinners unless there's a clear use case.

Dinner photos are often bad. Restaurants are dark. Flash is disruptive. Plates are messy. People are mid-conversation. If you don't require a photo for a specific purpose, skip it.

If you're going to take one, plan it: know who's taking it, when it happens, what angle you want, and whether it'll be posed or candid. If I had to pick a moment, it's right after the first plates come out — before the table gets messy — ideally timed to the end of your opening remarks. Take it once. Ask the server in advance if they can take it for you so it doesn't feel disruptive. Then move on.

If you don't know how you'll use the photo, don't take it at all.

Everyone who attended gets a short thank-you note within 24 hours. It should come from you, or from whoever on your team owns the relationship, depending on the goal.

Keep it personal and light. Reference something specific from the dinner. If you had a good conversation, mention it. If something funny happened, bring it up. Then include a light next step — not a sales pitch, just an invitation to continue:

Don't send a feedback survey. You'll know how the dinner went based on whether people write back to your thank-you note. If they had a good time, they usually do.

The thank-you note should extend the relationship, not convert the attendee.

After the dinner, update your records. Who attended, who dropped, who no-showed, what was discussed, what the next step is, who owns the follow-up.

Then send a simple internal recap. It doesn't need to be elaborate — just one slide or one page covering what the dinner was, why you hosted it, who was in the room, what the goals were, what happened, what you learned, and what comes next.

If your goal was sales, did those accounts move? If your goal was recruiting, did the right relationships deepen? If your goal was to gather insights, what did you learn? What are they spending on? What aren't they touching? The dinner should produce institutional knowledge, not just a nice evening.

If the dinner mattered, document what it produced.

If the dinner was good, it becomes proof for the next one.

Your next invite can open with: "Our recent dinner brought together leaders from X, Y, and Z. We're hosting a similar group next month and I think you'd be a great fit."

That's a much stronger starting point than going in cold. The people who attended become social proof. Some of them will refer others. Some will tell a friend who asks if it was worth going. All of that increases your conversion rate on the next round.

Great rooms compound. If you keep the bar high, each dinner makes the next one easier to fill, more credible, and more valuable. That's the flywheel. The goal isn't to throw one good dinner — it's to build the kind of reputation where the right people want to be in the room.

The best way to improve your next dinner's conversion rate is to make this dinner genuinely excellent.

The goal is not to fill seats.

The goal is to build a room that your best guest is glad they attended.

A mediocre dinner is easy to host. A great dinner is designed — in the list, the invite, the confirmation, the seating chart, and the follow-up. None of it is complicated, but every single step matters.