Problem-Solution Hooks That Stop the Scroll

The problem-solution hook is the most honest structure in advertising: name the pain the viewer already carries, then earn the right to present the fix. But the generic version is worthless. 'Struggling with productivity?' describes almost everyone and therefore speaks to no one. 'I was copying the same client notes into three tools every Monday' names a behavior, a context, and a consequence — and the viewer's recognition does the stopping, not your words.

This guide covers the five-part structure, how to mine your customers for the real problem, problem-first examples across verticals, and the credibility rules that keep a problem-solution hook from becoming a bait-and-switch. It's the problem-led complement to curiosity hooks — where curiosity sells the gap, problem-solution sells the recognition — and both sit on the video hook mechanics this site is built on.

The structure

Every working problem-solution hook runs the same five beats. Skip one and the ad leaks attention:

1. Name a visible situation: what the person is doing, seeing, or avoiding. A behavior, not a category.
2. Add the cost: time, money, uncertainty, embarrassment, or missed opportunity. The cost converts recognition into discomfort.
3. Create a gap: hint that a simpler path exists without explaining it immediately.
4. Show the solution in action before making a broad claim.
5. Close with the next step that lets the viewer test the answer.

Recognition is the cheapest form of attention — and the problem-solution hook is the only hook that can buy it on the very first frame.

Why specificity beats category pain

'Project management is chaotic' is a category complaint — it's true, and it costs nothing to hear. 'I find out a deadline moved when it's already late' is a lived problem with a visible moment and a visible consequence. The second one works because the viewer doesn't have to translate your words into their life; you've already done it. This is the same specificity that powers the best ad hooks, and it's why the most clickable problem hooks read like confessions rather than marketing.

• Write the problem as a verb and a consequence, never a label. 'Reconciling receipts on Sundays' beats 'expense management.'
• Use the customer's own phrasing — the words from reviews, support tickets, and sales calls, not your positioning doc.
• Name the frequency or the moment: 'every Monday,' 'the night before a deadline,' 'during client calls.'
• If a competitor could run the same hook, it isn't specific enough.

Examples by pain type

The same structure, mapped to the five pains that drive most purchases. Use these as starting points, then swap in your customer's real situation:

For the line-by-line execution of these — including the exact scripts and CTAs that follow each proof frame — the UGC script library and the ad script templates are the closest thing to a fill-in-the-blank version of this table.

Find the real problem

You can't invent a believable problem. Mine the places customers already describe it: support tickets, sales call notes, app reviews, cancellation surveys, and search queries. Look for verbs and consequences, not category labels — 'the import keeps dropping rows' beats 'data sync issues.' Then write the hook in the customer's words and remove anything your product cannot actually solve.

1. Pull 30 real complaints across support, reviews, and sales notes.
2. Group them by the moment they happen in the customer's week.
3. Pick the top complaint that your product genuinely, visibly solves.
4. Write the hook in the customer's own phrasing, trimmed to a single sentence.
5. Cut every word that promises more than the first session delivers.

Problem-first hooks by vertical

Mobile apps

Apps win with the interaction visible: 'I gave this app my worst [problem] and watched what happened.' The proof is the on-screen action, and the mobile app hook guide has the full category breakdown with 20 ready lines.

SaaS and B2B

B2B hooks live and die on the role-specific moment: 'The status update took longer than the work. Again.' The SaaS hook guide covers the workflow-first structure and the objection angle that converts cold traffic.

Ecommerce and physical products

Physical products win on the in-hand reveal: 'I was skeptical until I held it.' The proof is sensory — texture, fit, the box, the packaging — and the UGC ad examples show how the demo cashes those promises.

Avoid the bait-and-switch

A problem-solution hook that overstates the pain or the cure doesn't just lose that viewer — it trains the platform that your ads under-deliver, which raises your costs on every future impression. The credibility rules are non-negotiable:

• Do not exaggerate the problem to create urgency.
• Do not imply a feature removes work it only reduces.
• Show the solution within the first few seconds after the hook.
• Use a realistic time frame and name limitations when they matter.
• Make the landing page repeat the same problem and outcome.

Testing problem hooks

Problem-solution is a hypothesis about recognition — and the only way to confirm recognition is to put it in front of the audience. Hold the demo and destination constant, and ship the problem hook against the alternatives:

1. Test the problem against the promise. A problem hook vs. a curiosity hook on the same demo tells you which sells your audience better.
2. Test the moment, not the wording. If 'every Monday' wins, test other recurring moments rather than rewording the same one.
3. Judge qualified clicks, not just holds. A hook that holds but doesn't click has the right recognition and the wrong payoff.
4. Match the landing page. The page must restate the same problem and outcome or the click dies on arrival.

This is the standard creative testing loop, and the benchmark tables in UGC benchmarks give you the numbers that make 'winning' measurable. For the full ad structure around the hook — reaction open, demo, CTA — the UGC ads playbook connects every piece.