Voice & Structure — the calibrated formula

Every rule below is derived from a 100-post performance dataset (top-15 posts vs bottom-50 by engagement). Markers that separate winners from flops, with prevalence in top posts vs the rest:

Marker	Top 15	Bottom 50
Comment-word CTA	100%	46%
Ellipsis line-pacing	100%	52%
P.S. line	60%	24%
"(steal X, completely free)" parenthetical	present	never
Specific number/tool in hook	60%	46%
Median length	~1,300 chars	~850 chars

Treat the 100% markers as mandatory. Treat the rest as strong defaults.

The five-part structure (fixed order, every post)

1. Outcome-first hook — a concrete result, number, or named tool in line one. Never a topic, never a question, never "thoughts on X".
2. Free-claim parenthetical — immediately under the hook, in brackets: "(steal the exact blueprint, completely free)". Vary the verb (steal/grab/swipe) and the noun; keep the shape.
3. Context/pain block — why this matters now. Name the ICP's specific pain in their own words. Often opens with "For context..." and builds through 4–8 short lines to a turn ("The fix isn't X. It's Y...").
4. Deliverable stack — the "inside:" list. Formatting rules live in titles-and-deliverables.md; follow them exactly.
5. CTA + P.S. — two valid formats. Single-line: "Comment "WORD" and I'll DM you the [thing]." Or two-step: 👉 Comment "WORD" / 👉 Connect with me so the DM goes through — always the low-friction comment step FIRST; readers do the first action they see. The P.S. is the second-most-read line in the post after the hook — never waste it. Best uses in order: a proof/asset pointer ("full sample report in the first comment"), a trust line ("unedited output, one chat"), or the connection note if the CTA didn't already carry it.

Media direction accompanies every post: the visual must prove the hook's claim (dashboard screenshot, results chart, the actual resource open on screen). A post whose image proves nothing is running four parts of a five-part formula. For video: cold-open on the before state (the raw file, the messy dashboard) — the payoff only lands after the pain is seen — and burn the hook line in as overlay text, because most feeds autoplay silent.

Voice rules

• One idea per line. Blank line between every line or two. The post should read as a fast vertical scan, never paragraphs.
• Ellipsis pacing. Use "..." to end a line that pulls the reader to the next one. 2–4 per post — pacing device, not tic.
• CAPS for emphasis on 1–4 load-bearing words per post (ONE, EXACT, ENTIRE, FIRST, RARELY). Never full caps sentences except a pattern-interrupt hook.
• Specific numbers everywhere. "5 agents", "27 calls in 48 hours", "4.5 focused hours" — round numbers read as invented; precise ones read as true.
• Length target: 1,100–1,600 characters, roughly 20–30 rendered lines. Under ~900 chars reads thin; over ~1,800 loses the scan.
• Bullets: "-->" arrows for mechanism/how-it-works lists, "✅" checks for the deliverable stack, "-" dashes for quick result lists.
• Second person pivot. The pain block must move from "I/we" (proof) to "you" (their situation) before the deliverable stack.
• No hashtags. No links in the post body. The comment word is the whole conversion mechanic.
• Comment word: single word, CAPS, in quotes, thematically tied to the magnet (a systems magnet → "STACK", "AGENTS", "SOP"; a template pack → "TEMPLATES", "KIT").

Pre-delivery checklist

Score every draft. Fix failures before presenting.

1. Hook contains a specific number, named tool, or hard contrast — not a topic
2. Free-claim parenthetical present within the first three lines
3. Pain block names the ICP's problem in their language and pivots to "you"
4. Deliverable stack passes all rules in titles-and-deliverables.md
5. Single comment word, quoted, CAPS; in a two-step CTA the comment step comes before the connect step
6. P.S. line present and working (proof pointer, trust line, or connection note — not filler)
7. 1,100–1,600 characters
8. At least two ellipsis pace-lines
9. Zero fabricated metrics
10. Media direction line written and it proves the hook