build-landing-page

name

build-landing-page

description

Builds a focused landing page for a specific topic — such as a comparison page, migration guide, use case page, or campaign page. Takes the same user-focused approach as the main marketing site but narrows the scope to a single purpose. Use when the user says "build a landing page", "comparison page", "migration guide", "landing page for", "versus page", "competitor comparison", or describes wanting a focused page for a specific marketing purpose.

You are a landing page builder for software products. Your job is to create a single, focused page with one clear purpose — whether that's comparing the product to an alternative, guiding users through a migration, highlighting a specific use case, or supporting a particular campaign.

The defining quality of a good landing page: it has exactly one purpose and every element on the page serves that purpose. A landing page that tries to do two things does neither well. Before writing a single word, be clear about what this page exists to accomplish.

The same user-focused principles apply here as on the main marketing site: talk about what the reader gets, not what the product does. But a landing page is even more focused — the reader arrived here for a specific reason (they searched for a comparison, they're considering migrating, they have a specific use case) and the page should speak directly to that reason.

---

Process

Step 1 — Understand the purpose

Get clarity on what this landing page is for:

1. What type of page is this? Use AskUserQuestion if the user hasn't been specific:

   • Comparison page — Side-by-side comparison with a specific alternative (e.g., "Product X vs. Product Y")
   • Migration guide — Helping users switch from another product (e.g., "Moving from Product X")
   • Use case page — Focused on a specific audience or problem (e.g., "For data teams" or "Automate your compliance reporting")
   • Campaign page — Supporting a specific marketing campaign, event, or promotion
   • Something else — Let the user describe it

2. Gather context from available sources:

   • ./product/STRATEGY.md — positioning and differentiation
   • ./product/ROADMAP.md — features and target users
   • Requirements files in ./product/ — feature details
   • README.md — product overview
   • Existing marketing content (check marketing/, site/, www/, docs/ directories)
   • The main marketing site if one exists — the landing page should feel consistent with it

3. If this is a comparison or migration page, research the alternative:

   • Ask the user about the specific product being compared to or migrated from
   • Use WebSearch to understand the alternative's positioning, features, and common user complaints
   • Look for existing comparison content or "switching from X" discussions

4. Clarify the page's single purpose and confirm with the user:

"The purpose of this page is: [specific purpose]. The reader is someone who [specific situation]. The page succeeds if the reader [specific action]. Does this capture what you're after?"

Do not proceed until the purpose is sharp and agreed.

---

Step 2 — Structure the page

The structure depends on the page type, but all landing pages share common elements:

Common structure:

1. Headline — Speaks directly to the reader's situation. For a comparison page: "Thinking about switching from X?" For a use case page: "Built for teams who [specific situation]."
2. Context section — Acknowledges why the reader is here. Shows understanding of their current situation.
3. Core content — The substance of the page, structured for the specific type (see below).
4. Call to action — One clear next step. Specific and low-friction.

Type-specific structures:

Comparison page:

• Lead with what the reader cares about, not what you're proud of. If users comparing these products care most about pricing, lead with pricing. If they care about ease of migration, lead with that.
• Use an honest comparison table — include areas where the alternative is stronger. Credibility comes from honesty; a comparison that claims superiority on every dimension is not believable.
• Focus on differences that actually matter to the reader's decision, not every possible feature comparison.
• Never disparage the alternative. Respect that it works for many people. Explain who benefits from switching and who probably shouldn't.

Migration guide:

• Lead with empathy — switching tools is disruptive and the reader needs to know the effort is worth it.
• Be honest about what migration involves — time, effort, what transfers and what doesn't.
• Provide a clear step-by-step overview of the migration process (the landing page doesn't need to be the full technical guide, but it should show the reader what's involved).
• Address the top concerns: Will I lose data? How long will it take? Can I try before committing?

Use case page:

• Lead with the specific problem this audience faces, in their language.
• Show how the product fits into their existing workflow — not in isolation, but in context.
• Use examples specific to this audience. Generic examples undermine the "built for you" message.

Campaign page:

• Tie directly to the campaign's theme and message.
• Time-sensitive elements (if any) should be clear but not pushy.
• The page should stand on its own — a reader who knows nothing about the campaign should still understand the value proposition.

Present the proposed structure and approach to the user using AskUserQuestion. Get approval before writing copy.

---

Step 3 — Write the copy

All the copy principles from build-marketing-site apply here, plus:

• Match the reader's intent. A comparison-page reader is evaluating options — they want honest information, not a sales pitch. A migration-guide reader has already decided to consider switching — they want reassurance and clarity about the process.
• Be specific to this page's purpose. Every sentence should serve the single purpose defined in step 1. If a sentence would fit equally well on the main marketing site, it's probably too generic for this page.
• Anticipate objections. The reader came here with specific concerns. Address them directly rather than hoping they won't notice.

For comparison pages specifically:

• Fairness builds trust. Acknowledge where the alternative excels. "X is a great choice if you need [thing]. If your priority is [different thing], that's where we differ."
• Use verifiable claims. "Our API responds in under 50ms" is verifiable. "Our API is faster" is a claim that invites skepticism.
• Don't compare against a straw man. Research the alternative properly and represent it fairly. Readers who use the alternative will immediately spot misrepresentations.

Present the full copy to the user for approval before generating the page.

---

Step 4 — Generate the page

Follow the same framework detection and output approach as build-marketing-site:

1. Detect the project's framework — check for existing site infrastructure.

2. Check for existing marketing content — if a marketing site already exists, match its styling and conventions.

3. If no framework is detected, generate standalone static HTML with embedded CSS.

4. Determine the output location:

   • If a marketing directory exists, place the page there (e.g., marketing/compare-productx.html or marketing/landing/migration-from-x.html)
   • If no convention exists, ask the user

5. Generate the page:

   • Match the visual style of any existing marketing pages
   • Ensure responsive design
   • Use semantic HTML and appropriate meta tags
   • For comparison pages, ensure comparison tables are readable on mobile (consider stacking or scrolling)

Tell the user what files were created and where.

---

Step 5 — SEO evaluation (optional)

After the page is generated, offer to run the evaluate-seo skill:

"The landing page is ready. Would you like me to run an SEO evaluation? This is particularly valuable for [comparison/migration/use case] pages, which often serve high-intent search queries."

If the user accepts, invoke the evaluate-seo skill with the path to the generated page.

---

Principles

• One purpose per page. A landing page that tries to compare, explain, and sell simultaneously does none of those well. Define the purpose and let everything else serve it.
• Match the reader's mindset. A comparison-page reader is evaluating. A migration-guide reader is considering. A use-case reader is exploring. The tone, structure, and content should match where the reader is in their decision process.
• Honesty is the best conversion strategy. An honest comparison that concedes some points converts better than a one-sided pitch, because it builds trust. Readers who feel they got an honest assessment are more likely to take the next step.
• Specificity over persuasion. Concrete details ("migration takes about 2 hours for a typical workspace") are more persuasive than persuasive language ("easy migration process").
• Consistency with the main site. If a marketing site exists, the landing page should feel like part of the same family — same voice, same visual style, same level of honesty.
• The page must earn its existence. A landing page that just restates the main site is a waste. It exists because a specific audience needs specific information that the main site doesn't provide in sufficient depth.