The useful record is made during the evening, not reconstructed from a photograph afterwards.
| Capture | Why it matters later |
|---|---|
| Who actually attended | The guest list is not the attendance list; a third of a room routinely changes |
| Who each guest arrived with | A +1 is a stakeholder your targeting did not know about |
| Who talked to whom | The relationships formed between guests are the asset most teams lose |
| What each guest said they were working on | The only legitimate hook for the follow-up |
| Who hosted each guest | Decides who sends the next message |
That last row is the one that gets skipped, and it is the one that makes the follow-up work.
The follow-up should come from the colleague who invited the guest, reference something that person actually said, and ask for one specific thing.
Not from the alias. Not a recap deck. Not "it was great to see you at our event" sent to fourteen people at once - senior guests can tell, and it converts a relationship back into a campaign.
Forty-eight hours is the window in which the evening is still a shared memory rather than a thing that happened.
The stalled deal. A dinner is the single most reliable way to restart a deal that went quiet, because it bypasses the channel that went quiet. The follow-up names the conversation, not the proposal.
The new stakeholder. Every +1 is someone the buying committee includes and your CRM did not. Add them to the account map that evening, with who they came with and what they care about - that relationship is the second thread into an account that was single-threaded.
The peer introduction. Two guests found each other useful. Making that introduction formally, afterwards, costs you nothing and is the most valuable thing you will do all week for the relationship - and it is the reason both of them accept the next invitation.
Attendance belongs on the account, not in an events tool nobody opens again. At minimum:
Six months later this is what tells a rep that a cold-looking account has a warm path and who holds it.
Treating the dinner as the deliverable. The room is an input; the output is a set of relationships that need to be recorded and acted on individually, by the people who hold them.
Most programs spend eighty per cent of their effort on the evening and almost none on the week after it, which is the week that produces the pipeline.