Best Problem Section Design

Hand-picked 11 problem sections from SaaS landing pages, scored across conversion best practices. See how the best agitate pain and drive action.

[WHY THIS GALLERY]

BEYOND PRETTY SCREENSHOTS

SCR
[01]

Scored, Not Curated by Taste

Every problem section is scored across 5 conversion best practices. Copy the best practice stack, not the layout. See what converts and why.

DB
[02]

11+ Real SaaS Pages

Hand-picked from 290+ companies and analyzed by our AI conversion agent. Real problem sections on live landing pages. Every entry earns its spot.

VS
[03]

Benchmark Your Own Problem Section

Found a problem section you admire? Run yours through the same scoring engine. See where you stand on the same best practices, and what to fix first.

What 11 Problem Sections Taught Us About Conversion

What Makes a Good Problem Section?

We scored 11 problem sections from SaaS companies across conversion best practices. The table below shows how widely each element is adopted. The lower the number, the bigger your edge by adding it.

Conversion best practices found in 11 SaaS problem sections, with adoption rate and opportunity level
ElementWhat it meansUse itType
Before/after setupOld way vs. new way, side-by-side. Creates visual contrast between the painful status quo and the product's world36%Opportunity
Quantified pain"$X wasted monthly," "Y hours lost per week," "Z% of leads never contacted." Specific numbers that make the pain concrete45%Opportunity
Emotional resonanceThe copy "feels true" to the visitor. Uses words like "frustrated," "stuck," "overwhelmed" that mirror real internal dialogue55%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 this73%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 frustration82%Table stakes

Persona-specific pain is the most common best practice (82% use it), but the biggest gap is quantified pain. Only 45% of problem sections put a number on the cost. The best-in-class section does. Saying “you waste time on manual data entry” is weaker than “your team loses 12 hours per week on manual data entry.”

The surprise: before/after setup, the format most people associate with problem sections, doesn’t appear in the best-in-class at all. Equals scores 100 without it. The data suggests that stacking four other best practices matters more than the before/after visual.

How We Score Each Problem Section

Our AI conversion agent evaluates every problem section against a weighted checklist that spans three dimensions. Each best practice gets a pass or fail based on the actual page content and screenshot.

  • Copywriting, persona-specific pain, quantified pain, cost of inaction
  • Psychology, emotional resonance, before/after setup
  • Specificity, real numbers, named roles, concrete scenarios

Not every best practice carries the same weight. Quantified pain and cost of inaction pull the score up more because in our dataset, problem sections with those two create more urgency than sections that rely on vague emotional appeals alone.

Sections flagged best-in-class are hand-picked by our team from the highest-scoring sections. A high score gets you on the list. Best-in-class means the copy and psychology work together to make the visitor feel the pain and want the fix.

What the Best Problem Sections Have in Common

1 problem section in our library is flagged best-in-class: Equals, with a perfect 100. It stacks 4 out of 5 conversion best practices.

What makes it work: the section doesn’t describe the problem in the abstract. It names the persona, puts a number on the pain, shows what happens if you ignore it, and makes the reader feel it.

  1. Names the persona and their specific frustration. Not “teams struggle with data.” More like “finance teams stuck reconciling spreadsheets at month-end.” The visitor immediately knows this section is about them.
  2. Puts a dollar amount or time cost on the problem. “12 hours per week” or “$4,200 per month in lost deals.” The pain has a price tag. 45% of problem sections skip this entirely.
  3. Shows the cost of doing nothing. What happens next month, next quarter, if you keep doing it the old way? 73% of all problem sections use this, but only the best combine it with quantified pain.
  4. Triggers emotional recognition. The copy uses language the visitor has said to themselves: “frustrated,” “stuck,” “drowning in.” 55% of all problem sections do this, but the best do it alongside the numbers.

Why Low-Scoring Problem Sections Fail

The lowest-scoring problem sections in our library aren’t wrong about the problem. They just don’t go deep enough.

A problem section scoring 33/100 typically has 2 conversion best practices: persona-specific pain and emotional resonance. The section acknowledges who the visitor is and that they’re frustrated. But it stops there.

The most common gap: no quantified pain. 55% of all problem sections don't put a number on the cost. “Manual data entry is tedious” vs. “Your team wastes 12 hours per week on manual data entry.” The first is a complaint. The second is a business case.

Second: no cost of inaction. 27% of problem sections skip this entirely. The visitor reads about the pain, nods along, and thinks “yeah, but I've lived with this for months.” Without showing what the problem costs them over time, there's no urgency to act now.

The fix is straightforward. Add one stat that quantifies the pain. Add one sentence about what happens if they don’t fix it. Two additions that separate a 33 from a 67 in our scoring.

Want to know which best practices your problem section is missing? Run a free audit →

See what’s wrong with your problem section

Paste your URL. Get a scored analysis of your problem section with specific fixes. Free, no signup.

[FAQ]

PROBLEM SECTION: FREQUENTLY ASKED QUESTIONS

Everything you need to know about problem section design, based on our analysis of real SaaS 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 11 problem sections, the highest-scoring one stays under 120 words.

What’s the difference between a problem section and pain points?

[02]

A problem section is a specific block on your landing page that surfaces the visitor’s frustration before presenting your solution. Pain points are the individual frustrations themselves (slow processes, lost revenue, wasted time). The problem section organizes pain points into a story. 82% of problem sections in our library name the persona alongside the pain to make it personal.

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).

What’s the biggest mistake in problem section design?

[04]

Describing the problem without quantifying it. In our analysis of 11 problem sections, 55% skip the numbers entirely. "Manual data entry is tedious" reads like a complaint. "Your team loses 12 hours per week on manual data entry" reads like a business case. The best problem section scores 100 by stacking quantified pain with cost of inaction.

Should I use before/after or pain-first copy in my problem section?

[05]

Pain-first works better in our data. The only best-in-class problem section (score: 100) uses persona-specific pain, quantified pain, emotional resonance, and cost of inaction, with no before/after format. Before/after appears in 36% of problem sections but 0% of best-in-class. Use before/after in your solution section instead, where the contrast lands harder.

How do I test if my problem section is good?

[06]

Run your page through our landing page analyzer. You’ll get a scored breakdown of your problem section across 5 conversion best practices (persona-specific pain, quantified pain, emotional resonance, cost of inaction, before/after setup) with specific fixes prioritized by impact.