---
title: "How to Book Meetings Before a Conference: A 4-Week Plan"
description: "A four-week outreach plan to fill your calendar before a crypto conference: target list, first wave, one follow-up, confirmations and a meeting slot grid."
author: "Shilika Jain"
date: "2026-10-28T02:20:50.255+00:00"
tags: ["conference marketing", "events", "cold email", "media relations"]
canonical: "https://www.shilikajain.com/blog/book-meetings-before-crypto-conference"
---

# How to Book Meetings Before a Conference: A 4-Week Plan

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

A four-week outreach plan to fill your calendar before a crypto conference: target list, first wave, one follow-up, confirmations and a meeting slot grid.

---

# How to Book Meetings Before a Conference: A 4-Week Plan

To book meetings before a conference, start four weeks out: build a tiered target list in week one, send personal first-wave outreach in week two, follow up once and open a second wave in week three, and confirm every slot with a calendar invite in the final week. Offer specific times and places rather than "let's meet at the event", because a concrete slot is easier to accept than an open question. Most senior people's calendars are full before the week begins, so anything left to the floor is left to luck.

I treat the pre-booked calendar as the core of any conference trip. Booths, dinners and parties sit on top of it. If the calendar is empty when you land, no amount of side events will fix it.

## Why four weeks, and not two?

Two weeks out, the people you most want to meet have already said yes to someone else. Four weeks gives you room for a first message, one follow-up, a second wave and a confirmation round, without anything feeling rushed.

I know the timing from both sides. In 2024 I was on the ground at TOKEN2049 and Solana's conference doing interviews for CryptoDaily UK, and in late August, about a month before Singapore, I was already [asking publicly who I should interview](https://x.com/Shilika_jain/status/1828436310408692042). My slots were being filled weeks before the first panel.

Reporters and content people plan like that. So do fund partners and BD leads at larger teams. If you reach them in the final week, you're asking them to move something, which is a much bigger ask than filling an empty slot.

## The four-week plan at a glance

| Week | Days out | Main job | Done when |
| --- | --- | --- | --- |
| 1 | 28 to 22 | Build and tier the target list, set your slot grid, announce you're attending | 25 to 40 names, each with a reason and a channel |
| 2 | 21 to 15 | First wave to A-tier, warm intros requested | Every A-tier name has a personal message or an intro in motion |
| 3 | 14 to 8 | One follow-up to non-replies, second wave to B-tier, press requests | Half or more of your slots held, even if not yet confirmed |
| 4 | 7 to 1 | Calendar invites, locations, contact details, reshuffles | Every meeting has an invite with time, place and a phone or Telegram handle |

The numbers are logic, not data. A three-person team can rarely hold more than six to eight good meetings a day each, and 25 to 40 targets usually yields enough acceptances to fill that without overbooking.

## Week 1: build a target list you can actually work

A target list is a spreadsheet, not a vibe. For every name, write down three things: why them, what you want from the meeting, and the channel most likely to reach them.

Sort into three tiers.

- **A-tier:** people whose yes changes your quarter. A partner you need for an integration, an investor in your raise, a reporter on your exact beat. Usually 8 to 12 names.
- **B-tier:** useful, but a no doesn't hurt much. Adjacent ecosystems, secondary investors, podcasters, regional press.
- **C-tier:** nice to meet if the day allows. Leave them for dinners and hallways.

To find out who's going, check speaker lists, published side-event hosts, sponsor pages and people posting that they'll be there. For press, start from a proper [media list](/blog/how-to-build-a-media-list) and narrow it to reporters who are attending or covering the week.

Two small housekeeping jobs belong here as well. First, post that you're going, with one line on what you're working on, so inbound has somewhere to land. My own TOKEN2049 checklist post this year ended with exactly that kind of open door:

