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

Source: https://mcpforgtm.com/recipes/objection-library (StackMCP, independent directory of official MCP servers)

## Goal

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.

## Connected tools

- Fireflies: https://api.fireflies.ai/mcp (setup: https://mcpforgtm.com/tools/fireflies)
- Notion: https://mcp.notion.com/mcp (setup: https://mcpforgtm.com/tools/notion)

## Guardrails

- Read only in Fireflies. Don't share, rename, move or clip any meeting.
- Use only external sales calls in the quarter I name, and show me the list before searching transcripts.
- Quote the buyer and the rep for every objection and reply, with the meeting title and date.
- Leave buyer names out of the page. Company names and dates are fine.
- Show me the full page draft, and create it in Notion only after I approve it.

## Steps

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.

## Expected output

Q3 objection library draft, waiting for approval. Example (all names 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.
```

## Watch for

- Questions counted as objections: "How does pricing work?" is a question, not pushback. Require a buyer quote for every objection, and drop any line where the buyer was only asking for information.
- A reply credited for a win it didn't cause: A follow-up meeting can happen for other reasons. Count a reply as 'moved forward' only if a next meeting was agreed on the same call or a later call with the same company appears in Fireflies, and show both numbers next to each other.
- Internal calls and the wrong quarter mixed in: Team syncs and deal reviews mention objections too. Confirm the meeting list (external attendees, dates inside the quarter) before any transcript search, and say how many calls were left out.
- Quotes that aren't in the transcript: The model may tidy a quote or merge two lines. Have it give the meeting title and date for every quote, and spot-check three in Fireflies before you approve the page.