Sales Call Notes

---
name: Sales Call Notes
description: 'A shape for the calls that move deals. Calls, deals, objections, pain
  points, next steps. Claude and ChatGPT prep the next call with real history, not
  a generic outreach script.

  '
tags:
- call
- deal
- objection
- pain-point
- next-step
containers:
- name: Sales Call Notes
  description: Every call, every deal, every objection. The memory between you and
    your AI.
  llm_instructions: |
    This is a sales call notes system. The goal is to keep every conversation grounded in the real history of the deal.
    - Before drafting a follow-up, prep, or proposal, search the relevant Deal note and the most recent Call note. Cite both.
    - Never invent a customer quote, a price discussion, or a commitment. If the answer is not in the folder, ask.
    - When the user finishes a call in conversation, suggest saving a Call note and updating the Deal note.
    - Treat the Deals folder as the source of truth for stage and next step. If a draft contradicts the deal stage, flag it.
    - Be discreet. Do not include notes from one prospect in drafts going to another.
    - This is a notes system, not a CRM. Do not pretend to sync with Salesforce or HubSpot.
  children:
  - name: Calls
    description: One note per call. Attendees, notes, decisions, next steps.
    llm_instructions: |
      Use this folder for call notes.
      - One note per call. Title format: "<Account> call <YYYY-MM-DD>".
      - Use the shipped skeleton: Attendees, Stage, Notes, Decisions, Objections raised, Next step, Owner of next step.
      - Always cross-link to the matching Deal note.
      - Tag every note with "call".
  - name: Deals
    description: One note per deal. Stage, decision criteria, stakeholders, history.
    llm_instructions: |
      Use this folder for the deal itself.
      - One note per deal. Title format: "<Account> <Year>".
      - Include: Stage, Decision criteria, Buying group, Champion, Detractors, Last call, Next step.
      - Update Stage and Next step after every call. Do not let them drift.
      - Tag every note with "deal".
  - name: Objections
    description: Recurring objections and how they have been handled.
    llm_instructions: |
      Use this folder for the objections you keep hearing.
      - One objection per note. Title is the objection in the customer's own words, as close as possible.
      - Include: When it tends to come up, What has actually worked, What has not worked, Supporting deal references.
      - When the user mentions an objection in conversation, suggest checking this folder for an existing handler.
      - Tag every note with "objection".
  - name: Pain Points
    description: Recurring problems your prospects describe. Real language only.
    llm_instructions: |
      Use this folder for the problems prospects describe.
      - One pain point per note. Title is the pain point in the customer's own words.
      - Include: Supporting calls (with dates), Quotes that landed, Which segment it shows up in.
      - When drafting outreach, pull from these notes rather than inventing pain in the abstract.
      - Tag every note with "pain-point".
  - name: Next Steps
    description: Open commitments by call. The reliable answer to 'what did I promise'.
    llm_instructions: |
      Use this folder for the things you committed to between calls.
      - One next-step per note. Title format: "<Account>: <Short action>".
      - When asked "what did I promise", return open items by account.
      - These are notes, not a live task system. If the user tracks tasks elsewhere, suggest mirroring there.
      - Tag every note with "next-step".
  notes:
  - title: Acme Corp 2026
    body: |
      A starter deal note. Replace with a real one.

      ## Stage
      Discovery.

      ## Decision criteria
      - Needs to support per-folder AI instructions.
      - Two security questions, one about data residency, one about audit logs.
      - Budget owned by Head of Engineering.

      ## Buying group
      - Champion: Sarah, Head of Product.
      - Economic buyer: Marcus, Head of Engineering.
      - Detractor: Liam, Security lead (cautious about new vendors).

      ## Last call
      [[Acme Corp call 2026-05-12]]

      ## Next step
      Send the security overview by Friday. Owner: us.

      This is a starter note. Replace it with a real deal.
    tags:
    - deal
    container_path: Sales Call Notes > Deals
  - title: Acme Corp call 2026-05-12
    body: |
      A starter call note. Replace with a real one.

      ## Attendees
      Sarah (Head of Product), Liam (Security lead). Us: Marcos.

      ## Stage entering the call
      Discovery.

      ## Notes
      Sarah walked through their current workflow. Five sources of truth, no shared memory across the product team. Liam raised data residency and audit logs early.

      ## Decisions
      Move to a security-focused follow-up call before any pricing discussion.

      ## Objections raised
      - "We do not store customer data in tools without audit logs."

      ## Next step
      Send the security overview by Friday.

      ## Owner of next step
      Us.

      See [[Acme Corp 2026]].

      This is a starter note. Replace it with a real call.
    tags:
    - call
    container_path: Sales Call Notes > Calls
  - title: 'Objection: We do not store customer data without audit logs'
    body: |
      A starter objection note. Replace with a real one.

      ## When it tends to come up
      Security-conscious buyers, usually on the first or second call. Often surfaces after the champion shows the tool internally.

      ## What has actually worked
      Sending a one-page security overview before the next call. Letting the security lead read it without us in the room.

      ## What has not worked
      Sending a longer security questionnaire. Two prospects dropped after we sent it.

      ## Supporting deal references
      - [[Acme Corp 2026]]

      This is a starter note. Replace it with a real objection.
    tags:
    - objection
    container_path: Sales Call Notes > Objections
  - title: 'Pain point: No shared memory across the product team'
    body: |
      A starter pain-point note. Replace with a real one.

      ## Description
      Product teams describe five sources of truth for customer context. None of them work for the whole team.

      ## Supporting calls
      - [[Acme Corp call 2026-05-12]]

      ## Quotes that landed
      - "Every quarter I rebuild the same picture from scratch." (Sarah, Acme, 2026-05-12)

      ## Which segment it shows up in
      Mid-stage SaaS product teams with at least one product manager and one researcher.

      This is a starter note. Replace it with a real pain point.
    tags:
    - pain-point
    container_path: Sales Call Notes > Pain Points
  - title: 'Acme Corp: send the security overview'
    body: |
      A starter next-step. Replace with a real one.

      Committed on the 2026-05-12 call. Owner: us. Target: by Friday this week.

      See [[Acme Corp 2026]] and [[Acme Corp call 2026-05-12]].

      This is a starter note. Replace it with a real commitment.
    tags:
    - next-step
    container_path: Sales Call Notes > Next Steps