> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stefanbrain.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Follow the content contract in AGENTS.md.
> Treat text as the canonical explanation; video and screenshots enhance it.
> Do not publish unverified product behavior or duplicate an existing canonical article.

# Chat: Turn 20 ad hooks into conversational UGC scripts

> Use Stefan's outline-first workflow to fix forced transitions, write a complete talking-to-camera ad, and carry your feedback into the next concept.

Turn a promising hook into a complete talking-to-camera script without rewriting the whole ad every time a transition feels wrong.

In this playbook, Stefan writes conversational “yapper” ads: story-led scripts that sound like someone talking, rather than reading a sales presentation. His main checkpoint is the outline. Fix the story there, then write the dialogue.

## Practical use cases

> [card] Build your next creator brief
>
> Turn one hook from a 20-concept batch into complete spoken copy, giving your creator a connected story instead of disconnected talking points.

> [card] Fix an ad that suddenly sounds salesy
>
> Find where a character starts reciting product details and rewrite the transition so the recommendation follows naturally from the conversation.

> [card] Stop repeating the same corrections
>
> Carry your accepted edits into the next concept so you spend review time on its new story, not the same voice and structure problems.

## Watch Stefan's playbook

<video controls playsInline preload="metadata" poster="/images/tutorials/qa/yapper-ad-poster.jpg" alt="Stefan reviews a conversational ad outline in Chat" aria-label="Stefan's outline-first workflow for conversational UGC ad scripts">
  <source src="https://stefanbrain.com/api/video/adaptive/tutorials/write-conversational-ugc-ad-scripts/full-frame-2026-10-14.mp4" type="video/mp4" />

  [Watch Stefan's UGC script playbook](https://stefanbrain.com/api/video/adaptive/tutorials/write-conversational-ugc-ad-scripts/full-frame-2026-10-14.mp4)
</video>

[Watch on Loom](https://www.loom.com/share/39fb5583fa4b40ac9ea60893a7d4dc9b)

[Open Stefan's example Chat and script](https://stefanbrain.com/share/c1541894-914a-4f8f-b6ff-378f1057ec95?workspace=outputs%2Fnorse_organics_medspa_insider_script.md)

## Before you start

Open [Chat](https://stefanbrain.com/chat) with your Product context, intended audience, and current offer. Attach your ad-writing framework if you have one.

Stefan uses a reusable framework to guide the story. You can use your own, or start with the outline request below. Keep brand facts separate from any reference used for voice.

## Follow the workflow

**1. Generate 20 hooks, then choose one story**

Look for different situations and points of view, not 20 ways of saying the same opening line. Use this batch to choose which stories deserve a full outline:

```text wrap theme={"system"}
Give me 20 distinct hooks and concepts for conversational talking-to-camera ads for our Product and [audience]. For each, give me the opening line, speaker, situation, and the story it could lead into. Use the attached framework if relevant. Vary the ideas, not just the wording.
```

Choose one concept you can develop with your actual product information and usable source material. You do not need to write all 20 scripts at once.

**2. Ask for an outline before the script**

Catch missing story connections before they become several paragraphs of dialogue:

```text wrap theme={"system"}
Outline concept [number] first. Show the opening, what happens next, how the speaker discovers a different approach, the product introduction, and the close. Use our Product facts and offer. Wait for my feedback before writing the script.
```

For a longer story, Stefan's example follows these beats: hook, incident, turning point, explanation, product discovery, research, decision, early experience, later progress, and CTA.

Use only beats your material supports. Do not invent customer experiences, professional credentials, or results to fill a slot.

**3. Check what each person knows and why they say it**

Read the outline as a conversation. Why does this topic come up? How does the person know the answer? Does the next beat follow from the previous one?

In the walkthrough, Stefan challenges a relative suddenly explaining technical skincare details. Changing the speaker alone does not fix everything: the conversation still needs a reason to begin.

Use focused feedback to repair the weak beat while preserving what works:

```text wrap theme={"system"}
Keep the hook and first two beats. The transition in beat three feels forced: the other person starts explaining the problem without being asked. Have the speaker raise their frustration first, then make the reply respond to it. Keep the explanation within what this person would actually know. Return the revised outline.
```

**4. Separate a recommendation from a product pitch**

A friend recommending something does not need to deliver its entire product page. Let the recommendation lead to the speaker's own research where that fits the story.

Use this revision when a believable conversation turns into a feature list:

```text wrap theme={"system"}
Keep the recommendation brief and conversational. Move the detailed product explanation into the speaker's later research, using our supplied facts. Preserve the reason they become interested and the connection to the opening. Return the revised outline.
```

If Chat keeps borrowing the wrong story from a reference, start a fresh Chat with the framework, chosen concept, and Product facts. Compare the outlines before carrying over the full example.

**5. Write complete spoken copy and read it aloud**

Once the outline connects, produce a script you can review from beginning to end:

```text wrap theme={"system"}
This outline works. Write the complete spoken script using the corrections we agreed on. No timestamps or production directions—just the script. Keep the dialogue natural and preserve our Product facts and offer.
```

Listen for abrupt questions, repeated explanations, exaggerated metaphors, and phrases the speaker would not say. Check that the hook still leads into the body.

If one transition is still wrong, name it. You do not have to restart the whole draft:

```text wrap theme={"system"}
Keep the opening and everything after the product discovery. Rewrite only the conversation that connects them: the speaker should bring up the problem before the other person responds. Then return the full script with that change included.
```

**6. Apply your feedback to the next concept**

Once one script works, use the same Chat to develop the next selected idea. Preserve your writing decisions without cloning the previous story:

```text wrap theme={"system"}
Next, develop concept [number]. Apply the feedback we agreed on about natural transitions and concise recommendations. Give this concept its own situation and story. Outline first and wait for my feedback before writing.
```

Save each finished script with its concept name so your creator or editor can identify the right version.

## Try it in other situations

* **A founder-led ad:** Start with a real customer question and the founder's reason for building the product. Check that the explanation answers that question before introducing the offer.
* **A customer-story ad:** Use an actual interview or review to outline the problem, discovery, and experience. Keep quotations and results faithful to that source.
* **A product demonstration:** Build the outline around a visible frustration and demonstration. Let the demonstration explain the difference instead of adding an invented expert endorsement.

## Before handing the script to a creator

* Can someone follow the story without seeing the outline?
* Does every recommendation or explanation have a natural trigger?
* Are personal experiences, qualifications, product claims, and offer details supported by your source material?
* Have you saved one complete script rather than a collection of revision fragments?

For visual directions and production notes, turn the chosen script into [one complete editor brief](https://docs.stefanbrain.com/knowledge-base/chat/write-and-generate-ads.md#create-one-complete-editor-brief).

## Related playbooks

* [Develop more original hooks and turn one into an ad](https://docs.stefanbrain.com/knowledge-base/chat/develop-original-hooks-and-ad-copy.md)
* [Turn competitor ads into native ads for your product](https://docs.stefanbrain.com/knowledge-base/chat/write-a-batch-of-native-ads.md)
* [Save and reuse your best prompts with Snippets](https://docs.stefanbrain.com/knowledge-base/chat/reuse-prompts-with-snippets.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.