Conversation Log
When To Use
You told three people "I will send you that" and cannot remember which three. In a job, a system and a team caught those; now a dropped promise is the whole impression someone has of your new practice. This log answers: what is still open, and who am I due to get back to?
When Not To Use
If you want to decide what to do this week, the log feeds Weekly Selling Hour and is not a to-do list. If you want notes on how keen or how senior someone seemed, that is not kept here or anywhere in this guide.
Inputs
- Your own notes from a call, a coffee chat or a reply, in any form
- The existing log, if you have one
- Where it lives: a private Project, or a spreadsheet through file creation that you keep yourself. Never a shared space.
If you have none of this, I start from what you remember of your last conversation and mark the output as a first draft.
Approach
A contact log is old, plain practice. Its risk is equally old: notes about people slowly turn into profiles of them. So this log holds two kinds of thing only, facts about a conversation and promises, yours and theirs. No sales system is needed for a first year of conversations; a table you actually keep is enough. The failure it prevents is the quiet one: you said "I will introduce you to someone who has done exactly this", meant it, and three weeks later they have stopped expecting it.
Workflow
- Ask at most three questions: who you spoke to and when, what kind of conversation it was, and whether anything was promised on either side.
- Write one row per conversation: date, who, context, what they said they need (paraphrased in your words, never pasted from a message), what you promised and by when, what they promised, and the next date you set.
- Pull every promise into the open list, yours first. A promise without a date gets one now, set by you; "soon" is how introductions get lost.
- Strip anything that is not a fact or a promise: ratings, "warm" or "cold", impressions, guesses about budget or intent, anything personal shared in confidence. I flag those lines and leave them out.
- Mark promises kept with the date you kept them, and keep the row; the monthly review counts what you did.
- Check where the log lives. If any copy sits somewhere shared, including a former employer's tools, move it to your private place before adding more.
Output Format
# Conversation Log
Kept in: [my private Project or file] | Last updated: [date]
## Open promises
| Who | What was promised | By whom | By when | Status |
|---|---|---|---|---|
| [name] | [introduction, document, answer] | [me / them] | [date] | [open / kept on date] |
## Conversations
| Date | Who | Context | What they said they need | What I promised | What they promised | Next date |
|---|---|---|---|---|---|---|
| [date] | [name] | [call / coffee chat / reply] | [my paraphrase] | [promise and date, or none] | [promise, or none] | [date I set] |
## Left out
- [line removed: rating, impression or confidence]
## Decision
[Your name] decides by [date] which open promise to keep first, and sets each next date personally.
Done When
- Every conversation row has a date, a context and a next date.
- Every promise has an owner and a date, and open promises are listed first.
- No rating, impression or confidential detail remains.
- The log sits in a private place only.
Quality Bar
- Paraphrase in your words; never paste message or email text.
- What they said they need is about their work, never about them as a person.
- No column for warmth, value, likelihood or priority of a person.
- Holding notes on other people carries data protection duties: check with a qualified adviser.
- Facts and promises from your own conversations, kept private by you; no one is rated.
Next
Run start-monthly-practice-review (Monthly Practice Review) at the end of the month, to see what these conversations and your numbers add up to.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: start-conversation-log3description: Keeps a private Conversation Log of who you spoke to and when, what they said they need, what you promised and by when, what they promised and the next date, holding facts and promises only with no ratings. Use for "run start-conversation-log", "log this conversation", "what did I promise", "who did I say I would send that to", "personal CRM for a one-person business", "keep track of my conversations", "what is still open from my calls", part of the Claude Guide for New Founders Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/start-conversation-log6---78# Conversation Log910## When To Use11You told three people "I will send you that" and cannot remember which three. In a job, a system and a team caught those; now a dropped promise is the whole impression someone has of your new practice. This log answers: what is still open, and who am I due to get back to?1213## When Not To Use14If you want to decide what to do this week, the log feeds Weekly Selling Hour and is not a to-do list. If you want notes on how keen or how senior someone seemed, that is not kept here or anywhere in this guide.1516## Inputs17- Your own notes from a call, a coffee chat or a reply, in any form18- The existing log, if you have one19- Where it lives: a private Project, or a spreadsheet through file creation that you keep yourself. Never a shared space.20If you have none of this, I start from what you remember of your last conversation and mark the output as a first draft.2122## Approach23A contact log is old, plain practice. Its risk is equally old: notes about people slowly turn into profiles of them. So this log holds two kinds of thing only, facts about a conversation and promises, yours and theirs. No sales system is needed for a first year of conversations; a table you actually keep is enough. The failure it prevents is the quiet one: you said "I will introduce you to someone who has done exactly this", meant it, and three weeks later they have stopped expecting it.2425## Workflow261. Ask at most three questions: who you spoke to and when, what kind of conversation it was, and whether anything was promised on either side.272. Write one row per conversation: date, who, context, what they said they need (paraphrased in your words, never pasted from a message), what you promised and by when, what they promised, and the next date you set.283. Pull every promise into the open list, yours first. A promise without a date gets one now, set by you; "soon" is how introductions get lost.294. Strip anything that is not a fact or a promise: ratings, "warm" or "cold", impressions, guesses about budget or intent, anything personal shared in confidence. I flag those lines and leave them out.305. Mark promises kept with the date you kept them, and keep the row; the monthly review counts what you did.316. Check where the log lives. If any copy sits somewhere shared, including a former employer's tools, move it to your private place before adding more.3233## Output Format34```markdown35# Conversation Log36Kept in: [my private Project or file] | Last updated: [date]37## Open promises38| Who | What was promised | By whom | By when | Status |39|---|---|---|---|---|40| [name] | [introduction, document, answer] | [me / them] | [date] | [open / kept on date] |41## Conversations42| Date | Who | Context | What they said they need | What I promised | What they promised | Next date |43|---|---|---|---|---|---|---|44| [date] | [name] | [call / coffee chat / reply] | [my paraphrase] | [promise and date, or none] | [promise, or none] | [date I set] |45## Left out46- [line removed: rating, impression or confidence]47## Decision48[Your name] decides by [date] which open promise to keep first, and sets each next date personally.49```5051## Done When52- Every conversation row has a date, a context and a next date.53- Every promise has an owner and a date, and open promises are listed first.54- No rating, impression or confidential detail remains.55- The log sits in a private place only.5657## Quality Bar58- Paraphrase in your words; never paste message or email text.59- What they said they need is about their work, never about them as a person.60- No column for warmth, value, likelihood or priority of a person.61- Holding notes on other people carries data protection duties: check with a qualified adviser.62- Facts and promises from your own conversations, kept private by you; no one is rated.6364## Next65Run start-monthly-practice-review (Monthly Practice Review) at the end of the month, to see what these conversations and your numbers add up to.6667## About the makers6869This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).