Below are 7 example UGC ad plans for software, each a second by second table you can copy. They are example plans we wrote for fictional but realistic products. They are not real ads, and they come with no results. Each one shows a different hook and a different way to prove the claim on screen.
How to read these examples
Every plan follows the same order: hook, problem, proof on screen, payoff, call to action. "Creator" is the person on camera, real or AI. "Recording" is the product's real screen. Only example 3 opens with a personal story, and it says how to change it for an AI creator. The others work as written with a paid creator or an AI creator. The UGC ad guide explains each part.
Example 1: invoicing app for freelancers (20 seconds, TikTok)
Example plan. Product type: online invoicing with automatic payment reminders.
| Time | On screen | Said |
|---|---|---|
| 0 to 3 s | Creator at a desk, phone at arm's length | "Stop writing 'just following up' emails." |
| 3 to 6 s | Creator, slightly annoyed | "Clients pay late. Chasing them takes forever." |
| 6 to 12 s | Recording: create an invoice, switch on "Remind every 3 days" | "Turn on reminders once, when you send the invoice." |
| 12 to 17 s | Recording: the reminder schedule, then a "Paid" badge | "It nudges them for you, until it's paid." |
| 17 to 20 s | Creator, then the sign-up page | "Free for your first 3 clients. Link below." |
Why it is built this way: the hook quotes a phrase the viewer has typed many times. The proof is one switch, so it fits in 6 seconds.
Example 2: AI meeting notes (15 seconds, YouTube Shorts)
Example plan. Product type: a web app that turns a meeting recording into notes and tasks.
| Time | On screen | Said |
|---|---|---|
| 0 to 2 s | Recording: a finished task list, already filled | "This list wrote itself." |
| 2 to 6 s | Creator as a circle in the corner, over the recording | "Upload the meeting. Get the decisions and who owns what." |
| 6 to 12 s | Recording: upload, then notes and tasks appear | "Each task has a name and a date." |
| 12 to 15 s | Creator full frame | "Try it on your next meeting." |
Why it is built this way: it starts on the result (a "show first" hook). In 15 seconds there is no room for a problem shot, so the result is the problem's answer.
Example 3: team task manager (30 seconds, Instagram Reels)
Example plan. Product type: a task board for teams of 5 to 20.
| Time | On screen | Said |
|---|---|---|
| 0 to 3 s | Creator in a kitchen, coffee in hand | "Monday standups used to take my team 40 minutes." |
| 3 to 7 s | Screen of a long chat thread, scrolling | "Half of it was 'who's doing what?'" |
| 7 to 14 s | Recording: the board, filtered to "This week" | "Now it's one board. Filter to this week." |
| 14 to 21 s | Recording: tasks with owners and due dates; creator as a cut-out at the bottom | "Every task has an owner and a date. No guessing." |
| 21 to 26 s | Recording: a teammate's name added to a card | "Assign it and they get a notification." |
| 26 to 30 s | Creator, then the sign-up page | "Free for small teams. Link in bio." |
Why it is built this way: the first line is a story, so a real team lead fits it best. With an AI creator, change it to "Standups shouldn't take 40 minutes." and keep the rest.
Example 4: website builder for local businesses (20 seconds, Facebook feed)
Example plan. Product type: a site builder that makes a 1 page site from a business name.
| Time | On screen | Said |
|---|---|---|
| 0 to 3 s | Creator in front of a café counter | "Your café needs a website. Here's one in 2 minutes." |
| 3 to 9 s | Recording: type the business name and town, press "Build" | "Type your name and your town." |
| 9 to 15 s | Recording: the generated site scrolls, with menu and hours | "It writes the page, the menu and your opening hours." |
| 15 to 20 s | Recording: the "Publish" button, then the live URL | "Press publish. That's it. Start free." |
Why it is built this way: the creator appears only once, because the product is the visual. The setting (a café) tells the viewer who it is for before any word.
Example 5: API monitoring for developers (25 seconds, YouTube Shorts)
Example plan. Product type: uptime and error alerts for an API.
| Time | On screen | Said |
|---|---|---|
| 0 to 3 s | Creator at a desk with 2 monitors, hoodie | "You should hear about the outage before your users do." |
| 3 to 8 s | Recording: paste an API URL, choose "Every 30 seconds" | "Paste your endpoint. Pick how often to check." |
| 8 to 14 s | Recording: the check fails, an alert appears in a chat app | "When it fails, the alert goes to your team chat." |
| 14 to 20 s | Recording: the incident timeline with response times | "You get the timeline, so you know when it started." |
| 20 to 25 s | Creator, then the docs page | "Free for 5 monitors. Docs in the link." |
Why it is built this way: developers distrust ads, so the creator speaks plainly and the screen does the work. The call to action points to docs, not a sales page.
Example 6: language learning web app (20 seconds, TikTok)
Example plan. Product type: short daily speaking lessons with feedback on pronunciation.
| Time | On screen | Said |
|---|---|---|
| 0 to 3 s | Creator walking, phone held up, outdoors | "5 minutes of Spanish on the way to work." |
| 3 to 9 s | Recording, phone layout: a lesson card, a microphone button | "You say the sentence out loud." |
| 9 to 15 s | Recording: the feedback highlights one word in orange | "It shows which word to fix, and how." |
| 15 to 20 s | Creator, then the app's start page | "First week free. Start today's lesson." |
Why it is built this way: the setting shows when the viewer would use it. The phone layout recording fills the vertical frame, so nothing is letterboxed.
Example 7: CRM for real estate agents (30 seconds, Facebook and Instagram)
Example plan. Product type: a contact and follow-up tool for agents.
| Time | On screen | Said |
|---|---|---|
| 0 to 3 s | Creator in a car, parked, phone on the dashboard mount | "Open houses give you 20 names. Most never hear from you again." |
| 3 to 8 s | Creator | "Not because you don't care. Because it's on paper." |
| 8 to 15 s | Recording: scan a sign-in sheet, contacts appear | "Scan the sign-in sheet. Every name is a contact." |
| 15 to 22 s | Recording: a follow-up plan, "Text day 1, call day 3" | "Pick a follow-up plan. It reminds you each day." |
| 22 to 27 s | Recording: today's list of 4 calls | "Your morning list is ready when you are." |
| 27 to 30 s | Creator, then the sign-up page | "Try it free for 14 days." |
Why it is built this way: the problem takes two shots, because the viewer must feel it before the fix matters. The offer in the last line is a placeholder; use your real offer or none.
What these examples have in common
| Choice | Why |
|---|---|
| The hook names a situation, not the product | People stop for their own problem, not a brand name |
| The proof is 1 to 3 real actions in the product | A viewer can check a screen; they cannot check a claim |
| The creator presents rather than testifies | It keeps paid and AI creators honest, see what is AI UGC |
| One call to action | Two links split the few people who act |
| Length fits the proof | 15 seconds for one action, 30 seconds for a 3 step flow |
Doing this with distrorig
distrorig makes marketing videos for software: an AI agent uses your product and records it, an AI creator introduces it on camera, and an AI voice narrates. Paste one of these plans into the chat with your product's URL, and the assistant adapts it to your product. The agent records the steps in the "Recording" rows in your real product, and the creator shots are generated. See AI UGC ads for software.