# Playbook: Four Ps — Promise · Picture · Proof · Push

> Make the claim, make it vivid, back it, then close — ideal for mid-length email and landing copy.

## Origin

**Henry Hoke**, a lesser-known but tightly disciplined formula built for exactly the length range the other nine playbooks tend to either overshoot (RMBC, Big-Idea VSL) or undershoot (AIDA). MANUAL.md places it explicitly at "mid-length email and landing copy" (§6.9) — the space between a 12-word ad and a 2,000-word sales page. Its four beats deliberately borrow from two different traditions in the same short span: Promise is Hopkins's reason-why compressed to a claim, Picture draws on the Heath brothers' *Concrete* criterion (§2.4), and Push is Fogg's behavior-model discipline (§2.10) applied to a single line.

## When to use it

- **Mid-length surfaces**: marketing emails, landing-page body sections, product-page copy blocks — per §5.2's decision table ("channel = email body → Four-Ps or PAS").
- Where the audience needs more than an ad's four words but doesn't have 20 minutes for a VSL or 2,000 words for a sales letter.
- Good default when a Solution-Aware or Product-Aware prospect (§3.1) needs one tight, self-contained persuasive unit rather than a full-spine sales page.

## When NOT to use it

- **Very short cold-ad surfaces** — four full beats won't fit in a hook line; use AIDA's Attention/Interest compression instead.
- **Long-form, high-ticket, skeptical-buyer contexts** where a single Proof beat isn't enough weight — Ogilvy factual long-form or RMBC's proof-stacking is the better fit once the buyer needs multiple, varied proof elements rather than one.
- **Most-Aware audiences already past the Promise/Picture stage** — for them, Offer-lead directness (skip straight toward Push) respects their readiness better than re-walking them through vividness they don't need.

## Step-by-step build

1. **Promise** — one sentence, the core claim, stated plainly. No hedging, no compound claims — one promise, per the Rule of One (Zajonc, §2.5).
2. **Picture** — make the promise sensory and concrete (Heath's *Concrete*): a specific scene, a specific number, a specific before/after — not an abstraction of the benefit.
3. **Proof** — back the Picture with one tagged proof element (`[testimonial|data|demo|authority|story]`, per §3.2.4's tagging discipline). In this compressed format, one strong, specific proof element outperforms three thin ones.
4. **Push** — single CTA, verb-first, friction-minimized per Fogg's model (reduce required ability, deliver a clear, unambiguous prompt).

Total length target: tight enough to read in under a minute — if any beat is expanding past a short paragraph, the piece has outgrown Four-Ps and belongs in a longer spine instead.

## Worked mini-example

**Promise:** "You can prove your business is buyer-ready in one sitting."

**Picture:** "Instead of a buyer's team taking three weeks to quietly conclude your business can't survive you leaving the room, they open a single page with your Ladder score already on it — Level 7, founder-dependency at 34%, revenue durability documented."

**Proof:** "Three builders used this exact audit to move from Level 4 to Level 7 in one quarter, with their founder-dependency ratio dropping from 91% to 34% [data]."

**Push:** "Start the 12-minute audit."

## How the verify gate applies

In email form, falls under §8.4's `email-subject-bank` rubric for the subject line specifically (≤9 words, no ALL-CAPS, ≤1 emoji, no spam-trigger words) and the general §8.6 universal bar for the body. In landing-page-block form, it's checked against the same proof-coverage and single-CTA rules as §8.1 — Push must be the page's **one** distinct CTA target, not an additional competing action. Because the format compresses to a single Proof beat, that one element carries disproportionate weight in the **proof-coverage gate**: if the single number in Picture doesn't have a tagged source backing it in Proof, the whole unit fails, since there's no second or third proof element elsewhere in the piece to fall back on.