agentleFS
puretechnycpuretechnyc/purebrain-skills/skills/marketing/landing-page-funnel/SKILL.md

landing-page-funnel

Skill0 starsChanged 6 months agoMITView on GitHub

Build high-converting SaaS landing page funnels using proven patterns from top-performing companies. Page structure template, copy frameworks, design rules, conversion tactics, anti-patterns.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when building, auditing, or redesigning a SaaS landing page, pricing page, or signup funnel.

    line 13
  2. Distinctive:

    Use an action verb.

    line 53
  3. Distinctive:

    No jargon. No buzzwords.

    line 54
  4. Distinctive:

    Always add micro-copy below primary CTA: "No credit card required" or "Free 14-day trial."

    line 73
  5. Distinctive:

    Never use "Submit" or "Click Here."

    line 75
  6. Distinctive:

    Use one font family max. Sans-serif.

    line 86
  7. Distinctive:

    Every hero section gets two CTAs side by side:

    line 114
  8. Distinctive:

    Ask 2-3 questions at signup to personalize the experience:

    line 125
  9. Distinctive:

    Every testimonial MUST include all five elements:

    line 144

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Landing Page Funnel Skill

When to Use This Skill

Use when building, auditing, or redesigning a SaaS landing page, pricing page, or signup funnel.


1. Page Structure Template (Exact Section Order)

Build every landing page in this order. Do not skip sections. Do not reorder.

#SectionPurposeKey Rule
1Nav barOrientation + persistent CTALogo left, 3-5 links center, CTA button right
2HeroHook + primary conversionHeadline (under 8 words) + subheadline (1-2 sentences) + primary CTA + product screenshot or 15s demo
3Logo barInstant credibility5-8 recognizable customer/press logos. Scrolling carousel on mobile
4Problem/painEmotional resonanceName the specific pain. No features here. Only the broken status quo
5Solution showcaseOutcome-driven features3-5 feature cards or use-case sections. Benefits, not features. Bento grid or card layout
6Social proofTrust through evidenceTestimonials with photo + full name + title + company + specific metric. Never generic quotes
7How it worksSimplify the mental model3-step visual process. Numbered. Icons or illustrations per step
8Pricing previewRemove ambiguityEmbedded pricing or "See Pricing" link. If embedded: 3 tiers max, middle highlighted
9FAQ / objection handlingOvercome hesitation5-8 most common questions. Accordion format on mobile
10Final CTAClose the loopRepeat hero CTA with urgency-adjacent copy. "No credit card required" micro-copy
11FooterNavigation + legalLinks, legal, secondary nav

2. Copy Frameworks

Framework Selection Guide

FrameworkBest ForStructure
Problem-Solution-ProofEnterprise B2B, long considerationState problem > show solution > prove with data
PAS (Problem-Agitate-Solution)High-ticket, emotional purchasesName pain > twist the knife > present relief
Before-After-BridgeProduct-led growth, transformationShow "before" state > show "after" state > bridge = your product
AIDAContent-heavy pages, multiple CTAsAttention > Interest > Desire > Action
Outcome-firstDeveloper/creative audiences who hate hypeLead with result, explain mechanism second

Headline Rules

  • Under 8 words. Always.
  • Lead with the OUTCOME the customer gets, not the tool's features.
  • Use an action verb.
  • No jargon. No buzzwords.

10 Headline Templates

  1. Outcome + price anchor: "[Product] that runs your [function]. $X/mo."
  2. Aspirational identity: "You're one [product unit] away from [transformation]."
  3. Anti-status-quo: "Goodbye [old way]. Hello [new way]."
  4. Developer empathy: "We built [thing] so you don't have to."
  5. Contrast pair: "One [noun]. Zero [pain point]."
  6. Speed promise: "[Verb] [outcome] in [timeframe]."
  7. Action + specificity: "Put [technology] to work for [job]."
  8. Parallel structure: "[Verb] anything. [Verb] anywhere."
  9. Reframe + outcome: "More than [category]. [Business result]."
  10. Imperative + scale: "Stop [wasteful action]. Start [desired action]."

CTA Button Copy Rules

  • Primary CTA: filled/solid button. Text = action + value ("Start Free Trial", "See It In Action").
  • Secondary CTA: outlined/ghost button. Text = lower commitment ("Watch Demo", "Learn More").
  • Always add micro-copy below primary CTA: "No credit card required" or "Free 14-day trial."
  • Repeat primary CTA every 2-3 scroll sections.
  • Never use "Submit" or "Click Here."

3. Design Rules

Typography

  • Headline: 48-64px desktop, 32-40px mobile. Bold weight (700+).
  • Subheadline: 20-24px desktop, 16-18px mobile. Regular weight (400).
  • Body: 16-18px desktop, 14-16px mobile. Line height 1.5-1.6.
  • Use one font family max. Sans-serif. Inter, Geist, or system fonts.

Mobile-First Rules

  • Design mobile layout first, then scale up to desktop.
  • 58% of SaaS pricing page visits are mobile. 79-83% of total visits are mobile.
  • CTA buttons: minimum 48px height (WCAG), optimal 56-64px on mobile. Full-width on mobile viewports.
  • Thumb zone: place primary CTAs in bottom third of screen.
  • Sticky/floating CTA on long-scroll pages.
  • Stack pricing tiers vertically on mobile. Never horizontal scroll.
  • Collapsible feature comparison tables, not wide grids.
  • Logo bar: scrolling horizontal carousel on mobile.

