Recipes / Objection library from calls: this quarter's objections and the replies that worked

Objection library from calls: this quarter's objections and the replies that worked

Fireflies + Notion

IntermediateAEsSales leadersMarketing

Who it's for

AEs, sales leaders and product marketers who want the objections buyers actually raised this quarter, with the rep replies that kept deals moving, in one page the team can use. Fireflies can be swapped for Gong (deal-by-deal summaries, no quotes) or Granola. Notion can be swapped for keeping the library as text, and Highspot can check what objection content you already have.

What you get

Q3 objection library draft, waiting for approval. Sample output: every company and person in it is fictional.

Q3 2026 (Jul 1 to Sep 30): 58 external sales calls in Fireflies. You confirmed 41 (17 internal or no-show meetings left out).
Objections found: 63 across 34 calls.

1. "We already have a process for this" (status quo): 19 mentions in 16 calls
   Buyer, Fernhill Software (fictional), Aug 12: "Honestly the spreadsheet works fine for us today."
   Reply that moved it: "Totally fair. How long did last month's close take with the spreadsheet?" The buyer said 6 days, and a scoping call was booked on the same call.
   Moved forward after this reply: 9 of 16 calls (a follow-up meeting with the same company appears later in Fireflies).

2. Price: 14 mentions in 12 calls
   Buyer, Quarry Lane Analytics (fictional), Sep 3: "That's about double what we budgeted."
   Reply that moved it: Alex Rivera offered to start with one team and set the expansion terms in writing. Pricing review booked for Sep 10.
   Moved forward: 5 of 12 calls.
   Reply that stalled: discounting on the call before asking about budget. 0 of 4 calls had a follow-up.

3. Security review timing: 11 mentions in 10 calls
   Buyer, Larkspur Freightworks (fictional), Jul 22: "Our security team is booked through October."
   Reply that moved it: sending the completed questionnaire up front. Moved forward: 7 of 10 calls.

Not enough evidence (fewer than 3 calls): data residency (2), contract length (2).
Buyer names are left out of the page. Companies and dates are kept so reps can find the call.

Notion page (not created yet): 'Objection library: Q3 2026' under Sales Enablement. Reply 'approve' to create it.

Time and cost

Estimate About 30–45 minutes, most of it checking quotes and choosing which replies to keep.

Assumptions: One quarter with about 60 recorded calls, of which about 40 are external sales calls you confirm.

Exact credit costs depend on your plan with each vendor. Check the tool pages before a large run.

MCP servers

Every server is confirmed in: ClaudeChatGPTCursor

Set up in a chat app

Every server in this recipe is confirmed for Claude and ChatGPT. Connect each one, then paste the prompts below into one conversation.

Developer setup

Auth setup and mcp.json for Claude Code and Cursor
  • Fireflies: Sign in with OAuth, or pass an API key as a Bearer token for headless use.
  • Notion: Sign in with OAuth in your client (run /mcp in Claude Code). Do it once interactively, and the client stores and refreshes the token.

Put this in .mcp.json (Claude Code, project root) or ~/.cursor/mcp.json (Cursor). Swap the example keys for your own, and don't commit real ones. Remove the // comment lines if your client requires strict JSON.

{
  "mcpServers": {
    "fireflies": {
      "url": "https://api.fireflies.ai/mcp"
      // headless alternative: "headers": { "Authorization": "Bearer YOUR_FIREFLIES_API_KEY" }
    },
    "notion": {
      "url": "https://mcp.notion.com/mcp"
    }
  }
}

Step-by-step prompts

  1. List my Fireflies meetings between {quarter_start} and {quarter_end} that were external sales calls: date, title, company and attendees. Leave out internal meetings and give me the total. Wait for me to confirm the list.
  2. Search the transcripts of the confirmed calls for objections: price, timing, status quo, security, competitors, and any others you find. For each one, quote what the buyer said and what the rep replied, with the meeting title and date. Show me a table. Don't change anything in Fireflies.
  3. For each objection, mark whether the call moved forward: a next meeting agreed on the call, or a later Fireflies meeting with the same company. Group by objection, most common first, and show the replies that moved forward next to the ones that stalled.
  4. Draft a Notion page called 'Objection library: {quarter}' with one section per objection: how often it came up, two buyer quotes, the best reply to use, and one reply to avoid. Leave out buyer names. Show me the full draft, and find {parent_page} in Notion.
  5. After I approve the draft, create the page under {parent_page} in Notion. Don't edit any other page.

Run it on a schedule (optional)

Where this goes wrong

Gotchas

Download

Get the prompts, guardrails and expected output as one Markdown file. Paste it into a Claude Project or ChatGPT project's instructions, or save it as CLAUDE.md for Claude Code.

Download objection-library.md