Sales Meeting Notes Template
The buyer said the quiet part out loud on minute 34. "Our current process broke this quarter, and it cost us a renewal." You thought about writing it down. Then someone asked a question, the conversation moved on, and by the time you hung up, the exact sentence was gone.
A transcript would have kept the words. A transcript would not have told you the deal moved. Sales notes, done right, do both. They keep the proof and the motion.
This is a sales meeting notes template you can copy into any doc, CRM note, or notes app. It is built around one idea: the note exists to advance the deal, not to record it.
Why most sales notes go nowhere
Most reps write what happened, in the order it happened. That reads like a transcript with the words shuffled. It doesn't tell you, or your manager, what to do next.
A sales note should answer seven questions:
- Why did we meet?
- What is the buyer trying to change?
- How do we know it matters to them?
- What did we agree or decide?
- What could still kill the deal?
- Who is actually deciding?
- What happens next, and who owns it by when?
If your note can't answer those, it's a diary entry, not a sales note.
The template
Copy this and fill in the brackets. Leave nothing blank. "Unconfirmed" is a valid answer, and it becomes the first thing on your next call.
Deal overview
- Account:
- Date:
- Stage (discovery / demo / proposal / closing):
- Our attendees:
- Their attendees (name, title, role in the buying process):
What they're trying to fix
- Surface complaint:
- Underlying pain (whose job, which workflow, why, what gets worse):
- Business impact:
Why now
- Trigger or timing:
- Target timeline:
- Cost of doing nothing:
Who decides
- User:
- Champion:
- Budget holder:
- Possible blocker:
What landed and what didn't
- Feature or point that resonated, and the pain it maps to:
- What fell flat:
Open questions and objections
- Concern, who raised it, and what we owe them:
Decisions made
- What was agreed (even "no decision" is a decision):
Next steps
- Owner: [name] will [action] by [date]
- Owner: [name] will [action] by [date]
Follow-ups promised
- What we promised, to whom, by when:
- What they promised, to whom, by when:
Next meeting
- Date, purpose, required attendees:
How to fill each field
Deal overview. Notes that don't map to an account, a deal, and a stage are orphaned the moment the call ends. Write the buying role next to every name, not just the title. "VP Operations" tells you nothing; "the person who runs the workflow we'd replace" does.
What they're trying to fix. Dig past the surface. "They're unhappy with their tool" is a surface complaint. "Three regional managers rebuild deal history by hand before every coaching call" is a pain you can sell against. Record it in their words, not yours.
Why now. A pain without a date is a nice conversation. Write the trigger: a renewal coming up, a new hire, a leadership change. If you don't know, write "unconfirmed" and ask on the next call.
Who decides. The person on the call is rarely the only person in the deal. Map user, champion, budget holder, and blocker separately. A champion who can't approve budget is still a champion, just not a close.
What landed and what didn't. Both matter. What fell flat today is what you don't repeat next call, and it's usually the real objection wearing a costume.
Open questions and objections. Write the concern and what you owe them. A security question with no owner and no deadline is a deal risk you've chosen not to see.
Decisions made. "We'll move to a technical review" is a decision. So is "the buyer is ghosting us." Write both.
Next steps. An owner and a date, or it isn't a step. "Send the deck" is a wish. "Jordan will send the security overview by Thursday" is a commitment.
Follow-ups promised. Track what each side promised. The fastest way to lose a deal is to forget something you said you'd do.
Templates for each call type
The same fields shift weight depending on the call.
| Call | Capture first | Where it goes next |
|---|---|---|
| Discovery | Trigger, pain, decision path | CRM note + follow-up task |
| Demo | What resonated, what didn't, open questions | Follow-up email + next validation step |
| Pricing | Budget, approvals, objections, alternatives | Proposal + deal-risk flag |
| Pilot | Success measures, users, owners, checkpoints | Pilot plan + evaluation date |
Fill most of it automatically
Meetbook captures this same structure while the call is happening. Its sales notes pull out budget, authority, need, timeline, objections, next steps, and a low-to-high deal-risk read, and every point links back to the quote, the speaker, and the timestamp it came from. When the call ends you get the summary and action items with owners, delivered to Slack or Notion.
So you can stop transcribing your own calls and keep the parts of this template a machine can't do: the "why now" read, the blocker nobody named, the next step that actually moves the deal.
If you'd rather hand-type it, the template above works in any doc. Either way, the note has one job. Advance the deal.
