Workflow · Content Production ~30 min run Web search · Optional GSC

Build "[Competitor] alternative" pages
that convert at 8-15%.

A copy-paste Claude prompt that researches a competitor, identifies switching triggers from review data, and outputs a complete production-ready alternatives page brief — H1 to FAQ, comparison table to schema. Skip the 6-10 hours of strategy and competitor research. Hand the brief to your writer and ship the page in two weeks.

8-15%
Conversion vs 2-4% homepage
8sections
Complete page anatomy
5-7triggers
Pulled from review data
30min
Brief production time
01 The Problem in 60 Seconds

"[Competitor] alternative" is the
cleanest buyer intent in B2B SaaS.

Someone searching "[Competitor] alternative" has already decided their current option is wrong. They're not in awareness mode, they're not browsing — they're shopping for a replacement. The conversion math reflects this: a generic homepage converts that traffic at 2-4%, a well-built alternatives page converts it at 8-15%. Same traffic, 3-4x the pipeline. Most B2B SaaS brands either don't have alternatives pages at all or have one weak page that targets multiple competitors with generic positioning.

The page itself isn't complicated — but the strategy and research underneath it usually is. A senior content lead typically spends 6-10 hours per page reading competitor reviews, identifying switching triggers, sourcing customer quotes, mapping comparison features, building FAQ from real search queries, and structuring schema for AI citation. Then a writer takes the brief and writes copy. Then dev builds the page.

This workflow compresses the 6-10 hour research and strategy step to 30 minutes. Claude pulls switching triggers from G2/Capterra reviews and Reddit threads, structures the page anatomy, drafts FAQ questions matching real buyer queries, and outputs a production-ready brief. Your team writes the copy and ships the page — instead of also doing the research.

The 8-Section Page Anatomy Conversion-tested structure
01 Hero with switching-trigger headlineLead with the buyer's pain — why they're looking to switch 5-sec test
02 "Why teams switch from [Competitor]" section3-5 specific triggers, each tied to a buyer pain point Validate intent
03 Feature comparison table8-12 rows of factual feature-by-feature comparison AI citation magnet
04 "What you get instead" — your differentiators3-5 unique strengths, each addressing a [Competitor] weakness Position your win
05 Customer switch story1-2 case studies from companies that switched from [Competitor] Social proof
06 FAQ with 6-8 questions matching real search queriesPricing, migration, support, key feature questions FAQ schema
07 Migration commitmentConcrete switching support — migration help, parallel pricing, dedicated CSM Reduce friction
08 Single CTA to migration assessmentNot "book a demo" — "see your migration plan" or "calculate switching cost" Convert
02 The Prompt

Copy this prompt into
Claude Desktop.

The gold variables — your brand, your competitor, the category — are the parts you edit. Pick a competitor where you've already won deals so you have win-back data to validate the brief against.

