Problem Sections That Set Up a Before and After (36)

What a before/after setup actually is

A before/after setup is a problem section that describes the old, messy way of working in enough detail that the product's fix reads as a clean contrast. It spends its first half on the before, the scattered tools, the manual copying, the hours lost, so the after the product promises has something concrete to beat. The section is not there to depress the reader. It is there to name the status quo so precisely that the fix feels inevitable.

The best problem sections build the contrast in one of a few ways:

• A named status-quo line. A single sentence that pins the old way, like Altura's "spreadsheets cannot keep up in complicated tender processes," so the reader sees their own setup on the screen.
• A bridge line into the fix. A closing sentence that turns the page toward the solution, the way Saleshandy ends on "There is a much easier way to do this."
• A reframe. A line that recasts the pain as fixable, like SocialEcho's "It's not a skills problem. It's a tools problem."
• A one-to-one after. A crisp promise that answers the exact mess above it, like Payaca's "One system. One database. One source of truth."

Why it works

A product claim in a vacuum is just an adjective. "Simple," "all in one," and "fast" mean nothing until the reader has felt the opposite. The before/after setup supplies that opposite first, so by the time the product speaks, the reader is already nodding along to the pain and primed for the relief.

It also earns trust in the diagnosis. When a section describes the current mess in the reader's own words, the reader concludes that the people behind the product actually understand the job. A fix offered by someone who clearly gets the problem is far easier to believe than a fix that arrives cold, ahead of any evidence the problem was understood.

How the best problem sections do it

Across the scored examples below, the strongest before/after setups make the before specific and the after tight. Lokalise splits its section into two current setups and defuses the pain with a subhead ("Both are fixable"), so the contrast motivates instead of deflating. Omnibound sets its after directly against the alternative, framing generic AI output as slop next to content that actually fits. The move is the same shape every time: stage a concrete before, then hand over an after that answers it point for point.

The after does not have to live in the same block. Many pages let the problem section carry the before and pass the after to the feature section's before/after contrast, or you can browse the full problem section gallery to see the range of setups.

100/100

Common mistakes

10/100

The most common failure is a before that is too vague to recognize. "Managing your work is hard" describes no one's Tuesday, so no one leans in. The fix is specificity: name the real tools, the real hours, the real workaround, the way the best examples do. The second failure is a before with no bridge, a section that stacks up pain and then stops, leaving the reader stranded in the mess with no visible way out. Every strong before/after setup closes on a line that turns the page toward the fix.