The 2-7-30 sequence: your first follow-up is only a second introduction.

Day 31, and the draft that won't start

Day 31 after the trade show. You open the contact, read the note you typed at the booth (“procurement, cares about lead times, kid starting at Purdue”), and start writing. Three lines in, the problem shows up. The draft opens with “Great to meet you at the show,” and that sentence is now a month old.

So you delete it. You try “Hope you've been well,” which is what you'd send a stranger. And a stranger is what they are again.

The first follow-up went out on day two. It was good. They replied. Then four weeks passed, and that reply is still the last thing either of you said.

One follow-up doesn't build anything. It's a second introduction, and second introductions fade on the same curve the first one did.

The 2-7-30 sequence

Call it 2-7-30. Three touches in the first month, each timed to a different state of the other person's memory.

Day 2 (anywhere from 48 to 72 hours): the recap. You confirm the conversation happened and name the one specific thing from it. Context is fresh on both sides, so the message can be short. The case for this window is laid out in The 72-Hour Memory Cliff, and it isn't repeated here.

Day 7: the value-add. The article they'd want, the intro you offered, the spec sheet they asked about. They still remember the conversation, but it's already competing with everything else from that week. This message gives the memory something new to attach to.

Day 30: the re-engagement. A question, an update, a reason to talk again. This is the one almost everyone skips. It's also the one that decides whether you're a contact or a name they can't place.

The numbers aren't sacred. Day 6 or day 9 is fine. The shape matters: gaps that widen, and a third touch that lands before a month of other people has buried the first two.

Why “stay in touch” advice fails here

Most follow-up advice answers a different question. It's built for cold outreach: how many emails to send someone who hasn't replied before you stop. That's a persistence problem, and counting touches is a reasonable way to manage it.

A person you met in a hallway who already wrote back isn't a persistence problem. They said yes to a conversation. The risk isn't that they'll ignore you, it's that they'll forget you, slowly and without meaning to, while you wait for a good enough reason to write.

The other common answer is “stay in touch,” which has no clock at all. And advice without a clock turns into a guilt loop. You remember the person in November, feel bad it's been so long, and send a message that reads like it went to your whole list.

Timing is the variable that matters. Memory research has a lot to say about it.

What is the 2 7 30 rule for memory?

The 2-7-30 pattern comes from studying, not networking. It's a spaced-review schedule: revisit material a couple of days after learning it, again around a week, again around a month. The 2-7-30 Rule for spaced-repetition study review has no widely credited origin or single known creator ([source](https://taproot.com/2-7-30-rule/))

The science underneath is old. Hermann Ebbinghaus measured his own forgetting in the 1880s by memorizing lists of nonsense syllables and timing how long it took to relearn them. His curve drops hardest in the first day, keeps sliding through the first week, then flattens. Jaap Murre and Joeri Dros replicated it in 2015.

Two parts of that shape matter for contacts. The steep early drop is why the day-2 message works: you catch them before most of the conversation is gone. The flat tail is the other half. Whatever trace of you survives to about a month is roughly what they'll keep, and Ebbinghaus's measure was savings, the finding that relearning something is cheaper than learning it fresh. A day-30 message is relearning. Wait until month four and you're closer to starting over, with a quarter's worth of other introductions stacked on top of yours.

Two days, seven, thirty is an expanding schedule, gaps that grow instead of staying even. That shape follows the same logic as the forgetting curve itself: hit the steep early drop while it still matters, then let the intervals stretch as the curve flattens out.

The sequence, walked through

Say you meet a fleet operations director at an industry expo on a Tuesday. Ten minutes at a coffee station. They mention they're re-bidding telematics contracts in Q1, and that their team hates the current dashboard.

Thursday, you send the recap. Two sentences: good talking at the coffee station, and you'll send the case study you brought up about the re-bid. No ask.

The following Tuesday, you send the case study. You add one line about the dashboard complaint, because that detail proves you were listening and nobody else from that expo will remember it. Still no ask.

Day 30, you write about the re-bid. Is it still on track for Q1? Did the dashboard problem make it into the requirements? And if the timing's right, would 20 minutes in the next two weeks be useful?

That third message can carry an ask because the first two didn't. It opens on something they told you, not on who you are. Nobody has to wonder where they met you.

How many times should I follow up after meeting someone?

Three times in the first 30 days. Then drop to a slower cadence driven by real events: their company news, a conference you'll both attend, the quarter their project was due.

If you only have the discipline for two of the three, keep day 2 and day 30. Cut day 7. The recap anchors the memory, and the month mark is the last point where re-engagement still counts as relearning instead of a cold email. Skipping it is how a good first conversation turns into a name you can't place.

The bigger shift is when you decide. Under 2-7-30, follow-up stops being a message you remember to send and becomes a schedule you set the moment you meet someone. Three dates, fixed on day zero. That's all the system is.

The day-30 message depends on the day-0 note

The schedule is the easy part. Any calendar can hold three dates.

The hard part is what goes in the third message, because by day 30 your memory has decayed on the same curve theirs has. The telematics re-bid, the dashboard complaint, the Q1 deadline: if those details weren't written down at the coffee station, the day-30 message falls back to “Hope you've been well,” and the sequence collapses into the thing it was meant to prevent.

That's the gap Met is built for. Event Mode keeps capture running while you keep talking, so the specific detail goes onto the contact in the moment instead of into a pile of cards on Friday. Contacts stay in your own iCloud, not on someone else's server. And when it's time to write, the follow-up starts from what they actually said.

The timing is yours to keep. The context doesn't have to be.