reach-call-recap
Turns your notes from a first call into a recap, with what they said in their words, what you promised and by when, what they said they would do, the agreed next step and date, points for the recap no
SKILL.mdpacks/outreach-pack/skills/reach-call-recap/SKILL.md
GitHubCall Recap
When To Use
The call went well, and a week later neither of you remembers what was agreed. Run this within the hour. It answers: what did they actually say, who promised what, and what happens next?
When Not To Use
Not for analysing a deal: there is no qualification, likelihood or forecast here. If no call took place, the Follow-Up Tracker is the right tool. If you took no notes at all, write down what you remember first, and say so.
Inputs
- Your own notes from the call, in any form, or what you remember.
- Your First Call Prep, to compare the questions you planned with what you learned.
- Anything either side said they would send or do. If you have none of this, I start from five lines you write from memory now and mark the recap "from memory, to confirm with them".
Approach
A recap of facts and promises, with the agreed step first: a plain writing habit, described generically. Two lists matter more than any summary: what you said you would do, and what they said they would do, each with a date. The recap note you send is how you find out whether you both heard the same thing. I work from your notes only; if you have a recording or transcript, their agreement to it comes first and is yours to confirm. The failure it prevents: "great call, let's stay in touch", and nothing after.
Workflow
- Ask at most three questions: what the agreed next step was, what you promised, and whether anything was said in confidence.
- Separate what they said from what you concluded. Their statements go in as close to their words as your notes allow, marked "they said". Your conclusions go in a separate list marked "my reading".
- List your promises with a date each. A promise with no date gets one now, set by you.
- List what they said they would do, with the date they gave or "no date given". Nothing is added that they did not say.
- Write the agreed next step and its date. If none was agreed, write "none agreed": that is the first thing your note should settle.
- Give points for the recap note you will write: the agreed step first, then your promises, then theirs, then one line inviting corrections. Points, not a note.
- List the rows for your Outreach Log: date, first call held, promises open. Leave out anything said in confidence and every impression of the person.
Output Format
# Call Recap
Call with: [name, role] | Date: [date] | Written from: [your notes / memory] | Recap note to send by: [date]
## What they said
- "[their words, as noted]" (they said)
## My reading, to check
- [your conclusion, kept apart from their words]
## Promises
| Who | What | By when |
|---|---|---|
| You | [what you said you would do] | [date] |
| They | [what they said they would do] | [date, or "no date given"] |
## Agreed next step
[Step and date, or "none agreed".]
## Points for your recap note
1. [the agreed step] 2. [your promises] 3. [theirs] 4. [an invitation to correct you]
## For the log
[date] · first call held · [promises open]
## Decision
[Your name] writes and sends the recap note by [date] and decides which promise to keep first.
Done When
- Their words and your reading are in separate lists.
- Every promise has an owner and a date, or says "no date given".
- The next step is stated, or "none agreed" is.
- The recap note itself was not written for you.
Quality Bar
- Nothing is attributed to them that your notes do not support.
- No likelihood, score or stage is attached to the conversation.
- Confidential remarks stay out of the recap and the log.
- Recording or transcribing a call needs the other person's agreement: check with a qualified adviser.
- Claude sorts your notes into facts and promises; you write the recap note and send it.
Next
Run reach-outreach-log (Outreach Log) to record the call and the promises that are still open.
About the makers
This pack is made by Polar Bear, a consultancy built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).