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 saves drafts to your notes or vault as markdown before any export.
- Draft destination:
[your-drafts-folder]/[Brand]/YYYY-MM-DD - [page-slug]/ - Hub file:
00 - [Page Title].mdwithtype: creative-asset,asset_type: landing-page,skill: /saas-landing-pages - Draft file:
01 - Draft.mdwithtype: creative-draft - Default export format:
docx - Export triggers: "export to docx", "export to pdf", "export both", "ready for delivery"
Brand detection: Ask which brand or client this page is for, and save it under that brand's or client's folder.
Document integrity. Write every draft this skill saves as a current-state document. When feedback or new facts arrive, rewrite the affected section in place and fix anything elsewhere in the file (and in related files) that the change contradicts. Never append dated addenda, update blocks, or change narration to a draft. Record each revision as one short line in the hub, and before finishing, reread every file you touched and remove stale claims, duplicate sections, and change narration.
No .docx or .pdf is produced on first pass. Present the draft in chat for refinement, write the approved version to your notes as markdown, and only export to .docx/.pdf when explicitly triggered.
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
- Homepage / Main Landing Page: Primary brand and product page
- Product / Feature Page: Single feature or product deep-dive
- Solution / Persona Page: Industry, team, or persona-specific
- Use Case Page: Specific workflow or job-to-be-done
- Comparison Page: Competitor differentiation (vs pages)
- Integration Page: Partner/tool integration showcase
- Pricing Page: Plans, tiers, and conversion
Instructions
- Confirm page type before writing
- Collect inputs based on page type
- Generate complete draft following framework structure
- 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
| Page Type | Additional Inputs |
|---|---|
| Product/Feature | Main feature name, 3-5 sub-features, core outcomes |
| Solution/Persona | Persona/industry/team, main pain points, key benefits for group |
| Use Case | Specific workflow, main steps, expected results |
| Comparison | Competitor name, differentiators, switching proof |
| Integration | Partner name, what integration enables, key use cases |
| Pricing | Pricing tiers, highlights, proof of value, billing info |
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.