> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getjurni.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Build a problem-solution landing page

> Move high-intent visitors from a specific problem to product relevance with focused education, proof, and a clear path to purchase.

# Build a problem-solution landing page

Use this playbook when the visitor arrives with a **specific problem, frustration, or job-to-be-done** and needs to understand why your product is a relevant solution.

This is often a stronger choice than an advertorial when the problem is already understood and the visitor does not need a long editorial argument.

## When to use it

Good fits include:

* Google or paid-social traffic around one clear problem
* a product with several use cases, where this campaign focuses on one
* audience-specific pain points
* a product that needs brief mechanism education but not a full category lesson
* campaigns where relevance matters more than storytelling

## Step 1: define the problem narrowly

Avoid broad problems such as “I want to feel better.” Use the real campaign context.

```text theme={null}
AUDIENCE
[audience]

PROBLEM / JOB
[specific problem]

CURRENT APPROACH
[what they do now, if relevant]

MAIN FRICTION
[why that approach disappoints / what remains unresolved]

PRODUCT REASON
[approved reason your product is relevant]

PROOF
[approved evidence]

PRIMARY ACTION
[action]
```

The page should be able to stay on this problem without drifting into every possible benefit of the product.

## Step 2: use a simple conversion story

A useful structure is:

1. **Problem-matched hero** — show immediate relevance.
2. **Recognition** — describe the situation accurately.
3. **What matters in a solution** — teach the criteria without overcomplicating.
4. **Product fit** — show how the approved product characteristics address those criteria.
5. **Proof** — support the key claims.
6. **Purchase decision** — make the product and next step clear.
7. **FAQ** — resolve remaining objections.

## Copy-ready Jurni prompt

```text theme={null}
Build a problem-solution landing page for [audience] arriving from [traffic source].

PROBLEM
[specific problem]

CAMPAIGN PROMISE
[approved promise]

PRODUCT RELEVANCE
[approved product reason]

SOURCES
Use the attached product, campaign creative, approved claims, proof, and AI Knowledge.

FLOW
1. Hero that immediately names the problem / desired outcome in the campaign's language.
2. Short recognition section showing the relevant friction.
3. Explain the 2–3 qualities that matter in a solution.
4. Introduce [product] and connect its approved features to those qualities.
5. Add approved proof near the claims it supports.
6. Product / purchase section.
7. FAQ for [objections].

KEEP FOCUSED
Do not expand into every product benefit. Prioritize information relevant to this problem and audience.

DO NOT
Invent outcomes, studies, comparisons, testimonials, pricing, discounts, or guarantees.
```

## Step 3: distinguish empathy from exaggeration

Recognition copy should make the visitor feel understood, not frightened or manipulated.

Prefer specific everyday friction over dramatic statements that are unsupported.

**Better:** “You remember your routine in the morning, then forget it once the workday starts.”

**Weaker:** “Your entire day is being ruined by…”

Use the audience's real language when available from research or customer conversations.

## Step 4: teach decision criteria before product claims

A powerful problem-solution pattern is:

> “If you are trying to solve X, look for A, B, and C.”

Then show how your product fits those approved criteria.

This makes the product explanation feel useful rather than self-congratulatory.

Example:

```text theme={null}
WHAT MATTERS
- [criterion]
- [criterion]
- [criterion]

OUR PRODUCT
Explain exactly how the approved product information maps to those criteria.
```

## Step 5: keep proof specific to the problem

A five-star review saying “love it!” adds less to a problem-specific page than an approved customer quote directly related to the campaign's use case.

Use proof that answers:

* does the product fit this use case?
* is the claim credible?
* is the product easy to use in this context?
* can I trust the purchase?

## Step 6: know when the product should appear

For highly aware traffic, introduce the product early. For less aware traffic, one short problem/criteria section may create useful context first.

Do not hide the product until the bottom just because “storytelling converts.” That is a hypothesis, not a rule.

## Step 7: review for benefit drift

```text theme={null}
Review this problem-solution page.
Do not edit yet.

Campaign problem: [problem]
Audience: [audience]

For each section:
- state how it helps resolve this specific customer's decision
- flag benefits that are true but irrelevant to this campaign
- flag generic copy that could be removed without changing the argument
- flag unsupported escalation of the problem

Recommend the shortest page flow that preserves the necessary education, proof, and purchase decision.
```

## What good looks like

The visitor should feel that the page is specifically about the problem they clicked to solve. The product should enter as a logical answer, with enough proof to earn the next action.

The page should not read like a full catalog of everything the product can do.

## Common mistakes

**Problem too broad.** The page loses campaign specificity.

**Over-dramatizing pain.** This can damage trust and create unsupported claims.

**Introducing product without criteria.** The page jumps from “you have a problem” to “buy ours” without explaining fit.

**Using unrelated proof.** Keep proof connected to the decision.

**Too much education for high-intent traffic.** Match page depth to awareness.

## What to test next

* problem-first versus product-first hero
* criteria section before product versus after
* one core proof point above fold versus later
* short direct path versus a longer educational path

## Next playbooks

* [Advertorial](/academy/playbooks/advertorial)
* [Comparison page](/academy/playbooks/comparison-page)
* [Ad → landing page](/academy/playbooks/ad-to-landing-page)
* [CRO review](/academy/playbooks/cro-review)


## Related topics

- [Build an advertorial landing page](/academy/playbooks/advertorial.md)
- [Build a founder-story landing page](/academy/playbooks/founder-story.md)
- [Build a listicle landing page](/academy/playbooks/listicle.md)
- [Build a creator or influencer landing page](/academy/playbooks/creator-page.md)
- [Recreate a landing page from a reference](/academy/playbooks/recreate-reference-page.md)