Website Copy Specialist

Website Copy Specialist

Expert website copywriter specializing in SaaS and B2B website pages — from homepage messaging to conversion-focused CTAs across every page type.

Philosophy

Great website copy does four things:

1. Answers "What is this?" — Visitors decide in 3-5 seconds if they're in the right place 2. Creates a clear path — Every page guides toward one primary action 3. Speaks to the visitor — "You" language, not "we" language 4. Reduces friction — Anticipates objections and addresses them proactively

How This Skill Works

When invoked, apply the guidelines in rules/ organized by:

• homepage-* — Homepage messaging hierarchy and structure
• feature-* — Feature page copy and organization
• about-* — About page storytelling
• pricing-* — Pricing page copy optimization
• comparison-* — Comparison and alternative pages
• tour-* — Product tour pages
• integration-* — Integration pages
• usecase-* — Use case and solution pages
• conversion-* — Demo request and contact pages
• navigation-* — Navigation and microcopy

Core Frameworks

The Clarity Hierarchy

Every page follows the same priority:

1. WHAT (What is this thing?)
   ↓
2. WHO (Is this for me?)
   ↓
3. WHY (Why should I care?)
   ↓
4. HOW (How does it work?)
   ↓
5. PROOF (Can I trust this?)
   ↓
6. ACTION (What do I do next?)

Message-Market Match

Page Types and Goals

The Specificity Ladder

More specific = more persuasive:

Weak:    "Save time"
Better:  "Save hours every week"
Strong:  "Save 5 hours per week"
Best:    "Save 5 hours per week on code reviews"

Website Copy Spectrum

Content Hierarchy by Page

Homepage Sections (Order)

1. Hero (value prop + CTA) 2. Social proof bar (logos) 3. Problem/solution overview 4. Key features/benefits 5. How it works 6. Testimonials/case studies 7. Secondary features 8. Final CTA

Feature Page Sections

1. Feature headline + subhead 2. Hero visual (screenshot/video) 3. Key benefits (3-5) 4. Detailed capabilities 5. Use cases 6. Social proof 7. Related features 8. CTA

Anti-Patterns

• "We" focused copy — "We built" vs "You get"
• Feature lists without benefits — Features tell, benefits sell
• Generic headlines — "Welcome to [Company]" tells nothing
• Buried CTAs — Make the action obvious and repeated
• Missing social proof — Claims without evidence
• One-size-fits-all — Different pages need different voices
• Jargon overload — Write for humans, not search engines
• No clear hierarchy — Visitors scan, they don't read
• Competing CTAs — One primary action per page
• Ignoring objections — Address concerns before they derail

1. Homepage Messaging (homepage)

Impact: CRITICAL Description: Homepage messaging hierarchy, hero sections, value propositions, and visitor routing.

2. Feature Pages (feature)

Impact: CRITICAL Description: Feature page structure, benefit-led copy, capability demonstration, and feature-level CTAs.

3. Pricing Pages (pricing)

Impact: CRITICAL Description: Pricing page copy, tier differentiation, value framing, and purchase facilitation.

4. About Pages (about)

Impact: HIGH Description: Company storytelling, mission statements, team presentation, and trust building.

5. Comparison Pages (comparison)

Impact: HIGH Description: Competitive positioning, alternative pages, switch messaging, and differentiation.

6. Product Tour Pages (tour)

Impact: HIGH Description: Product walkthrough copy, guided experiences, and visual demonstration support.

7. Integration Pages (integration)

Impact: MEDIUM-HIGH Description: Integration landing pages, ecosystem positioning, and technical-adjacent copy.

8. Use Case Pages (usecase)

Impact: MEDIUM-HIGH Description: Use case and solution pages, persona-specific messaging, and vertical positioning.

9. Conversion Pages (conversion)

Impact: CRITICAL Description: Demo request pages, contact forms, sales enablement copy, and conversion optimization.

10. Navigation & Microcopy (navigation)

Impact: MEDIUM Description: Navigation labels, button copy, form microcopy, error messages, and UI text.

About Page Storytelling

Impact: HIGH

The about page builds trust and connection. It answers: "Who is behind this product, and can I trust them?" Done well, it turns evaluators into believers.

About Page Structure

┌────────────────────────────────────────────────────┐
│ 1. OPENING STATEMENT                               │
│    Who you are + what you believe                  │
│    (Not "Welcome to our about page")               │
├────────────────────────────────────────────────────┤
│ 2. ORIGIN STORY                                    │
│    Why you exist — the problem you saw             │
│    The moment that sparked the company             │
├────────────────────────────────────────────────────┤
│ 3. MISSION/VISION                                  │
│    Where you're going + why it matters             │
│    The change you want to create                   │
├────────────────────────────────────────────────────┤
│ 4. VALUES/PRINCIPLES                               │
│    What you believe + how you operate              │
│    3-5 core values with real meaning               │
├────────────────────────────────────────────────────┤
│ 5. THE TEAM                                        │
│    Leadership + key team members                   │
│    Humanizing photos + brief bios                  │
├────────────────────────────────────────────────────┤
│ 6. TRACTION/PROOF                                  │
│    Customers, funding, milestones                  │
│    Credibility markers                             │
├────────────────────────────────────────────────────┤
│ 7. CULTURE GLIMPSE                                 │
│    What it's like to work here                     │
│    (Optional, good for recruiting)                 │
├────────────────────────────────────────────────────┤
│ 8. JOIN US CTA                                     │
│    Careers, contact, or newsletter                 │
└────────────────────────────────────────────────────┘

The Three Audiences

Your about page serves three different readers:

Opening Statement Formulas

Good Opening Statements

✓ "We believe the best infrastructure is the kind you never think about."
  → Clear belief, implies their approach

✓ "Great products come from teams that talk to their customers."
  → Values-driven, customer-centric

✓ "We're building the financial tools we wished existed."
  → Origin hint, relatable motivation

✓ "Enterprise software should be as good as consumer software.
   That's why we exist."
  → Problem → Mission in two sentences

Bad Opening Statements

✗ "Welcome to our about page! We're so glad you're here."
  → Wastes prime real estate

✗ "Founded in 2019, Acme Inc. is a leading provider of..."
  → Boring, could be any company

✗ "Our mission is to leverage synergies to drive innovation."
  → Meaningless corporate speak

✗ "We're passionate about helping businesses succeed."
  → Generic, could describe anyone

Origin Story Framework

The best origin stories follow this arc:

1. THE PROBLEM (Conflict)
   "We were [doing X] when we realized [Y was broken]"

2. THE INSIGHT (Turning point)
   "We discovered that [unexpected truth]"

3. THE SOLUTION (Resolution)
   "So we built [product] to [solve problem]"

4. THE MISSION (Forward look)
   "Now we're on a mission to [bigger vision]"

Good Origin Story

✓ "In 2019, we were a team of four engineers building a fintech product.
   Every week, we'd waste hours hunting for API keys scattered across
   Slack, .env files, and sticky notes.

   When a leaked credential almost cost us a launch, we knew something
   had to change. We looked for a solution that was secure, simple,
   and didn't require a PhD in DevOps. It didn't exist.

   So we built SecretStash. What started as an internal tool now helps
   10,000+ teams ship faster without compromising security.

   We're just getting started."

Bad Origin Story

✗ "Acme was founded by three Harvard Business School graduates who
   identified a gap in the market for enterprise SaaS solutions.
   After extensive market research and strategic planning, they
   secured $5M in seed funding and began building the platform."
   → No emotion, no problem, sounds like a press release

Mission vs. Vision

Good Mission Statements

✓ "We exist to make security invisible."
  → Clear, specific, memorable

✓ "Help teams do their best work, faster."
  → Outcome-focused, concise

✓ "Give every startup enterprise-grade tools."
  → Specific audience, clear value

Bad Mission Statements

✗ "To be the world's leading provider of innovative solutions"
  → Generic, unmemorable, vague

✗ "Empowering businesses to achieve digital transformation"
  → Buzzword soup

