# Build a sales-coaching corpus from public teardowns

> Import the best teardown channels and coach reps by querying situations — "show me discovery-call openers."

- For: Sales manager
- Category: Team Knowledge & Library Ops
- MCP tools: library_import_youtube_channel, deep_context
- HTML version: https://veridive.com/mcp/use-cases/sales-coaching-corpus

## The problem

Sales coaching runs on examples, and managers ration them from a thin supply: their own calls (limited, dated), the team's recordings (compliance-gated, awkward to teardown publicly), and whatever clips they've bookmarked over the years. Meanwhile the coaching moment is always specific — this rep, this weakness, right now — and the ration rarely has the right example on hand.

The supply problem is solved in public: sales-training channels publish teardowns, role-plays and technique breakdowns continuously — hundreds of coachable moments, professionally dissected. What's missing is retrieval by situation: when the rep needs discovery-openers, you need every strong discovery-opener example, not a channel to browse.

## How veridive MCP helps

**library_import_youtube_channel** builds the corpus: the two or three best teardown channels for your motion, imported and tagged — a permanent coaching asset that grows with their publishing schedule.

**deep_context** is the retrieval-by-situation: *"show me the moments across the corpus where sellers handle an early pricing push"* — answered with **citations to the videos and minutes**, ready to drop into a coaching session. The rep watches four strong examples of exactly their weakness, back to back, sourced in two minutes. Coaching stops being rationed by the manager's memory and starts running on a library that always has the right clip.

## 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. **Build the corpus once** — The best teardown channels for your motion, imported and tagged 'coaching'.

   ```
   Import these sales-teardown channels into my library, tagged 'coaching': <channel URLs> — use veridive's library_import_youtube_channel. Skip Shorts.
   ```
3. **Retrieve by situation** — The coaching moment's exact need, pulled across the whole corpus with citations.

   ```
   From the coaching corpus: find the moments where sellers handle <situation — e.g. an early pricing push in discovery>. Cite the videos and minutes.
   ```
4. **Run the session on examples** — Four strong examples of the rep's exact weakness, back to back — then the rep's own attempt.

   ```
   Summarize what the strongest of those examples have in common — the pattern I should coach toward.
   ```

## Problems it solves

- Coaching examples are rationed from the manager's memory and bookmarks.
- The right example for this rep's weakness is never on hand at the coaching moment.
- Team call recordings are compliance-gated and awkward for public teardown.
- Reps hear technique described when watching it performed is what transfers.

## Why it's valuable

- Situation-level retrieval: any weakness, four strong examples, two minutes.
- The corpus compounds on the channels' publishing schedule — import once, refresh cheaply.
- Coaching sessions run on watching and comparing, the mode that actually transfers.
- Pairs with the objection playbook: the playbook drills the words; the corpus shows the delivery.

## Example prompts

```
Import these teardown channels, tagged 'coaching', skip Shorts: <URLs> — use veridive's library_import_youtube_channel.
```

```
Moments where sellers handle <situation>, cited to video and minute.
```

```
What do the strongest examples share? The coachable pattern.
```

## FAQ

**How is this different from the objection-playbook use case?**

The playbook (search + key-quotes) extracts objection-response pairs as drill text; the corpus (import + context) retrieves performed examples by situation for watching. Enablement builds the playbook once; managers query the corpus weekly.

**Which channels belong in the corpus?**

The teardown channels whose calls match your motion — B2B discovery, enterprise, transactional. Two or three good ones beat ten mediocre; the import spend should follow your coaching taste.

**Can reps query it themselves?**

That's the mature version: the corpus shared via the team's MCP config, reps pulling examples before the manager asks. Self-serve coaching supply, manager keeps the diagnosis.

## Related use cases

- [Build an objection playbook from call teardowns](https://veridive.com/mcp/use-cases/objection-handling-playbook.md) — Public sales-call teardowns hold hundreds of live objections; extract them with key-quotes into a playbook.
- [Mine public demos for win/loss signals](https://veridive.com/mcp/use-cases/demo-mining-win-loss.md) — Watch how rivals demo the features you lose deals on and get a cited summary of the exact claims they make.
- [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