Conference and Event Follow-Up

Leave a Conference With the Follow-Up Already Moving

Ten meetings a day turned into ten follow-ups, sorted by how warm each one actually was.

It runs in the systems you already have

  • Granola
  • Slack
  • Salesforce
  • Google Calendar
  • Microsoft Teams
What it looks like

Conference and Event Follow-Up, once it is built.

You ask in your own words. It does the work in the systems that already hold it, and tells you what it changed.

Sort the conversations from the conference.

Sixty-one cards and scans, sorted by how the conversation actually went:

  • Hot — 9, follow-up drafted referencing what you discussed
  • Warm — 23, into the nurture sequence with the session context
  • Cold — 29, added to the list, no sequence

The nine go out today if you approve them. Your read on the conversation decides the sort.

How it gets built

Connect, describe, run.

The same three steps whatever the process is.

  1. 01

    Connect

    The agent is wired into the systems the work already lives in. Nothing moves and nobody learns a new tool.

  2. 02

    Build

    The rules are described rather than drawn, in the words you already use to make the call.

  3. 03

    Run

    It runs on its own and hands back the decisions that need a person. The handover is designed, not left over.

Questions

What people ask about conference and event follow-up

How does it know how warm a conversation was?
It does not — you do. It sorts against your definition and whatever you noted at the time; the read on the room stays yours.
How fast does follow-up go out?
Same day, which is the difference between follow-up and a note two weeks later. A conference conversation has about a fortnight of half-life.
What about badge scans with nothing attached?
They go to the list and nowhere else. A scan is not a conversation and pretending otherwise is how a follow-up reads as spam.

Pick this one, or the one costing you more.