Building B2B Landing Pages
Identify which of the four core page types the user needs, then apply its structure:
- Overview page (paid media homepage) — first-touch page, answers basics fast, routes buyers by role/industry/use case
- Comparison page — trustworthy, honest differentiation vs. alternatives for AI search/"best of" shortlisting
- Social proof page — curated reviews, case studies, testimonials (single page or per-audience)
- Demo request page — reduces hesitation for a high-friction conversion ask
Ask which page type and pull in context (buyer persona, competitors, value props, product count) before drafting structure/copy.
Progress:
- [ ] Identify page type (overview / comparison / social proof / demo)
- [ ] Gather inputs: target buyer, competitors, product/audience count, key value props
- [ ] Choose structural variant (e.g., overview: single vs. multi-product template)
- [ ] Draft section-by-section outline
- [ ] Write first-pass copy per section, defending each value prop against buyer skepticism
- [ ] Run against audit checklist (technical, messaging, conversion path, load time)
1. Overview / Paid Media Homepage
- Lead with a clear, immediate answer to "what is this and is it for me"
- Build audience-routing paths (by role, industry, or use case) below the fold
- If multiple products: use the multi-product template variant with product-selector navigation
- If single product, multiple audiences: use persona-branching sections instead
2. Comparison Page
- State positioning plainly — don't hide the comparison intent
- Give honest differentiation: concede where competitors win, be specific where you win
- Use concrete, checkable details (pricing tiers, feature specifics, use-case fit) — avoid vague superiority claims
- Structure: intro framing → comparison table → "when to choose us / them" → proof → CTA
3. Social Proof Page
- Decide: one unified page or segmented by audience/vertical
- Mix formats: short testimonial quotes, case study summaries with metrics, logos
- Lead with the proof point most relevant to the traffic source (match ad messaging to page proof)
- Always pair proof with a direct next-step CTA (demo, trial, contact)
4. Demo Request Page
Run this as a structured interview before writing, not a one-shot generation:
- Ask about the buyer's role, stage of awareness, and objections
- Ask about competitors and how this offer differs
- Have the user defend each value prop — if they can't justify it, cut it
- Address the 7 things every demo page must get right:
- What happens during the demo (set expectations, reduce ambiguity)
- Time commitment required
- Who should attend / is this the right fit
- What they'll walk away with
- Proof this is worth their time (proof points near the form)
- Friction reduction in the form itself (minimal fields, clear next step)
- Objection handling (pricing, implementation, security) addressed before the ask
- Output: a full page structure plus first-pass copy per section
Example 1: Input: "We have 3 products, enterprise + SMB buyers, need an overview page for paid search traffic." Output: Multi-product template outline — hero answers "who we are + who it's for" in one line, product-selector module below hero, audience-branch sections (enterprise vs. SMB) with tailored proof points per branch, single unified CTA bar.
Example 2: Input: "Write a demo request page for a mid-market SaaS tool competing against [Competitor X]." Output: Interview questions first (buyer role? what makes them hesitate vs. Competitor X? what's the actual demo format?) → page outline: hero (clear ask + time commitment) → "who this is for" → what happens in the demo → proof block countering Competitor X's known strength → short form → objection-handling FAQ.
- Match page copy to the specific traffic source (paid search ≠ retargeting ≠ social)
- Comparisons must be genuinely honest — credibility beats spin, especially for AI-search shortlisting
- Every value prop needs a one-line defense; cut anything the buyer can't be convinced of
- Demo pages: reduce ambiguity about time/format before asking for the form fill
- Run every finished page through the audit checklist: technical setup, messaging clarity, conversion path, load time
- Treating the overview page as a generic homepage instead of a routed, audience-aware first-touch page
- Comparison pages that oversell and under-detail — buyers and AI systems both discount vague claims
- Demo pages that ask for the meeting before explaining what it is or why it's worth the buyer's time
- One-shot copy generation without first interrogating buyer objections and competitive context
- Social proof pages with generic testimonials not matched to the audience segment viewing the page