Three episodes on landing page conversion as a designable system. Why most landing pages don't convert despite looking professional (the visual hierarchy doesn't match the buying decision the page is asking for, and the proof layer arrives at the wrong moment), the structural moves that move the rate, and the testing patterns that distinguish a real winner from variance. Built for the marketer or growth lead with a landing page in production that's underperforming and ready for the operator-tier read on what's actually broken.

The book on landing pages as a conversion engineering problem. Covers the structural moves: the hero promise that has to land in three seconds, the credibility stack that builds trust at each scroll position, the pain-desire bridge that closes the gap between problem and solution, the objection-handling layer that prevents the buyer from stalling, and the call-to-action design that doesn't read as a sales pitch. Worked examples across SaaS, services, and ecommerce landing pages. Built for the marketer ready to treat landing pages as the conversion infrastructure they actually are.

The structured check for the section of any landing page that bridges the problem to the solution — the part most pages either skip entirely (going straight from features to CTA) or overdo (turning into a pain-amplification exercise that reads as manipulative). Walks through the pain articulation that respects the reader, the solution framing that connects to the actual problem, the proof anchoring that prevents the bridge from feeling like a leap of faith, and the structural placement that puts the bridge at the right scroll position. Run on every landing page draft.

The detailed framework for writing the hero promise — the headline plus subhead plus visual that has to land in three seconds. Covers the specificity calibration that prevents the hero from being either too vague (so the visitor doesn't know what's offered) or too narrow (so they don't know if it applies to them), the audience-clarity step (you can't optimise a hero for everyone), and the visual-text balance that signals what kind of company this is before the visitor reads anything. Worked example through fifteen real heroes with the structural critique.

The detailed framework for building the credibility layer of a landing page. Covers the hierarchy: the high-impact signals that go above the fold (logos, headline numbers, the one specific testimonial), the supporting layer that builds trust as the visitor scrolls (specific case studies, named customers, third-party validation), and the foundation layer near the conversion point (guarantees, security signals, the small details that close trust gaps). Built for the marketer noticing their page has all the credibility elements but they're in the wrong order or wrong place.

Thirteen specific landing-page frameworks, each suited to a particular buying context. The PAS (problem-agitate-solve) for buyers stuck on a specific pain. The hero's-journey framework for transformations. The before-after-bridge for product comparisons. The features-as-outcomes pattern for technical buyers. Each framework gets a one-paragraph description, a use case, and a specific implementation note. Read in fifteen minutes. Most marketers default to one framework for everything; matching the framework to the buying context is the unlock.

Seven cognitive mechanisms used ethically to move conversion on landing pages. Specificity (concrete numbers and names beat adjectives by enormous multiples). Loss aversion (framing what's at stake without manufactured urgency). Social proof (placement matters more than volume). Authority anchoring (the right credibility signal at the right moment). The endowment effect (mental ownership before purchase). Each gets a one-paragraph mechanism explanation and a placement note. Read in twelve minutes.

Seven daily emails that walk through redesigning a landing page that isn't converting. Day 1: diagnostic — where in the page do visitors actually drop. Day 2: hero-promise rewrite. Day 3: credibility-stack reorganisation. Day 4: pain-desire bridge installation. Day 5: objection-handling section. Day 6: CTA design and placement. Day 7: testing and ongoing rhythm. Designed to be done on an actual page, not as a thought experiment.

Working prompts for the AI-assisted parts of landing page work: the hero-promise variant generator (against a defined audience and offer), the credibility-stack analyser (paste your current page, get the structured critique on what's missing or in the wrong order), the pain-desire bridge drafter, the page post-mortem from analytics data. Each prompt comes with input/output format. Tested across Claude and ChatGPT.