claude_desktop — alternatives_page_brief.md
RoleYou are a senior B2B SaaS content strategist building a "[Competitor] alternative" page brief for my brand. The output is a production-ready brief — H1 to FAQ schema — that my writer can turn into copy in 4-6 hours. The brief targets the buyer who has already decided to switch from [Competitor] and is shopping for a replacement. My BrandBrand: [your B2B SaaS brand name] Category: [e.g. customer onboarding, devops monitoring, revenue intelligence] ICP: [e.g. mid-market B2B SaaS, 50-500 employees, US/EU] Top 3 differentiators: [your three strongest unique strengths vs the category] Target CompetitorCompetitor: [competitor name] Competitor URL: [their homepage] Why we usually win: [brief — pricing, missing feature, support, etc. — pull from win-back deals if available] Task1. Run web_search on the following queries to gather competitor intelligence: - "[Competitor name] reviews" - "[Competitor name] G2" - "[Competitor name] complaints" - "[Competitor name] alternative reddit" - "[Competitor name] pricing complaints" - "[Competitor name] vs" - "[Competitor name] cancel" 2. Identify 5-7 switching triggers — specific complaints that appear in 3+ independent sources (G2 reviews, Reddit, Capterra, Twitter). Generic complaints don't count. Each trigger should be: - Specific enough to quote ("pricing escalates 40% on renewal" not "pricing concerns") - Tied to a buyer pain point your product addresses - Verifiable from at least 3 independent sources 3. Build the page brief in the structure below. Output: Page Brief// Brief should be production-ready — writer needs to add copy, not strategy. PAGE METADATA - URL slug: /alternatives/[competitor-name] - Title tag (60 char max): "[Brand]: The [Competitor] Alternative for [ICP]" - Meta description (160 char max): pain-led, addresses why they're searching - Target query: "[competitor] alternative" - Secondary queries: 4-6 long-tail variants SECTION 01 · HERO - H1 (lead with switching trigger, not "Better than [Competitor]"): draft 3 H1 options - Subhead: address the specific pain in 1 sentence - Hero CTA: NOT "book a demo" — use "see your migration plan" or "calculate switching cost" - Hero visual recommendation SECTION 02 · WHY TEAMS SWITCH - 3-5 switching triggers, each as a short H3 - For each trigger: 1-sentence problem statement, 1-sentence "what we do instead" - Quote 1-2 verbatim review snippets (under 15 words each, with attribution) SECTION 03 · FEATURE COMPARISON TABLE - 8-12 rows comparing [Competitor] vs [Your Brand] - First row: pricing model (most-searched comparison signal) - Rows should reflect the actual 5-7 switching triggers identified - Use "Yes / No / Limited" rather than checkmarks for AI parseability - Include direct factual comparison only — no marketing language SECTION 04 · WHAT YOU GET INSTEAD - 3-5 differentiator blocks tied to the top 3 differentiators in inputs - Each block: feature name (H3), 2-sentence value prop, micro-screenshot or icon recommendation SECTION 05 · CUSTOMER SWITCH STORIES - 1-2 case study slot recommendations - Ideal customer profile: who they switched from, why, what changed - If the brand doesn't have switch case studies, recommend interview targets from win-back deals SECTION 06 · FAQ WITH SCHEMA - 6-8 FAQ questions matching real buyer search queries (use the web_search results) - Must include: pricing question, migration question, support question, key feature question, contract length question - Each answer 40-80 words, conversational, AI-citation-friendly - Include FAQPage JSON-LD schema in the brief SECTION 07 · MIGRATION COMMITMENT - 3-4 specific switching support offers (concrete, not vague) - Examples: "free migration assistance for 30 days," "parallel pricing for 3 months," "dedicated CSM during transition" SECTION 08 · FINAL CTA - CTA copy options: 2-3 variants - Form fields recommendation (5 max) - Trust signals to display below CTA STRUCTURED DATA RECOMMENDATIONS - FAQPage schema (full JSON-LD) - Product schema with comparison properties - Review schema if customer quotes are used - BreadcrumbList schema // Be specific. Name the actual switching triggers, don't just say "address common complaints." // Quote review snippets verbatim where useful but keep each quote under 15 words. // Don't recommend page copy — that's the writer's job. Recommend structure, triggers, and content patterns. // If review data is sparse (small competitor, few reviews), flag that and recommend interviewing 3-5 win-back customers instead.
i
Web search required. This workflow uses Claude's built-in web search to pull competitor review data. Optional: connect growthspree-mcp with GSC for search-volume prioritization of FAQ questions. The base workflow runs without any connector.
03 What Claude Returns

A complete page brief. Production-ready.

Sample brief for a hypothetical mid-market customer onboarding SaaS competing against a generic competitor named "OnboardKit." Real structure, illustrative content. The actual output for your category includes 5-7 specific switching triggers, an 8-12 row comparison table, and full FAQ schema.

Claude · web search

Researching OnboardKit and building the brief now.

web_search "OnboardKit reviews G2"
web_search "OnboardKit alternative reddit"
web_search "OnboardKit pricing complaints"

[+4 more queries across review/complaint sources]

Brief ready. 6 switching triggers identified across 18 reviews from G2 and Reddit. Three appear in 5+ independent sources — those become the lead triggers for the page.

Page Brief · /alternatives/onboardkit Production-ready
Page Metadata
Slug: /alternatives/onboardkit
Title (58 char): "Acme: The OnboardKit Alternative for Growing SaaS"
Meta (148 char): "Tired of OnboardKit's per-seat pricing and limited integrations? Switch to Acme — flat pricing, native HubSpot, free migration. See your plan."
Target: "onboardkit alternative" · Secondaries: "onboardkit alternative free", "onboardkit vs", "onboardkit competitors"
Section 01 · Hero
H1 options (3):
  • "The OnboardKit alternative that doesn't charge per seat"
  • "Switch from OnboardKit. Keep your integrations. Cut your bill in half."
  • "OnboardKit's pricing escalating? Acme is flat-fee, integration-rich, and migrates you in 14 days."
