The 4 Ps of copywriting (Promise, Picture, Proof, Push) applied to a landing page

We've already covered AIDA (Attention, Interest, Desire, Action) and PAS (Problem, Agitate, Solve), two structures that share a common starting point: they open on the visitor's attention or on their problem. The 4 Ps — Promise, Picture, Proof, Push — take the other route. It's a classic of direct-response copywriting (mail order, catalog sales, info products), taught for decades in copywriting handbooks, that opens on a promise rather than a pain point. Four steps, one simple principle: state a precise result, make it imaginable, prove it, then ask for the action.

Where the formula comes from, and how it differs from PAS or AIDA

The three structures aren't interchangeable, because they don't start from the same place. PAS assumes a pain the visitor has already identified — a leak, a delay, money lost — and opens by naming it. AIDA assumes you need to build interest before desire, useful when the offer doesn't fix anything specific but creates a want (a course, something new). The 4 Ps assume something else: an offer with one strong, specific, defensible benefit, able to carry the page opening on its own. It's the most natural structure for an ebook, an online course, a coaching program, or any product whose end result is the real selling point — the territory covered in our ebook sales page examples.

Promise — a promise, not a feature list

The promise is a result, stated in the singular and dated if possible — never a list of features. "Write your first landing page that converts in a weekend" is a promise; "A visual editor, 10 templates, Next.js export" isn't one yet, even if those are real strengths. The difference lies in specificity: the narrower and more measurable the promise, the more credible it is, and paradoxically the wider the audience that recognises itself in it. It usually plays out in the page's headline, sometimes rephrased in the subhead to absorb a nuance or condition ("no coding required", "even with no ad budget").

Picture — make the result vivid, without forcing the imagination

The second step is about giving the promise a body: concretely describing what changes once the result is achieved, rather than stating it a second time in different words. This is where the method is most often applied wrong, because "making the reader imagine" isn't automatically a positive move. A study by Petrova and Cialdini published in 2005 in the Journal of Consumer Research shows that imagery appeals can backfire: when the requested image is hard to generate — too abstract, too far from the reader's own experience — the appeal to imagination lowers preference for the product instead of raising it (study on Google Scholar). In practice, that means dropping the vague image ("imagine a calmer life") in favour of a precise, sensory scene anchored to an identifiable moment: a Sunday evening with no bill-related stress, a client replying "yes" five minutes after the quote is sent. A before/after photo or a screenshot of the product doing what it promises — see our approach to showing a SaaS product — often works better than a purely verbal image, precisely because it asks no imaginative effort from the reader.

Proof — proof should answer doubt first, not show off

A strong promise mechanically creates skepticism: the more impressive the stated result, the more the visitor looks for a reason not to believe it. The Proof section should therefore be built as an answer to that doubt rather than a showcase of the best reviews. That means calibrating carefully what you display: a study by Chevalier and Mayzlin published in 2006 in the Journal of Marketing Research, looking at book sales on Amazon.com and BarnesandNoble.com, found that the impact of a negative review on sales is stronger than that of an equivalent positive one (study on Google Scholar) — the same negative/positive asymmetry found in loss aversion. In practice, a page showing only testimonials without a single rough edge draws attention to what it's hiding; better to show a reasonable number of credible reviews, a verifiable figure, or a guarantee that explicitly absorbs the risk that the promise won't hold — three ways of addressing doubt instead of ignoring it.

Push — turn the promise into a click

The last P is the shortest to write and the most often rushed: a generic button ("Learn more") that breaks the thread built by the three previous steps. An effective Push rephrases the promise as a command — "Get your weekend back" rather than "Submit" — and addresses the most likely objection one last time, right before or right after the button, in the spirit of our converting CTA examples. Genuine urgency (limited spots, a price about to change) can legitimately speed up the decision, as long as it stays true — the subject of our article on honest urgency and scarcity. And if one objection keeps coming up with customers, it deserves its own line near the button rather than a paragraph buried higher up, as detailed in our guide to handling objections.

4 Ps, PAS or AIDA: how to choose

In practice these structures combine more than they exclude one another: a page can open in 4 Ps (promise, picture of the result) then handle objections the way PAS would. What matters is never the acronym but the logical order it imposes — never start with yourself, always end with a clear action. To see where each block fits in a full page, our anatomy of a landing page that converts details the section-by-section flow, and our form guide covers what happens after the click on Push. LanderKit's Ebook Infoproduit template (€89 on its own, €229 for the full pack) starts from this exact structure: a promise slot at the top of the page, a section dedicated to picturing the result, a calibrated proof block, and a button that restates the promise instead of a generic "Buy".