Recipes / Competitor battlecard from a call mention

Competitor battlecard from a call mention

Gong + Perplexity + Notion

IntermediateAEs

Who it's for

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.

What you get

Battlecard draft, waiting for approval before it goes into Notion. Sample output: every company and person in it is 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.

Time and cost

Estimate About 10–15 minutes, most of it checking sources.

Assumptions: One competitor mentioned in one deal, with three to five web lookups.

Gong: One ask_deal call about the competitor, which uses Gong credits. Every call uses credits. All three tools (ask_account, ask_deal, generate_brief) consume Gong credits based on the volume of calls and emails analyzed; briefs cost more per open-ended section. Same consumption as the equivalent API requests. Source: help.gong.io, checked 2026-10-16
Perplexity: Three to five search calls, each billed to your Perplexity API key or organization. Every call uses credits. Tool calls are billed at standard Perplexity API pricing to the connected API key or to the API organization chosen at sign-in; the organization's rate limits apply. Source: docs.perplexity.ai, checked 2026-10-16
Notion: One search for an existing page, then one new page after you approve it. Credit use not confirmed by Notion.

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: Claude

Gong Up · auth

ClaudeChatGPTRead onlyEvery call uses credits
https://mcp.gong.io/mcp
Perplexity Up · auth

ClaudeClaude CodeCursorRead onlyEvery call uses credits
https://api.perplexity.ai/mcp
Notion Up · auth

ClaudeChatGPTClaude CodeCursorCopilotRead + writeCredits not confirmed
https://mcp.notion.com/mcp

Set up in a chat app

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

Connect Gong without code (Claude, ChatGPT)
Connect Perplexity without code (Claude)
Connect Notion without code (Claude, ChatGPT)

Developer setup

Auth setup and mcp.json for Claude Code and Cursor

Gong: Sign in with OAuth in your client (run /mcp in Claude Code). Do it once interactively, and the client stores and refreshes the token.
Perplexity: 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": {
    "gong": {
      "url": "https://mcp.gong.io/mcp"
    },
    "perplexity": {
      "url": "https://api.perplexity.ai/mcp"
      // headless alternative: "headers": { "Authorization": "Bearer YOUR_PERPLEXITY_API_KEY" }
    },
    "notion": {
      "url": "https://mcp.notion.com/mcp"
    }
  }
}

Step-by-step prompts

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.
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.
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.
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.

Run it on a schedule (optional)

This works best run by hand, the same day a competitor comes up on a call.
A monthly scheduled refresh of the public section can work: draft the update and send it to you, and change Notion only after you approve it.
Perplexity needs an API key or an API organization that can pay for usage, and every call is billed. Set that up before you schedule anything.

Where this goes wrong

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.

Gotchas

Perplexity's OAuth sign-in needs you to be an admin of a Perplexity API organization that can pay for usage. Otherwise use an API key. In claude.ai you add it as a custom connector with the server URL.
Perplexity calls are billed at standard API pricing, and your organization's rate limits apply. This listing hasn't confirmed Perplexity for ChatGPT.
Gong charges credits per call and leaves out private calls. If the competitor came up on a private call, Gong won't find it.
Notion's help center names ChatGPT Pro as the supported ChatGPT tier. Workspace admins can also control MCP access, so check with yours if you can't connect.

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 competitor-battlecard-notion.md

Vendor sites: Perplexity. If we join an affiliate program, these links will be labeled as affiliate links.