Free app marketing library

Creator prompts

UGC Opening-Line Prompt Cards

Use 24 creator-friendly opening prompts with delivery direction, an alternate take, and an honest proof guardrail.

Showing 24 of 24

Problem prompt · 1

The recurring annoyance

Delivery: Answer like you are sending a voice note to a friend; name the exact moment it happened. Alternate take: Start with: 'The part that kept getting on my nerves was...'. Proof guardrail: Keep it to your real experience and avoid saying everyone has the same problem.

Tell me about the small [task] that kept interrupting your day before you tried this app.
ProblemCreator direction

Problem prompt · 2

The messy workaround

Delivery: Hold the old notes, tabs, or files in frame before looking back to camera. Alternate take: Start with: 'This was my system before I found a cleaner way...'. Proof guardrail: Do not stage a fake workaround or exaggerate how unusable it was.

Show the workaround you used before, then explain what made it annoying.
ProblemCreator direction

Problem prompt · 3

The stuck moment

Delivery: Pause after naming the stuck point so the editor has room for a visual cutaway. Alternate take: Start with: 'I was fine until I got to this part...'. Proof guardrail: Do not imply the app removes decisions or work that still belong to the user.

Describe the exact point where you would get stuck during [workflow].
ProblemCreator direction

Problem prompt · 4

The overlooked cost

Delivery: Use one concrete consequence, such as another message or a missed handoff, without dramatizing it. Alternate take: Start with: 'It was not just [task]—it also meant...'. Proof guardrail: Avoid financial, health, or performance consequences you cannot document.

Explain what [problem] made harder besides the obvious task itself.
ProblemCreator direction

Surprise prompt · 5

The feature you almost missed

Delivery: Glance toward the phone, then point to where the feature appears on screen. Alternate take: Start with: 'I downloaded this for [reason], but this is what I keep using...'. Proof guardrail: Frame frequency as your own behavior, not a popularity claim.

Name the small app feature you did not expect to use this often.
SurpriseCreator direction

Surprise prompt · 6

The simpler answer

Delivery: Sound pleasantly surprised, then leave a beat before the demo begins. Alternate take: Start with: 'I thought this would be a whole process, but...'. Proof guardrail: Do not hide required setup or claim a step count you cannot show.

Share the part of [workflow] that turned out to need fewer steps than you expected.
SurpriseCreator direction

Surprise prompt · 7

The unexpected use case

Delivery: Tell the short before-and-after story in one breath, then show the new use. Alternate take: Start with: 'I did not download this for [use], but now...'. Proof guardrail: Make sure the use is supported and does not violate the product's intended boundaries.

Describe a useful way you ended up using the app that was not your original plan.
SurpriseCreator direction

Surprise prompt · 8

The detail that changed the feel

Delivery: Keep the reaction low-key and specific instead of sounding amazed on command. Alternate take: Start with: 'This is such a small thing, but I noticed it right away...'. Proof guardrail: Describe personal preference rather than claiming objective usability.

Point out one tiny design detail that made the workflow feel clearer to you.
SurpriseCreator direction

Objection prompt · 9

Another-app hesitation

Delivery: Say the objection plainly before softening your tone for the specific use case. Alternate take: Start with: 'Honestly, I did not want another app for this...'. Proof guardrail: Do not pretend reluctance or claim the app replaces tools you still use.

Explain why you did not want another app, then name the one job that made you try it.
ObjectionCreator direction

Objection prompt · 10

Setup hesitation

Delivery: Count the real steps with your fingers while the editor shows matching footage. Alternate take: Start with: 'I was worried setup would take forever, so I only did...'. Proof guardrail: Do not state a setup time or ease claim unless it matches the captured process.

Talk through the smallest setup you completed before the app became useful.
ObjectionCreator direction

Objection prompt · 11

Not-techy hesitation

Delivery: Use your natural vocabulary; do not perform confusion for the camera. Alternate take: Start with: 'I am not someone who wants to learn a complicated system...'. Proof guardrail: Keep it personal and do not label whole groups of people as bad with technology.

Describe the first screen or action that made the app feel approachable to you.
ObjectionCreator direction

Objection prompt · 12

Worth-it hesitation

Delivery: Talk about the job you use, not an assumed return on money or time. Alternate take: Start with: 'The question for me was whether I would actually use it for...'. Proof guardrail: Do not make savings, ROI, or performance claims without the viewer's own numbers.

Name the repeated job you considered when deciding whether the app fit your routine.
ObjectionCreator direction

Demo prompt · 13

Show the first useful step

Delivery: Keep your spoken line short and physically point toward the upcoming demo. Alternate take: Start with: 'If you are opening this for the first time, start here...'. Proof guardrail: Make sure it is a supported starting point for the current app version.

Introduce the one action a new user should try first, then hand off to the screen recording.
DemoCreator direction

Demo prompt · 14

Show the saved setup

Delivery: Hold up one finger for the original setup, then gesture forward for the next use. Alternate take: Start with: 'I set this up once, and now I use it whenever...'. Proof guardrail: Do not imply reuse is automatic or needs no review when details still change.

