Sales meeting notes template (discovery calls, free)
Last updated
This sales meeting notes template follows a discovery call from the prospect's current situation through to the next step both sides agreed. Each heading maps to a field most CRMs already have, so the notes can be typed up once and the deal record updated from them without rewriting. It is written for the first or second call with a prospect, but works for any sales meeting where you need to know where the deal stands.
Download it as a Word file, copy the plain-text version into your CRM, or read the filled-in example of a discovery call for a payroll software deal.
Word file (.docx), free and without signing up. Opens in Google Docs and Pages too.
What’s in the template
The minutes open with these details:
- Company
- Contact (name, role)
- Other attendees (name, role)
- Our attendees
- Date
- Meeting type (discovery / demo / proposal / negotiation)
- Source of the lead
- Notes taken by
Then the body follows the meeting in this order:
- 1. Current situation — How they do it today: tools, process, team size, volumes. Facts, in their words.
- 2. Pain — What is going wrong and what it costs them in time, money or risk. If they gave a number, write the number.
- 3. Goals — What they want to be different, and by when. Separate must-haves from nice-to-haves.
- 4. Decision process — Who decides, who influences, what steps they go through (pilot, security review, procurement) and their timeline.Decision maker: · Influencers: · Steps before signing: · Target decision date:
- 5. Budget — Whether a budget exists, roughly how much, and what they pay today. "Not discussed" is a valid answer; a guess is not.
- 6. Competition — Other vendors they are talking to, and the option of doing nothing.
- 7. Objections and concerns — What they pushed back on, and how you answered. Unanswered objections go to the action list.
- 8. Next step agreed — A specific action with a date, agreed by the prospect in the call. A call without a next step is not a qualified opportunity.Next step: · Date: · Who does what:
- 9. Deal assessment — Your view in one or two lines: fit, likelihood, stage. Internal only.
At the end: action items, as a table you can keep across meetings.
The template
Download it as a Word file, or copy the text version into your own document.
Sales Meeting Notes Company: Contact (name, role): Other attendees (name, role): Our attendees: Date: Meeting type (discovery / demo / proposal / negotiation): Source of the lead: Notes taken by: 1. Current situation [How they do it today: tools, process, team size, volumes. Facts, in their words.] 2. Pain [What is going wrong and what it costs them in time, money or risk. If they gave a number, write the number.] 3. Goals [What they want to be different, and by when. Separate must-haves from nice-to-haves.] 4. Decision process [Who decides, who influences, what steps they go through (pilot, security review, procurement) and their timeline.] Decision maker: Influencers: Steps before signing: Target decision date: 5. Budget [Whether a budget exists, roughly how much, and what they pay today. "Not discussed" is a valid answer; a guess is not.] 6. Competition [Other vendors they are talking to, and the option of doing nothing.] 7. Objections and concerns [What they pushed back on, and how you answered. Unanswered objections go to the action list.] 8. Next step agreed [A specific action with a date, agreed by the prospect in the call. A call without a next step is not a qualified opportunity.] Next step: Date: Who does what: 9. Deal assessment [Your view in one or two lines: fit, likelihood, stage. Internal only.] Action items No. | Action | Owner (us / prospect) | Due | Status
What sales notes must record
Sales notes are read by people who were not on the call: your manager at pipeline review, a colleague who covers for you, and the person who takes over the account after the deal closes. For each of them the useful notes are facts the prospect stated, not your impression of how it went. "Positive call, keen to move forward" tells the next reader nothing. "Runs payroll for 140 staff across 6 sites on spreadsheets; finance director wants it automated before the April year-end; budget approved up to 15k a year" tells them everything.
- The current setup and numbers: headcount, volumes, systems, what they pay now.
- The pain in the prospect's words, and what it costs them if they said.
- Who makes the decision and the steps between here and a signature.
- The next step with a date the prospect agreed to.
- Objections you could not answer in the call.
Fields that map to a CRM
Most CRMs have fields for stage, close date, amount, decision maker, competitor and next step. The template's headings are ordered so you can fill those fields straight from the notes. Put the facts in the structured fields and keep the narrative in the notes body; a close date in a paragraph is invisible to a forecast report. Update the CRM the same day; a deal record that lags the notes by a week gets forecast wrong.
The handover
When the deal closes, the implementation or account team inherits these notes. Write for them from the first call: what the prospect was promised, what they were worried about, who the sceptic was, and which deadlines matter to them. A good handover note is mostly a tidy copy of the discovery notes with the outcome of each objection filled in. If notes are only in your head, the customer will have the same conversation twice and notice.
Common mistakes
- Writing how the call felt instead of what was said. Keep the assessment to the one internal line at the end.
- Recording your pitch. The prospect's answers are the notes; your slides are already in the deck.
- No next step, or a vague one. "Follow up in a couple of weeks" is not a next step; "demo for the finance team on 27 October, Luke to invite the HR manager" is.
- Guessing the budget. Write what they said, including "would not say".
- Leaving objections out because they were awkward. They are the part the next call has to handle.
Example: filled-in sales meeting notes
What the template looks like once it’s been used. The organisation and people are made up.
Discovery call notes: Bramble Creek Hospitality Group, Ledgerly Payroll
Company: Bramble Creek Hospitality Group (four restaurants, one hotel)
Contact: Luke Harrington, Finance Director
Other attendees: Jenna Cole, HR Manager
Our attendees: Sofia Marchetti, Account Executive, Ledgerly Payroll
Date: Friday 16 October 2026
Meeting type: Discovery call, 35 minutes
Source: Inbound, pricing page enquiry
Notes taken by: Sofia Marchetti
1. Current situation
Around 210 staff, roughly 160 of them hourly, across five sites. Payroll is run fortnightly by Jenna Cole and one assistant using a legacy desktop package plus spreadsheets for rota hours. Rotas are kept in a separate scheduling app with no integration, so hours are re-keyed every fortnight.
2. Pain
Re-keying takes about two days per pay run and produced errors in three of the last six runs, one of which underpaid 14 staff and had to be corrected with an off-cycle payment. Luke Harrington estimates the re-keying alone costs around 40 hours a month. Staff complaints about pay errors are reaching the general managers.
3. Goals
Must-have: hours flow from the scheduling app into payroll without re-keying, live before the financial year-end in April 2027. Nice-to-have: staff can see payslips on their phones; tips distribution handled in the same system.
4. Decision process
Decision maker: Luke Harrington, with sign-off from the managing director for anything over 10,000 a year. Influencers: Jenna Cole (day-to-day user), the group's external accountant, who files returns. Steps: demo to Jenna's team, a reference call with a similar hospitality customer, then a proposal. Target decision: end of November 2026, to allow implementation before April.
5. Budget
Currently paying about 3,800 a year for the desktop package plus the assistant's time. Luke said a budget of "up to around 12,000 a year" would be justified by the time saved, but it is not formally approved.
6. Competition
Has had one call with another cloud payroll vendor; Jenna found their scheduling integration limited to one app, not the one Bramble Creek uses. Doing nothing is an option Luke described as "not really", given the error rate.
7. Objections and concerns
Jenna Cole: worried about migrating mid-year and parallel-running two systems. Answered with the standard two-cycle parallel run; she wants to see it in the demo.
Luke Harrington: asked whether the scheduling app integration is live or on a roadmap. It is live; Sofia to send the integration documentation. Not fully answered in the call: how tips are handled; action raised.
8. Next step agreed
Demo for Jenna Cole and her assistant on Tuesday 27 October 2026 at 2:00 pm, focused on the scheduling integration and the parallel run. Luke Harrington will attend the first 15 minutes. Sofia Marchetti to send the integration documentation and a tips-handling note beforehand.
9. Deal assessment
Good fit: live integration with their scheduling app is the deciding feature. Realistic close in December if the demo lands. Stage: discovery complete, moving to demo.
Action items
| No. | Action | Owner | Due |
|---|---|---|---|
| 1 | Send scheduling integration documentation | Sofia Marchetti (us) | 19 October 2026 |
| 2 | Send note on tips distribution handling | Sofia Marchetti (us) | 23 October 2026 |
| 3 | Invite payroll assistant to the demo | Jenna Cole (prospect) | 20 October 2026 |
| 4 | Propose a hospitality reference customer for a call in November | Sofia Marchetti (us) | 30 October 2026 |
Tips for sales meeting notes
- Write numbers down the moment they are said: headcount, pay runs, current cost, error counts. They are what the proposal is built on.
- Ask who else is involved in the decision before the call ends, and write the names in. It is the field most often left blank.
- Record objections as questions you still owe answers to, with a date for the answer.
- Put the prospect's own phrases in quotes. They reappear usefully in the proposal and the demo.
- Fill the CRM from the notes within the hour. Discovery details are the first thing you forget.
- Keep the deal assessment to one or two lines and keep it out of anything you send the prospect.
Related templates
- Client meeting notes template — For agencies, consultants and advisers: a record of what the client asked for and what each side agreed to, written so it can be sent back to them.
- Meeting summary template — The short recap you send after a meeting: decisions, actions and open questions, written to be read in two minutes.
- One-on-one meeting template — A running record for the regular manager and report conversation: priorities, support needed, feedback and growth.
- Business meeting minutes template — A simple, professional format for any business meeting: agenda items with discussion, decision and action, and next steps.
- All meeting minutes templates
Or let the notes write themselves
A template helps when you’re the one typing. If you’d rather not be, an AI note taker can draft the summary and action items for you. Most send a bot into the call; QuietNote captures from your own computer instead, so nothing joins the meeting and you decide when capture starts. It’s in private beta. Whatever you use, read the draft before you send it, and tell attendees you’re recording where the rules require it.
Questions
What should you write down in a sales meeting?
The prospect's current setup and numbers, the problem they described and what it costs them, what they want and by when, who decides and how, budget if discussed, competitors, objections, and the next step with a date. Write what they said rather than how the call went; the next reader needs facts.
What questions should you ask on a discovery call?
Enough to fill each section of the notes: how do you do this today, what goes wrong, what would good look like, who else is involved in the decision, what is your timeline, have you set a budget, who else are you talking to. Ask them in a conversation rather than as a checklist, and write the answers in the prospect's words.
How do you take notes during a sales call without losing the conversation?
Keep the template open and type short fragments under the headings as the prospect talks, not full sentences. Numbers and names first. Fill the sentences in straight after the call while it is fresh. Some reps note only the facts during the call and write the next step and assessment immediately afterwards.
What is a good next step at the end of a sales call?
A specific meeting or action the prospect agreed to, with a date and attendees: a demo for a named team, an introduction to the decision maker, a reference call. "I will follow up next month" is not a next step. If the prospect will not commit to one, note that too; it is useful information about the deal.
Can sales calls be recorded or transcribed with AI?
Many sales teams use AI tools to transcribe calls and draft notes, and a transcript is a good source for exact figures and phrases. Recording requires consent in many places and it is good practice to say so at the start of the call. The structured fields, especially the decision process and the next step, still need a person to confirm them.