The Concept Comes First
The most common mistake organizers make is treating the concept as something that comes after the logistics. It doesn’t. It’s the first decision, and every other decision follows from it.
Kimberley Anya Tova Gantz, event producer at Crypto Beast Agency — who has worked on private Web3 side events during Bitcoin Conference Nashville, Token2049 Singapore, and Token2049 Dubai — frames it as a one-sentence test:
“If you can’t summarize the event in one sharp sentence, media and attendees can’t either. Ask: why does this exist? Why now? Why these people?”
She draws a sharp line between what traction looks like and what it doesn’t:
“High-traction events feel like: the only room where X founders and Y investors actually meet off-record. Ignored events feel like: happy hour during conference week.”
Mary Pedler, founder of INPUT Global — who has organized web3 side events at EthCC Cannes, Token2049 Singapore, ADWF, and Token2049 Dubai — points to the execution gap that follows when the concept is vague:
“You can’t just create a Luma link and wait for the magic to happen. The strategy should include placements on different event aggregators, posts in relevant communities, a social media campaign, cross-posting with co-hosts, and placements in relevant lists.”
The promotional infrastructure only works if it’s built around something specific. And specificity, Mary notes, means leaning into brands and names deliberately:
“Use catchy positioning and focus on brands — people follow name-dropping.”
In a saturated conference week, recognition is a filter. People use familiar names to decide which rooms are worth their time.
Timeline: How Far Out Should You Start
The answer depends entirely on what kind of web3 side event you’re running and what you need from it.
For a focused, invite-only side event where you’re not looking for co-sponsors or external speakers, Mary puts the minimum viable window at two to three weeks — with the caveat that the full promotion checklist still applies:
“If you are hosting an event exclusively and not looking for co-sponsors or speakers, 2–3 weeks is usually enough to start promotion. But you still need to follow all the steps, like listings on aggregators, which can take time.”
For anything larger — a side conference with partners, top-tier panelists, or sponsors covering premium packages — the timeline shifts significantly:
“I recommend starting much earlier — around 5–6 months in advance. The earlier you start, the higher your chances of filling the agenda with strong industry experts and big brands.”
Kimberley maps a middle ground that applies specifically to media coverage and ecosystem visibility. Six to eight weeks out is the sweet spot for locking concept and confirming anchor partners, securing high-signal attendees, and soft-pitching select media. Beyond that, the window for narrative shaping closes:
“Editors build conference coverage early. If you’re not on their radar before they assign stories, you’re likely out.”
At two to three weeks, the calculus changes. Attendance can still be driven through social channels, newsletter mentions, and reporters already attending the conference. What’s gone is the ability to shape the story around the event. As Kimberley puts it, at that point PR becomes amplification, not narrative shaping.
One signal that separates well-run Web3 side events from the rest: the best ones are already circulating socially two to three weeks before they happen, organically, because the concept and the guest list gave people something worth sharing:
“The best events are already circulating socially 2–3 weeks before they happen.”
The Room Is the Product
Most organizers spend their energy on venue, catering, and production. The organizers running the highest-signal events spend it on the guest list.
Kimberley is direct about the dynamic:
“The best side events are invitation-driven, intentionally over-subscribed, and pre-matched — investor/founder, operator/founder. The worst ones have open RSVP links blasted everywhere, 400 signups, 60 show up, no one knows anyone. Scarcity is a signal.”
An open RSVP attracts low-intent attendees and signals to high-intent ones that the room hasn’t been curated. The people you most want there are often the ones most sensitive to that signal.
Mary connects this directly to production, and the standards the crypto community now applies to Web3 side events:
“Production quality for sure. In the crypto space we’re honestly spoiled with upscale events, so any visible execution mistakes can damage your reputation in the community.”
Production quality is table stakes, not a differentiator. A polished room with the wrong people in it still fails. A well-curated room where the execution is visibly sloppy damages credibility. Both matter, but the sequencing matters more — get the room right first, then make sure the execution doesn’t undermine it.
What Makes a Web3 Side Event Media-Worthy
The framing most organizers use — “how do I get press coverage for my event?” — starts from the wrong place.
Kimberley reframes it:
“Journalists don’t cover events. They cover what happens at events.”
Media-worthiness comes down to whether the event creates a story a journalist can publish without stretching. The test is simple: if a reporter can’t answer “why would my editor approve this?”, it’s not media-worthy regardless of how well the event runs.
What moves the needle is a publishable angle — conflict, trend validation, new information, cultural shift, market implications. And the strongest single lever is an exclusive announcement tied to the event:
“New funding round revealed in-room, major partnership announced live, regulatory stance previewed, first-time public demo, product launch tied to trend. It creates news beyond the event itself.”
Mary approaches the same question from the journalist’s side:
“If you want media attention, you need to give journalists something exclusive — news, announcements, or unique insights. Well-known public speakers who are ready to share valuable commentary during interviews also help a lot, because that’s exactly the kind of content journalists are looking for.”
Media coverage requires something that exists independently of the event. Great vibes and quality networking are real outcomes — they’re just not publishable ones.
Where the Budget Goes
For organizers with limited budgets, the instinct is often to spread across venue, production, influencers, and distribution. Both Mary and Kimberley push back on that.
Kimberley’s priority is the social infrastructure around the Web3 side event — who is co-hosting, who is amplifying, who needs to be seen there:
“Most organizers focus on venue, food, and swag. High-traction organizers focus on who is tweeting this, who is co-hosting, who is amplifying. The best events are already circulating socially 2–3 weeks before they happen.”
And on where limited budget produces the highest return:
“A curated guest list is non-negotiable. If the room is wrong, no PR will save it, no influencer will save it, no lighting rig will save it. Budget here means someone dedicated to VIP outreach, intentional invite design, relationship-driven follow-ups, and smart room density — not headcount.”
Mary’s priority is production quality, with everything else structured to be lean:
“Everything else can be done on a lower budget. For example, you can offer media partnership — place their logo on the brand wall and they’ll often agree to do an event recap on a barter basis. Paid distribution is also not always necessary if you run a proper social media campaign, post in communities, and actively apply to side-event listicles.”
Production quality is the floor — visible execution mistakes damage reputation in a community with high standards. Within that floor, the budget that generates compounding return goes into the guest list and the social amplification around it, not the catering upgrade.
Once the Doors Close
The work that most organizers skip is what determines whether the Web3 side event compounds into something or stays a one-off.
Recap coverage, follow-up content, and relationship maintenance in the week after the event are where the visibility window either gets extended or closes. Protocol teams, investors, and journalists who weren’t there will see recap posts, highlight clips, and written summaries before they see anything else. A well-documented event reaches more people after it ends than during it.
The connections made in the room have a short half-life without follow-through. Most of the ongoing relationships we’ve seen come out of web3 side events started with a message sent in the first few days, while the context was still present.
If you’re scoping which conference week to build your Web3 side event around, the full calendar with filters by event type, ecosystem, and region is on Web3Voyager. If you’re organizing a side event, you can list it here.
