Create competitive landing pages from battlecards, positioning, and proof

Pick one competitor, legacy alternative, or status quo option and define the page's business job before generating copy. Decide whether the page is meant to capture paid search demand, support sales follow-up, explain a displacement narrative, compare categories, or convert existing comparison traffic. Write the primary buyer question in plain language, such as 'Why choose us over this competitor?' or 'When should a team switch from the old approach?' Add the target persona, stage of awareness, intended CTA, and proof standard. This prevents the page from becoming a generic comparison that tries to answer every competitive question at once.

Create a focused competitive landing page brief.

Competitor or alternative:
{{competitor_or_alternative}}

Business goal:
{{business_goal}}

Target persona:
{{target_persona}}

Traffic source:
{{traffic_source}}

Primary CTA:
{{primary_cta}}

Our positioning summary:
{{positioning_summary}}

Return:
1. Primary buyer question
2. Page job
3. Audience and awareness level
4. Recommended page angle
5. Proof standard required
6. Claims likely to need review
7. Sections the page should include
8. Sections to avoid

Keep the brief narrow enough for one page.

Create a Google Drive folder with the approved positioning guide, battlecard, product page guide, proof points, customer quotes, win-loss notes, legal claim rules, competitor notes, brand voice, and examples of comparison pages you like. Add a source index that says which documents are authoritative and which are background only. Separate approved claims from hypotheses so Claude does not treat sales notes as final positioning. Include links to screenshots, demo clips, analyst notes, or customer stories that can support the page. The source pack should make it obvious what the AI can use, what it must cite, and what it must flag for human review.