✗ "Making the world a better place through technology"
  → Grandiose, unclear

Writing Meaningful Values

For each value, provide: 1. The value name (2-3 words) 2. What it means in practice (1-2 sentences) 3. How you actually live it (optional example)

Good Values Section

✓ "Default to transparency"
   We share context, not just conclusions. Everyone at the company
   can see our board decks, financials, and strategic plans.

✓ "Ship, then iterate"
   Progress beats perfection. We'd rather ship something good today
   and improve it tomorrow than wait for something perfect.

✓ "Talk to users weekly"
   Everyone — engineers, designers, founders — talks to customers
   at least once a week. It's how we stay grounded.

Bad Values Section

✗ "Innovation"
   We are innovative.
   → No meaning, no evidence

✗ "Excellence"
   We strive for excellence in everything we do.
   → Generic, could be any company

✗ "Integrity"
   We operate with the highest integrity.
   → Baseline expectation, not differentiating

Team Section Best Practices

Good Team Bios

✓ "Sarah Chen, CEO"
   Sarah spent 10 years building infrastructure at Stripe before
   starting Acme. She's obsessed with developer experience and
   terrible at making sourdough.

✓ "Marcus Johnson, Head of Engineering"
   Former Staff Engineer at Notion. Believes the best code is the
   code you delete. Runs ultramarathons for reasons he can't explain.

Bad Team Bios

✗ "John Smith is a visionary leader with 20+ years of experience
   driving strategic initiatives across Fortune 500 companies.
   He holds an MBA from Wharton and a BS in Computer Science
   from MIT. Prior to Acme, John was Senior Vice President of
   Strategic Operations at..."
   → Resume, not personality

✗ "CEO"
   [Just a photo and title, no bio]
   → Missed opportunity to build connection

Traction Section Options

About Page CTAs

About Page Checklist

• [ ] Opening statement is specific to your company
• [ ] Origin story shows the problem you saw
• [ ] Mission is clear and memorable
• [ ] Values are specific and backed by examples
• [ ] Team photos are consistent and approachable
• [ ] Bios show personality, not just credentials
• [ ] Traction/proof section builds credibility
• [ ] CTA aligned with page goals (careers/product)
• [ ] Page serves both customers and candidates

Anti-Patterns

• "We" overload — About pages can use "we," but balance with "you"
• Corporate speak — "Synergize solutions" isn't human
• Resume culture — People connect with stories, not credentials
• Missing humanity — Show the people, not just the product
• Generic values — "Innovation, Excellence, Integrity" = nothing
• Stock team photos — Use real photos of real people
• No origin story — Every company has a "why"
• Purely promotional — It's an about page, not a sales page
• Outdated info — Wrong team members, old funding rounds

Comparison and Alternative Pages

Impact: HIGH

Comparison pages capture high-intent "vs" and "alternative" searches. These visitors are actively evaluating options. Win them with honesty, clarity, and confidence.

Types of Comparison Pages

Comparison Page Structure

┌────────────────────────────────────────────────────┐
│ 1. HEADLINE                                        │
│    "[You] vs [Competitor]" or                      │
│    "Looking for a [Competitor] alternative?"       │
├────────────────────────────────────────────────────┤
│ 2. TL;DR SUMMARY                                   │
│    2-3 sentence positioning of key differences     │
├────────────────────────────────────────────────────┤
│ 3. COMPARISON TABLE                                │
│    Feature-by-feature breakdown                    │
│    Fair representation of both                     │
├────────────────────────────────────────────────────┤
│ 4. YOUR ADVANTAGES                                 │
│    3-5 areas where you genuinely win               │
│    With supporting detail                          │
├────────────────────────────────────────────────────┤
│ 5. WHEN TO CHOOSE [COMPETITOR]                     │
│    Honest acknowledgment of their strengths        │
│    (Builds trust)                                  │
├────────────────────────────────────────────────────┤
│ 6. SWITCHING STORY                                 │
│    Customer who switched + their experience        │
├────────────────────────────────────────────────────┤
│ 7. MIGRATION SUPPORT                               │
│    How easy it is to switch                        │
│    Import tools, migration help                    │
├────────────────────────────────────────────────────┤
│ 8. CTA                                             │
│    "Try free" or "See how to switch"               │
└────────────────────────────────────────────────────┘

Headline Formulas

Good Comparison Headlines

✓ "Acme vs Notion: A detailed comparison"
  → Clear, SEO-friendly, balanced

✓ "The Notion alternative built for speed"
  → Differentiator in headline

✓ "Thinking about switching from Asana?"
  → Speaks to visitor intent

✓ "Acme vs Jira: Which project tool fits your team?"
  → Helpful framing, not adversarial

Bad Comparison Headlines

✗ "Why Acme is better than Notion"
  → Sounds biased, reduces trust

✗ "Acme destroys the competition"
  → Aggressive, unprofessional

✗ "Competitor Comparison"
  → Generic, no SEO value

✗ "The truth about Notion"
  → Sounds like attack marketing

TL;DR Summary Approach

Provide an honest, scannable summary:

✓ Good TL;DR:
   "Acme and Notion both help teams organize work. The key differences:
   Acme is faster and built for developers. Notion offers more
   flexibility for non-technical teams. If speed and integrations
   matter most, choose Acme. If customization is your priority,
   Notion might be better."

✗ Bad TL;DR:
   "Acme is simply better than Notion in every way. Here's why you
   should switch immediately."
   → One-sided, loses credibility

Comparison Table Best Practices

Good Comparison Table

✓ Feature                    Acme        Notion
  ───────────────────────────────────────────────
  Real-time collaboration    ✓           ✓
  Unlimited storage          ✓           ✓ (paid)
  API access                 ✓           ✓
  Offline mode               ✓           Limited
  Custom integrations        50+         200+
  Starting price             Free        Free
  Speed/Performance          Very fast   Moderate
  Learning curve             Low         Moderate
  Mobile app                 Native      Native

Bad Comparison Table

✗ Feature                    Acme        Competitor
  ───────────────────────────────────────────────
  Quality                    Excellent   Poor
  Value                      Great       Bad
  Support                    Amazing     Terrible
  Innovation                 10/10       2/10
  → Subjective, biased, lacks specifics

Advantage Sections

Structure each advantage as: 1. Clear benefit headline 2. Why it matters (1-2 sentences) 3. Specific evidence (metric, quote, or example)

✓ "Ship 3x faster with native Git integration"
   Acme syncs directly with your repos. No manual updates, no context
   switching. Every change is tracked automatically.

   "We cut our deploy time from 45 minutes to 12 minutes after
   switching from Notion." — VP Engineering, TechCorp

"When to Choose [Competitor]" Section

This counterintuitive section builds trust:

✓ "When Notion might be better for you:

   • You need a wiki + project management in one tool
   • Your team is primarily non-technical
   • You want maximum customization flexibility
   • You're already deeply embedded in Notion's ecosystem

   We're not the right fit for everyone, and that's okay. If these
   describe you, Notion might serve you better."

Why This Works

Switching Story Format

┌────────────────────────────────────────────────────┐
│ CUSTOMER SWITCHING STORY                           │
│                                                    │
│ "[Company] switched from [Competitor] to [You]"    │
│                                                    │
│ • Why they switched                                │
│ • How the migration went                           │
│ • Results after switching                          │
│ • Quote from champion                              │
└────────────────────────────────────────────────────┘

Good Switching Story

✓ "How Linear's engineering team switched from Jira"

   "We loved Jira's power, but it was slowing us down. Every sprint
   planning took hours. After switching to Acme, we cut planning time
   by 60% and actually started enjoying standups."

   Migration time: 1 week for 50-person team
   Data imported: 100% (projects, issues, history)
   Result: 60% faster sprint planning

   — Marcus Chen, Engineering Manager, Linear

Migration Support Section

Good Migration Copy