> if you’re around at token2049, lets chat up - DM me.
>
> [Shilika Jain on X, 2 Oct 2026](https://x.com/Shilika_jain/status/2106042264556654844)

Second, make yourself reachable:

> daily reminder to change you twitter DM settings so that folks can easily reach out/connect w you!
>
> [Shilika Jain on X, 17 Aug 2023](https://x.com/Shilika_jain/status/1692001191444840454)

It sounds trivial. I still see founders announce a conference trip with DMs closed.

## How do you set up a meeting slot grid?

Before sending anything, block your days into a grid. This is the part most teams skip, and it's why they end up double-booked across the city.

1. **Mark the fixed points.** Your talk, your side event, sessions you must attend.
2. **Cluster by location.** Main venue meetings on days you're at the venue. Hotel-lobby meetings near where most of your targets are staying. Conference-week traffic eats time between venues, so plan travel buffers you think are too generous.
3. **Use 30-minute slots with 15-minute gaps.** Meetings overrun and people get lost finding the café.
4. **Protect breakfasts.** Early slots have the fewest conflicts with parties and side events. Senior people often prefer them.
5. **Leave unbooked time.** I'd keep roughly a quarter of each day open for things that come up on the ground.

When you send outreach, offer two or three specific slots from the grid. "Thursday 9:00 or 9:45 at the venue café" gets accepted far more easily than "free to meet at some point?"

## Week 2: what should the first-wave message say?

Personal, short and specific. Every first-wave message should answer three things in a few lines: why you're writing to this person, what's in it for them, and when and where.

A shape that works:

```text
Hi [name], I'm [role] at [project]. We're [one line on what you do
and one proof point]. I saw you're at [event] and I think there's a fit
with [their specific thing], specifically [the idea]. Do you have
30 minutes on Wed 9:00 or Thu 10:30 near the venue?
```

Leave out the deck, the press release and the paragraph on your vision. Those come after a yes.

Cold outreach works better than people expect when it's done like this:

> cold emails can be life-changing, that’s a tweet!
>
> [Shilika Jain on X, 26 Jul 2023](https://x.com/Shilika_jain/status/1684228061271666688)

For A-tier names, ask for a warm introduction first if someone in your circle genuinely knows them. A good intro beats the best cold message. For more message structures, my [cold email templates for B2B founders](/blog/cold-email-templates-b2b-founders) adapt well to conference outreach.

Match the channel to the person:

| Who | Channel that usually works best | Note |
| --- | --- | --- |
| Crypto BD and partnerships leads | Telegram or X DM | Mention a mutual contact or a shared ecosystem |
| Fund partners and associates | Warm intro, then email | Cold DMs to partners have low odds |
| Journalists | Email, short and news-led | Offer substance, not a product demo |
| Founders of peer projects | X DM | Reference something specific they posted |
| Corporate or Web2 partners | LinkedIn or email | Formal tone, full context in the first message |

## Week 3: follow up once, then widen the net

Anyone who hasn't replied after three to four working days gets one follow-up. One. Reply in the same thread, add a single new piece of information (a new partner, a time change, a mutual connection who'll be at the meeting), and offer fresh slots.

At the same time, start the B-tier wave using the same structure. By the end of this week your grid should be about half held. If it's well below that, your target list is probably too senior for your current profile, or your "what's in it for them" line is weak. Fix the message before sending more.

This is also the week for press. Reporters at big crypto weeks are often most interested in industry-level conversation, especially regulation, so lead with the view your founder can offer, not the product. Have a short founder bio ready to attach once they say yes; [this guide](/blog/founder-bio-journalists-conference-programmers) covers what reporters want in one. The on-ground interviews I set up for Magna with CoinDesk at Messari Mainnet are the kind of meeting that has to be arranged ahead, because reporters rarely wander up to a B2B infrastructure team in a hallway. Press positioning for founders is a big part of my [founder profiling work](/services/founder-profiling).

## Week 4: confirm everything properly

Verbal yeses evaporate during conference week. Turn every one into a calendar invite containing:

- The exact time in the local time zone
- A specific place, not "the venue" (name the café, the hall, the hotel lobby)
- Both sides' phone numbers or Telegram handles
- One line on the agenda, so the other person remembers why they said yes

Send a short reminder the day before each A-tier meeting. Expect a few cancellations and reshuffles. Keep a short waitlist of B-tier names you can offer freed-up slots to.

Last, prepare a one-page brief per meeting for whoever's taking it: who they are, what you want, what they might want. If you're tracking the trip with my [cost-per-qualified-meeting model](/blog/crypto-conference-roi-cost-per-meeting), this is also when you record the pre-booked count.

## When does this plan not fit?

It's built for teams with a clear reason to meet specific people. A few situations call for something different.

- **Your first event in a new market.** You may not know who matters yet. Book fewer meetings and spend more time at ecosystem events learning the room.
- **You have no news and no clear ask.** Outreach without a reason converts poorly. Wait for a milestone, or go to listen.
- **The conference is less than two weeks away.** Compress the plan, skip B-tier, and focus on warm intros to A-tier only.

The other cost is time. Done properly, this is several hours a week for a month, usually from a founder or BD lead who has other work. Budget that time as honestly as you budget flights.

## FAQ

### How many meetings should I aim to book before a conference?

Work back from your capacity, not from ambition. If each person can hold six to eight meetings a day and you're there for three working days, fill around two-thirds of that with pre-booked slots and leave the rest open. Overbooked calendars lead to late arrivals and rushed conversations.

### Should I use a scheduling link instead of offering times?

For A-tier names, offer two or three specific slots in the message instead of a link, because it reads as personal. Links work fine for B-tier and inbound requests once someone has already agreed to meet.

### What if a target says they're too busy during the week?

Offer a call the week after, or a breakfast before the main programme starts. Some of the best conversations happen the day before the conference opens, when nobody's calendar is full yet.

### Is it worth paying for a meeting-booking platform at the event?

Some conferences offer official matchmaking apps, and they can help with B-tier volume. Don't rely on them for A-tier, though. The people you most want rarely accept random requests through an app.

*Got a conference coming up and a calendar that's still empty? [Book 30 minutes with me](https://calendly.com/shilikajain/30min/) and we'll turn your target list into a booked week.*

---

**Book a 30-min pre-conference outreach session with Shilika** - https://calendly.com/shilikajain/30min/

Canonical: https://www.shilikajain.com/blog/book-meetings-before-crypto-conference