# Connector launch film

Recipes / Preset / Motion graphics. Checked 2026-11-13.

The viewer sees that setting it up costs one line, then sees real answers.

- Use when: Launching an MCP server, a connector or any integration.
- Phrase: eight beats in about 40 seconds: a competitor's number ticking up, the pain, the turn, the install in the host's own dialog, the question typed, the answer, one result card per data source, the payoff
- Page: https://directorchair.ai/preset/preset-connector-launch
- JSON: https://directorchair.ai/api/preset/preset-connector-launch.json

## Watch out

- Every result card carries the tool call that produced it, and the headline swaps words for live tokens; both make the answers read as real output. (practitioner; Director Chair notes on Launch video structure on Poolday (Raphael Guilhem))
- Build the host's dialog and chat from real screenshots, never an invented interface. (practitioner; Director Chair field notes on motion graphics)
- The film it was measured from was posted behind a comment gate for a paid tool; the structure is visible in the film itself. (practitioner; Director Chair notes on Launch video structure on Poolday (Raphael Guilhem))

## The beats, measured off a 40-second film

| Beat | Until | On screen |
|---|---|---|
| Hook | 4.8 s | a competitor's number ticking up |
| Pain | 10.1 s | the manual way: searching, tabs piling up |
| Turn | 13.1 s | the question that changes it, and the connector's name as a chip |
| Plug it in | 15.4 s | the host's own add-connector dialog, the address typed |
| Just ask | 18.4 s | the question typed into the chat |
| The answer | 25.7 s | the first result cards |
| Every channel | 37.1 s | one result card per data source |
| Payoff | 40 s | connected, then the logo |

## Prompts

### Any chat model

```
Give me a production plan: the shots or scenes in order, what each one needs, and the edit settings, for a short video about [your product], for [your audience]. The technique is connector launch film: the viewer sees that setting it up costs one line, then sees real answers. How it works: eight beats in about 40 seconds: a competitor's number ticking up, the pain, the turn, the install in the host's own dialog, the question typed, the answer, one result card per data source, the payoff. It is right for: launching an MCP server, a connector or any integration. Every result card carries the tool call that produced it, and the headline swaps words for live tokens; both make the answers read as real output. Build the host's dialog and chat from real screenshots, never an invented interface. Be concrete: numbers, seconds and settings, no theory. Ask me one question first if something you need is missing.
```

## Goes well with

- Launch film arc: https://directorchair.ai/script/script-launch-arc
- Tool-call label on a result: https://directorchair.ai/effect/tool-call-label
- Live tokens inside the headline: https://directorchair.ai/effect/inline-tokens
- One background plate, few cuts: https://directorchair.ai/transition/enter-on-one-plate
- Type and shapes carry it: https://directorchair.ai/format/format-motion-graphics

## Source

Own words from Director Chair field notes on motion graphics and Director Chair notes on Launch video structure on Poolday (Raphael Guilhem)

Text CC BY 4.0, Director Chair (directorchair.ai). Reference clips and their card texts belong to their makers.
