---
title: "Crypto Conference Dinner vs Party: Why 12 Seats Can Win"
description: "Crypto conference dinner vs party: why a 12-seat dinner often beats a 500-person party for pipeline and press, and a run sheet for hosting one well."
author: "Shilika Jain"
date: "2026-10-28T01:00:50.255+00:00"
tags: ["conference marketing", "events", "crypto pr", "media relations"]
canonical: "https://www.shilikajain.com/blog/small-dinners-vs-big-parties-crypto-events"
---

# Crypto Conference Dinner vs Party: Why 12 Seats Can Win

By [Shilika Jain](https://www.shilikajain.com/authors/shilika-jain) - 10/28/2026

Crypto conference dinner vs party: why a 12-seat dinner often beats a 500-person party for pipeline and press, and a run sheet for hosting one well.

---

# Crypto Conference Dinner vs Party: Why 12 Seats Can Win

For pipeline and press, a closed dinner of around twelve well-chosen people usually beats a big party during a crypto conference. At a dinner you choose every guest, everyone sits down long enough to talk properly, and each person leaves knowing who you are. A party is better for visibility, community and team morale, but most guests are strangers you'll never follow up with. Pick the format by the goal: depth of relationships means a dinner, reach means a party.

That isn't a theory. It's what I keep seeing in the rooms themselves.

## What actually happens at a big conference party?

Big parties optimise for the wrong number. The host counts RSVPs and headcount, so the guest list is built for size. That brings in a mix of people: some you'd want, many who came for the open bar, the merch or simply because it was on a list of side events.

The music is loud, nobody sits down, and most conversations last a few minutes before someone else joins or the group drifts. You meet a lot of people and remember few of them. They remember even fewer of you, because they went to four other parties that night.

People do build relationships at conference weeks, though. They just tend to build them away from the dance floor. After TOKEN2049 in 2024 I asked for exactly that:

> comment if you’ve build one good relationship at @token2049
>
> I’d like to change the perception that everyone was at parties!
>
> [Shilika Jain on X, 25 Sep 2024](https://x.com/Shilika_jain/status/1838919544691208484)

By this year's edition, my notes from the week had settled on where those relationships come from:

> closed dinners + conversations had the cream crowd v/s mass events
>
> [Shilika Jain on X, 12 Oct 2026](https://x.com/Shilika_jain/status/2109581426924662975)

## How do a dinner and a party compare on what matters?

This is the comparison I walk founders through. I call it seat economics, because the question is what each seat at your event is worth, not how many there are.

| What you care about | 12-person dinner | 500-person party |
| --- | --- | --- |
| Control over who attends | Total. Every seat is an invitation | Low. RSVPs, plus-ones and door crashers |
| Time with each guest | An hour or more, seated | A few minutes, standing |
| Memorability | High. Guests remember the host and the table | Low. One of several parties that night |
| Follow-up rate | Most guests expect to hear from you | A small share of contacts lead anywhere |
| Press value | Useful for relationship building with one or two reporters | Rarely useful; hard to talk |
| Reach and visibility | Small, by design | Large, especially on social media |
| Community and morale | Limited | Strong, if that's the goal |
| Content | Few photos, quiet room | Plenty to film and post |
| Risk if it goes wrong | A slightly awkward evening | An expensive room of the wrong people |

The cost per head is higher at a dinner, but cost per head is the wrong measure. What matters is cost per useful relationship. A party that costs far more in total and produces a handful of real conversations can easily lose to a dinner that produces eight. My sibling post on [conference ROI and cost per meeting](/blog/crypto-conference-roi-cost-per-meeting) shows how to run that number.

## When does a party actually win?

Parties aren't useless. They're the right choice when the goal is reach, not depth.

- **Community.** If your users, holders or builders are at the conference, a party is a thank-you they'll remember and post about.
- **Launch visibility.** A launch needs noise. A well-themed party gives people something to share.
- **Hiring brand.** A team that throws a good event signals energy to people who might want to work there.
- **Ecosystem gatherings.** When several teams from the same ecosystem co-host, the crowd has a shared reason to talk, which fixes much of what's wrong with a generic party.

Even then, a party works better with a small closed moment inside it, such as a quiet room or an early hour for invited guests before the doors open. That gives you the reach and the depth in one evening.

## How do you choose the twelve guests?

Start with the list, not the restaurant. This is the twelve-seat mix I use as a starting point. Adjust it to your goal, but keep the principle: every seat has a reason, and every guest has someone at the table they'd want to meet.

1. **Two hosts.** The founder and one other senior person. Never more than a few from your own team, or it feels like a sales pitch.
2. **Three to four partners or prospects.** Teams you want to integrate with, sell to or co-market with.
3. **Two investors or ecosystem leads.** People who know everyone and can make introductions after the dinner.
4. **One or two respected builders or operators.** Guests others want to meet. They make the invitation attractive.
5. **One journalist, at most.** Only if the conversation is genuinely interesting for them and you've agreed how the evening will be treated. More on that below.
6. **One wildcard.** Someone outside your usual circle, a researcher, a regulator-facing lawyer, a founder from an adjacent sector, who changes the conversation.

Before sending invitations, check every seat with one question: would at least two other people at this table be glad this person came? If not, the seat should go to someone else.

## How should you run the dinner? A run sheet

Here's the run sheet, counting from the date of the dinner.

- **Three weeks before:** write the guest list and a backup list. Choose a venue with a private or semi-private room where people can hear each other. Ask about minimum spend and deposits before you commit.
- **Two and a half weeks before:** send personal invitations, one by one, explaining who else is coming in broad terms and why you thought of them. A mass invite link turns a dinner into a party.
- **One week before:** confirm attendance, send a short note on the venue, time and theme, and invite backups into any empty seats.
- **Day before:** plan the seating. Split your hosts so each end of the table has one. Seat people next to someone they'd want to meet.
- **On the night:** a short welcome, no slides, no product demo. One prompt question for the table helps conversation start, such as a debate everyone at the conference is talking about.
- **Within 48 hours after:** send each guest a personal note and, where it makes sense, an introduction to someone else from the table. Making introductions between guests is the best follow-up you can send.

A theme helps, too. People remember an evening with a reason more than one with a menu. I've even argued for a fruit:

> i don't understand why founders in the west aren't vibing on mango parties.
>
> this could be a crazy networking sess + experience for your community
>
> [Shilika Jain on X, 15 May 2026](https://x.com/Shilika_jain/status/2055352902928224622)

That one was half a joke, but the point stands. A shared experience gives guests something to talk about besides their own projects.

## Should you invite journalists to a conference dinner?

Carefully. A dinner can be a good way to build a relationship with a reporter, because most reporters' conference weeks are a blur of pitches and briefings. A seated conversation with interesting people is a relief.

But be clear about terms. Tell the journalist before the evening whether conversations are off the record, and tell the other guests that a journalist is attending. Never surprise anyone. If you want press coverage of something specific, a dinner is the wrong place to pitch it. Book a proper briefing instead. My guide to [tier-1 journalist relations](/blog/web3-tier1-journalist-relations) covers how those relationships are built over time.

Journalists at conferences, in my experience, are most interested in the bigger industry conversations, often regulation. A table that's discussing exactly that is a better invitation than any product.

When a dinner is part of a wider launch or press push, I plan it inside the campaign, not beside it. That's how event moments fit into my [Web3 PR campaigns](/services/web3-pr-campaigns).

## When is a dinner the wrong choice?

There are real limits.

- **If you can't fill the table with the right people,** a half-empty dinner or a table of filler guests is worse than not hosting. If your list is weak, spend the time booking one-to-one meetings first.
- **If the goal is awareness among many people,** a dinner won't do it. Twelve seats are twelve seats.
- **If your founder doesn't enjoy hosting,** the guests will feel it. Find a co-host who does, or choose a format with less pressure, such as a small breakfast or a walking coffee.
- **If the week is already overloaded,** dinners on the busiest nights compete with everything else. A breakfast or a dinner on the night before the main event often gets better attendance.

If you're still deciding whether to host anything at all, my sibling piece on [whether a startup should host its own event during conference week](/blog/should-startup-host-own-event-conference-week) helps you make that call first.

## FAQ

### How do you stop guests from cancelling at the last minute?

Invite personally, confirm a week before and again the day before, and keep a short backup list ready. Guests cancel less when they know who else is coming and that their seat matters. A generic invite is easy to ignore; a note explaining why you want them at that table is not.

### Should the dinner be sponsored or branded?

Light branding is fine, such as a menu card or a short welcome. Heavy branding, banners and a product presentation turn it back into a marketing event and change how guests behave. The host's name is the brand at a dinner.

### Can you host a dinner and a party in the same week?

Yes, and for some teams that's the best combination: a party for community and reach, a dinner for the people who matter most to the next quarter. Just don't hold them on the same night, and make sure the dinner guests don't feel like an afterthought to the party.

### What if we don't have the network to fill a dinner?

Co-host with someone who does, such as an investor, an ecosystem team or a respected operator, and agree on the guest list together. You can also start smaller, with six or eight seats. A smaller table of the right people is still better than a full table of the wrong ones.

*Thinking about a dinner instead of a party at your next conference? [Book a 30-minute call](https://calendly.com/shilikajain/30min/) and we'll build the guest list and run sheet together.*

---

**Book a 30-min call to plan your conference dinner** - https://calendly.com/shilikajain/30min/

Canonical: https://www.shilikajain.com/blog/small-dinners-vs-big-parties-crypto-events