saas-website-copy

Installation
SKILL.md

SaaS Website Copy

Create high-converting SaaS marketing websites targeting individual users (prosumers, developers, marketers, SMBs).

Discovery Process

Before creating website copy, gather the following information. If any is missing, ask the user through a consultative back-and-forth until all required information is collected.

Required Information

  1. Product basics

    • Product name
    • What the product does (one sentence)
    • Product category (e.g., "project management tool", "CRM", "analytics platform")
  2. Target user

    • Who is the ideal user? (role, industry, company size)
    • What are they trying to achieve? (save time, reduce costs, impress their team, etc.)
  3. Pain points (need at least 3)

    • What specific problems does this product solve?
    • What frustrations does the user currently experience?
    • What's the emotional impact of these problems?
  4. Unique value proposition

    • What makes this product different from alternatives?
    • Why should someone choose this over competitors?
  5. Key features/capabilities (3-5 most important)

    • What does the product do?
    • What outcome does each feature deliver?
  6. Social proof (if available)

    • Customer logos
    • Testimonials with specific results
    • Usage statistics
    • Awards, certifications, review ratings
  7. CTA goal

    • What action should visitors take? (start free trial, book demo, sign up, etc.)
    • Any risk-reducers? (no credit card, free tier, money-back guarantee)

Discovery Questions

If information is missing, ask questions like:

  • "What problem does [product] solve for your users?"
  • "Who is your ideal customer - what's their role and what are they trying to accomplish?"
  • "What makes your product different from alternatives they might consider?"
  • "What are 3-5 key features, and what outcome does each deliver for the user?"
  • "Do you have any customer testimonials, logos, or usage stats we can include?"
  • "What action do you want visitors to take - free trial, demo, or something else?"

Continue gathering information until you have enough to write compelling, specific copy.

Core Principles

  1. Speak to one person - Use "you/your" throughout. Address individual pain points, not company-wide problems. Only 27% of SaaS headlines use "you/your" - don't make this mistake
  2. Benefits over features - Always tie features to outcomes: "Real-time notifications → never miss an important update"
  3. Write conversationally - Sound like explaining to a friend, not a corporate brochure
  4. Show, don't just tell - Use product screenshots over stock photos; demonstrate claims with specifics

Homepage Structure

Follow this section order for optimal conversion flow:

1. Hero Section

  • Headline: 5-8 words, benefit-oriented, concrete (not vague hype)
    • Good: "Organize Your Team's Projects in One Place"
    • Bad: "Reinventing Collaboration"
  • Subheadline: Add specificity - target user, problem solved, key outcome. Answer "What is this and why should I care?"
  • Visual: Product screenshot or mockup (40% of SaaS pages use screenshots in hero). Some pages use no hero image (25%) to stay focused and fast-loading
  • Primary CTA: Single prominent button ("Start Free Trial", "Get Started")

2. Social Proof #1 (Logos)

  • 5-8 recognizable customer/partner logos (not a crowded collage)
  • Focus on logos your audience recognizes or aspires to
  • Caption: "Trusted by X+ [target audience] teams" or "[Company] helps [industry] achieve [outcome]"
  • Skip this section if no logos available yet

3. Problem Section

  • List 3 pain points your audience faces
  • Use visceral, emotional language describing frustration
  • Example: "Managing projects via email leads to tasks slipping through the cracks"
  • Touch on emotional impact: "It's stressful staying on top of it all"
  • Goal: Reader thinks "Yes, that's exactly my issue!"

4. Solution Introduction

  • Brief transition connecting product to the pains above
  • 1-2 sentences: "Meet [Product] – a [category] that [solves specific pain]"
  • Mention product category to clarify what it is, but frame around solving pain
  • Keep it punchy, don't overhype

5. Solution Details (Features)

  • 3-5 key capabilities, prioritized by impact (most attractive first)
  • Lead each with a results-driven subheadline
  • Consider "old way vs new way" contrast: "Stop doing X manually – ProductX automates it"
  • Keep scannable - short blocks, icons/screenshots alongside
  • For complex products: include short explainer video, GIF, or animation
  • Deeper info can live on separate pages or FAQ - just hook them here

6. Social Proof #2 (Testimonials)

  • Specific, results-focused quotes: "Cut project timelines by 25%"
  • Include: full name, photo, title, company (anonymous quotes lack credibility)
  • Real specifics > generic praise
  • Quote: "When you say it, it's marketing. When your customer says it, it's social proof"
  • Skip this section if no testimonials available yet

7. Results Section (Optional)

  • Quantified outcomes: "3x increase in lead volume within 3 months"
  • Use realistic, specific numbers (avoid "1000% improvement")
  • If no customer-specific data, use aggregates: "Over 5,000 tasks completed every week"
  • Skip if no meaningful data available

8. Final CTA

  • Re-emphasize value proposition in closing line: "Ready to streamline your workflow?"
  • Single prominent CTA button with action + benefit text
  • Risk-reduction note: "No credit card required" or "Free forever plan"

Optional Additions

  • How it works section with visuals/diagrams
  • FAQ to address common questions/objections

Copywriting Guidelines

Headlines

  • State what the product does for the user, not what it is
  • Focus on customer's needs and results, not your company

Tone

  • Conversational, warm, human - a differentiator in B2B
  • Avoid jargon - use terms your audience actually uses

Scannability

  • Short sentences and paragraphs (2-3 sentences each)
  • Break up with subheadings, bullet points, icons
  • Visitors skim - key messages, benefits, and CTAs must pop at a glance
  • Clarity trumps cleverness

Emotional Triggers

  • Acknowledge frustration in problem sections: "Missed deadlines are stressful and can make your team feel defeated"
  • Paint positive outcomes: relief, confidence, peace of mind
  • Use power words: "effortless", "frustration-free", "secure", "delightful"
  • Buying decisions are driven by feeling, then justified by logic

Claims

  • Make reasonable promises you can deliver
  • "Get results in days, not weeks" > "Triple your revenue guaranteed"
  • Exaggerated claims backfire - users won't trust them or will be disappointed

Trust Signals (Beyond Logos/Testimonials)

Include if available:

  • Usage statistics: "100,000 users" or "20 million files synced"
  • Review site ratings: G2, Trustpilot, Capterra badges with star ratings
  • Awards/recognitions: Industry awards, "Best of" lists
  • Security badges: SOC2 Certified, GDPR compliant (if handling sensitive data)

Design Principles

  • Minimize distractions: 91% of successful SaaS landing pages have no top navigation; 73% have single primary CTA
  • Mobile-first: Majority of visits are mobile - ensure CTAs are prominent on small screens
  • Speed matters: Compress images, minimize scripts - every second of delay costs conversions
  • Visual hierarchy: Guide eye through narrative - headings larger, sections flow logically, CTA stands out
  • White space: Clean, uncluttered layouts make content approachable
  • Consistent aesthetic: Brand colors, readable fonts, logical spacing; CTA in contrasting standout color
  • Authentic visuals: Product screenshots, diagrams - avoid cliched stock photos

CTA Best Practices

  • Action + benefit text: "Start My Free Trial", "Book a Demo", "Get Started – It's Free"
  • Contrasting color that stands out
  • If secondary CTA needed (e.g., "Watch a Video Demo"), make it less prominent
  • Repeat primary CTA at page bottom
  • One goal per page - multiple equal CTAs confuse visitors
Related skills

More from miketromba/skills

Installs
1
GitHub Stars
1
First Seen
Mar 23, 2026