# How to turn launch footage into a content kit with Claude

> A launch content kit is an inventory of the usable moments in your launch footage, sorted by where each one will run: the product reveal for paid social…

Canonical URL: https://vivu.ai/guide/turn-launch-footage-into-a-content-kit-with

A launch content kit is an inventory of the usable moments in your launch footage, sorted by where each one will run: the product reveal for paid social, the spoken benefit lines for cutdowns, the interface close-ups for the product page, the price and spec frames for retail partners. Claude can build and keep that inventory once it knows what is in the footage. Getting it there is the actual work, because much of what matters in launch footage is visual and a transcript won't reach it. Treat every number that appears on screen as unverified until it matches the approved price sheet.

## Write the kit from the placements backwards

Start from the placements. For each one, write what it needs in plain words ("product in hand, no text on screen", "presenter states the main benefit"), because those lines become your searches. Give each moment columns for source, range, status and rights. If the launch mixes agency or creator footage with your own, not all of it may be cleared for every channel, and the rights column is where that shows up. Before booking pickup shots for a gap, search what you already have, since a missing shot is sometimes one nobody logged.

## Four ways to get the footage in front of Claude

Export stills and the keynote transcript and attach them to the chat. That's quick for a single hero film, and on a multi-camera launch day the exporting becomes the job.

Connect a filesystem MCP server, and Claude reads the camera folders and any shot logs. It won't know which clip has the product in hand. A [folder structure that leaves camera originals untouched](https://vivu.ai/guide/how-do-i-organize-video-files-for-editing) helps the people on the team here more than it helps Claude.

Build a transcript index with a vector database behind it. It covers what the presenter said, and [searching by spoken words](https://vivu.ai/guide/search-video-by-spoken-words) shows where exact-word matching stops finding what you remember. B-roll and on-screen specs need a picture index on top, which is a bigger build.

Use a hosted video search connector that indexes picture and sound and lets Claude search over MCP. It costs an upload step and a usage allowance. It finds moments, and cutting and versioning stay in your editing tools.

## Inventory the launch footage from a Claude chat

Once [Vivu](https://vivu.ai/mcp) is added to Claude as a custom connector, upload the launch footage into one project, because a search only looks inside a single project. Ask for what each placement needs, such as "find the first time the product appears on screen" or "find the moment a price or cost breakdown appears on screen". A precise search returns once the whole job has finished, with short time ranges and a one-line reason for each, and for on-screen text the reason paraphrases what the screen shows, so you can tell at a glance whether it's the screen you wanted. Preview each range on the results page and export the original clip for the ones that make the kit.

Claude sorts the ranges into the kit doc by placement and lists the placements that are still empty. Any price or spec it lifted from a reason stays marked unverified, because a number in a demo or concept shot may only be illustrative, and a paraphrase sits one step further from the source.

## When this route doesn't fit a launch

It doesn't fit a kit that needs one search across several projects, since one search can't reach across projects, or a launch whose agency contract keeps masters off outside services, since the footage has to be uploaded to a Vivu project and indexed in the cloud. Every search in the kit comes out of a plan allowance too, and Vivu's MCP page sets out the free and paid tiers with their limits; what you get back are ranges to open, while exact frames and every cutdown stay with your editors.

## When you don't need any of this

A launch with one hero film and an agency that already delivered the cutdowns has a kit already; it just needs a list. The same goes when the editor who cut the launch film is building the kit, since nobody knows the footage better.

## Deciding whether your launch needs it

Count the placements and the footage. When there are more placements than anyone can hold in their head and more footage than anyone watched end to end, a kit built from searches gives the team something to check instead of something remembered. When one person watched everything, let them write the kit and use Claude to format it.

## FAQ

### Can I use prices and specs that a video search reads off the screen?

Not without checking. A search result that describes on-screen text is a paraphrase, and concept or launch footage can show numbers that were only ever illustrative. Open the frame, compare it with the approved price sheet, and only then let the number into copy.

### Can Claude make the cutdowns and social versions for a launch kit?

Not in this workflow. Claude organizes the kit, and the video search finds the moments and prepares original segments for download. Cutting and resizing happen in your editing tools, by your editors.

### Should agency footage and in-house footage go in the same project?

If you want one search to cover both, yes, since searches run inside a single project. Confirm first that the agency footage, raw takes included, is licensed for every channel in the kit.

### How do I check for existing shots before booking a reshoot?

Describe the shot you think is missing, search the launch project for it, and preview what comes back. A near match from the launch day may be usable with a different crop, and a shot that truly isn't there is worth booking with a clear note on why it's needed.