Writing UGC Scripts with Claude

The difference between a script that converts and one that gets scrolled past is not the offer it is whether it sounds like a real person talking

The difference between a script that converts and one that gets scrolled past is not the offer. It is whether the script sounds like a real person talking or a marketing team writing.

Claude can write both. Your job is to give it the right instructions so it produces the real-person version and not the marketing version.

What Makes a Script Sound Human

Most AI-generated scripts fail because they over-explain, use formal language, and sequence the offer too early. A real person talking about a service they genuinely liked does not start with features and benefits. They start with the moment they realised they had a problem.

What authentic UGC sounds like: incomplete sentences are fine such as "And the thing is." First-person specific details like "I was spending like four hours every Sunday doing bookings by hand." Conversational filler is normal such as "So basically what happened was." The outcome is specific and not vague: "Three weeks in, my no-show rate dropped from 20% to about 4%." And the CTA is casual and not salesy: "If you want the same, the link is in the bio."

What branded copy sounds like: "Introducing the revolutionary booking solution that transforms your business." "Our state-of-the-art platform delivers seamless customer experiences." Any sentence that sounds like it was written for a brochure.

The 6-Part UGC Script Structure

Every format follows this same underlying structure. The length changes. The emphasis changes. The structure stays consistent.

Hook (0 to 3 seconds)

One sentence. Makes the specific viewer stop. No greeting. No intro. No branding. Start mid-situation or mid-statement.

Problem (3 to 12 seconds)

Name the specific problem in the viewer's language and not your language and not industry language. The exact words they would use to describe what is frustrating them.

Bridge (12 to 20 seconds)

The moment of discovery. "Then I found" or "Then someone showed me" or "Then we tried." Keep it brief. This is the transition and not the explanation.

Solution (20 to 35 seconds)

Describe what the solution actually does. Not a list of features but the experience of using it. What it feels like after.

Proof (35 to 45 seconds)

One specific result. One number, one time frame, one outcome. Avoid vague words like "much better" or "way more." Say exactly what changed.

CTA (45 to 55 seconds)

One action. Casual tone. Platform-appropriate such as "link in bio" for Reels, "comment yes and I'll send it" for Facebook, or "DM me" for Instagram Story.

The Full Claude Script Prompt

Use this prompt every time you need a new UGC script:

Using @UGC.md and @SALES.MD — write a UGC script in the [FORMAT] format
for [PLATFORM].

Format: [Problem/Solution Talking Head / Client Story / Tutorial / etc.]

Platform: [Instagram Reels / Meta Ad / YouTube Shorts / TikTok]

Length target: [15-30 / 30-45 / 45-60 seconds]

Speaker perspective: [person speaking as themselves / as a client /

as a tutorial host]

Rules for this script:

• Do not start with "Hi" or any greeting
• Do not use the brand name in the first 3 seconds
• Use informal language — contractions and incomplete sentences are fine
• The problem must use words the audience would use and not our words
• The proof must include at least one specific number or time frame
• The CTA is one action only in a casual tone

Specific details to include:

- Problem we're solving: [PASTE FROM SALES.MD OR DESCRIBE]
- Outcome to feature: [SPECIFIC CLIENT RESULT OR TARGET OUTCOME]
- CTA: [WHAT ACTION DO YOU WANT THE VIEWER TO TAKE]

Write three versions:

1. Problem-first (start with their frustration)
2. Outcome-first (start with the result and work backwards)
3. Question hook (start with a direct question to the viewer)

Under each script note the word count and approximate duration at

normal speaking pace.

Script Editing Checklist

After Claude generates the three versions, review each one with these questions before moving to production.

Does it pass the real person test? Read it aloud. Does any sentence sound like it came from a brochure? If yes that sentence needs to be rewritten in simpler language.

Is the problem specific enough? "Struggling with time" is not specific. "Spending Sunday evenings manually entering bookings into a spreadsheet" is specific. The more specific the problem, the more the right viewer recognises themselves.

Is the proof real? Do not invent numbers. If you do not have a specific client result yet, use a range such as "most clients see" or use your own experience such as "since I started using this system myself."

Is the CTA singular? One action. Not "follow, comment, and click the link." One.

Is it under your target length? Count the words. 130 words is approximately 60 seconds at normal speaking pace. 65 words is approximately 30 seconds. For HeyGen, avatar speech tends to run slightly slower so aim for 10% fewer words than your target duration.

Prompt for Naturalising a Script

If Claude's output still sounds too polished, paste the draft back and use this:

This script sounds like marketing copy. Rewrite it so it sounds like

a real person talking casually — someone telling a friend about

something that actually worked for them.

Remove any sentence that sounds like it belongs in a brochure.

Replace formal language with contractions and simpler words.

Add one or two realistic hesitations or casual phrases.

Keep the structure but change the tone completely.

[PASTE SCRIPT]

Storing Scripts in UGC.md

Every script that performs, meaning it generates views, clicks, or leads, gets saved in UGC.md under a Scripts section. This lets you do two things.

You can ask Claude to write "another version of the script that got 3.2% CTR" without re-explaining the context. And you can see which formats and hook types actually work for your specific audience so you stop guessing and start building on what converts.

Before and After: Script Editing in Practice

Claude's first draft which is too polished: "Are you tired of spending hours managing bookings manually? Our revolutionary booking system automates your scheduling, reduces no-shows by up to 80%, and gives you your time back. Get started today and experience the difference."

After naturalising: "I was spending basically every Sunday night on booking admin. Like, manually texting confirmations, chasing people who didn't show up, re-entering everything into a spreadsheet. Then someone built me a proper booking system and that whole thing just stopped. No-shows went from about one in five to maybe one in twenty. If that sounds familiar, link in bio."

Same offer. Same outcome. Completely different conversion rate.