business-event-formats

First fix whether the goal is volume of qualified conversations or penetration of a named account list, because reach and account depth rank the shapes in exactly opposite orders. A roadshow leads reach per unit effort through content reuse, while a single-city conference is the only shape that becomes an owned annual property.

Invite-only dinners and roundtables top the account-depth axis and are the default for short named account lists, with executive summits as the next rung when the list outgrows one table. Without a named list, the dinner is deleted from the menu entirely because it degrades into a generic mixer.

Open submissions top the credibility axis but also top the effort axis, so they are only promoted when the event is a compounding annual property and the organizer has the political capital to refuse executive speakers. Otherwise the default is a mixed practitioner program with labelled company slots.

Presence on a third party's floor is the only rung that borrows an audience someone else assembled, so it fits when the company has no audience that will travel. The trade-off is bottom account depth, and this collection does not cover booth operations on someone else's floor.

It is a format catalog only: it states no headcounts, city counts, budgets, or prices, and it does not cover track counts, session mixes, floor operations, goals, or funding. Those decisions route to sibling skills, and community-run events are routed away entirely.

A seniority-gated guest list excludes the engineers who actually drive bottom-up adoption, inverting the assumed buying hierarchy. Summits also cannot carry a public launch, and their live risk is hospitality compliance on the guest's employer, not budget.