Layout Patterns (2026)

  • Bento grid for feature sections.
  • Card-based feature sections with hover animations.
  • Split-screen hero: text left, product screenshot right.
  • Scroll-triggered progressive disclosure.
  • Full-width sections alternating with contained-width text blocks.
  • Dark backgrounds work best for AI products, developer tools, premium positioning.

4. Conversion Tactics

Dual CTA Strategy

Every hero section gets two CTAs side by side:

PositionLabel PatternTarget
Primary (left)"Start Free Trial" / "Try for Free"Self-serve signups
Secondary (right)"Get a Demo" / "See It In Action"Enterprise / high-touch leads

This routes visitor intent without forcing a single path.

Intent Routing (Post-Signup)

Ask 2-3 questions at signup to personalize the experience:

  1. Business type / industry
  2. Team size (solo / small team / enterprise)
  3. Primary goal

Route answers to a personalized dashboard, onboarding checklist, and feature surfacing.

Social Proof Placement Strategy

LocationProof TypePurpose
Immediately after heroLogo bar (5-8 logos)Reduces bounce
Mid-pageFull testimonials with metricsBuilds trust for engaged scrollers
Next to pricing tiersShort testimonial quotesReduces plan hesitation
Near signup/payment formsSecurity badges (SOC 2, GDPR, SSL)Removes friction at conversion point

Testimonial Format (Mandatory)

Every testimonial MUST include all five elements:

  1. Photo of the person (not a logo, not an icon)
  2. Full name (never "John D." or initials)
  3. Title and company
  4. Specific metric or outcome ("$16M saved annually", "10,000+ hours saved", "5x more meetings")
  5. 1-sentence quote in their voice

Generic testimonials ("Great product!") are worse than no testimonials.

Pricing Page Rules

  • 3 tiers maximum. Two feels incomplete. Five causes paralysis.
  • Highlight middle tier as "Most Popular" with border, badge, or background color.
  • Annual/monthly toggle at top. Default to annual. Show savings in dollars, not percentages.
  • 8-10 key features per tier with checkmarks/dashes.
  • One CTA button per tier.
  • Feature comparison table below tier cards for deep evaluators.
  • Enterprise tier separated visually, not as a 4th column.

5. Anti-Patterns (What to Avoid)

Anti-PatternWhy It Fails
Fake countdown timersUsers know they reset on reload. Destroys trust.
"Only X spots left" (fabricated)Detected easily. Only use with real scarcity.
Exit-intent pop-upsBlocked by Safari, Firefox, Brave. Feels desperate.
Feature-dumping (20+ features listed)Overwhelms visitors. Focus on 3-5 outcomes.
Generic testimonials without names/metricsZero credibility. Worse than no testimonials.
More than 3 form fields at signupEach extra field drops conversion. Ask for email only.
Horizontal pricing tables on mobile58% of pricing visits are mobile. Horizontal scroll kills conversion.
Stock photos instead of product screenshotsSignals the product is not ready or not real. Show the actual product.
Gating all content behind demo requestsBuyers complete 69% of purchase decisions before talking to sales. Let them self-educate.

Visual Anti-Patterns (NEVER DO)

Anti-PatternWhy It Fails
Border-radius on section containersCreates "card" feel. Top SaaS pages use full-width sections.
Glassmorphism/blur effectsDated trend. No top-5 SaaS page uses frosted glass on content sections.
Card grids for main contentFragments the reading flow. Single-column text for core messaging.
Icon grids (4 icons in a row with labels)Feels like a template. Typography hierarchy replaces icon decoration.
Center-aligned body textHard to read past 2 lines. Left-align always except headlines.
More than 2 font weights per pageVisual clutter. Use only 400 (body) and 600-700 (headlines).
Generic SaaS copy ("Transform your business")Signals AI-generated. Specific, concrete language only.

6. Quality Checklist

Structure

  • Page follows the 11-section order
  • Hero headline is under 8 words and outcome-focused
  • Dual CTA in hero (primary + secondary)
  • Logo bar has 5-8 logos immediately after hero
  • Primary CTA repeats every 2-3 scroll sections

Copy

  • No feature-dumping. 3-5 outcomes max in solution section
  • Every testimonial has: photo, full name, title, company, specific metric, quote
  • Micro-copy below every CTA
  • FAQ covers 5-8 objections

Design

  • CTA buttons are 48px+ height on mobile, 44px+ on desktop
  • Mobile layout designed first, then scaled to desktop
  • Sticky CTA visible on mobile during scroll
  • Pricing tiers stack vertically on mobile
  • One font family. Sans-serif.

Conversion

  • Dual CTA routes to different paths
  • Pricing page defaults to annual toggle
  • Annual savings shown in dollars, not percentages
  • Money-back guarantee near pricing CTAs
  • Security badges near signup/payment forms

Technical

  • Lighthouse performance score 90+
  • Core Web Vitals pass (LCP < 2.5s, FID < 100ms, CLS < 0.1)
  • All images optimized (WebP/AVIF, lazy loaded below fold)
  • Semantic HTML (h1 once, proper heading hierarchy)
  • No layout shift on CTA buttons or pricing cards

Benchmarks to Target

MetricTarget
Visitor-to-lead5%+
Landing page conversion6%+
Free trial to paid25%+
Annual plan uptake55%+
Mobile conversion3%+

Built by PureBrain -- AI-powered marketing operations.

Want the full suite of 183+ production-tested skills? Start your trial ->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.