A booked meeting isn't a held meeting, and a held meeting isn't an accepted meeting. If you only count booked meetings, the pipeline looks better than it is, and whoever takes over the meeting inherits guesses. This template counts the three separately.
After a first meeting, the person who booked it and the person who takes it over agree on a verdict: accepted, pending (with what's missing and a date) or rejected (with a reason code). The handoff note quotes the prospect's reason for the meeting in their own words, not the rep's interpretation.
The template
MEETING QUALIFICATION
Company: [name] Meeting date: [date]
Present from the prospect: [name, role]
Present from us: [name, role]
Booked by: [name] Taken over by: [name]
Meeting held: Yes / No / No-show
1. WHY THEY TOOK THE MEETING, IN THEIR OWN WORDS
"[quote from the prospect]"
Said by: [name, role]
2. QUALIFICATION
Framework we use: [e.g. BANT, MEDDIC, SPICED or our own]
Status: Confirmed / Hypothesis / Unknown. Leave it blank rather than guess.
| Question | Answer | Status |
|------------------------|--------|--------|
| Need / pain | | |
| Impact | | |
| Who decides | | |
| Decision process | | |
| Timing | | |
| Budget | | |
3. NEXT STEP
What: [e.g. demo for the CFO]
Date: [date, agreed in the meeting]
Who from the prospect: [name]
4. VERDICT
Accepted / Pending / Rejected
Decided by: [who booked it] and [who takes it over]
If Pending:
What's missing: [e.g. who makes the decision]
Decide by: [date]
If Rejected, reason code:
- No need
- Wrong person
- No budget
- Bad timing
- Outside ICP
- Already bought
RULE
No next step with a date = not accepted.
How to fill it in
Meeting header
Write down who booked the meeting and who takes it over, even if it's the same person. Mark whether the meeting was held. A no-show isn't a rejected meeting; it's a meeting to rebook.
Why they took the meeting
Write what the prospect said, not what you hoped they'd say. "We lose deals because nobody calls back within a day" says more than "interested in efficiency." If no one on the prospect's side can say why they took the meeting, that's a signal in itself.
Qualification
Pick one framework and stick with it, so everyone judges meetings the same way. BANT, MEDDIC and SPICED are common choices. The rows in the template cover what most frameworks ask about, so rename them if your framework uses different words. Mark what the prospect confirmed, what you're guessing and what you don't know.
Next step
A next step is something the prospect has said yes to, with a date. "They'll get back to us" isn't a next step. Book the next meeting before you hang up.
Verdict
Make the call together, the same day. Accepted means the meeting moves forward. Pending needs a line on what's missing and a date when you'll decide. Rejected needs a reason code, so that over time you see why meetings fall through: the wrong people are being booked, the wrong companies, or at the wrong time.
Good questions for the first meeting
Need / pain
- What made you take this meeting now?
- How do you handle this today?
- What isn't working about that?
Impact
- What happens if you do nothing over the next six months?
- How does the problem show up in the numbers?
- Who's affected the most?
Who decides
- Who else needs to be involved before you decide?
- Who signed off the last time you bought something similar?
Decision process
- How did it go the last time you bought a new system?
- What steps are there between a yes from you and a signed contract?
- Does IT or legal need to review it?
Timing
- When does this need to be in place, and why then?
- Is anything driving the date, like a contract that's running out?
Budget
- How do you usually find money for something like this?
- Is there a budget already, or does someone need to put one together?
A fictional example
This example is made up. A sales development rep has booked a meeting with a Swedish logistics company. The meeting was held, with the CEO and the head of sales.
Why they took the meeting: "We have three reps calling from the same Excel file, and nobody knows who talked to whom last." (head of sales)
| Question | Answer | Status |
|---|---|---|
| Need / pain | Double calls and dropped follow-ups | Confirmed |
| Impact | The head of sales estimates a few deals a quarter slip away | Hypothesis |
| Who decides | The CEO | Confirmed |
| Decision process | The CEO and the CFO, no formal procurement | Hypothesis |
| Timing | Before the next sales year | Confirmed |
| Budget | Not discussed | Unknown |
Next step: a demo for the CEO and the CFO, date booked in the meeting.
Verdict: Accepted. The budget is unknown, but there's a next step with a date, and the CFO is joining the next meeting.
Funnelfeedr fills in part of this for you
- Qualification from the meeting. Qualification frameworks such as BANT, MEDDIC and SPICED, along with roles and decision makers, are picked out of recorded meetings and calls. Deal qualification
- No-shows get followed up. With booking pages, a no-show creates a rebooking task, so it doesn't get lost. Scheduler