# The sales call notes template top AEs actually use (with framework + download) > Source: > Published: 2026-06-05 00:00:00+00:00 # The sales call notes template top AEs actually use (with framework + download) June 5 TL;DR:Generic sales call templates track surface-level BANT data and miss the two elements that move complex deals: A stakeholder map and a running objection log. This guide's recommended 7-section format captures current state, quantified pain, stakeholder politics, objection patterns, and committed next steps. Below: That template in copy-paste form, plus a workflow comparison showing how an AI notepad like Granola enhances the template with transcript context after the call, so you can stay focused during the conversation. Most sales call templates were built for managers, not reps. They capture enough to tick a CRM field, but not enough to close a deal. The result: Manual CRM data entry consumes selling time, and the data often arrives late or incomplete by the time it matters. The context that would have won the deal never makes it out of the rep's head: Who is internally blocking the decision, which objection keeps resurfacing, what the champion's actual influence looks like. This guide breaks down a 7-section template for tracking complex deals, explains how to choose the right qualification framework, and shows the workflow that removes manual copy-paste between your notepad and your CRM. ## Why generic sales call templates fail AEs Managers built most sales call templates for reporting, not for helping reps close deals. They ask for budget range, timeline, and contact name. What they rarely ask for is who else sits in the buying committee, what resistance came up in the third call, or whether your champion actually has executive access. ### Missing stakeholder context across deals Most templates treat every call as a standalone event. You get no field for internal politics, no place to note that the VP of Finance has overridden two previous vendor decisions, and no structure for tracking how the buying committee shifts as the deal progresses. Yet the average call template gives you one field for "contact name." ### No objection tracking over time Objections do not disappear after you handle them. They resurface in the next call, get raised by a different stakeholder, or evolve into a negotiation anchor. A note that reads "prospect concerned about price" tells you nothing useful in week six of a deal. An objection log that captures the exact wording, the stakeholder who raised it, the response you used, and the outcome gives you something to work with. Most templates bury objections in paragraphs you will never read twice. ### Optimized for reporting, not recall The fields you populate for your CRM dashboard, close date, deal stage, ARR, are not the same fields that help you remember what the head of engineering said about the integration requirement on the third call. Most templates optimize for reporting rather than recall, and the [cost of that inefficiency compounds](https://granola.ai/blog/cost-manual-sales-notes-roi) across every deal in the pipeline. ## The 7-section sales call notes template The template below maps to the stages of a complex B2B deal. Use it verbatim, adapt section names to your methodology, or load it into your AI notepad as a [custom template](https://help.granola.ai/article/customise-notes-with-templates). **1. Meeting intro and attendees:** List every person present with their full name, title, and role in the buying process. Do not use shorthand like "IT guy": for example, "Marcus Reyes, Director of Infrastructure, technical evaluator." Note who was expected but absent. Flag absent stakeholders. They often signal deal risk. **2. Current state and situation:** Capture where the prospect is right now: The tools they use, the process they run, the team size involved, and any relevant context on why this problem has surfaced now. Keep this factual rather than interpretive. "150-person operations team running a legacy ERP with significant weekly manual reconciliation overhead" is useful. "They seem to be struggling" is not. **3. Pain quantification:** Capture pain in the prospect's language, with numbers attached. For example, if the head of finance says "it probably takes my team an hour a day just in updates," write that verbatim and calculate the annual labor cost. That quantified pain becomes the language for your follow-up email and your business case. **4. Stakeholder map:** See the full stakeholder mapping section below. Every call note should update your stakeholder entries with: name, title, role in the decision, position on your solution, and relationship quality. **5. Objections raised:** Capture objections with the exact wording used, not a paraphrase. Note who raised the objection, what stage the deal was at, and what response you gave. This feeds your objection log, covered in detail in its own section below. **6. Next steps and commitments:** List every commitment made by both sides, with an owner and a date. "[Prospect company] to complete [task] by [date] (Owner: [name]). Us to send [deliverable] by [date] (Owner: me)." If there is no committed date, the next step is not a next step: It is a hope. **7. Follow-up actions:** Separate from next steps, this captures internal actions needed before the next call: Updating the CRM, briefing your solutions engineer, pulling the ROI calculator, looping in customer success for a reference call. These belong in the notes so you do not lose them in a mental to-do list. You can [write these notes directly in Granola](https://help.granola.ai/article/taking-notes-in-granola) during the call, and the [AI enhancement](https://help.granola.ai/article/ai-enhanced-notes) fills in context from the transcript afterward. ## Which sales framework fields belong in your notes The 7-section template works with any qualification methodology. The framework you choose determines which specific fields you populate in sections 2, 3, and 4. | Framework | Core fields | Best fit | |---|---|---| | BANT | Budget, Authority, Need, Timeline | Short cycles, transactional sales, clear budget process | | MEDDIC | Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion | Enterprise deals, multiple stakeholders, long evaluations | | SPICED | Situation, Pain, Impact, Critical Event, Decision | Outcome-focused discovery, urgency-driven deals | ### BANT: Budget, authority, need, timeline BANT covers the four core qualification questions on a first call: Has the prospect allocated funds (Budget), who makes the final purchasing decision (Authority), does your product solve a specific problem they have now (Need), and when do they need to be live (Timeline). The limitation of BANT in complex deals is that it treats authority as a single person and ignores the buying committee dynamics that often determine outcomes. For multi-stakeholder deals, BANT is a starting point, not a complete picture. ### MEDDIC: Metrics, economic buyer, decision criteria MEDDIC goes deeper on the internal mechanics of a buying decision. Metrics quantify the impact your solution creates in the buyer's terms. Economic Buyer identifies who holds budget authority, often not the person you are talking to. Decision Criteria surfaces the factors that determine vendor selection. Decision Process maps the approval steps. Identify Pain uncovers the primary problem. Champion names the internal advocate who will sell on your behalf when you are not in the room. The Champion field is easy to underestimate when you're focused on getting the basics down. Your champion's strength and access determines whether deals move or stall after discovery. ### SPICED: Situation, pain, impact, critical event SPICED centers the framework on customer outcomes rather than rep qualification. Situation covers current state context. Pain identifies the specific problem. Impact quantifies what solving that problem means for the business. Critical Event surfaces the specific date or trigger that creates genuine urgency. Decision maps the people and process involved in the purchase. The methodology matters less than applying it consistently across every call so your notes are comparable across your pipeline. ### Choosing the right framework for your deal Use BANT for SMB deals under 30-day cycles. Use MEDDIC for deals with four or more stakeholders, budget over $50K annually, or an evaluation process that includes a procurement step. Use SPICED when your prospect's business case needs to be built, not just validated. Pick one and apply it consistently. ## How to build a stakeholder map in your notes The stakeholder map is the section most ranking templates skip entirely, and it determines whether you win multi-stakeholder deals. Every contact you engage is not equal: Some control budget, some influence the technical evaluation, some can kill a deal without attending a single call. ### Mapping decision makers vs influencers For each stakeholder, record: Full name and title, department, who they report to, their role in the buying process (economic buyer, technical evaluator, end user, champion, or blocker), and their current position on your solution (supporter, neutral, opposed, or unknown). This gives you a complete picture of the buying committee that you update after every call. ### Tracking champion strength and access Rate your champion's influence explicitly in your notes: Do they have regular access to the economic buyer? Have they successfully pushed through vendor decisions before? Have they committed to advocating internally, or just said they like the product? A champion who cannot access the economic buyer is an enthusiastic ally, not a deal-mover. ### Documenting internal politics and blockers Note which other vendors have been considered, who internally advocates for the incumbent, and whether organizational dynamics are affecting the timeline. These details rarely come out explicitly. They surface in how people answer questions and what they avoid. Write them down immediately after the call while the context is fresh. ### Updating the map after each call The stakeholder map is a living document. After each call, update your stakeholder entries to reflect anything that shifted: New names, changed positions, or a clearer read on champion access. [Sharing notes](https://docs.granola.ai/help-center/sharing/sharing-notes) with your manager or solutions engineer after key calls keeps the whole team aligned on the buying committee without a separate debrief. ## The objection log that compounds over your deal cycle An objection raised on call two will likely resurface before the contract is signed. If your notes treat each call in isolation, you handle the same objection repeatedly with no improvement in your response. An objection log turns individual moments into a cumulative asset. ### Why objections resurface in later calls A new stakeholder raises pricing concerns again. Implementation timeline pushback reappears in contract negotiations. Security requirements may resurface from evaluators who were not on the original discovery call. The pattern is predictable, but only if you have been tracking it. ### Logging objection patterns across stakeholders Use this structure for every objection entry: **Exact wording:** Write what was said, not your interpretation of it**Stakeholder and role:** Who raised it and their position in the buying committee**Date and deal stage:** When it appeared and where the deal stood at the time**Response used:** What you said or sent in response**Outcome:** What happened after your response: did the objection drop, resurface, require a follow-up commitment, or get passed to another stakeholder?**Follow-up required:** The next action that fully addresses the objection ### Tracking which responses work Over time, your objection log becomes a pattern-matching resource. You can see which responses moved specific objection types, which objections consistently preceded deal death, and which stakeholder roles raise which objections. Shared across a team, the same log that helps a single rep close a deal gives managers visibility into objection patterns across the full pipeline. This is the kind of deal intelligence that [a pipeline folder query](https://granola.ai/blog/eliminate-crm-data-entry-ai-notetakers-auto-populate-pipeline) can surface in seconds rather than hours of manual review. ### Using the log for deal reviews When a deal stalls, the objection log is your first diagnostic. Where did the last unresolved objection come from? Who raised it? What was promised in response? Has that follow-up happened? Deal reviews built on objection logs point to specific friction rather than just a slipped close date. ## Copy-paste the template The template below is ready to copy directly into your notes, CRM, or any document you already use. SALES CALL NOTES | [Company] | [Date] | [Rep Name] 1. ATTENDEES - [Name, Title, Role in deal] 2. CURRENT STATE - [Tools, process, team size, trigger for this evaluation] 3. PAIN QUANTIFICATION - [Pain in their words] | [$X / hours lost annually] 4. STAKEHOLDER MAP - [Name] | [Title] | [Role] | [Position: Supporter/Neutral/Opposed] | [Influence: H/M/L] - Champion access to Economic Buyer: [Yes/No/Unknown] 5. OBJECTIONS RAISED - [Category] | [Exact wording] | [Stakeholder] | [Response] | [Outcome] | [Follow-up] 6. NEXT STEPS (with owners and dates) - Them: [Action] by [Date] (Owner: [Name]) - Us: [Action] by [Date] (Owner: [Name]) 7. FOLLOW-UP ACTIONS (internal) - [Action] by [Date] (Owner: [Name]) ## Manual notes vs AI-enhanced notes: Workflow comparison The template is only as good as the discipline used to fill it out. Most reps know what good notes look like. The problem is filling them out in real time while also listening, asking follow-up questions, and building rapport with the prospect on the other end of the call. ### Time cost of manual template filling If a rep spends 20-30 minutes per call on notes and CRM updates across 10 calls a week, that is 3-5 hours of selling time lost to documentation. Across a five-person team, that is the equivalent of removing a full-time seller from the field. The hours do not come back unless the documentation workflow itself changes. ### How Granola enhances notes during and after the call Granola lets you stay present without sacrificing the record. During the call, you jot rough notes in Granola's notepad: The moments that matter, the exact phrase the CFO used about budget, the name of the stakeholder who was not on this call but controls the final sign-off. When the meeting ends, click "Enhance notes." Granola uses the transcript context to fill in the 7 sections of the template you have set up. Your original jotted notes stay visible in black while the AI-added context appears in gray, so you can see what came from you and what came from the transcript. Granola captures device audio without appearing as a participant in the call. This matters for pricing calls, executive recruiting conversations, and early-stage discovery where a visible recorder changes how people speak. "I use it for nearly every call to stay focused on the conversation instead of scribbling notes. The follow-up action items are especially useful. Huge time saver." -[Verified user on G2] The [HubSpot integration](https://docs.granola.ai/help-center/sharing/integrations/hub-spot) (Business plan and above) handles the CRM sync. Set up a Granola folder for your sales calls and configure the HubSpot integration with auto folder triggering so notes are sent to your CRM without manual sending. No manual copy-paste, no field-by-field entry, no logging into HubSpot after every call to update a note field. For deal reviews, Granola's folder-level chat lets you query across every sales call in your pipeline folder. Ask "Which objections are appearing most often in deals that stalled this quarter?" and Granola searches the transcript context from every call, finds the patterns, and cites the specific conversations. If your team is rolling this out, the [sales team adoption guide](https://granola.ai/blog/adoption-roadmap-sales-team-ai-notetakers) covers the playbook. Granola is [SOC 2 Type 2 compliant](https://granola.ai/updates/granola-is-soc2-type-2-compliant) and GDPR compliant. Audio is transcribed in real time and then deleted. Third-party AI providers are contractually prohibited from training on your meeting data. For sales calls that include pricing discussions or confidential deal terms, the architecture matters. ### When to use manual vs automated notes Jot what matters manually during the call: The specific phrase a prospect used, the name of a stakeholder who came up but was not on the invite, the moment the conversation shifted. These are signals a transcript cannot flag for you because you have the context to recognize them. Let Granola handle the structural heavy lifting: Populating the 7 sections, pulling relevant quotes from the transcript, and formatting the output for CRM sync. The human-in-the-loop approach means you guide what the AI captures rather than receiving a generic summary that misses the actual deal dynamics. "I can keep taking my own notes, and I never have to worry about missing anything important." -[Verified user on G2] Try Granola for free. [Download the app](https://granola.ai/download) for Mac, Windows, or iOS, connect your calendar, and run your next sales call to see the template enhancement in action. ## FAQs **What should every sales call note include?** At minimum: The buyer's core problem with a quantified impact, the stakeholders involved and their roles in the buying decision, objections raised with the exact wording used, and a committed next step with an owner and a date. If any of those four elements are missing, the note will not hold up across a multi-call deal cycle. **How detailed should call notes be?** The right length matches the deal complexity: Short-cycle SMB deals need less stakeholder depth than enterprise deals with multiple evaluators and a procurement step. Keep the main note scannable by using the structured 7-section format rather than paragraphs. **Should I take notes during or after calls?** With a transcription tool running, jot what matters during the call, not everything. Flag the moments that require follow-up, the exact phrases that belong in the business case, and the stakeholder signals that change the deal. The transcript handles capture. You handle judgment. ## Glossary **BANT**: A qualification framework covering Budget, Authority, Need, and Timeline. Used to assess whether a prospect meets the minimum criteria to enter a deal cycle. Most effective for short-cycle or transactional sales. **MEDDIC**: A qualification framework used in enterprise sales covering six fields: Metrics (quantified impact of your solution), Economic Buyer (who controls budget), Decision Criteria (how the vendor is evaluated), Decision Process (the internal approval steps), Identify Pain (the primary problem driving the purchase), and Champion (the internal advocate). **SPICED**: A qualification framework developed by Winning by Design that centers the sales process on customer outcomes. Covers five fields: Situation (current state context), Pain (the specific problem), Impact (the business value of solving it), Critical Event (the specific date or trigger that creates genuine urgency), and Decision (the people and process involved in the purchase).