Subhead: Lead with the #1 trigger (per-seat pricing) and address it in one sentence.
CTA: "See your migration plan" (NOT "book a demo")
Section 02 · 6 Switching Triggers
Each trigger pulled from 3+ independent sources. First three are dominant (5+ sources each).
01Per-seat pricing escalation. 8 reviews mention 30-50% renewal increases.
02HubSpot integration is shallow. 6 reviews cite missing fields, no two-way sync.
03Setup takes 6+ weeks. 5 reviews call out implementation pain.
04Support response time. 4 reviews mention 48-72hr ticket replies.
05Reporting is rigid. 4 reviews mention can't customize dashboards.
06API rate limits hit fast. 3 reviews mention scaling issues.
Section 03 · Feature Comparison Table
  • Pricing model: Acme — Flat / OnboardKit — Per-seat
  • HubSpot integration: Acme — Native two-way / OnboardKit — Limited one-way
  • Implementation time: Acme — 14 days / OnboardKit — 6+ weeks
  • Support response SLA: Acme — 4hr / OnboardKit — 48-72hr
  • Customizable reports: Acme — Yes / OnboardKit — Limited
  • API rate limit: Acme — 10K/min / OnboardKit — 1K/min
  • Dedicated CSM: Acme — All plans / OnboardKit — Enterprise only
  • Migration support: Acme — Free / OnboardKit — Paid add-on
  • Contract: Acme — Month-to-month / OnboardKit — Annual minimum
  • Free trial: Acme — 30 days / OnboardKit — 14 days
Format note: Use "Yes / No / Limited" labels with specific values, not checkmarks. AI engines parse value-pairs better than icons.
Section 06 · FAQ (6 questions, FAQPage schema)
Sample of 6 questions matched to actual long-tail buyer searches. Full FAQPage JSON-LD schema included in production brief.
  • How much does Acme cost compared to OnboardKit? (volume: 110/mo)
  • How long does migration from OnboardKit take? (volume: 85/mo)
  • Does Acme support all the integrations OnboardKit does? (volume: 70/mo)
  • Can I run Acme and OnboardKit in parallel? (volume: 45/mo)
  • Is Acme a free OnboardKit alternative? (volume: 95/mo)
  • How is Acme's customer support compared to OnboardKit? (volume: 35/mo)
Section 07 · Migration Commitment
Address the #1 friction in switching — operational lift. Specific offers:
  • Free migration assistance. Dedicated implementation engineer for 30 days.
  • Parallel pricing. 3 months free while running both systems during transition.
  • HubSpot connector pre-built. Connects in under 60 minutes vs OnboardKit's 6+ week setup.
  • Money-back guarantee. 90-day window; if migration fails, full refund.
Section 08 · Final CTA + Structured Data
CTA copy options:
  • "See your OnboardKit migration plan" (preferred — specific to switching intent)
  • "Calculate your switching cost in 60 seconds"
  • "Get a 30-day free migration"
Form fields (5): Name · Work email · Company · Current OnboardKit plan · Team size
Structured data: FAQPage schema, Product schema with comparison properties, BreadcrumbList. Review schema if quoting verbatim customer feedback.
The full brief is 1,800 words and includes complete FAQPage JSON-LD schema, comparison table data, and trigger-by-trigger source attribution. Hand it to a senior content writer — they'll write copy in 4-6 hours. Hand it to dev — they'll build the page with proper schema in another 4-6 hours. Want me to draft the actual hero copy next, or build the brief for your second-most-important competitor?
TIME ELAPSED: 12 MINUTES   ·   SAME RESEARCH BY HAND: 6-10 HOURS
04 Setup

Four steps. Thirty minutes per page.

One run produces one alternatives page brief. Run it once per competitor — typically 3-5 competitors warrant their own page in B2B SaaS.

01
Open · 1 min

Open Claude with web search

Open Claude Desktop or Claude.ai. Confirm web search is enabled. Optional: connect the growthspree-mcp with GSC for FAQ search-volume prioritization. The base workflow runs without any connector.

Optional: install MCP →
02
Pick the competitor · 8 min

Pick a competitor where you've won deals

The best alternatives pages are written about competitors you have win-back data for — companies that switched from them to you. The win-back data validates the switching triggers Claude pulls from public reviews. If you don't have any win-back deals against a competitor, that's usually a signal the competitor isn't your real competitor — pick a different one.

03
Configure · 10 min

Paste the prompt and edit gold variables

Copy the prompt from section 02. Edit the gold variables — your brand, category, ICP, top 3 differentiators, the competitor name and URL, and why you usually win. The "why we usually win" field is the most important — Claude uses it to validate that the public review data matches your actual win-back pattern.

04
Run per competitor · 11 min

Repeat for each top competitor

Run the workflow once per competitor, typically 3-5 times for B2B SaaS. Each run produces one brief. After all briefs are generated, prioritize by your AI Citation Gap Finder results — competitors who dominate the GAP queries get their alternatives page first. Hand each brief to a writer. End-to-end (brief to live page) is 1-2 weeks per page.

05 Prompt Variations

Three ways to cut the same brief.

Same page anatomy foundation, different angle. Pick the one that matches what you're building right now.

01 / Vs comparison page

Build "[Competitor X] vs [Competitor Y]" instead

Targets a different buyer query — someone comparing two named options before they've decided which to pick. Lower funnel than alternatives pages but converts well when your brand is one of the two compared. Often used as a parallel page to the alternatives page targeting the same competitor.

