Problem|
Best Problem Section Design
The problem section describes the pain or challenge your product solves. Explore 71 scored examples and see what the best do differently.
Updated October 2026
Showing 1–29 of 71 examples
Problem|
thestory.run Marketing Problem Design
Problem|
Quiver GTM Marketing Problem Design
Problem|
Ferndesk Customer Support Problem Design
Problem|
Widgo AI Problem Design
Problem|
Hyperprobe Developer Tools Problem Design
Problem|
Hyperprobe Developer Tools Problem Design
Problem|
Hello Inbox Marketing Problem Design
Problem|
Ami AI Lead Generation Problem Design
Problem|
Navigara Developer Tools Problem Design
Problem|
Prefactor AI Problem Design
Problem|
NINA Customer Support Problem Design
Problem|
Hardbook Productivity Problem Design
Problem|
Prodpad Product Management Problem Design
Problem|
Process Operations Problem Design
Problem|
Oneflow Legal Tech Problem Design
Problem|
Nautis Productivity Problem Design
Problem|
Lokalise Developer Tools Problem Design
Problem|
ClawTeams Ecommerce Problem Design
Problem|
Deep Creator Economy Problem Design
Problem|
Payaca Construction Problem Design
Problem|
Xano No-Code Problem Design
Problem|
Swytchcode CLI Developer Tools Problem Design
Problem|
Elvin AI Problem Design
Problem|
Edgee Turbo Models Developer Tools Problem Design
Problem|
VC Boom Startup Problem Design
Problem|
Shippit Logistics Problem Design
Problem|
SocialEcho Social Media Problem Design
Problem|
Saleshandy Lead Generation Problem Design
What is a problem section?
A problem section is the block of a website that names the pain your product removes, before you show the fix. With the block that follows it, it is often called a problem and solution section. Its job is to make the visitor think "that is exactly my situation", so the solution feels made for them.
It usually does three things:
- Names who has the pain. "For sales teams tired of manual CRM updates." 82% of the problem sections we scored do this.
- Puts a number on it. "Your team loses 12 hours a week on data entry." Only 45% do.
- Says what waiting costs. What it costs next month if nothing changes. 73% do.
Place it between the hero and the solution or features, in the second or third screen. The best examples above name the person, give the number and say what waiting costs.
What We Learned From Analyzing Problem Sections
What Makes a Good Problem Section?
We checked the problem sections in our library for the elements below. The lower the number, the fewer pages do it, and the bigger your edge when you add it.
Before/after setup
Old way vs. new way, side-by-side. Creates visual contrast between the painful status quo and the product's world
36%
Quantified pain
"$X wasted monthly," "Y hours lost per week," "Z% of leads never contacted." Specific numbers that make the pain concrete
45%
Emotional resonance
The copy "feels true" to the visitor. Uses words like "frustrated," "stuck," "overwhelmed" that mirror real internal dialogue
55%
Cost of inaction
"Every month without this costs you $4,200 in lost deals" or "Your team wastes 12 hours per week." What happens if you don't fix this
73%
Persona-specific pain
"For sales teams tired of manual CRM updates" or "If you're a founder drowning in spreadsheets." The visitor sees their own role and frustration
82%
| Element | What it means | Use it | Type |
|---|---|---|---|
| Before/after setup | Old way vs. new way, side-by-side. Creates visual contrast between the painful status quo and the product's world | 36% | Opportunity |
| Quantified pain | "$X wasted monthly," "Y hours lost per week," "Z% of leads never contacted." Specific numbers that make the pain concrete | 45% | Opportunity |
| Emotional resonance | The copy "feels true" to the visitor. Uses words like "frustrated," "stuck," "overwhelmed" that mirror real internal dialogue | 55% | Common |
| Cost of inaction | "Every month without this costs you $4,200 in lost deals" or "Your team wastes 12 hours per week." What happens if you don't fix this | 73% | Common |
| Persona-specific pain | "For sales teams tired of manual CRM updates" or "If you're a founder drowning in spreadsheets." The visitor sees their own role and frustration | 82% | Table stakes |
One surprise: the before and after setup, the format most people picture for a problem section, is the least used (36%), and the highest-scoring section in our library does without it. Naming the person, the number and the cost of waiting matters more.
How We Score Each Problem Section
We check every problem section against a weighted checklist, from the page itself and its screenshot:
- Copy: who has the pain, a number on it, the cost of waiting
- Emotion: words that mirror what the visitor says to themselves, a before and after
- Specificity: real numbers, named roles, concrete scenarios
A number on the pain and the cost of waiting weigh the most, because the highest-scoring problem sections lean on them. Sections flagged best-in-class are picked by hand from the highest scores.
Interactive quiz
What would your problem section score?
Question 1 of 5
0%
Does your copy name the specific role or persona feeling the pain?
"For sales teams tired of manual CRM updates"
What the Best Problem Sections Have in Common
The best problem sections don't describe the problem in the abstract. They do four things together:
- Name the persona and their exact frustration. Not "teams struggle with data". More like "finance teams stuck reconciling spreadsheets at month-end". The visitor knows at once that the section is about them.
- Put a time or money cost on the problem. "12 hours per week" or "$4,200 per month in lost deals". The pain has a price tag, where only 45% of problem sections give one.
- Show the cost of doing nothing. What happens next month, next quarter, if you keep the old way? 73% of problem sections say it, but the best pair it with a number.
- Use the visitor's own words. "Frustrated", "stuck", "drowning in": language the visitor has said to themselves. 55% of problem sections do this, and the best do it alongside the numbers.
100/100Why Weak Problem Sections Fall Short
The weakest problem sections are not wrong about the problem. They name who has it and say it is frustrating, then stop. 55% of problem sections never put a number on the pain, and 27% never say what waiting costs. "Manual data entry is tedious" is a complaint. "Your team wastes 12 hours a week on manual data entry" is a business case.
The fix: add one number that sizes the pain, and one sentence about what happens if nothing changes.
Want to know which best practices your problem section is missing? Get your 3 free opportunities →
10/100More problem best practices
Curated by
Gabriel Amzallag , Founder, Web Anatomy
5 years CRO + SEO at Qonto (2021–2025). After advising 15+ SaaS on their websites (Payfit, Pigment…), the same patterns kept breaking, so I decided to build the source of truth on what works on the web: the intelligence layer every tool, builder, and team uses to ship sites that perform.
Keep exploring section examples
Real examples from top landing pages, scored and analyzed.
[FAQ]
PROBLEM SECTION: FREQUENTLY ASKED QUESTIONS
Everything you need to know about problem section design, based on our analysis of real landing pages.
How big should a problem section be?
[01]A problem section should be 2-4 short paragraphs, roughly 80-150 words. It lives before your solution or features section. Long enough to make the visitor feel the pain, short enough that they don't leave before seeing the fix. In our library of 71 problem sections, the highest-scoring one stays under 120 words.
Where does the problem section go on the page?
[02]Between the hero and the solution, almost always. The hero hooks the visitor; the problem section earns the right to pitch. Place it in the second or third scroll, right before your features or how-it-works block. Skip it if your hero already frames the pain explicitly. Don't bury it below testimonials. By then the visitor has either bought in or left. On long-form landing pages, repeat a compressed version of the pain before the pricing CTA to reset the stakes before the ask.
Do I need a problem section?
[03]Yes, if your product solves a pain the visitor might not fully recognize yet. SaaS landing pages, campaign pages, and product launch pages benefit most. A problem section primes the visitor to care about your solution. Skip it if your audience already knows the problem (e.g., searching "CRM software" implies they know they need one).
How do I find the pain points my customers actually feel?
[04]Go to the source, not your imagination. Read 20-30 sales call transcripts or support tickets (Gong and Intercom both export these) and write down the exact phrasing people use. Run five 20-minute customer interviews and ask "what did you try before this?" The complaints about the old way are your copy. Scrape review-site snippets (G2, Reddit, Trustpilot) for the verbs people use when they describe the pain. The best problem sections paraphrase real sentences, not invented ones.
Problem section vs hero problem statement: what's different?
[05]Different jobs. A hero problem statement is one line. It signals "this page is for someone like you" in under two seconds. The problem section is a block of 80-150 words that makes the visitor feel the cost. The hero frames the problem. The problem section agitates it. If your hero already quantifies the pain ("Your team loses 12 hours a week on X"), you can skip the full problem section. If the hero is benefit-led ("Close more deals"), you need the block to surface the pain the benefit is solving.
How do I test if my problem section is good?
[06]Check that the pain is specific to one persona and that it carries some emotion. Then look for a number on the pain, the cost of doing nothing, and a before and after setup. Or get your 3 free opportunities, ranked with the evidence behind each.
Show the pain is widely shared
The problem section that proves the pain is widely shared, with aggregate stats and cited numbers, so the reader sees it is not just them.