Explain the cost before introducing the feature

The fictional scheduling tool Juniper opens its landing page with “Intelligent calendar technology for modern teams.” The copy sounds polished but does not explain why a workshop coordinator should care. The team wants to describe a specific frustration: registration details and calendar updates drift apart.

PAS organizes copy around a problem, its consequences, and a solution. Copyhackers’ Joanna Wiebe describes the structure as problem, agitation, and solution. The Juniper copy in this guide is invented and has not been tested with customers.

Begin with a real, recognizable problem

Juniper drafts: “Changed the workshop time, but attendees still have the old calendar invitation?” It names a situation and the person affected. It also narrows the audience to coordinators facing this particular problem.

Before publishing it, the team should confirm that the situation appears in relevant customer accounts. A vivid sentence can still describe something uncommon or unimportant. Research should guide the message rather than provide convenient phrases for an already chosen pitch.

If the audience does not experience the problem, agitation will only make the mismatch louder. Another page might need a different opening or a different offer.

Problem → agitation → solution

Recognize the situation

Problem

Name a difficulty the intended reader actually experiences.

Make the consequence concrete

Agitation

Explain relevant costs or frustration without exaggerating them.

Offer a credible next step

Solution

Show how the offer addresses the stated problem and what to do next.

This is a writing structure, not proof of a customer need or a guarantee of conversion. Keep the consequence and the promise supported.

Make the consequence specific and proportionate

Juniper’s next draft says: “You update the registration page, send a correction, and answer messages from people checking which time is right.” That is the agitation: showing why the problem deserves attention through recognizable consequences.

The team should avoid claims such as “One missed update will destroy your reputation.” That outcome has not been established, and the drama adds little useful information. A reader deciding whether to change tools needs a fair picture of the current cost.

Agitation need not be long. One concrete sequence can do more than several paragraphs of anxious adjectives. The length should reflect what the reader needs to understand, the format, and the seriousness of the situation.

Make the solution answer the stated problem

The proposed solution copy reads: “Keep registration details and attendee calendar updates in one workflow. See how a time change is sent before you publish your next workshop.”

This draft connects the offer to the problem and offers a bounded next step. It deliberately makes no claim that every calendar system updates instantly. Juniper would need to explain supported calendars, notification behavior, and any limits that affect the buying decision.

Part Original draft Review question
Problem Attendees still have the old calendar invitation Does the intended audience recognize this situation?
Agitation Corrections and clarification messages multiply Is this consequence supported and proportionate?
Solution One workflow for registration and updates Does the product actually do this under stated conditions?
Next step See how a time change is sent Can the reader inspect the relevant behavior?

The next step supports the solution; it is not a fourth letter added to PAS. Readers still need an obvious way to act on the message.

Review the whole chain, then test it

A useful review asks whether the opening identifies the intended reader, the consequences follow from the problem, and the solution addresses those consequences. Check every operational claim with the people who know the product.

Then inspect the page with representative readers. Ask what they think the product does and what they expect after clicking. Confusion is actionable evidence even when someone says the writing sounds good. Compliments alone do not establish purchase intent.

If you compare two versions experimentally, define the outcome and eligible audience in advance. More button clicks are not necessarily better if they produce unsuitable signups or disappointment after purchase. Keep the rest of the experience in view.

Know when another structure fits better

PAS suits a message whose audience recognizes a difficulty and needs to understand an available response. It can feel forced when the offer is mainly about exploration, enjoyment, or a need the reader has not yet identified. Some messages should begin with useful information or a positive possibility.

Use AIDA when you want to inspect attention, interest, desire, and action across a fuller message. Use Buyer Personas to keep audience evidence close to the draft. Neither structure can repair an unsupported customer claim.

Juniper’s next task is to check the problem against customer episodes and demonstrate the update behavior. The copy becomes ready when the promised solution matches what readers can actually expect.

Sources and further reading