✓ "Switching is easier than you think"

   1. Export your data from Notion (we'll show you how)
   2. Import with one click — everything comes over
   3. Invite your team — they'll feel at home immediately

   Average migration time: 47 minutes
   Data loss: None. Ever.

   Need help? Our team has migrated 500+ companies from Notion.
   [Book a free migration call]

Comparison Page CTAs

SEO Considerations

Comparison Page Checklist

• [ ] Headline matches search intent
• [ ] TL;DR gives honest summary
• [ ] Comparison table is fair and specific
• [ ] Advantages are backed by evidence
• [ ] Competitor strengths are acknowledged
• [ ] Switching story from real customer
• [ ] Migration support is clearly explained
• [ ] Page is dated and kept current
• [ ] CTA matches visitor intent
• [ ] SEO elements optimized

Anti-Patterns

• Bashing competitors — Attacking feels desperate and loses trust
• Inflating your wins — Exaggeration backfires when people try the product
• Ignoring their strengths — One-sided comparisons aren't credible
• Outdated information — Using old competitor info is misleading
• Missing migration path — "Switch" without "how" creates friction
• No real customer stories — Generic claims don't convince
• Invisible updates — Date your comparisons, update regularly
• Aggressive tone — Confident beats combative
• Feature-only comparison — Include pricing, support, ecosystem
• No self-disqualification — Help wrong-fit prospects leave

Demo Request and Contact Pages

Impact: CRITICAL

Demo and contact pages are conversion endpoints. Every word either reduces friction or adds it. These pages should make taking action feel easy, valuable, and low-risk.

Types of Conversion Pages

Demo Request Page Structure

┌────────────────────────────────────────────────────┐
│ 1. HEADLINE                                        │
│    Value-focused, not "Request a Demo"             │
│    What they'll get from the call                  │
├────────────────────────────────────────────────────┤
│ 2. VALUE PROPOSITION                               │
│    Why the demo is worth their time                │
│    2-4 bullets on what they'll see/learn           │
├────────────────────────────────────────────────────┤
│ 3. FORM                                            │
│    Essential fields only                           │
│    Clear submit button                             │
├────────────────────────────────────────────────────┤
│ 4. SOCIAL PROOF                                    │
│    Logos or testimonial                            │
│    "Join 1,000+ companies"                         │
├────────────────────────────────────────────────────┤
│ 5. FAQ / OBJECTION HANDLING                        │
│    "What happens next?"                            │
│    Time commitment, no-pressure                    │
├────────────────────────────────────────────────────┤
│ 6. ALTERNATIVE OPTION                              │
│    "Prefer to explore on your own?"                │
│    Link to self-serve or resources                 │
└────────────────────────────────────────────────────┘

Demo Page Headlines

Good Demo Headlines

✓ "See how Acme can help your team ship faster"
  → Outcome-focused, personalized

✓ "Get a personalized demo in 30 minutes"
  → Clear time commitment

✓ "Let's find the right solution for your team"
  → Consultative, not pushy

✓ "Your questions, answered live"
  → Addresses the value of human interaction

Bad Demo Headlines

✗ "Request a Demo"
  → Zero value proposition

✗ "Contact Us"
  → Generic, cold

✗ "Fill Out This Form to Get Started"
  → Focuses on the task, not the value

✗ "Schedule Your Personalized AI-Powered Demo Experience"
  → Over-engineered, buzzwordy

Value Proposition for Demos

Tell them what they'll get:

✓ "In your 30-minute demo, you'll:"
   • See Acme configured for your use case
   • Get answers to your specific questions
   • Learn about pricing and implementation
   • Receive a custom proposal (if you want one)

✓ "What to expect:"
   • A quick needs assessment (5 min)
   • A personalized walkthrough (20 min)
   • Q&A and next steps (5 min)
   • No pressure, no hard sell

Bad Value Propositions

✗ "Request a demo today!"
   → No information about what they get

✗ "Our team will reach out to discuss your needs"
   → Vague, feels like entering a sales funnel

✗ "Fill out the form to begin your journey with us"
   → Corporate speak, no specifics

Form Field Strategy

Optimal Form Length

Good Form Design

✓ First name [_____________]
   Work email [_____________]
   Company    [_____________]
   Company size [Dropdown: 1-10, 11-50, 51-200, 200+]

   [ Book my demo ]

   We'll respond within 24 hours

Bad Form Design

✗ 15 fields including:
   - Fax number
   - How did you hear about us (required)
   - Describe your challenges in detail (required)
   - Budget range (required)
   - Timeline (required)
   → Too much friction, feels like an interrogation

Submit Button Copy

Good Submit Buttons

✓ "Book my demo"
✓ "Request my personalized demo"
✓ "Talk to our team"
✓ "Get my custom quote"
✓ "Start the conversation"

Social Proof Placement

Good Social Proof

✓ "Join 2,000+ teams who've made the switch"
   [Stripe logo] [Figma logo] [Linear logo]

✓ "★★★★★ 4.9/5 on G2 (500+ reviews)"

✓ "Trusted by teams at companies you know"
   [Logo bar of recognizable brands]

✓ Quote: "The best decision we made this year."
   — VP Engineering, Series B Startup

Objection Handling Section

Address common hesitations:

Good FAQ Section

✓ "What happens after I submit?"
   We'll email you within 24 hours to schedule a time that works.
   If you don't see our email, check spam (and mark us safe!).

✓ "What if I'm just exploring?"
   That's totally fine. Most demos are exploratory.
   No pressure to make any decisions.

✓ "Can I bring my team?"
   Absolutely. Invite anyone who'd find the demo useful.

Alternative Path Section

Always offer an alternative for those not ready:

✓ "Not ready for a call?"
   • Watch a 5-minute product tour
   • Explore our documentation
   • Start a free trial

✓ "Prefer to self-serve?"
   [Start free trial — no credit card required]

Contact Page vs Demo Page

Contact Page Structure

┌────────────────────────────────────────────────────┐
│ 1. HEADLINE                                        │
│    "Let's talk" or "Questions? We're here"         │
├────────────────────────────────────────────────────┤
│ 2. CONTACT OPTIONS                                 │
│    Form + email + phone (if applicable)            │
├────────────────────────────────────────────────────┤
│ 3. SIMPLE FORM                                     │
│    Name, email, message                            │
├────────────────────────────────────────────────────┤
│ 4. RESPONSE EXPECTATION                            │
│    "We typically respond within..."                │
├────────────────────────────────────────────────────┤
│ 5. ALTERNATIVE RESOURCES                           │
│    Help docs, FAQ, community                       │
└────────────────────────────────────────────────────┘

Good Contact Page Copy

✓ "Get in touch"
   Have a question? Want to learn more? Just want to say hi?
   We'd love to hear from you.

   [Simple form: Name, Email, Message]

   We typically respond within 1 business day.

   Looking for support? Visit our help center.
   Want a demo? Book a time with our team.

Post-Submission Experience

Conversion Page Checklist

• [ ] Headline communicates value, not just action
• [ ] Form asks only essential questions
• [ ] Submit button is specific and action-oriented
• [ ] Social proof visible near form
• [ ] Response time expectation set
• [ ] Objections addressed (FAQ or inline)
• [ ] Alternative path for non-ready visitors
• [ ] Mobile-optimized form and CTA
• [ ] Confirmation message/page after submission
• [ ] Follow-up email automated

Anti-Patterns

• "Submit" buttons — Use specific, value-oriented copy
• Too many fields — Every field costs conversions
• No response expectation — People wonder if it worked
• Missing social proof — Trust is crucial at conversion
• Buried form — Above fold, easy to find
• No alternative — Offer options for different readiness
• Generic headline — "Contact Us" is a missed opportunity
• Required phone — Many people won't give phone numbers
• CAPTCHA friction — Use invisible alternatives if possible
• No mobile optimization — Thumb-friendly fields and buttons

Feature Page Copy

Impact: CRITICAL

Feature pages bridge the gap between "this sounds interesting" and "I can see myself using this." They demonstrate capability while selling outcomes.

Feature Page Structure

┌────────────────────────────────────────────────────┐
│ 1. FEATURE HERO                                    │
│    Benefit headline + Capability subhead           │
│    Screenshot/video + CTA                          │
├────────────────────────────────────────────────────┤
│ 2. PROBLEM STATEMENT                               │
│    The pain this feature solves                    │
│    (Optional: "Before [Product]...")               │
├────────────────────────────────────────────────────┤
│ 3. KEY BENEFITS (3-5)                              │
│    Outcome-focused, not feature-focused            │
│    Each with supporting detail                     │
├────────────────────────────────────────────────────┤
│ 4. HOW IT WORKS                                    │
│    Visual walkthrough or steps                     │
│    Screenshots with captions                       │
├────────────────────────────────────────────────────┤
│ 5. DETAILED CAPABILITIES                           │
│    Expandable or tabbed feature list               │
│    Technical details for evaluators                │
├────────────────────────────────────────────────────┤
│ 6. USE CASES                                       │
│    2-3 specific scenarios                          │
│    "Perfect for..." format                         │
├────────────────────────────────────────────────────┤
│ 7. SOCIAL PROOF                                    │
│    Testimonial specific to this feature            │
│    Metric if available                             │
├────────────────────────────────────────────────────┤
│ 8. RELATED FEATURES                                │
│    Cross-link to complementary features            │
├────────────────────────────────────────────────────┤
│ 9. CTA SECTION                                     │
│    "Try [Feature]" or "See [Feature] in action"    │
└────────────────────────────────────────────────────┘

The Benefit-First Principle

Always lead with the outcome, then explain the mechanism:

Feature Headline Formulas

Good Feature Headlines

✓ "Reporting that writes itself"
  → Outcome-focused, implies ease

✓ "Real-time collaboration without the chaos"
  → Benefit + addresses concern

✓ "Find any file in milliseconds"
  → Specific, measurable outcome

✓ "Integrations that just work"
  → Addresses integration pain

✓ "Automated workflows: Set it and forget it"
  → Feature name + benefit summary

Bad Feature Headlines

✗ "Reporting"
  → Zero value proposition

✗ "Advanced Analytics Dashboard v2.0"
  → Technical naming, no benefit

✗ "Powerful Collaboration Tools"
  → Generic, could be any product

✗ "Our Best Feature Yet"
  → Self-congratulatory, no information

✗ "Next-Gen Automation Engine"
  → Buzzwords without substance

Writing Benefit Statements

Transform features into benefits using this structure:

Good Benefit Sections

✓ "Get answers in seconds, not hours"
   Your team stops waiting. With instant search across all your documents,
   the information you need is always one query away.

✓ "Never lose a conversation again"
   Every message, every thread, every decision — automatically saved and
   searchable. No more "Can you resend that?"

✓ "Scale without scaling your team"
   Automation handles the repetitive work. Handle 10x the volume with
   the same headcount.

Bad Benefit Sections

✗ "Powerful Search Capabilities"
   Our search feature uses advanced algorithms to find your content.
   → Technical focus, no user benefit

✗ "Industry-Leading Technology"
   We've invested millions in our cutting-edge infrastructure.
   → About you, not about them

✗ "Robust and Scalable"
   Built on enterprise-grade architecture for maximum performance.
   → Jargon without meaning

Capability vs. Benefit Matrix

How It Works Section

Use 3-5 steps maximum. Each step should be:

• Titled with an action verb
• Described in one sentence
• Accompanied by a visual

✓ Good "How It Works":

1. Connect your tools
   Link your existing apps in one click. We support 50+ integrations.
   [Screenshot of integration setup]

2. Set your rules
   Define what triggers automation and what happens next.
   [Screenshot of rule builder]

3. Watch it work
   Sit back as repetitive tasks handle themselves.
   [Screenshot of automation running]

✗ Bad "How It Works":

1. First, create an account and verify your email
2. Then navigate to settings and configure your preferences
3. Next, set up your first project by clicking the + button
4. After that, invite your team members
5. Now you can start using the platform
6. Don't forget to check out our documentation
   → Too many steps, too much detail, no visuals

Use Case Formatting

✓ "Perfect for product teams who..."
   • Need to track feature requests across channels
   • Want to prioritize based on customer impact
   • Hate switching between tools

✓ "Built for engineering teams that..."
   • Deploy multiple times per day
   • Need visibility into what's shipping
   • Want to catch issues before users do

Feature Page CTAs

Social Proof for Feature Pages

Feature Page Checklist

• [ ] Headline leads with benefit, not feature name
• [ ] Subheadline explains the "how" or adds specificity
• [ ] Hero visual shows the feature in action
• [ ] 3-5 key benefits with supporting detail
• [ ] "How it works" in 3-5 clear steps
• [ ] At least one testimonial or proof point
• [ ] CTA specific to this feature
• [ ] Cross-links to related features
• [ ] Mobile-optimized visuals and layout

Anti-Patterns

• Listing features without benefits — "We have X" vs "You get Y"
• Technical jargon — Write for users, not engineers
• Generic screenshots — Show the feature in realistic use
• Missing "so what" — Every capability needs an outcome
• Wall of text — Scannable beats readable
• No proof points — Claims need evidence
• Weak CTA — "Learn more" is not a feature CTA
• Feature isolation — Show how it connects to other features

Homepage Messaging Hierarchy

Impact: CRITICAL

Your homepage has 3-5 seconds to answer: "What is this, and is it for me?" The messaging hierarchy determines whether visitors explore or bounce.

The Hero Section Formula

Homepage Section Order

┌────────────────────────────────────────────────────┐
│ 1. HERO                                            │
│    Headline + Subhead + CTA + Social Proof         │
│    (Answer: What is this?)                         │
├────────────────────────────────────────────────────┤
│ 2. LOGO BAR                                        │
│    5-8 customer logos                              │
│    (Answer: Who else uses this?)                   │
├────────────────────────────────────────────────────┤
│ 3. PROBLEM/SOLUTION                                │
│    Pain point → Your approach                      │
│    (Answer: Do they understand my problem?)        │
├────────────────────────────────────────────────────┤
│ 4. KEY FEATURES                                    │
│    3-4 primary capabilities with benefits          │
│    (Answer: What can I do with this?)              │
├────────────────────────────────────────────────────┤
│ 5. HOW IT WORKS                                    │
│    3-step process or visual demo                   │
│    (Answer: Is this easy to use?)                  │
├────────────────────────────────────────────────────┤
│ 6. SOCIAL PROOF DEEP                               │
│    Testimonials, case studies, metrics             │
│    (Answer: Does this actually work?)              │
├────────────────────────────────────────────────────┤
│ 7. SECONDARY FEATURES                              │
│    Additional capabilities, integrations           │
│    (Answer: What else can it do?)                  │
├────────────────────────────────────────────────────┤
│ 8. FINAL CTA                                       │
│    Repeated hero CTA with urgency/incentive        │
│    (Answer: What should I do now?)                 │
└────────────────────────────────────────────────────┘

Headline Formulas That Work

Good Homepage Headlines

✓ "Ship code without breaking things"
  → Clear outcome, implies audience (developers)

✓ "Customer support that scales with you"
  → Benefit + addresses growth concern

✓ "Turn customer feedback into product roadmap"
  → Input → Output transformation

✓ "The analytics platform built for product teams"
  → Category + specific audience

✓ "Contracts signed in minutes, not weeks"
  → Before/after with specificity

Bad Homepage Headlines

✗ "Welcome to Acme Inc."
  → Zero information about what you do

✗ "Next-Generation Enterprise Solutions"
  → Meaningless buzzwords

✗ "We're changing the way teams work"
  → Vague, self-focused

✗ "The Future of [Industry]"
  → Grandiose, unsubstantiated

✗ "Powerful. Simple. Fast."
  → Adjectives without context

Subheadline Best Practices

The subheadline expands on the headline with specificity:

Good Subheadlines

Headline: "Ship code without breaking things"
✓ Subhead: "Automated testing that catches bugs before your customers do.
   Set up in 5 minutes, integrates with your CI/CD pipeline."
   → Explains how, adds speed + ease proof

Headline: "Customer support that scales with you"
✓ Subhead: "AI-powered ticketing that resolves 40% of requests automatically
   while keeping your human touch."
   → Mechanism + specific metric + addresses concern

Bad Subheadlines

✗ "We're on a mission to help teams succeed"
  → Vague, doesn't expand on headline

✗ "Learn more about our innovative platform"
  → Says nothing, wastes prime real estate

✗ "Trusted by thousands of companies worldwide"
  → Better as social proof, not subhead

CTA Hierarchy

Good CTA Combinations

✓ Primary: "Start free trial"
  Secondary: "See it in action"
  → Clear path for ready + curious visitors

✓ Primary: "Get started free"
  Secondary: "Talk to sales"
  → Self-serve + enterprise paths

✓ Primary: "Book a demo"
  Secondary: "Watch 2-min overview"
  → Qualified path + quick preview

Bad CTA Combinations

✗ Primary: "Learn more"
  Secondary: "Contact us"
  → Both vague, no clear hierarchy

✗ Primary: "Start trial"
  Secondary: "Start trial"
  → No alternative path

✗ Three equal CTAs
  → Choice paralysis, no clear direction

Social Proof Placement

Above-the-Fold Checklist

• [ ] Headline answers "What is this?"
• [ ] Subheadline explains the "how" or "why"
• [ ] Primary CTA is specific and action-oriented
• [ ] Secondary CTA offers alternative path
• [ ] Social proof element visible (logos or stat)
• [ ] No competing navigation distractions
• [ ] Mobile: CTA visible without scrolling

Homepage Metrics to Track

Anti-Patterns

• "We" focus — Homepage is about the visitor, not you
• Feature list as hero — Lead with outcomes, not capabilities
• Jargon in headlines — "AI-powered synergistic solutions" means nothing
• No clear CTA — Every homepage needs one primary action
• Competing messages — One value prop, not five
• Buried differentiation — If you're different, say it above the fold
• Missing social proof — Claims without credibility
• Navigation overload — Too many choices = no choice

Integration Pages

Impact: MEDIUM-HIGH

Integration pages capture high-intent searches like "[Your Product] + [Tool]" and prove your product fits their existing workflow. They're SEO goldmines and trust builders.

Integration Page Types

Integration Hub Structure

┌────────────────────────────────────────────────────┐
│ 1. HERO                                            │
│    "Connect [Product] to your favorite tools"      │
│    Number of integrations + search bar             │
├────────────────────────────────────────────────────┤
│ 2. FEATURED INTEGRATIONS                           │
│    Most popular or requested (6-12)                │
│    Logos with quick descriptions                   │
├────────────────────────────────────────────────────┤
│ 3. CATEGORY SECTIONS                               │
│    Grouped by use case or tool type                │
│    Expandable or filterable list                   │
├────────────────────────────────────────────────────┤
│ 4. API/BUILD YOUR OWN                              │
│    Developer resources for custom integrations     │
├────────────────────────────────────────────────────┤
│ 5. REQUEST INTEGRATION                             │
│    Form or link to request new integrations        │
├────────────────────────────────────────────────────┤
│ 6. CTA                                             │
│    "Start free and connect your tools"             │
└────────────────────────────────────────────────────┘

Single Integration Page Structure

┌────────────────────────────────────────────────────┐
│ 1. HERO                                            │
│    "[Product] + [Tool]" with both logos            │
│    One-line value prop                             │
├────────────────────────────────────────────────────┤
│ 2. KEY BENEFITS                                    │
│    What this integration enables (3-5)             │
│    Specific to this combination                    │
├────────────────────────────────────────────────────┤
│ 3. HOW IT WORKS                                    │
│    Setup process (usually 3 steps)                 │
│    What syncs, triggers, actions                   │
├────────────────────────────────────────────────────┤
│ 4. USE CASES                                       │
│    2-3 specific scenarios                          │
│    "Perfect for teams who..."                      │
├────────────────────────────────────────────────────┤
│ 5. TECHNICAL DETAILS                               │
│    Data sync, permissions, security                │
│    For evaluators doing due diligence              │
├────────────────────────────────────────────────────┤
│ 6. TESTIMONIAL                                     │
│    Customer using this specific integration        │
├────────────────────────────────────────────────────┤
│ 7. RELATED INTEGRATIONS                            │
│    Other tools in same category                    │
├────────────────────────────────────────────────────┤
│ 8. CTA                                             │
│    "Connect [Tool] now" or "Start free trial"      │
└────────────────────────────────────────────────────┘

Integration Page Headlines

Good Integration Headlines

✓ "Acme + GitHub: Code changes, automatically tracked"
  → Both products + specific value

✓ "Bring Acme into Slack"
  → Action-oriented, tool-first

✓ "Sync your CRM with Acme"
  → Category approach for hub pages

✓ "Two-way sync with Salesforce"
  → Technical specificity

Bad Integration Headlines

✗ "Integration"
  → Zero information

✗ "Our Slack Solution"
  → Vague, generic

✗ "Powerful Third-Party Connectivity"
  → Jargon, no specificity

✗ "Integrations Page"
  → Wasted headline opportunity

Writing Integration Benefits

Focus on what becomes possible, not what's connected:

Good Integration Benefits

✓ "Acme + Slack"

   • Get notified instantly
     New comments, assignments, and updates appear in your Slack
     channels automatically.

   • Reply without leaving Slack
     Respond to comments, update statuses, and assign tasks
     directly from Slack.

   • Keep everyone in the loop
     Weekly digests and real-time alerts keep your team aligned.

Bad Integration Benefits

✗ "Acme + Slack"

   • Slack integration
   • Real-time notifications
   • Data synchronization
   • Bi-directional communication
   → Feature list without user value

How It Works Section

Keep it to 3 steps maximum:

✓ "How to connect Acme and Slack"

   1. Click "Connect to Slack" in your Acme settings
      Authorize Acme to access your Slack workspace.

   2. Choose your channels
      Select which Slack channels receive Acme updates.

   3. You're connected
      Updates flow automatically. Customize in settings anytime.

   Setup time: Under 2 minutes
   Permissions required: Read/write to selected channels

Technical Details Section

Good Technical Details

✓ "Technical Details"

   Sync type: Real-time, bi-directional
   Data synced: Projects, tasks, comments, attachments
   Permissions: Read/write access to selected channels
   Security: OAuth 2.0, data encrypted in transit
   Rate limits: 10,000 API calls per hour
   Requirements: Slack Business plan or higher

Use Cases for Integration Pages

✓ "Perfect for teams who..."

   • Track GitHub issues alongside product tasks
   • Want developers notified without leaving their IDE
   • Need deployment events linked to project milestones

✓ "Common workflows"

   • When a PR is merged → Task marked complete
   • When a bug is filed → Slack alert + task created
   • When a release ships → Stakeholders notified

Integration Page CTAs

Good Integration CTAs

✓ "Already have an Acme account?"
   [Connect Slack now]

✓ "New to Acme?"
   [Start free trial — connect Slack in minutes]

✓ For enterprise integrations:
   [Contact sales for Salesforce Enterprise setup]

Category Organization

Integration Hub Categories

✓ "DevOps & Engineering"
   Connect your development workflow

   GitHub • GitLab • Bitbucket • Jenkins • CircleCI
   [See all DevOps integrations →]

✓ "Communication"
   Stay informed where you work

   Slack • Microsoft Teams • Discord • Email
   [See all communication integrations →]

SEO Optimization

Integration Page Checklist

• [ ] Headline uses both product names
• [ ] Logos for both products displayed
• [ ] Benefits are integration-specific, not generic
• [ ] Setup steps are clear and numbered
• [ ] Technical details for evaluators
• [ ] Testimonial from user of this integration
• [ ] Related integrations cross-linked
• [ ] CTA matches user's likely account status
• [ ] SEO elements optimized
• [ ] Page stays updated when integration changes

Anti-Patterns

• Generic benefits — "Sync your data" means nothing
• Missing logos — Visual recognition matters
• No setup info — How hard is it to connect?
• Technical-only — Balance tech details with user value
• Outdated pages — Old screenshots, deprecated features
• No use cases — Show what becomes possible
• Isolated pages — Cross-link related integrations
• Missing requirements — What plan/version is needed?
• No testimonials — Integration-specific proof helps
• Buried in navigation — Make integrations easy to find

Navigation and Microcopy

Impact: MEDIUM

Microcopy is the small text that guides users through your site — navigation labels, button text, form hints, error messages, and empty states. It's invisible when done well and frustrating when done poorly.

Types of Microcopy

Navigation Label Principles

Good Navigation Labels

✓ Main navigation:
   Product | Pricing | Customers | Resources | Company

✓ Footer navigation:
   Product: Features, Integrations, Security, Changelog
   Company: About, Careers, Press, Contact
   Resources: Blog, Help Center, API Docs, Status

✓ Dropdown menu:
   Resources
   ├── Blog
   ├── Help Center
   ├── API Documentation
   ├── Community
   └── What's New

Bad Navigation Labels

✗ "Discover" (discover what?)
✗ "Solutions" without context (too vague)
✗ "Hub" (hub of what?)
✗ "Explore Our Offerings" (too wordy)
✗ "Innovation Center" (corporate speak)
✗ "Start Your Journey" (for a nav item)

Navigation Structure Patterns

Good Navigation Hierarchies

✓ Simple SaaS:
   [Logo] Product • Pricing • Docs • Blog     [Login] [Sign Up]

✓ Platform company:
   [Logo] Products ▾ • Solutions ▾ • Resources ▾ • Pricing     [Login] [Get Started]

✓ Enterprise:
   [Logo] Platform • Solutions • Customers • Resources • Company     [Contact Sales]

Button Copy Principles

Button Copy by Action

Good Button Copy

✓ Primary actions:
   "Start free trial"
   "Get started — it's free"
   "Create your account"
   "Book a demo"

✓ Secondary actions:
   "See how it works"
   "View pricing"
   "Read the docs"
   "Talk to sales"

✓ Form submissions:
   "Send message"
   "Subscribe"
   "Save changes"
   "Apply filters"

Bad Button Copy

✗ "Submit" (submit what?)
✗ "Click here" (obvious)
✗ "Go" (go where?)
✗ "Yes" / "No" (for complex actions)
✗ "Process" (what happens?)
✗ "Continue" (without context)

Form Microcopy

Good Form Microcopy

✓ Email
   [you@company.com________________]
   We'll use this to send your login details

✓ Password
   [••••••••••••••________________]
   At least 8 characters with one number

✓ Error:
   ⚠ "Please enter a valid email address"

✓ Success:
   ✓ "Your account has been created. Check your email to verify."

Bad Form Microcopy

✗ EMAIL: (all caps, unfriendly)
✗ [Enter email here] (redundant placeholder)
✗ Error: "Invalid input" (unhelpful)
✗ "Error 422: Validation failed" (technical)
✗ No hint text at all (leaves users guessing)

Error Message Formula

What went wrong + How to fix it

✓ "That email is already registered. Try logging in instead."
✓ "Password must be at least 8 characters."
✓ "We couldn't process your payment. Please check your card details."

✗ "Error"
✗ "Invalid"
✗ "Something went wrong"
✗ "Please try again"

Empty State Microcopy

Good Empty States

✓ First project:
   "No projects yet"
   Projects help you organize your work. Create your first one
   to get started.
   [Create project]

✓ No search results:
   "No results for 'xyz'"
   Try adjusting your search or browse all items.
   [Clear search] [Browse all]

✓ Empty dashboard:
   "Nothing here yet"
   Once your team starts using Acme, you'll see activity here.
   [Invite your team]

Bad Empty States

✗ "No data"
   → Unhelpful, no guidance

✗ "0 results found"
   → Technical, no next step

✗ [Blank space with no message]
   → Confusing, broken-feeling

Tooltip Microcopy

Good Tooltips

✓ [?] "Daily active users who completed at least one action"
✓ [?] "Press ⌘K to open quick search"
✓ [?] "This setting affects all team members"

Bad Tooltips

✗ [?] "Click this button" (obvious)
✗ [?] "This is the save button" (obvious)
✗ [?] A full paragraph of explanation (too long)

Confirmation Messages

Good Confirmation Messages

✓ "Changes saved"
   Brief, appears near the action

✓ "Message sent! We'll respond within 1 business day"
   Confirms action + sets expectation

✓ "Project deleted" [Undo]
   Acknowledges + offers recovery

✓ "Welcome to Acme! Check your email to get started"
   Confirms + provides next step

Loading State Microcopy

Good Loading Messages

✓ "Generating your report..."
✓ "Syncing your data... this usually takes about 30 seconds"
✓ "Almost there..."
✓ [Progress bar] "Processing 47 of 100 items"

Microcopy Voice Guidelines

Microcopy Checklist

• [ ] Navigation labels are clear nouns
• [ ] Buttons lead with verbs
• [ ] Form labels are specific
• [ ] Error messages explain how to fix
• [ ] Empty states guide users forward
• [ ] Success messages confirm and suggest next step
• [ ] Loading states set expectations
• [ ] Tooltips add value, not obvious info
• [ ] Consistent voice across all touchpoints
• [ ] Mobile-appropriate length

Anti-Patterns

• "Click here" — The action should be in the link text
• "Submit" — Always specify what's being submitted
• Technical error codes — Users don't need error 500 details
• Blaming language — "You entered an invalid email"
• Missing empty states — Blank areas feel broken
• Long loading without explanation — Users think it's frozen
• Clever over clear — Puns and jokes that confuse
• Inconsistent terminology — "Sign up" vs "Register" vs "Create account"
• All caps labels — FEELS LIKE SHOUTING
• No recovery options — Delete without undo feels dangerous

Pricing Page Copy

Impact: CRITICAL

The pricing page is where intent becomes decision. Copy here must reduce anxiety, clarify value, and make the right choice obvious. This is one of your highest-converting pages.

Pricing Page Structure

┌────────────────────────────────────────────────────┐
│ 1. HEADLINE + SUBHEAD                              │
│    Value-framing, not "Pricing"                    │
│    Set expectations for what they'll see           │
├────────────────────────────────────────────────────┤
│ 2. PRICING TIERS                                   │
│    2-4 tiers with clear differentiation            │
│    Recommended tier highlighted                    │
├────────────────────────────────────────────────────┤
│ 3. FEATURE COMPARISON TABLE                        │
│    What's included in each tier                    │
│    (Expandable for detailed view)                  │
├────────────────────────────────────────────────────┤
│ 4. FAQ SECTION                                     │
│    Common pricing questions                        │
│    Objection handling                              │
├────────────────────────────────────────────────────┤
│ 5. SOCIAL PROOF                                    │
│    Testimonials about value/ROI                    │
│    Customer logos                                  │
├────────────────────────────────────────────────────┤
│ 6. CONTACT/ENTERPRISE CTA                          │
│    "Questions? Talk to us"                         │
│    Enterprise inquiry option                       │
└────────────────────────────────────────────────────┘

Pricing Page Headlines

Good Pricing Headlines

✓ "Plans that scale with you"
  → Addresses growth concern

✓ "Simple pricing. Powerful features."
  → Sets expectation of clarity + value

✓ "Start free, upgrade when you're ready"
  → Low-commitment framing

✓ "The right plan for every team"
  → Inclusive, reduces "not for me" concern

Bad Pricing Headlines

✗ "Pricing"
  → Missed opportunity for value framing

✗ "Our Premium Pricing Packages"
  → "Premium" sounds expensive

✗ "Investment Options for Your Business"
  → Corporate speak, feels salesy

✗ "World-Class Pricing for World-Class Results"
  → Empty hyperbole

Tier Naming Strategy

Good Tier Names

✓ "Free" → "Pro" → "Team" → "Enterprise"
  → Clear progression, familiar naming

✓ "Starter" → "Growth" → "Scale"
  → Journey-based, implies progression

✓ "Developer" → "Team" → "Organization"
  → Audience clarity

Bad Tier Names

✗ "Bronze" → "Silver" → "Gold" → "Platinum"
  → Feels like credit cards, dated

✗ "Good" → "Better" → "Best"
  → Implies lower tiers are inadequate

✗ "Basic" → "Standard" → "Advanced" → "Premium" → "Ultimate"
  → Too many tiers, unclear differentiation

Tier Description Copy

Each tier needs: 1. Tier name 2. Price (and billing period) 3. One-line description (who this is for) 4. Key features (3-5 differentiating features) 5. CTA button

Good Tier Descriptions

✓ "Pro — $29/month"
   For growing teams that need more power.
   • Unlimited projects
   • Advanced analytics
   • Priority support
   • API access
   [Start 14-day free trial]

✓ "Team — $15/user/month"
   Everything you need to collaborate at scale.
   • Shared workspaces
   • Team permissions
   • SSO included
   • 99.9% uptime SLA
   [Get started free]

Bad Tier Descriptions

✗ "Premium Plan — $99/month"
   Our best plan with all the features.
   • Feature 1
   • Feature 2
   • Feature 3
   • Feature 4
   • Feature 5
   • Feature 6
   • Feature 7
   [Buy Now]
   → No audience targeting, feature dump, no differentiation

✗ "Enterprise"
   Contact us for pricing.
   → No information, no features, creates friction

Highlighting the Recommended Tier

Writing Feature Comparisons

Good Feature Table Section

✓ "Collaboration"
   └─ Shared workspaces    ✓ ✓ ✓
   └─ Team members         5  25 Unlimited
   └─ Guest access         ✗ ✓ ✓
   └─ SSO                  ✗ ✗ ✓

✓ "Support"
   └─ Email support        ✓ ✓ ✓
   └─ Priority support     ✗ ✓ ✓
   └─ Dedicated CSM        ✗ ✗ ✓
   └─ SLA guarantee        ✗ 99.9% 99.99%

Pricing FAQs That Convert

Good FAQ Answers

✓ Q: "Can I change plans later?"
   A: "Absolutely. Upgrade or downgrade anytime from your dashboard.
      If you upgrade, you'll be prorated for the remainder of your
      billing period. If you downgrade, the change takes effect at
      your next billing date."

✓ Q: "What happens when my trial ends?"
   A: "We'll send you a reminder 3 days before. If you don't add a
      payment method, you'll be moved to our free plan automatically.
      Your data stays safe either way."

Bad FAQ Answers

✗ Q: "What's your refund policy?"
   A: "Please refer to our Terms of Service for detailed information
      regarding our refund policy and procedures."
   → Creates friction, feels defensive

✗ Q: "Can I cancel anytime?"
   A: "Yes."
   → Missed opportunity to build trust

Enterprise Tier Copy

Good Enterprise Section

✓ "Enterprise"
   For organizations with advanced security and scale needs.

   Everything in Team, plus:
   • SAML SSO & SCIM
   • SOC 2 Type II compliance
   • 99.99% SLA
   • Dedicated success manager
   • Custom integrations
   • Volume discounts

   [Talk to sales]
   Usually responds within 24 hours

Social Proof for Pricing Pages

Pricing Page CTAs

Friction Reducers

Pricing Page Checklist

• [ ] Headline frames value, not just "Pricing"
• [ ] 2-4 clearly differentiated tiers
• [ ] Recommended tier is visually highlighted
• [ ] Each tier has a clear audience description
• [ ] Feature comparison is scannable
• [ ] FAQ addresses top objections
• [ ] Social proof focused on value/ROI
• [ ] Enterprise option with clear CTA
• [ ] Friction reducers visible (trial, cancel policy)
• [ ] Mobile-optimized tier display

Anti-Patterns

• Hidden pricing — If you hide it, people assume the worst
• Too many tiers — 3-4 is ideal, more creates confusion
• Feature overload — Highlight differences, not everything
• Jargon in features — "SSO" needs explanation for some audiences
• Buried enterprise option — Make it easy to find for large buyers
• No social proof — Pricing pages need trust signals
• Vague enterprise tier — "Contact us" with no features listed
• Missing FAQ — Unanswered questions = lost conversions
• No recommended tier — Help people choose
• Complex pricing math — Per user + per seat + usage = confusion

Product Tour Pages

Impact: HIGH

Product tour pages show your product in action before signup. They reduce the friction of "I need to see it first" and give visitors confidence about what they're getting into.

Product Tour Types

Product Tour Structure

┌────────────────────────────────────────────────────┐
│ 1. INTRO/HOOK                                      │
│    What they'll see + time commitment              │
│    "See how [Product] works in 3 minutes"          │
├────────────────────────────────────────────────────┤
│ 2. KEY WORKFLOW #1                                 │
│    Core job-to-be-done                             │
│    Setup or getting started flow                   │
├────────────────────────────────────────────────────┤
│ 3. KEY WORKFLOW #2                                 │
│    Primary value moment                            │
│    "This is where the magic happens"               │
├────────────────────────────────────────────────────┤
│ 4. KEY WORKFLOW #3                                 │
│    Secondary value or collaboration                │
│    Team features, sharing, results                 │
├────────────────────────────────────────────────────┤
│ 5. OUTCOME                                         │
│    What they've accomplished                       │
│    Results or deliverable                          │
├────────────────────────────────────────────────────┤
│ 6. CTA                                             │
│    "Start free" or "Try it yourself"               │
└────────────────────────────────────────────────────┘

Tour Page Headlines

Good Tour Headlines

✓ "See how teams ship faster with Acme"
  → Outcome-focused, audience clarity

✓ "A 3-minute tour of your new workspace"
  → Time commitment + ownership language

✓ "Watch: From zero to deployed in 5 minutes"
  → Specific outcome, time-based

✓ "Take Acme for a spin"
  → Casual, low-pressure

Bad Tour Headlines

✗ "Product Demo"
  → Generic, no value proposition

✗ "Watch Our Amazing Features"
  → Self-congratulatory

✗ "Welcome to the Acme Experience"
  → Vague, no clear expectation

✗ "Click Here to Learn More"
  → Not a headline, weak CTA

Writing Tour Narration/Copy

Each tour step needs: 1. What they're seeing (orient the viewer) 2. Why it matters (connect to their goal) 3. What to notice (guide attention)

Good Tour Step Copy

✓ Step 1: "Connect your repository"
   "Start by connecting your GitHub repo. One click, and Acme
   automatically syncs with every branch. No config files needed."
   [Screenshot showing GitHub connection UI]

✓ Step 2: "See your first insights"
   "Within seconds, you'll see code quality metrics across your
   entire codebase. Spot issues before they become problems."
   [Screenshot showing dashboard with metrics]

✓ Step 3: "Share with your team"
   "Invite teammates in seconds. Everyone sees the same view,
   comments stay connected to the code."
   [Screenshot showing team invitation flow]

Bad Tour Step Copy

✗ "Step 1: Here is the dashboard"
   → No value, just labeling

✗ "This is our powerful integration engine"
   → About you, not them

✗ "Next, click the blue button"
   → Instructions without value

✗ "As you can see, there are many features here"
   → Vague, unfocused

Screenshot Guidelines

Good Screenshot Practices

✓ Show realistic data
   Project names like "Q4 Marketing Campaign" not "Test Project 1"

✓ Highlight the focus area
   Dim or blur irrelevant parts of the screen

✓ Use callouts sparingly
   One arrow pointing to the key element

✓ Show before/after
   Empty state → filled state progression

✓ Include realistic team members
   "Sarah (Marketing)" not "User 1"

Bad Screenshot Practices

✗ Empty or dummy data
   "Lorem ipsum" or "Test data here"

✗ Cluttered annotations
   10 arrows pointing everywhere

✗ Full screenshot with no focus
   Everything equally visible

✗ Outdated UI
   Screenshots from 3 versions ago

✗ Admin/debug views
   Technical screens normal users won't see

Video Tour Best Practices

Good Video Structure

✓ 0:00-0:15 — Hook: The problem/outcome
   "Tired of losing track of customer requests?"

✓ 0:15-1:00 — Setup: Quick context
   "Let me show you how Acme solves this in 3 steps"

✓ 1:00-3:00 — Core workflow
   Show the primary use case, narrate value

✓ 3:00-3:30 — Results
   "Now you have a complete view of..."

✓ 3:30-4:00 — CTA
   "Start your free trial at acme.com"

Interactive Demo Guidelines

Good Interactive Demo Copy

✓ Tooltip: "Click here to create your first project"
   Hint: In the real product, you can create unlimited projects.

✓ Progress: "Step 2 of 5: Setting up integrations"

✓ Callout: "This is where your team's activity appears"
   Notice how every action is timestamped and attributed.

✓ End screen: "That's the basics! Ready to try the real thing?"
   [Start free trial] [Replay tour]

Tour Completion CTAs

Good Tour CTAs

✓ After video: "Ready to try it yourself?"
   [Start free trial — no credit card required]

✓ After interactive: "That was just a preview"
   [Create your free account and explore everything]

✓ After screenshot tour: "Seeing is believing"
   [Start free] or [Book a personalized demo]

Tour Page Metrics

Tour Page Checklist

• [ ] Headline sets clear expectation (time, content)
• [ ] Tour follows logical workflow
• [ ] Each step has value-focused copy
• [ ] Screenshots/videos use realistic data
• [ ] Focus areas are highlighted
• [ ] Progress indicator shows position
• [ ] Skip/exit options available
• [ ] CTA appears at end and optionally throughout
• [ ] Mobile experience is considered
• [ ] Tour stays updated with product changes

Anti-Patterns

• Feature parade — Tours should follow workflows, not feature lists
• No context — Don't show screens without explaining why they matter
• Stale content — Outdated screenshots erode trust
• Too long — Attention drops after 4-5 minutes
• No clear CTA — Tour should lead somewhere
• Forced completion — Let people skip or exit
• Technical jargon — Tours are for prospects, not power users
• Perfect scenarios — Show realistic use, not idealized demos
• Missing audio/captions — Many watch without sound
• Desktop only — Consider mobile viewers

Use Case and Solution Pages

Impact: MEDIUM-HIGH

Use case pages answer "Is this for me?" by showing your product through the lens of specific personas, industries, or problems. They turn generic features into relevant solutions.

Types of Solution Pages

Solution Page Structure

┌────────────────────────────────────────────────────┐
│ 1. HERO                                            │
│    "[Product] for [Audience/Problem]"              │
│    Segment-specific value prop                     │
├────────────────────────────────────────────────────┤
│ 2. PROBLEM STATEMENT                               │
│    "You know the pain of..."                       │
│    Specific to this audience                       │
├────────────────────────────────────────────────────┤
│ 3. SOLUTION OVERVIEW                               │
│    How your product addresses their needs          │
│    Audience-relevant features highlighted          │
├────────────────────────────────────────────────────┤
│ 4. KEY CAPABILITIES                                │
│    Features framed for this audience               │
│    3-5 most relevant capabilities                  │
├────────────────────────────────────────────────────┤
│ 5. SOCIAL PROOF                                    │
│    Testimonials/cases from similar customers       │
│    Logos from the same segment                     │
├────────────────────────────────────────────────────┤
│ 6. WORKFLOW/USE CASE EXAMPLES                      │
│    "Here's how [Audience] uses [Product]"          │
│    Day-in-the-life scenarios                       │
├────────────────────────────────────────────────────┤
│ 7. COMPARISON TO STATUS QUO                        │
│    Before/after or vs spreadsheets/old way         │
├────────────────────────────────────────────────────┤
│ 8. CTA                                             │
│    Segment-specific call to action                 │
└────────────────────────────────────────────────────┘

Solution Page Headlines

Good Solution Headlines

✓ "Project management built for engineering teams"
  → Clear audience + category positioning

✓ "Ship faster without the chaos"
  → Outcome + pain point addressed

✓ "Enterprise-grade security, startup-speed setup"
  → Addresses enterprise concerns with agility

✓ "Remote teams deserve better tools"
  → Validates the audience + implies solution

Bad Solution Headlines

✗ "Solutions"
  → Says nothing

✗ "Our Enterprise Offering"
  → About you, not them

✗ "Acme for Everyone"
  → Defeats the purpose of segmentation

✗ "The Best Project Management Tool"
  → Generic, undifferentiated

Writing Problem Statements

Speak to the specific pain points of this audience:

Persona-Specific Problems

Industry-Specific Problems

Good Problem Section

✓ "Engineering teams spend 30% of their time on coordination, not code.

   You've tried Jira. You've tried spreadsheets. You've built internal tools.
   But sprint planning still takes hours. Standups still run over. And nobody
   knows what shipped last week without digging through Slack.

   Sound familiar?"

Bad Problem Section

✗ "Companies today face many challenges in the modern business landscape.
   Collaboration is increasingly important, and teams need tools that
   help them work together effectively."
   → Generic, could apply to anyone

Feature Framing by Audience

Same feature, different framing:

Good Capability Sections

✓ "For Engineering Teams"

   Sprint planning in minutes, not hours
   Drag-and-drop planning with automatic capacity calculation.
   Know exactly what fits in each sprint.

   Every code change, tracked
   GitHub integration links commits to tasks automatically.
   See the full context without leaving your workflow.

   Standups that run themselves
   Automated standup prompts and rollups.
   Get updates in Slack, keep everyone moving.

Bad Capability Sections

✗ "Features"
   • Advanced dashboard capabilities
   • Real-time collaboration features
   • Powerful integration engine
   • Enterprise-grade security
   → Generic, not audience-specific

Social Proof Strategy

Good Social Proof

✓ "Engineering teams at Stripe, Figma, and Linear use Acme to ship faster"

   "We cut our sprint planning time by 60% and actually enjoy standups now."
   — Marcus Chen, VP Engineering, Linear

✓ "Trusted by 500+ healthcare organizations"
   [Logos: Cleveland Clinic, Kaiser, One Medical]
   HIPAA compliant • SOC 2 Type II • BAA available

Use Case Example Format

✓ "A day in the life with Acme"

   8:30 AM — Morning standup
   Your team's updates are already collected. Just review and go.

   10:00 AM — Sprint planning
   Drag tasks, see capacity, assign work. Done in 15 minutes.

   2:00 PM — Code review
   PR merged, task auto-updated, Slack notified. No manual steps.

   5:00 PM — End of day
   Your dashboard shows what shipped. Ready for tomorrow's standup.

Before/After Comparisons

Good Before/After

✓ Before Acme:
   • Sprint planning takes 3+ hours
   • Status updates buried in Slack
   • Nobody knows what shipped

   After Acme:
   • Planning done in 30 minutes
   • Updates automatic and visible
   • Real-time shipping dashboard

Segment-Specific CTAs

Solution Page Checklist

• [ ] Headline speaks directly to the audience
• [ ] Problem statement is audience-specific
• [ ] Features are framed for this audience
• [ ] Social proof from similar customers
• [ ] Use cases relevant to their workflow
• [ ] Before/after shows clear improvement
• [ ] CTA matches audience expectations
• [ ] Cross-links to relevant case studies
• [ ] Page can stand alone (visitors may land here first)

SEO Optimization

Anti-Patterns

• Copy-paste pages — Each solution page must be genuinely different
• Generic features — Frame everything for the specific audience
• Wrong social proof — Enterprise logos on startup page fails
• No problem validation — Show you understand their pain
• One-size-fits-all CTAs — Enterprises want to "talk to sales"
• Missing specificity — "Marketing teams" is too broad
• Ignoring objections — Address segment-specific concerns
• No workflow examples — Show the product in their context
• Jargon mismatch — Use their vocabulary, not yours
• Orphaned pages — Link from navigation and other pages