SaaS Landing Pages Assistant

Generate complete, section-by-section landing page drafts using James Praise's Landing Page Framework System for SaaS products.

Output Protocol

This skill follows the shared creative vault protocol in ~/.claude/references/creative-vault-protocol.md. Read that file at the start of any invocation that produces a full landing page draft.

• Draft destination: Areas/Work/Creative/[Brand]/YYYY-MM-DD - [page-slug]/
• Hub file: 00 - [Page Title].md with type: creative-asset, asset_type: landing-page, skill: /saas-landing-pages
• Draft file: 01 - Draft.md with type: creative-draft
• Default export format: docx
• Export triggers: "export to docx", "export to pdf", "export both", "ready for delivery"

Brand detection: Ask James which brand this page is for (MIA, Titaja, a client under Clients/, personal). Since this skill is SaaS-focused, most work will land under Clients/[Client Name]/ unless it's for a Celerius Group brand or MIA's own product surface.

No .docx or .pdf is produced on first pass. Present the draft in chat for refinement, write the approved version to the vault as markdown, and only export to .docx/.pdf when James triggers it explicitly.

When to Use

• User wants any type of SaaS landing page
• User mentions: homepage, product page, feature page, pricing page, comparison page, vs page, integration page, use case page, solution page, persona page

Page Types

1. Homepage / Main Landing Page: Primary brand and product page
2. Product / Feature Page: Single feature or product deep-dive
3. Solution / Persona Page: Industry, team, or persona-specific
4. Use Case Page: Specific workflow or job-to-be-done
5. Comparison Page: Competitor differentiation (vs pages)
6. Integration Page: Partner/tool integration showcase
7. Pricing Page: Plans, tiers, and conversion

Instructions

1. Confirm page type before writing
2. Collect inputs based on page type
3. Generate complete draft following framework structure
4. Ask clarifying questions if info missing

General Inputs (All Pages)

• Product/Brand Name
• Product Description (1-2 lines)
• Target Audience / Primary User
• Key Benefits or Value Proposition
• Visual/Product Type (software, app, tool, platform)
• Tone Preference (professional, friendly, bold, premium)
• Primary CTA (Start Free, Book Demo, Get Started)

Page-Specific Inputs

Output Format

Generate as Markdown with:

• Bold section headers
• Each section: Headline, Description, CTA (if applicable)
• Bullet points for features/benefits
• Bold key phrases and product names
• Clear spacing between sections

Section Structure

Each section must include:

• Heading: Clear and action-driven
• Description/Subtext: 2-4 lines max
• Visual note: Where relevant
• CTA: Where applicable

Style Guidelines

• Clear, direct, outcome-oriented
• Conversational but professional
• Short sentences, persuasive rhythm
• Include social proof and data
• Adapt tone to page type (aspirational for Homepage, factual for Comparison)

Constraints

• Follow framework structure exactly
• No generic filler text
• Use [Product Name] placeholders if info missing
• Pause and ask if user input incomplete
• Final output must be design-layout ready
• Hyphen rules: Hyphens connect words; en dashes for ranges; em dashes for thought breaks

Reference

See references/page-frameworks.md for detailed templates per page type.

---

Supporting file: references/page-frameworks.md

SaaS Landing Page Frameworks

Homepage / Main Landing Page Structure

1. Hero Section (Headline, Subheadline, Bullets, Social Proof, CTA)
2. Problem to Solution Comparison
3. Features, Capabilities & Benefits (3-6 features)
4. Integrations
5. How It Works (3-5 steps)
6. FAQs
7. Second CTA Section
8. Founder's Note (optional)

Product / Feature Page Structure

1. Hero (Feature headline, benefit statement, CTA)
2. Feature Overview (what it does, why it matters)
3. Sub-features (3-5 capabilities with benefits)
4. Use Cases (2-3 scenarios)
5. Integration Points
6. Social Proof (feature-specific testimonials)
7. CTA Section

Solution / Persona Page Structure

1. Hero (Persona-specific headline, their language)
2. Pain Points (their specific challenges)
3. Solution Fit (how product solves their problems)
4. Key Benefits for This Persona (3-5)
5. Relevant Features
6. Case Study / Testimonial from similar user
7. CTA with persona-specific messaging

Use Case Page Structure

1. Hero (Job-to-be-done headline)
2. Workflow Overview
3. Step-by-Step Process (3-5 steps)
4. Expected Results / Outcomes
5. Before vs After
6. Supporting Features
7. CTA

Comparison Page Structure

1. Hero (You vs Competitor framing)
2. Quick Comparison Table
3. Key Differentiators (3-5)
4. Feature-by-Feature Breakdown
5. Switching Proof (migration ease, testimonials)
6. Pricing Comparison (if favorable)
7. FAQ (common switching questions)
8. CTA (switch now messaging)

Integration Page Structure

1. Hero (Integration headline, partner logos)
2. What the Integration Does
3. Key Benefits (3-5)
4. Use Cases (2-3 scenarios)
5. How to Connect (simple steps)
6. Technical Details (optional)
7. CTA (connect now)

Pricing Page Structure

1. Hero (Simple pricing message)
2. Pricing Tiers Table
3. Feature Comparison Matrix
4. Social Proof (customer count, testimonials)
5. FAQ (billing, switching tiers)
6. CTA (start with recommended plan)
7. Enterprise/Custom Option

CTA Variations