Your conference ROI lives in the second conversation.

Sixty contacts and no idea if it worked

It's the Tuesday after a three-day conference. Your phone has sixty new contacts in it, more if you let every booth scan your badge. Then someone, your manager or your own nagging brain, asks the obvious thing: was it worth going?

And sixty is the only number you've got.

So you say it out loud. It sounds decent, and everyone moves on. Nobody asks what sixty means, or how many of those people would recognize your name in a subject line next month, or how many would take a second meeting without you explaining who you are again. Those are harder questions. They're also the only ones that tell you whether the trip returned anything.

The second-exchange test

Contact count measures how many first exchanges you had. Conference networking pays off in the second one.

Call it the second-exchange test. A conference relationship starts being worth something once the other person does something they didn't have to do: reply with substance, come back without needing a reintroduction, send someone your way, or offer something first. Until one of those happens, a contact is a record of a conversation. Records don't compound.

It's a stricter bar than most people use, on purpose. It turns a fuzzy question (did I meet good people?) into one you can check against your inbox in a few minutes.

Why more contacts doesn't mean better networking

Contact count is attractive because you control it completely. Stand near the coffee station, scan every badge that drifts past, and the number climbs. That's exactly the problem. A metric that moves on your effort alone can't tell you anything about the other side of the relationship, and the other side is the whole point.

It also punishes the right behavior. The forty-minute conversation that becomes a real working relationship counts as one. So does the ninety-second badge swap with someone who'll never think of you again. Chase the count and you'll get more of the second kind and less of the first.

The financial view of conference ROI, ticket plus travel set against deals closed, has the opposite flaw. It's honest, but it lands too late to steer by. Relationships that matter often take a long time to show up as revenue, and you can't wait that long to decide whether to book next year's trip. So you need something in between: early enough to act on, specific enough to be real.

Four signals a conference relationship is progressing

Each of these is observable. You can point to the email, the message, the calendar invite. None of them depend on how the conversation felt at the time.

The second conversation without a reintroduction is the baseline: they remember who you are and what you talked about. A reply that asks something back is the most common early signal, and the easiest to miss, because it hides among courtesy replies. The unprompted warm intro is the strongest, because it costs them social capital. Value they initiate, a lead, an article, an invite, a heads-up, means the relationship has started flowing in your direction.

Most people track none of these. The evidence is in the inbox the whole time.

What this looks like six weeks after a conference

Say you're a founder back from a fintech conference with forty contacts.

Six weeks later you open a note and sort them by the four signals. Most sit at zero: you followed up, and they either didn't answer or answered with a pleasantry. A handful asked a real question back. Two took a second call, and neither needed reminding who you were. One introduced you to a partner at a firm you'd been trying to reach for a year.

That's the report. Five progressing relationships, one of them already generating intros.

Now put it next to another event from the same spring, where you came home with ninety contacts and, six weeks on, nobody has done a single thing you didn't prompt. The bigger number came from the worse event. Contact count would have sent you back. The second-exchange test says skip it.

The tally tells you something else too. The people who asked a question and then went quiet are your warmest open threads, and they get your time this week, ahead of everyone who never replied.

What changes when you measure progression

The shift starts before the event, not after it.

You capture differently. If the second conversation is the goal, the most valuable thing you can leave a room with is context: what they're working on, what they asked you, what you promised to send. A name and a job title can't pass the reintroduction test. Your notes can.

You follow up differently. A message written to earn a question back looks nothing like one written to confirm a connection. It names the specific thing and leaves an opening. Timing matters here too, since context fades fast once you're home (more on that in [The 72-Hour Memory Cliff](/articles/72-hour-memory-cliff/)).

And you judge events differently. Progressing relationships per event, checked at six weeks, is a number you can compare across conferences. It gives the breakeven math something earlier to anchor to, and it gives you a defensible reason to drop the events that pad your contact list and return nothing.

Where Met fits

The second-exchange test is mostly won or lost in the room. If you can't remember what someone told you, you can't write a follow-up that invites a real reply, and you can't have a second conversation without reintroducing yourself.

That's the gap Met is built around. Event Mode keeps the room captured while you keep talking, so the contact and the context you'd otherwise lose by Thursday stay together. Follow-up drafts start from that context instead of a template. Storage is iCloud-only, so the people you meet stay yours, not on someone's server.

Met won't score your relationships for you. You'll do that with the four signals. What it does is make sure you have something specific to say when the second exchange comes around.