# Make your own webinars institutional memory

> Import your company's channel; three years of webinars stop being dead links and start answering questions.

- For: Marketing ops
- Category: Team Knowledge & Library Ops
- MCP tools: library_import_youtube_channel, library_search
- HTML version: https://veridive.com/mcp/use-cases/own-webinar-institutional-memory

## The problem

Your company has produced hours of expert content — webinars, product deep-dives, customer sessions, conference talks — and stores it as a YouTube channel nobody can search by what was *said*. The knowledge inside is real: your best SE explaining the integration story, the CEO's sharpest articulation of the category, the customer Q&A that answered every objection. Functionally, it's write-only memory with a play button.

The waste compounds through turnover: when the SE leaves, their recorded explanations remain — unfindable. New teammates re-derive answers the archive already holds. The content team plans next quarter's webinar without a searchable record of what the last twelve covered.

## How veridive MCP helps

**library_import_youtube_channel** converts the channel into memory: one import, every video, transcripts included. **library_search** makes the shelves navigable by title, tag and type — the instant, free layer that answers "do we have a session on X?" before anyone re-records one.

From there, the whole library stack applies to your own content: deep_context interrogation for "how did we explain <feature> in past webinars?" (cited to the minute — see the cite-the-exact-minute use case), repurposing via the webinar-to-SEO workflow, case-study extraction from customer sessions. The archive stops depreciating and starts compounding — which is what institutional memory means.

## 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. **Import the company channel** — The full archive — webinars, talks, sessions — tagged by content type as it lands.

   ```
   Import our company's YouTube channel into my veridive library, tagged 'company-archive': <channel URL> — use veridive's library_import_youtube_channel.
   ```
3. **Make it the first stop** — The 'do we already have this?' check — free, instant, before anyone re-records.

   ```
   Search the company-archive: do we have sessions covering <topic>? List them.
   ```
4. **Put the memory to work** — Interrogation, repurposing, planning — the downstream workflows all run on this import.

   ```
   From the company-archive: which topics have we covered repeatedly, and which planned topics for next quarter would duplicate existing sessions?
   ```

## Problems it solves

- Years of expert content stored as unsearchable video — write-only memory.
- Turnover erases explanations that were recorded all along.
- Content teams re-record sessions the archive already holds.
- The 'didn't our SE explain this once?' question has no retrieval path.

## Why it's valuable

- One import converts the depreciation curve: the archive compounds instead of rotting.
- The free search layer kills duplicate production before it's scheduled.
- Departed experts keep answering questions — their sessions stay queryable.
- Every downstream workflow (repurposing, case studies, interrogation) runs on this foundation.

## Example prompts

```
Import our channel, tagged 'company-archive' — use veridive's library_import_youtube_channel.
```

```
Do we have sessions on <topic>? List from the archive.
```

```
Repeated topics vs next quarter's plan — where would we duplicate?
```

## FAQ

**What does importing a whole company channel cost?**

Charged per video — a few years of webinars is a modest, one-time spend against content that cost thousands of hours to produce. Re-imports dedupe, so keeping current costs only the new uploads.

**What about unlisted webinar recordings?**

Unlisted videos import by URL individually. If the archive is split public/unlisted, import the channel plus the unlisted list — same library, one memory.

**Which use cases build on this one?**

It's the foundation layer: cite-the-exact-minute (interrogation), webinar-to-SEO posts (repurposing), customer-webinar case studies (extraction), and the ramp kit (onboarding) all assume this import exists.

## Related use cases

- [Repurpose webinars into SEO blog posts](https://veridive.com/mcp/use-cases/webinar-to-seo-posts.md) — That hour-long webinar is three blog posts; import it and draft them with structure and quotes intact.
- [Turn customer webinars into case-study drafts](https://veridive.com/mcp/use-cases/customer-webinar-case-studies.md) — Your customers already told the story on stage; import and draft the case study from their own words.
- [Settle debates by citing the exact minute](https://veridive.com/mcp/use-cases/cite-the-exact-minute.md) — "He never said that" — yes he did, at 23:41, here's the transcript. Team debates end with links, not memories.

---

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