The standard approach is to filter the CRM for titles and accounts, export a list, and send a branded invitation from a marketing address. It produces a predictable result: a low single-digit acceptance rate, a scramble in the last ten days, and a room padded with whoever was available.
The reason is not the copy. A VP who receives forty vendor emails a week has no way to tell yours apart, and nothing about a branded invitation from an unknown sender says this is worth an evening.
A useful invite list has five segments, and only the first is obvious:
| Segment | Why they belong in the room |
|---|---|
| Champions and advocates | They vouch for you without being asked, and other guests trust a peer over a vendor |
| Active pipeline | A dinner moves a stalled deal further than three follow-up emails |
| Closed-lost | They already evaluated you. Circumstances change, and nobody else is inviting them |
| Customers | They answer the question every prospect actually has |
| Unengaged targets | The reason you are hosting - but they only come if the first four are in the room |
Most teams invite only the fifth group and wonder why nobody accepts.
This is the step that changes the acceptance rate. For each person on the list, find who at your company has the strongest existing relationship with them - a former colleague, the account's CSM, someone who worked with them two jobs ago - and have that person send the invitation.
That requires knowing who knows whom across the whole company, not just the sales team. The relationship usually belongs to someone who has never been asked: an engineer, a founder, a customer success manager.
A dinner invitation from someone you worked with for three years is a different object from a dinner invitation from a brand.
Every person who accepts knows other people worth having in the room. Ask each registrant to bring one guest, and be specific about who: a named person in their network who fits your ICP, not an open invitation to bring a colleague.
This does two things. It fills seats you could not have filled directly, and it arrives pre-warmed, because the guest is coming with someone they trust rather than responding to a vendor.
Seat a customer or champion next to a prospect they already know. The introduction then happens by itself, over a starter, instead of being engineered afterwards by a rep.
This is the whole argument for a dinner over a webinar: the format only pays for itself if the relationships in the room are deliberate.
Orbb's Events Agent builds the list by those five segments from your relationship graph, assigns each invitation to the colleague with the warmest tie, sources a qualified +1 for every registrant, and pairs champions with prospects they already know. It also chooses the city, based on where your ICP density and your team's relationships actually overlap.