---
title: "Conference Follow-Up Email: A 48-Hour System That Gets Replies"
description: "Conference follow-up emails that turn meetings into next steps: a 48-hour clock, a promise ledger, and short templates for partners, investors and press."
author: "Shilika Jain"
date: "2026-10-28T02:00:50.255+00:00"
tags: ["conference marketing", "events", "media relations", "cold email"]
canonical: "https://www.shilikajain.com/blog/conference-follow-up-system-48-hours"
---

# Conference Follow-Up Email: A 48-Hour System That Gets Replies

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

Conference follow-up emails that turn meetings into next steps: a 48-hour clock, a promise ledger, and short templates for partners, investors and press.

---

# Conference Follow-Up Email: A 48-Hour System That Gets Replies

Send your conference follow-up emails within 48 hours of the event ending, and within 24 hours for the handful of meetings that matter most. A good one is short: where you met, one specific thing the other person said, what each side promised, and a dated next step. Sort every contact the night the event closes, so the most important follow-ups go out first and nothing promised on the floor gets forgotten.

Most of the value of a conference is created after it. The meeting is the opening. The follow-up decides whether it becomes a partnership, a story or a cheque, or just a name in your phone.

## Why 48 hours, and not "next week"?

Three things happen after a big conference week, and all of them work against you.

People forget. Your contact met dozens of others, often over several days and several venues. By the following week, you're a blurred face from a dinner. Then the inbox flood arrives. Everyone else who met them is sending follow-ups too, on top of the normal work they missed while travelling. Finally, attention moves on. Within a week or two, the next event, launch or fundraise takes over their calendar.

Within 48 hours, the conversation is still fresh and your email arrives before most of the pile. After that, every day makes the reply less likely. I don't have a statistic for this, just years of watching which follow-ups got answered and which didn't.

## The 48-hour clock

Time starts when your last session or dinner ends. This is the sequence I'd run for a team of two or three.

| Time | Task | Output |
| --- | --- | --- |
| Hour 0 (that night) | Triage every contact into Hot, Warm or Network. Fill the promise ledger. | One sheet, every contact sorted, every promise listed |
| Hours 1 to 12 (next morning) | Send all Hot follow-ups, personally written | Every Hot contact has an email with a dated next step |
| Hours 12 to 24 | Deliver anything you promised to Hot contacts: decks, docs, intros | Promise ledger items for Hot contacts closed |
| Hours 24 to 36 | Send Warm follow-ups and journalist notes | Every Warm contact and reporter has heard from you |
| Hours 36 to 48 | Connect with Network contacts on X or LinkedIn with a one-line note. Close the sheet. | Sheet complete, owners assigned for every next step |

If you're travelling home in that window, the morning block is the one to protect. Write Hot follow-ups at the airport if you have to.

## How do you triage contacts the night it ends?

Go through every card, scan, voice note and chat thread from the event. Put each person in one of three buckets.

- **Hot:** on your target list, able to act, and you agreed a next step. These are the meetings that pass every test in my [cost-per-qualified-meeting model](/blog/crypto-conference-roi-cost-per-meeting).
- **Warm:** relevant, interested, but no specific next step yet. You need to create one.
- **Network:** good people with no near-term reason to work together. Keep the relationship, skip the ask.

Then build the **promise ledger**. This is a list of every promise made during the week, by you or to you, with an owner and a due date. "I'll send you our integration docs." "She said she'd intro us to their ecosystem lead." "I told the reporter I'd share our usage data once it's public." These are the items that quietly die when nobody writes them down, and they're the most damaging to drop, because the other person remembers you promised.

## What should a conference follow-up email say?

Four parts, in this order, in under 120 words.

1. **Where you met.** One line. "Great to meet you at the ecosystem dinner on Wednesday."
2. **One specific detail.** Something they said that shows you were listening. This is what separates your email from the 40 generic ones in their inbox.
3. **The promises.** What you said you'd send (attached or linked) and what they offered, stated plainly.
4. **A dated next step.** A specific call time, or two options. Not "let's stay in touch".

Compare these two.

Weak: *"Hi, great meeting you at the conference! Would love to explore synergies. Let me know when you're free to chat."*

Strong: *"Hi [name], good to meet at the ecosystem dinner on Wednesday. Your point about wallet drop-off at the bridging step stuck with me, because it's exactly what our SDK handles. Docs attached as promised. Could we do 30 minutes with your engineer on Tuesday at 10:00 or Thursday at 15:00 (Singapore time)?"*

The second one is easy to say yes to. The first one asks the reader to do all the work.

## Follow-up templates by meeting type

Adjust the details. Keep the shape.

**Partner or integration lead.** Make the mutual benefit explicit, because goodwill alone doesn't move a partnership forward:

