Build a competitor intelligence brief from Zoom calls

Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Zoom and Lusha connector output, but were not pulled from a live session. Run the prompt with your own call data and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.

Competitors show up in deals in fragments — one mention on a discovery call, another on a proposal review, a passing reference in a renewal conversation. No single call tells the full story. This Claude prompt pulls every competitor mention across 30 days of Zoom transcripts, clusters patterns by frequency and stage, checks Lusha for talent moves between competitors and target accounts, and returns a monthly competitive brief with an intelligence card per competitor and two specific talking points for each.

 

The prompt

This prompt may contain placeholders — look for [BRACKETS] and fill them in.

<context>
I want to understand how competitors are showing up in my deals — not from one call, but across my last 30 days of Zoom calls. I want to know which competitors come up most often, what prospects say about them, at what stage they appear, and whether any of them recently hired from my accounts or target companies. This is a monthly competitive intelligence review, not just prep for one call.

My review:
- Timeframe: [e.g. "last 30 days" OR "last 60 days"]
- My target accounts or companies to focus on: [PASTE COMPANY NAMES — or "all calls in the timeframe"]
- What I sell: [PRODUCT / SOLUTION]
- Competitors I'm most concerned about: [LIST — or "surface from the calls"]
</context>

<task>
1. Pull all Zoom call transcripts from the specified timeframe:
   - Identify every mention of a competitor, alternative product, or "we're also looking at X"
   - Note which company raised the competitor, which call, which stage the deal was at
   - Extract the exact language used — how did the prospect describe the competitor?
   - Note whether the competitor was raised as a concern, a current vendor, or an active evaluation

2. Build a competitor frequency table:
   - Which competitors were mentioned most across all calls
   - At what deal stage do they tend to appear
   - What language do prospects use when mentioning each one — neutral, favourable, or a blocker?

3. For each competitor that appeared in 2+ calls, build an intelligence card:
   - Name and how prospects describe it
   - What the prospect said was appealing about it
   - What concern or weakness the prospect mentioned (if any)
   - How it was handled on the call — and whether the handling worked
   - Recommended response for future calls where this competitor comes up

4. Use Lusha to check whether any competitor recently hired key people from your target accounts:
   - Search for recent hires at the named competitors who previously worked at companies in your target list
   - Flag any talent moves that signal a competitor deepening relationships with your accounts

5. Return:
   - Competitor frequency table
   - Intelligence card per competitor (2+ mentions)
   - Lusha talent move flags
   - One strategic read: which competitor is the most active threat this month and why
   - Two suggested talking points to use when each main competitor comes up
</task>

<constraints>
- Use the prospect's exact language when describing what was said — don't summarise away the nuance.
- Talent move flags from Lusha must be specific: name, previous company, new company, approximate date.
- The strategic read must be based on evidence from the calls — not a general market assessment.
- If a competitor was mentioned only once: include in the frequency table but don't build a full card.
</constraints>

What you'll get back

The situation: A sales manager runs this monthly review for a team of 3 AEs. Last 30 days of Zoom calls across all target accounts. 14 calls reviewed.


Competitor frequency table — last 30 days

CompetitorMentionsCallsStage when raisedSentiment
Vendor A64 different companiesDiscovery + ProposalMixed — coverage praised, pricing questioned
Vendor B33 different companiesProposal onlyNeutral — “we’re evaluating them in parallel”
Vendor C11 companyDiscoveryNegative — “we used them before, had issues”
Internal build22 companiesDiscoveryNeutral — “we’re wondering if we could just build it”

Intelligence card — Vendor A (6 mentions)

How prospects describe it: “more data coverage in our sector” (Ashford, Dunmore) · “the enterprise-grade option” (Crestline) · “we’ve used them before and the team knows it” (Halcyon)

What prospects find appealing:

  • Sector-specific data depth mentioned by 2 prospects
  • Familiarity / previous experience at 1 account — switching cost is the real concern

What prospects mentioned as a weakness:

  • “Their pricing is way higher and the contract structure is rigid” — D.R., Ashford, May 14 call
  • “The interface is more complex than we want for the SDR team” — M.L., Ashford, May 27 call

How it was handled: Addressed on the Ashford call by referencing ease of use and per-seat flexibility. Handling worked — D.R. moved the conversation to pricing rather than switching back to Vendor A.

Recommended response: Lead with implementation speed and SDR adoption rate when Vendor A comes up — prospects who cite sector coverage are usually comparing databases, not workflows. “Coverage matters at search time — but your SDRs need to find a person and call them in 30 seconds, not run a research project.”