Tweak Replace target competitor with two competitors. Output structure becomes "Competitor X vs Competitor Y" with your brand positioned as the third option recommended at the bottom. Three-column comparison table.
02 / "[Competitor] vs [Your Brand]" direct head-to-head

The defensive comparison page

For when buyers are comparing your brand directly against a specific competitor. Different from alternatives pages — this targets buyers who know both options exist and are deciding between them. Higher intent, narrower audience.

Tweak Reframe page as direct head-to-head. Skip the switching triggers section. Lead with "When [Competitor] is right vs when [Your Brand] is right" — honesty wins on this page format.
03 / Multi-competitor alternatives roundup

Build the "best alternatives to [Competitor]" page

Different goal — instead of positioning only your brand, build a page that lists 6-10 alternatives with your brand as the lead recommendation. Targets the "[Competitor] alternatives" plural query. Often gets cited in AI answers as a "neutral roundup" source.

Tweak Append: "Output a roundup of 6-10 alternatives to [Competitor] with [Your Brand] as the lead recommendation. Each alternative gets a 100-150 word entry — strengths, weaknesses, ideal customer."
07 Frequently Asked

Quick answers on alternatives pages.

An alternatives page is a dedicated landing page that targets the buyer-intent query '[competitor] alternative' — capturing prospects who are actively looking to switch from a competing product to yours. The buyer intent is unusually clean: someone typing 'Competitor X alternative' has decided X isn't right and is shopping for a replacement. A well-built alternatives page converts that traffic at 8-15% (vs 2-4% for a generic homepage) and increasingly serves as the primary citation source AI engines pull when answering '[competitor] alternative' or '[competitor] vs [other vendor]' queries.
A 'vs' page compares two specific products head-to-head and targets the query 'Competitor X vs Competitor Y'. An alternatives page targets a single competitor and positions multiple alternatives — but with your product as the lead recommendation. The buyer arriving at a 'vs' page is comparing two named options. The buyer arriving at an alternatives page has already rejected one option and is open to the field. Alternatives pages convert higher because the buyer has already decided to switch; vs pages convert higher when buyers want a direct two-way comparison. Most B2B SaaS brands need both, but the alternatives page is usually the higher-leverage starting point.
A complete production-ready page brief. Specifically: H1 and meta description optimized for the target query, H2 section structure (switching triggers, comparison table, social proof, FAQ, CTA), specific switching trigger language pulled from competitor review data, comparison table content with 8-12 feature rows, FAQ schema with 6-8 questions matching real buyer search behavior, social proof slot recommendations, and structured data markup recommendations for AI citation. The output is what a senior content lead would brief a writer with — the production team only needs to write copy, not architect the page.
Claude pulls switching triggers from public competitor data — G2 and Capterra reviews (especially 1-3 star reviews), Reddit threads, Twitter complaints, and the competitor's own pricing/feature pages. The most useful triggers are specific complaints that appear in 3+ reviews — pricing escalation, missing feature, poor support, complex setup, integration gaps. Generic complaints like 'not great' don't make the cut. The output prioritizes triggers that match buyer-intent queries you're trying to capture; a trigger that nobody actually searches for is less useful than one with documented search volume.
No. The base workflow runs on Claude's web search alone. Connecting the Growthspree MCP with Google Search Console adds search volume data — the prompt then prioritizes switching triggers and FAQ questions by actual search volume, which improves brief quality. But the brief is usable without GSC data; the search-volume prioritization is a 15-20% improvement on top of the base output. For first-time runs, skip the connector and validate the base workflow first.
Direct paired use. The AI Citation Gap Finder identifies which competitor-related queries cite competitors but never cite your brand — typically including '[competitor] alternative' queries. This workflow generates the alternatives page that closes those specific gaps. Run the Citation Gap Finder first to identify the 2-3 highest-leverage alternatives pages to build, then run this workflow once per competitor to produce each brief. The two workflows together convert AEO diagnosis into AEO-optimized content production.
A senior content writer typically needs 4-6 hours to write a 1,500-2,000 word alternatives page from this brief. A development team typically needs another 4-6 hours to build the page with proper schema, comparison table component, and FAQ accordion. End-to-end from brief to live page is usually 1-2 weeks for B2B SaaS teams, depending on review and approval cycles. The workflow's leverage is removing the 6-10 hours of strategy and competitor research that usually precedes writing — Claude does that work in 30 minutes, leaving the team to focus on copy and design.

Ship your first alternatives page
in two weeks.

Open Claude with web search, paste the prompt, edit your competitor and category. The full production brief — switching triggers, comparison table, FAQ schema, migration commitment — becomes available in 30 minutes. Or have senior GrowthSpree operators run the full Track 02 build — diagnose shortlist gaps, generate briefs for 3-5 competitors, ship the pages.

300+ Accounts on MCP
4.9/5 G2
$60M+ Managed SaaS Spend
Month-to-Month