How do you invite executives to a dinner by email and LinkedIn?

Fewer invitees, every message personal.

Why is a dinner invitation different from a webinar invitation?

A webinar needs hundreds of registrations, so you write one sequence and send it to a list. A dinner has eight to twelve seats. Every seat matters, every guest will meet every other guest, and one wrong title in the room changes the evening for everyone. So the campaign is smaller, slower and more personal. You are not optimising an open rate. You are filling a table.

Three things follow from that. The guest list is the strategy, not a mailing list. Introductions beat broadcasts, because a senior person reads a note from someone they know before they read a note from a stranger. And the messages are written one at a time, by the person who will be at the table. If you are planning a larger event, the event invitation email sequence is the better guide. This one is for the small room.

Who goes on the guest list, and who can introduce you?

Start with the question the dinner is about, then list the people who would want to argue about it. Be specific about title and company type: "CTOs and VPs of Engineering at retailers with an online store" is a guest list; "technology leaders" is not. Aim for a list three to four times the number of seats, because senior people decline often and decide late.

Then add a second column: who can introduce you to each name. Mutual connections, existing customers, investors, a partner firm, a former colleague. In Sawa's public CTO dinner case study, the team used relationship mapping across a partner's network and found roughly 30 target buyers with strong connections to people already in that network. That column is where the first wave of invitations comes from. Direct outreach fills the rest.

Write one line per guest on why them: the project they are known for, the post they wrote, the company they just joined. You will use it in every message.

In what order should you use introductions, LinkedIn and email?

Warm introduction first, LinkedIn second, email third, founder follow-up last. The order matters because each step borrows trust from the one before it.

1. Warm introduction. Ask the connector to send a two-line note: who you are, what the dinner is, and that you will follow up. Give them the text so it takes them one minute.
2. LinkedIn message. Short, personal, one subject, one date, one ask. If you are not connected, the connection request note is tiny, so use it to name the connector and the dinner, then write properly once they accept.
3. Email invitation. The full picture: the evening's subject, who else is coming, what they leave with, the practical details and a reply-by date.
4. Founder follow-up. One more note, from the most senior person on your side, carrying one new fact: a guest who just confirmed, or a change to the topic.

The case study above reports a 6% LinkedIn reply rate on one wave of outreach, after the team narrowed the targeting to ecommerce leaders. That is a reply rate, not an attendance rate, and it came from a tightly defined list. The lesson is the narrowing, not the number.

What should the invitation itself say?

Four things, in roughly this order, and nothing about your product.

• The subject of the evening. One question the table will argue about. Not a theme, a question.
• Who else is coming. Titles and company types, and names once you have permission. Peers are the reason to say yes.
• What they leave with. A written summary, a few new peers, an honest conversation. Say it plainly.
• The practical part. Date, time, place, how many seats, and when you need an answer.

No selling. If the host company gets mentioned, it is as the host. The dinner is the product. Guests know who is paying for the wine; writing a paragraph about your platform only tells them the evening will be a pitch. For the same reason, do not attach a deck.

What does the timeline look like over four weeks?

Here is the sequence Sawa plans against for a dinner about a month out. Weeks overlap, because introductions take time to land and some guests need all four steps while others say yes to the first.

Each message carries only one job. Resist adding the logistics to the invitation or a pitch to the thank-you. The same idea runs through every campaign in the B2B email campaigns guide: one email, one purpose.

What do the three key messages look like?

The three examples below are illustrative. The names, companies and dates are invented to show the shape and length of each message. The invitations from the CTO dinner campaign Sawa ran with Chameleon Collective are not reproduced here. What they shared with the examples: the dinner's subject in the first line, a named introduction where one existed, a message written for the person's company, and a follow-up only when the person showed interest.

What do you send after they say yes, and after the dinner?

The confirmation goes out the day they accept: a calendar invitation, the address, any dietary question, and a line that you will send the guest list the day before. The day-before note does three jobs. It reminds. It shows the guest list, which is the strongest reason to turn up. And it gives an honest way out, so you hear about a cancellation in time to offer the seat to a reserve.

The day after, the host writes to every guest individually. Thank them, send the summary you promised, and mention one thing they said. Then propose a single next conversation only where it fits: "you mentioned the migration is stuck on vendor contracts, I can introduce you to the person who handled ours." People who declined get a shorter note with the summary and a line about the next dinner. Guests who go quiet for months can be approached again later with a re-engagement sequence, but the first follow-up should feel like a host writing, not a campaign starting.

What does "it worked" mean for a dinner campaign?

Not the number of invitations sent, and not the reply rate on its own. A dinner campaign worked when the seats were filled with the titles you set out to reach, the room had the conversation you promised, and conversations continued afterwards. Count three things: seats filled with the right titles, introductions made at the table, and follow-up meetings in the month after. In the CTO dinner case study, the goal was eight seats in under a month and the combined campaign brought in nearly 15 signups, which is what let the host choose the room rather than fill it.

Two limits worth saying out loud. A dinner reaches a handful of people, so it is a poor tool for building a list and a good tool for deepening a few relationships. And the result depends heavily on the host: if the most senior person on your side will not write the notes and sit at the table, the campaign will read as sales outreach, whatever the subject line says. Sawa runs these as part of its convert work, alongside launch and nurture campaigns.

Planning a dinner? See how Sawa handles event and launch campaigns, or book an intro call.