Talking points:

  1. “Reps who switch from Vendor A always tell me the same thing — the data was good but nobody used it after month 3. Adoption is the real metric.”
  2. “On sector coverage — tell me which specific industries you’re worried about and I’ll show you the comparison head-to-head rather than talking in generalities.”

Intelligence card — Vendor B (3 mentions)

How prospects describe it: “we’re running a parallel evaluation” (Dunmore, Briarwood, Greenway)

What prospects find appealing: Not clearly articulated — appears to be a procurement-driven parallel track rather than genuine preference.

What prospects mentioned as a weakness: None mentioned — Vendor B comes up as a process step, not a strong preference.

How it was handled: Not directly addressed in most calls — treated as background noise.

Recommended response: Don’t compete with Vendor B directly — these are procurement parallel evaluations, not genuine comparisons. Ask “what would Vendor B need to show you that we haven’t?” to surface whether there’s a real comparison or just a checkbox process.

Talking points:

  1. “Parallel evaluations are fine — I’d rather you have full information. What specific thing is Vendor B offering that you haven’t seen from us yet?”
  2. “If this is a procurement requirement rather than a genuine preference, let’s make sure we’re solving the right problem — is there something you’re not getting from us that’s driving the parallel track?”

Lusha talent move flags

⚠ J.K., previously VP of Sales at Halcyon Data, joined Vendor A as Enterprise Account Director 6 weeks ago. Halcyon is an active target account. J.K. has existing relationships with the buying team at Halcyon. This is a competitive risk — Vendor A now has an insider relationship at one of the target accounts.

Recommended action: Accelerate the Halcyon outreach. The window before J.K. re-engages the former team is narrow.


Strategic read: Vendor A is the most active threat this month

Vendor A came up in 4 of 14 calls and the language is evolving — from “we’re looking at them” (Proposal stage) to “we’ve used them before” (existing relationship). The talent move at Halcyon confirms the pattern: Vendor A is actively investing in account relationships, not just competing on product. The J.K. hire is the most concrete threat in this batch — an insider relationship at an active target account moves faster than any cold outreach. Act on Halcyon this week.

Illustrative example — fictional company and competitor names used. Run with your own Zoom calls to see live results.

Built by: Lusha
Time to build: 5 min
Difficulty: Medium
Tools: Claude, Lusha, Zoom
Type: Prompt

Why it works

The Lusha talent move flag is the finding that changes the urgency of this brief. J.K. moved from Halcyon Data to Vendor A six weeks ago. Without the flag, the Halcyon account sits in the normal pipeline cadence. With it, the Halcyon account needs to move this week — before J.K. calls the former team. The competitor frequency table and intelligence cards are useful pre-call preparation. The talent move flag is actionable intelligence that changes what happens today. No competitor intelligence system surfaces this automatically. Zoom holds the call mentions. Lusha holds the people data. The combination is what makes this brief different from reading a battle card.

Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.

FAQ

  • How often should I run this?

    Monthly for individuals, weekly for managers covering a full team. Monthly gives enough call volume to identify patterns — a single week of calls may have only one or two competitor mentions. For a team of 5+ reps running 10+ calls a week, the weekly volume justifies a weekly brief.

  • What if a competitor is mentioned but the prospect never names it directly — just says "another vendor"?

    The prompt extracts these as “unnamed alternative” and clusters each one separately. Context usually narrows it down — if the prospect says “another vendor with more coverage” in the same breath as discussing sector data, the brief flags it as likely Vendor A. Unnamed mentions are tracked but not included in named competitor cards unless the identity is reasonably clear from context.

  • Can I run this for a specific deal rather than the whole territory?

    Yes — set the target accounts field to one company name. The output scopes to that account’s calls only. For deal-specific prep, pair this with the objection brief from Zoom calls — this play gives the competitive picture, the objection brief gives the full conversation pattern.

  • What if a competitor is consistently mentioned but the team has no good response?

    The intelligence card includes “how it was handled and whether the handling worked.” If the same competitor keeps coming up and the handling consistently fails — the prospect doesn’t move on from it — the card flags that pattern. That’s a signal to bring the brief to product or marketing: the team needs a better response, not just more practice with the current one.

  • How is this different from using a battle card?

    A battle card is a static document based on product comparisons. This brief is based on what prospects actually said about a competitor in live conversations — the specific language, the context, the stage, and whether the team’s current response is working. Battle cards tell reps what to say. This brief tells reps what the prospect already thinks. The two are complementary — use this brief to update the battle cards when the field intelligence diverges from the product team’s assumptions.

Ready to build this?

Get started with Lusha and set up this play in minutes.