The problem-solution script structure for ads is the most dependable way to turn a scroll into a sale in a 15- to 30-second video. You name a frustration the viewer already has, make it feel real for a few seconds, then show your product resolving it with proof and a clear next step. It works because it mirrors how people actually decide to buy: they don't want a product, they want a problem gone.
What the Problem-Solution Script Structure Actually Is
At its core, a problem-solution script does three jobs in order: it surfaces a pain the viewer recognizes, it shows a product fixing that pain, and it tells the viewer exactly what to do next. That's different from a storytelling ad (which opens with a character or scene) or a pure demo ad (which opens with the product in action without naming the pain first). The problem-solution format front-loads relevance — the viewer sees themselves in the first few seconds, which is what earns the rest of the watch time.
This structure also tends to perform well on mute, since the problem can be shown visually (a cluttered drawer, a sore neck, a slow checkout) before any voiceover kicks in. If you want the deeper design logic behind that, see how to design ads for muted autoplay feeds.
The Five-Part Problem-Solution Framework
Every strong problem-solution script, regardless of product, moves through the same five beats. Here's what each one needs to do and a sample line for a few invented products so you can see the pattern repeat.
- Hook / Problem (0–3 seconds): Open on the pain, not the brand. Example for a posture corrector: "Your shoulders are rounding forward and you don't even notice anymore." Example for a phone stand: "Your neck hurts after every video call and you blame the chair."
- Agitation (3–6 seconds): Make the cost of the problem concrete in one or two lines — don't stretch this beat, it's a bridge, not the destination. "It's not just posture. It's the headaches by 3pm and the photos you keep deleting."
- Solution reveal (6–14 seconds): Introduce the product as the direct answer to the exact pain you named. Show it in use, not just sitting on a table. "This brace pulls your shoulders back for you, so you don't have to think about it."
- Proof (14–22 seconds): Give the viewer a reason to believe it works — a visual before/after, a demonstration, or a specific use case. Avoid invented statistics; show the mechanism instead. "Put it on, adjust the strap once, and it holds the position all day."
- Offer and CTA (22–30 seconds): State the single action you want, paired with any offer or urgency that's genuinely true. "Get yours at 20% off this week — tap the link below."
If you need a general-purpose scaffold for turning this into a full script with timing, pair this framework with how to write a script for a 30-second product ad.
A Problem-Solution Script Template You Can Copy
Here's a timing template you can reuse for most e-commerce products. Swap in your own product details, but keep the beats in this order — reordering them (for example, leading with proof) usually weakens the hook.
| Time | Beat | On-screen text example | Voiceover line example |
|---|---|---|---|
| 0–3s | Hook / Problem | "Still untangling cables every morning?" | "This is the last time you'll untangle cables." |
| 3–6s | Agitation | "5 minutes lost. Every. Single. Day." | "It's not a big deal — until it's every morning for a year." |
| 6–14s | Solution reveal | "Meet [Product Name]" | "One slot for every cable, color-coded, done." |
| 14–22s | Proof | "Before / After" | "Watch how fast this goes from mess to sorted." |
| 22–30s | Offer + CTA | "20% off today" | "Tap below to grab yours before the offer ends." |
For more ready-to-adapt structures across product categories, see the video ad script template for ecommerce products.
Problem-Solution vs Other Script Structures
Problem-solution isn't the only way to write an ad script, and it isn't always the best fit. Here's how it compares to three other common structures.
| Structure | Best for | Main strength | Main risk |
|---|---|---|---|
| Problem-solution | Products that fix a clear, named pain (gadgets, skincare, organization tools) | Fast relevance, works well on mute | Falls flat if the problem feels manufactured or too vague |
| Before/after | Visual transformations (cleaning, fitness, beauty) | Proof is built into the format itself | Needs a genuinely strong visual difference to land |
| Testimonial-led | Products that rely on trust (supplements, services) | Borrowed credibility from a relatable voice | Can feel slow if the testimonial rambles before the point |
| Storytelling | Lifestyle or gift products, brand-building campaigns | Emotional pull, memorable | Harder to fit a clear CTA into a short runtime |
In practice, most winning e-commerce ads blend problem-solution with a short before/after inside the proof beat — the structures aren't mutually exclusive.
Common Mistakes That Weaken Problem-Solution Ads
The framework is simple, but most scripts that use it still underperform because of a few repeatable errors.
- The problem is too vague. "Life is busy" isn't a problem a viewer can picture. "Your charger cable is always tangled with three others" is.
- The agitation beat runs too long. If the first 10 seconds are all complaint and no product, you lose viewers before they see the point.
- The proof is a claim, not a demonstration. Saying "it works great" is weaker than showing the product actually doing the thing, even in three seconds.
- The CTA arrives too late or is too soft. "Check it out sometime" gives the viewer permission to do nothing. Be specific about the action and the moment to take it.
- The script ignores viewers who have the sound off. If the problem and solution only exist in the voiceover, half your audience never gets the message — design the on-screen text and visuals to carry the story alone, as covered in designing ads for muted autoplay feeds.
Example Script: Before and After Rewrite
Here's a weak problem-solution script for an invented product, a kitchen knife sharpener, followed by a rewrite using the five-beat framework.
Before (weak version)
"Cooking is hard when your tools aren't good. Introducing the SharpEdge knife sharpener. It's great for your kitchen. Many people love it. Buy now and improve your cooking experience."
This version never names a specific, felt problem, the solution shows up with no proof, and the CTA is generic. There's nothing here that stops a scroll or earns a click.
After (problem-solution version)
"(0-3s) Your knife is dragging through a tomato instead of slicing it. (3-6s) That's not the tomato's fault — it's a dull blade, and it's making every meal slower and messier. (6-14s) This is SharpEdge. Three pulls, both sides, and the edge comes back. (14-22s) Watch this: same knife, same tomato, clean slice. (22-30s) Get SharpEdge for 15% off this week — link below."
Same product, same runtime — but now the viewer sees themselves in the problem, watches the fix happen, and knows exactly what to do next.
Writing the Call to Action for a Problem-Solution Script
The offer-and-CTA beat is where most problem-solution scripts lose their nerve. After naming a real problem and showing a real fix, the ad should ask for a specific, low-friction action — not a vague invitation. If you're unsure how direct to be or how to phrase urgency without sounding generic, how to write a call to action for video ads that convert covers phrasing you can adapt directly into this last beat.
How FrameNotion Fits Into This Framework
If you'd rather not write every beat from scratch for each product, FrameNotion can take a product link and have FrameNotion AI draft a full ad built on the same hook, problem, benefit, proof, offer and call-to-action structure described above — then render it as a 30-second vertical MP4 with voiceover, music and captions in about 10 to 20 minutes. You can see finished examples of this structure in action on the examples page, and compare plans on the pricing page if you're producing scripts like this for more than one product a month.
Whether you write the script by hand or generate a first draft and edit it, the same rule holds: name a real problem, show the fix fast, prove it works, and ask clearly for the action you want.
Key Takeaways
A problem-solution script works because it gives the viewer a reason to keep watching in the first three seconds and a reason to act in the last three. Keep the problem specific, keep the agitation short, show the fix rather than just claiming it, and make the CTA concrete.
Frequently asked questions
How long should the problem section be in a video ad script?+
Keep the problem and agitation combined to roughly the first 6 seconds of a 30-second ad. Long enough to feel specific, short enough that the viewer sees the product before losing interest.
Does the problem-solution structure work for every product?+
It works best when the product solves a clear, nameable frustration. For products sold mainly on emotion, identity, or gifting, a storytelling structure often performs better — you can still borrow the proof and CTA beats from problem-solution.
Should the problem be shown visually or just stated in the voiceover?+
Both, when possible. Many viewers will have sound off, so the opening visual and on-screen text should make the problem clear on their own, with the voiceover reinforcing it.
Can problem-solution scripts work for service or B2B ads?+
Yes. The framework still applies: name the operational pain (slow onboarding, missed leads, manual reporting), show the product or service resolving it, add proof such as a short demo, then state the next step clearly.
How many hook variations should I test for a problem-solution ad?+
Start with two or three different ways of naming the same problem, since the hook is usually the highest-leverage line in the script. Keep the rest of the script identical so you can isolate what the hook change actually affects.