Explain what you made once and now reuse for a recurring task.
DemoCreator direction

Demo prompt · 15

Show the handoff

Delivery: Name the receiver and the missing context, then cut directly to the share view. Alternate take: Start with: 'Before I send this to [person], I make sure they can see...'. Proof guardrail: Do not show private data or imply the recipient has access they may not have.

Tell the viewer what another person needs to know when you hand this work over.
DemoCreator direction

Demo prompt · 16

Show the recovery path

Delivery: Let the mistake sound normal, then show the real recovery without a jump cut. Alternate take: Start with: 'If you accidentally [action], here is where you fix it...'. Proof guardrail: Only promise recovery for actions the app can genuinely reverse.

Describe a small mistake you can undo or correct inside the app.
DemoCreator direction

Confession prompt · 17

The habit you dropped

Delivery: Smile at the old behavior without shaming yourself or the viewer. Alternate take: Start with: 'I used to [old behavior] every single time...'. Proof guardrail: Keep the story true and avoid implying the change guarantees a result.

Admit one unhelpful way you used to handle [task] and what you do differently now.
ConfessionCreator direction

Confession prompt · 18

The feature-first mistake

Delivery: Sound matter-of-fact, then point to the real moment it finally made sense. Alternate take: Start with: 'I skipped this feature for way too long because...'. Proof guardrail: Do not invent ignorance to make the feature sound more impressive.

Share the app feature you ignored because you misunderstood when it was useful.
ConfessionCreator direction

Confession prompt · 19

The overcomplicated system

Delivery: Use a quick visual prop or gesture to show the extra step, then simplify. Alternate take: Start with: 'I was making this so much harder than it needed to be...'. Proof guardrail: Present the simplification as your preference, not the only correct method.

Describe the unnecessary step you added to your own workflow.
ConfessionCreator direction

Confession prompt · 20

The honest limitation

Delivery: Deliver the limitation confidently, then transition into the narrow demo. Alternate take: Start with: 'This will not [unsupported job], but it does help me...'. Proof guardrail: Verify the limitation and avoid using honesty as a setup for an exaggerated claim.

Name one thing the app does not do and the specific job you still use it for.
ConfessionCreator direction

Outcome prompt · 21

The visible finish

Delivery: Name the final state, then leave room for the editor to show it clearly. Alternate take: Start with: 'I know this task is ready when I can see...'. Proof guardrail: Do not call the wider job complete if outside approval or action still remains.

Describe what 'done' looks like inside the app for one specific task.
OutcomeCreator direction

Outcome prompt · 22

The prepared feeling

Delivery: Use calm delivery and name the exact information shown in the demo. Alternate take: Start with: 'Before [event], I like knowing...'. Proof guardrail: Keep the claim about preparation, not guaranteed performance or confidence.

Explain what you can see before [recurring event] that helps you feel prepared.
OutcomeCreator direction

Outcome prompt · 23

The easier handoff

Delivery: Quote the old question naturally, then show where the answer lives. Alternate take: Start with: 'The question I used to get every time was...'. Proof guardrail: Do not claim questions disappear entirely or invent team feedback.

Describe the question you hear less often because the handoff now includes the answer.
OutcomeCreator direction

Outcome prompt · 24

The reusable result

Delivery: Hold the reusable piece in frame, then mention the details that still need changing. Alternate take: Start with: 'The part I do not have to rebuild next time is...'. Proof guardrail: Do not imply the whole result can be reused unchanged.

Explain which part of today's work will still be useful for the next version.
OutcomeCreator direction

More useful ideas

Get the next app-marketing tool.

Join the ClipStitchr mailing list for practical tools, creative ideas, and product updates made for app founders.

The tools are free. ClipStitchr is a paid product, and joining this list does not create an account. Unsubscribe anytime. Read our Privacy Policy.

How to use it

Capture natural openings without handing over a rigid script.

Give the creator a prompt instead of a sentence to memorize. A natural answer usually sounds more believable and gives the editor more usable choices.

Record the main prompt and its alternate as separate clips. Keep a clean pause before and after each take, then capture the demo or supporting visual as its own file.

These cards help with source capture only. ClipStitchr remains the paid place to organize those takes and assemble finished app ads.

Questions

What to know before you use it.

Are these complete UGC scripts?

No. Each card gives you one opening prompt, a delivery note, and an alternate take. The creator should answer in their own voice and only describe real experience.

Can a creator record several cards in one session?

Yes. Capture each opening as a separate clean take, leave a short pause at both ends, and keep the product-demo footage separate so the pieces are easier to reuse.

What should I do with the proof guardrail?

Treat it as a quick honesty check. Remove or soften any line the creator cannot support from personal experience or footage you can actually show.

Ready to make the ads?

Keep planning free. Use ClipStitchr when it is time to produce.

ClipStitchr is paid software for organizing reusable footage and turning it into finished short-form ads.

See paid plans