---
name: exec-dinner-planner
description: Plans executive dinners and small VIP events for ABM and field marketing. Picks invitees from target accounts, sets invite volume from expected acceptance, writes personal invites from executives and AEs, tracks RSVPs with a waitlist instead of overbooking, confirms 48 to 72 hours out, and drafts seating, a run of show and a host brief with guest context and conversation prompts. Use for executive dinners, VIP dinners, roundtables or side events at a conference.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: trade-shows-and-field
  source: https://eventmarketingsoftware.com/skills/exec-dinner-planner
---

# Executive dinner planner

Plan a small, high-value dinner end to end: who to invite and how many, the invites and follow-ups, an RSVP tracker
with a waitlist, confirmations, seating, a simple run of show, and a host brief so every host knows who they're
sitting with and why it matters.

## Intake

If the user has an `event-context.md` file, read it first. Then ask for anything missing in ONE message:

1. Date, city, time, and whether it's tied to a conference (and that show's schedule, so you avoid clashes).
2. Venue status: booked or not, private room or not, seat count, menu format, minimum spend if known.
3. Goal: pipeline acceleration, new logos, customer advocacy, or a mix; and the target persona (for example CIOs).
4. Candidate list: target accounts and contacts with tier, owner, title, open opp stage, and customer status.
5. Hosts: execs, AEs and any customer or partner co-host, and how many seats they take.
6. Topic or hook: a theme, a guest speaker, a roundtable question. A dinner with a reason gets more yeses.
7. Past yield, if they have it: invites sent vs accepted vs attended for similar dinners.

## Connectors (optional)

- **CRM connector:** read target accounts, contacts, owners and opp stages; after approval, add guests to the event
  campaign with the right member status.
- **Google Sheets connector:** read the candidate list; write the RSVP tracker to a new tab after approval.
- **No connector:** work from pasted text or CSV/XLSX; return Markdown and CSV files.

## Method

```
- [ ] 1. Seat math and invite volume
- [ ] 2. Pick and rank invitees
- [ ] 3. Plan invite waves and the waitlist
- [ ] 4. Write invites and follow-ups
- [ ] 5. Build the RSVP tracker
- [ ] 6. Confirm 48 to 72 hours out
- [ ] 7. Seating plan and run of show
- [ ] 8. Host brief
- [ ] 9. Validate
```

### 1. Seat math
Guest seats = total seats minus host seats. Keep roughly one host per 3 to 5 guests so every guest has a real
conversation (a planning assumption; adjust to the room). Invite volume = guest seats / expected acceptance rate.
There's no reliable published acceptance benchmark for executive dinners, so use the user's own past yield. If they
have none, ask them to pick an assumption, show the math at two rates (for example 25% and 40%), and plan waves so you
don't overbook. Also plan for some accepted guests not showing; that's what the waitlist and confirmations are for.

### 2. Pick and rank invitees
Rank by: open opportunity or named target account first, then customers who'll be strong voices at the table, then
good-fit prospects. Exclude competitors; include partners only as co-hosts. One or two people per account at most. Check for competitors at the same table and for seniority
fit (peers talk more openly). Use the account tier (Tier 1, 2, 3) from the target list, if there is one.

### 3. Waves and waitlist
- Wave 1 (4 to 6 weeks out): top-ranked invitees, personal invites from the exec or AE.
- Wave 2 (about 3 weeks out): fill remaining seats from the ranked list based on wave 1 replies.
- Waitlist: everyone who said yes after seats filled, plus strong backups. Offer seats in rank order as people
  decline. Never confirm more guests than seats.

### 4. Invites and follow-ups
Write: exec invite (under 120 words, first person, the hook, date, place, small group, RSVP ask), AE follow-up
(two lines, offers to answer questions), reminder for non-responders, acceptance reply with logistics, waitlist
reply, and a decline reply that keeps the door open. Examples: [references/invite-examples.md](references/invite-examples.md).
Leave `[brackets]` for lines only the sender can write.

### 5. RSVP tracker
Columns:

`rank, account, tier, guest_name, title, owner, invite_wave, invited_date, status, dietary_or_access_needs,
plus_one, confirmed_48h, seat, notes`

Status values follow your CRM's campaign member statuses. If none exist, use: Invited, Accepted, Declined,
Waitlisted, Confirmed, Attended, No Show. Keep the labels identical across dinners so yield can be compared.

### 6. Confirmations
48 to 72 hours before: personal confirmation with time, address, dress, parking or transport, the host's mobile if
they agree. Anyone who doesn't confirm by the day before: the AE checks in personally; release the seat to the
waitlist if they can't come.

### 7. Seating and run of show
Seat each guest next to a host. Keep colleagues from the same company apart, and keep known competitors apart.
Put the most senior guests near the main host. Run of show: arrival and drinks, seated welcome (2 to 3 minutes),
topic prompt, courses, closing thanks, no hard pitch. The event-run-of-show skill can expand this.

### 8. Host brief
One section per guest: name, title, company, account tier, relationship (customer, open opp stage, prospect),
owner, what we want from tonight, two or three conversation starters, and topics to avoid. Plus the evening's goal,
the seating chart and the follow-up plan. Template: [references/host-brief-template.md](references/host-brief-template.md).
Use only what's in the user's data or CRM; don't look people up online or guess personal details.

### 9. Validate
- Confirmed guests + hosts never exceed seats.
- Every guest has an owner and a follow-up step.
- No two guests from competing companies are seated together unless the user approves.
- Dietary and access needs are captured for every confirmed guest.

## Output

1. **Plan summary:** seats, hosts, guest seats, invite volume at the chosen acceptance rate, wave dates.
2. **Ranked invite list** with tier, owner, reason to invite, wave.
3. **Copy pack:** headings `Exec invite`, `AE follow-up`, `Reminder`, `Acceptance`, `Waitlist`, `Decline reply`,
   `Confirmation (48 to 72 hours)`, `Thank-you and next step`.
4. **RSVP tracker** (CSV).
5. **Seating plan** (table list by seat) and **run of show**.
6. **Host brief** (document).

## Approval gates

- Default to drafts. Don't send invites, add campaign members or post anywhere without showing the exact content,
  recipients and count and getting a clear yes.

## Privacy and compliance

- Dietary and access needs are personal data and can be sensitive (health, religion). Collect only what the venue
  needs, keep it in the tracker, and delete it after the event if the user's policy says so.
- Flag guests in the EU or UK for consent before adding them to any marketing follow-up; a personal thank-you from
  the host is fine.
- Remind the user to check gift and hospitality rules for guests from government, healthcare or regulated firms
  (many have limits on meals and gifts).

## Related skills

event-target-accounts (who to invite), pre-show-meeting-outreach (meetings around the dinner), event-run-of-show
(detailed evening schedule).

Sample input: `assets/sample-dinner-candidates.csv`.
