# Competitor battlecard from a call mention

Source: https://mcpforgtm.com/recipes/competitor-battlecard-notion (StackMCP, independent directory of official MCP servers)

## Goal

AEs who hear a competitor named on a call and want a short battlecard before the next one, saved where the team can find it. Gong can be swapped for Fireflies or Granola. No Notion? Ask for the battlecard as text and paste it into your team's doc.

## Connected tools

- Gong: https://mcp.gong.io/mcp (setup: https://mcpforgtm.com/tools/gong)
- Perplexity: https://api.perplexity.ai/mcp (setup: https://mcpforgtm.com/tools/perplexity)
- Notion: https://mcp.notion.com/mcp (setup: https://mcpforgtm.com/tools/notion)

## Guardrails

- Read only in Gong and Perplexity.
- Every public claim needs a source link and a date. Drop anything without one.
- Label everything from Gong as a summary, not a quote.
- Show me the full battlecard draft first. Create the Notion page only after I approve it.
- Never edit, move or delete an existing Notion page. If a battlecard already exists, show it to me and ask what to do.

## Steps

1. Use Gong ask_deal on my {company} deal to find what the prospect said about {competitor}: what they liked, what worried them, any pricing or offers they mentioned, and who said it on which call. Label it as Gong's summary, not quotes.
2. Use Perplexity to find current public information about {competitor}: their pricing page, product news from the last six months, and common complaints in public reviews. Start with their website domain, and give me a link and date for every claim. Drop anything without a source.
3. Draft a one-page battlecard: what the prospect said, what's public (with links), where we win, where we're weak, three landmine questions, and how to answer their top objection. Mark anything I should verify. Show me the draft here.
4. Search Notion for an existing page about {competitor} under {battlecard_parent_page}. If one exists, show it to me and stop. If not, create the battlecard as a new page under {battlecard_parent_page} only after I approve it, and send me the link.

## Expected output

Battlecard draft, waiting for approval before it goes into Notion. Example (all names fictional):

```
Battlecard: Tidewell Metrics (fictional)
Triggered by: Fernhill Software (fictional) deal, call on Oct 14 with Priya Raman

What the prospect said (Gong summary, not quotes)
- Priya likes Tidewell's built-in dashboards and said their demo looked finished.
- She worried about Tidewell's per-seat pricing as the team grows past 50 users.
- Tidewell offered a free 30-day pilot.

What's public (Perplexity, with sources)
- Pricing page lists three per-seat tiers; the top tier adds SSO. [1] tidewell.example/pricing, checked Oct 16
- Announced a new forecasting module in September. [2] tidewell.example/blog/forecasting, Sep 22
- Public reviews mention slow support response times. [3] reviews.example/tidewell, Aug to Oct 2026

Where we win: flat pricing at 50+ users; SSO in every tier.
Where we're weak: fewer ready-made dashboards out of the box.

Landmine questions:
1. What will your cost look like at 80 users next year?
2. Is SSO a must-have, and which tier gives you that?
3. How fast did support respond during the pilot?

Top objection ('Their dashboards look more finished'): offer a 20-minute build of Priya's own weekly report.

Verify before sharing: [3] is based on a small number of reviews.
Not created yet. Notion: no existing 'Tidewell' page found under Battlecards. Reply 'create' to add it as a new page.
```

## Watch for

- Stale or unsourced public claims: Competitor pricing and features change often. Require a link and a date for every public claim, drop anything without one, and open the pricing link yourself before the card is shared.
- A different company with a similar name: Web results can mix up companies with similar names. Have the draft list the competitor's website domain at the top, and check that every source matches it.
- A Gong summary used as a customer quote: Gong's MCP server returns AI answers, not raw transcripts. Keep the prospect section labelled as a summary, and check the call in Gong before anyone quotes it.
- Prospect details in a shared space: A battlecard is read by the whole team. Before you approve the Notion page, decide whether the prospect's name and pricing comments should be in it, and remove them if not.