# Build a living competitor dossier your team can query

> One shared library of rival content, searchable and chat-able — new teammates stop asking "where's the competitor doc?"

- For: Chief of Staff
- Category: Market & Competitor Research
- MCP tools: library_import_youtube_channel, library_search, deep_context
- HTML version: https://veridive.com/mcp/use-cases/living-competitor-dossier

## The problem

Somewhere in your company there's a doc titled "Competitive Landscape — FINAL (updated)". It was accurate the week it was written. Since then: two rival launches, a repositioning, a pricing change, and forty Slack messages that each contained one perishable insight about a competitor, now unfindable. Competitive knowledge doesn't die of wrongness — it dies of staleness and scatter.

The fix isn't a better doc; docs freeze. What compounds is a *dossier that stays primary-source*: the rivals' actual launches, demos, talks and interviews, collected as they happen, queryable by anyone on the team the moment a deal, a roadmap debate or a board question makes a competitor suddenly urgent.

## How veridive MCP helps

**library_import_youtube_channel** is the collection mechanism: each rival's channel imported and tagged, transcripts and all. New uploads join with a re-import — the dossier grows on their publishing schedule, not your update discipline.

**library_search** and library_list keep the shelves navigable — find the right launches and talks by title and tag in seconds, free. **deep_context** is the interrogation room: scope a question to a competitor's videos and get an answer **cited to the exact chunk** — "what does <rival> claim about security?" answered in thirty seconds, with receipts, by anyone. And because the MCP connection is shareable config, the dossier answers inside every teammate's own assistant: sales prepping a deal, product prepping a review, you prepping the board.

## How to run it

1. **Connect veridive MCP** — One-time setup: add the veridive MCP server to Claude, ChatGPT, Cursor or any MCP client and generate your API key. Takes about two minutes.
2. **Found the dossier** — Import each tracked rival's channel, tagged by company. Skip Shorts to keep the signal density high.

   ```
   Import <rival A>'s and <rival B>'s YouTube channels into my veridive library, tagged by company, skip Shorts — use veridive's library_import_youtube_channel.
   ```
3. **Prove it answers** — Ask the questions your team currently answers from memory. deep_context scopes to the tagged videos and cites the moments.

   ```
   From the <rival A> videos in my library: what do they claim about <capability>, and which customer types appear in their stories? Cite the videos and moments.
   ```
4. **Hand the team the keys** — Share the MCP connection the way you share tool config — project-level mcp.json or a shared connector. The dossier now answers wherever anyone works.

   ```
   Search my library for <rival B>'s launch videos from their latest release and summarize what shipped, with citations.
   ```

## Problems it solves

- Competitive docs freeze on their write date while rivals keep shipping.
- Insights scatter across Slack threads and individual memories — unfindable exactly when a deal needs them.
- Every new PM and AE re-does the same competitor research their predecessor already did.
- Claims about rivals circulate unsourced, so strategy debates run on folklore.

## Why it's valuable

- The dossier stays primary-source and current — it's the rivals' own published record, continuously collected.
- Anyone answers competitor questions in seconds, cited; the CoS stops being the bottleneck.
- Onboarding a hire onto the competitive landscape becomes "ask the dossier," not a week of link archaeology.
- Free searching and listing means browsing the shelves costs nothing; credits go only to imports and deep questions.

## Example prompts

```
Import <rival>'s channel into my library, tagged '<rival>', skip Shorts — use veridive's library_import_youtube_channel.
```

```
From the <rival> videos: what do they claim about <capability>? Cite moments.
```

```
Search my library for <rival> launch videos and summarize what shipped in their last release, cited.
```

## FAQ

**How is this different from the competitor-channel watchtower?**

Same foundation, different job: the watchtower is a strategy team's monitoring loop (themes, drift, quarter-over-quarter). The dossier is the whole team's reference desk — deal prep, roadmap reviews, board questions — built to be queried by many hands.

**How does the team actually share it?**

An MCP connection is configuration — share it like any tool config (a project-level mcp.json, a shared connector in your assistant). Everyone's AI then queries the same curated library.

**How does it stay current?**

Re-import each rival's channel on a cadence (idempotent — already-imported videos dedupe; you're charged per new video). The dossier updates on their publishing schedule.

## Related use cases

- [Stand up a competitor-channel watchtower](https://veridive.com/mcp/use-cases/competitor-channel-watchtower.md) — Import every competitor's channel and interrogate all of it in one conversation — "what did they emphasize this quarter that they didn't last?"
- [Stand up a research library your whole team queries](https://veridive.com/mcp/use-cases/company-research-library.md) — Curate once, query forever: shared imports become a common brain with citations instead of link-dump Slack threads.
- [Assemble a new-hire ramp kit from curated videos](https://veridive.com/mcp/use-cases/new-hire-ramp-kit.md) — Point new hires at the library, generate study notes per module, and let them ask the library questions instead of you.

---

Part of the veridive MCP use-case library: https://veridive.com/mcp/use-cases.md
Server docs for agents: https://veridive.com/mcp.md