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

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.