> you can close partnerships only if the parties involved have a mutual benefit!
>
> [Shilika Jain on X, 3 Oct 2022](https://x.com/Shilika_jain/status/1576978609478459392)

```text
Subject: [Your project] x [Their project]: next step from [event]

Hi [name], thanks for the time at [place] on [day]. You mentioned
[their problem or goal]. On our side, [what you get]. On yours,
[what they get]. I've attached [promised doc]. Could our [role] and
your [role] meet on [date option 1] or [date option 2]?
```

**Investor.** Lead with what changed or what they asked for. Attach only what they requested.

```text
Subject: [Project] deck, as discussed at [event]

Hi [name], good to meet at [place]. You asked about [their question].
The short answer: [one line]. The deck is attached, with [the section
they cared about] on page [x]. Happy to walk you through it on
[date option 1] or [date option 2].
```

**Someone who promised you an introduction.** Make it effortless. Write the forwardable blurb for them.

```text
Subject: Intro to [target name], as offered

Hi [name], thanks again for offering to connect me with [target].
To make it easy, here's a two-line blurb you can forward: [blurb].
No pressure on timing, and thanks for thinking of us.
```

**Service relationship.** If you sell a service, don't pitch. Follow up on the person, not the deal. I wrote this years ago, and it applies to post-conference follow-ups more than anywhere:

> “Don’t always look for transactional relationships”
>
> [Shilika Jain on X, 2 Aug 2022](https://x.com/Shilika_jain/status/1554363361894182912)

Send the article you mentioned, the contact you said you'd share, or simply a note that you enjoyed the conversation. The work comes later, from people who remember you were useful without asking for anything.

## How should you follow up with journalists you met?

Reporters get the most follow-ups of anyone after a conference, so yours has to give them something. Thank them briefly, share the one thing you discussed that could be useful to their beat (a data point, a founder view on a regulatory debate, a contact), and say when you'll have news, if you will. Attach or link a proper [press kit](/blog/web3-press-kit-what-journalists-need) only if they asked.

Don't ask for coverage of your booth or your party. Ask for nothing at all, if you can. Press relationships are built over many small, useful exchanges:

> agree w this 100%, it’s a relationship game🙏🏻
>
> [Shilika Jain on X, 13 Aug 2025](https://x.com/Shilika_jain/status/1955609025514778823)

If a reporter doesn't reply, follow the cadence in my guide on [how many times to follow up with a journalist](/blog/crypto-journalist-follow-up-etiquette-how-many-times) rather than chasing. Turning conference conversations with reporters into briefings and coverage is a regular part of my [Web3 PR campaigns](/services/web3-pr-campaigns).

## What happens after the first 48 hours?

The clock gets you started. A light rhythm keeps things moving.

- **Day 5 to 7:** one nudge to Hot and Warm contacts who haven't replied, in the same thread, with one new piece of information.
- **Day 14:** check the promise ledger. Anything still open gets done or explicitly closed.
- **Day 30:** count how many Hot contacts reached a second step. This is the number that tells you whether the event was worth it.
- **Day 90:** revisit the Network bucket. Some of those people now have a reason to talk.

After one nudge without a reply, stop. Move the contact to Network and look for a natural reason to reconnect later, such as your next announcement or their next raise.

## When doesn't this system fit?

A few situations need a different approach.

- **Very large volumes.** If you collected hundreds of booth scans, don't pretend to personalise them all. Send one honest, useful email to the scan list, and save personal writing for Hot and Warm.
- **Someone who asked for no follow-up.** Respect it. Note it in the sheet.
- **Contacts who prefer another channel.** Many crypto BD people live on Telegram, not email. Follow up where they contacted you or where you agreed to talk.
- **Sensitive conversations.** If you discussed something confidential, like a raise that isn't public or a deal under negotiation, keep the written follow-up neutral and save detail for the call.

The cost of this system is time, mostly a founder's or BD lead's, in the two days when they're tired and catching up on everything else. Block that time before you fly. A follow-up you meant to send is worth nothing.

## FAQ

### Should I send a follow-up email even if we already connected on X or Telegram?

Yes, if there's a next step to confirm or something to send. Chat threads get buried fast after conference week, while an email is easier to forward internally. Keep it short and refer to the chat so it doesn't feel repetitive.

### Is it better to send all follow-ups from the founder or from the person who took the meeting?

From the person who took the meeting, with the founder copied for Hot partner and investor contacts. The other side remembers the face they spoke to. Copying the founder signals the conversation matters without making the email feel impersonal.

### What subject line works best for a conference follow-up?

Name the event or place and the next step, so it's searchable later. Something like "[Your project] x [their project]: next step from [event]" works well. Avoid vague lines like "Great to meet you", which look like every other follow-up that week.

### Can I use AI to write conference follow-ups?

AI can help draft the structure or clean up grammar, but the specific detail from the conversation has to come from you. That detail is what makes the email work. A follow-up that could have been sent to anyone tends to get treated like one.

*Back from a conference with a full sheet and no system? [Book 30 minutes with me](https://calendly.com/shilikajain/30min/) and we'll triage it together before the 48 hours run out.*

---

**Book a 30-min post-conference pipeline review with Shilika** - https://calendly.com/shilikajain/30min/

Canonical: https://www.shilikajain.com/blog/conference-follow-up-system-48-hours