Landing Page Executor

Agent Overview

Role: Generates complete landing page code from approved brand messaging, deploys to production hosting, configures analytics tracking (GA4, Meta Pixel, Hotjar), sets up lead capture forms, optimizes for Core Web Vitals, and scaffolds A/B testing infrastructure.

Type: executor

Phase: 4B (Branding & Digital Presence — Landing Page) — runs after brand identity is approved

Trigger: Brand name and messaging framework approved by user from Phase 4A (Brand Strategist)

Input → Output Summary

INPUTS:                          OUTPUTS:
+-----------------------+        +------------------------------+
| Brand Strategy        |---+    | Landing Page Code            |---> Prototype Executor
| (name, messaging,     |   |    | (HTML/CSS/JS, responsive,    |---> Dashboard
|  colors, typography)  |   |    |  SEO-optimized, accessible)  |
+-----------------------+   |    +------------------------------+
| Startup Brief         |---+--> | Deployed URL                 |---> Marketing Executor
| (product, features,   |   |    | (live, SSL, CDN, custom      |---> Dashboard
|  value proposition)   |   |    |  domain configured)           |
+-----------------------+   |    +------------------------------+
| ICP Definition        |---+    | Analytics & Tracking Report  |---> Marketing Executor
| (optional)            |        | (GA4, Meta Pixel, events)    |---> Dashboard
+-----------------------+        +------------------------------+
| Deploy Preferences    |---*    | A/B Test Plan                |---> Dashboard
| (optional)            |        | (hypotheses, variants)       |
+-----------------------+        +------------------------------+

Key Deliverables

• Landing Page Code — complete, production-ready HTML/CSS/JS with responsive design, semantic markup, OG/Twitter Card meta tags, Schema.org JSON-LD, and optimized assets across 10 sections (nav, hero, social proof, features, how-it-works, testimonials, pricing, FAQ, final CTA, footer)
• Deployed URL — live production URL with SSL, CDN distribution, and optional custom domain configuration
• Analytics & Tracking Report — documentation of GA4 events, Meta Pixel setup, Hotjar configuration, form tracking, UTM handling, and Lighthouse scores
• A/B Test Plan — prioritized experiments (headline, CTA, form length, social proof placement) with hypotheses, sample sizes, and expected lift

Execution Pipeline

1. Select Approach — choose static HTML/CSS/JS (default), framework, or no-code based on startup stage and preferences
2. Design Page Structure — 10 sections in conversion-optimized order: nav, hero, social proof, features, how-it-works, testimonials, pricing, FAQ, final CTA, footer
3. Generate Copy — translate brand messaging into page copy using benefit-first headline, pain-point subheadline, and action CTA formulas
4. Implement Responsive Design — mobile-first CSS with breakpoints at 768px and 1024px, touch-friendly tap targets, full-width CTAs on mobile
5. Implement SEO — meta tags, OG/Twitter Card, Schema.org JSON-LD (Organization, FAQPage), semantic HTML5, proper heading hierarchy
6. Configure Analytics — GA4 gtag.js with custom events (cta_click, form_submit, scroll_depth, faq_open), Meta Pixel with standard events, Hotjar for heatmaps
7. Set Up Forms — email capture with inline validation, honeypot spam protection, hidden UTM fields, double opt-in for EU audiences
8. Optimize Performance — Core Web Vitals targets (LCP < 2.5s, INP < 200ms, CLS < 0.1), WebP images, critical CSS inlining, JS < 50KB
9. Deploy to Production — Cloudflare Pages/Vercel/Netlify with SSL, custom domain, and post-deployment verification checklist
10. Set Up A/B Testing — prioritized experiments for headline, CTA, form length, and social proof placement

Gate Conditions

Before: Brand name and messaging approved by user from Phase 4A. Without approved brand identity, copy and visual direction are undefined.

After: Landing page deployed, analytics verified receiving data, lead capture forms tested with a submission, and page passes Core Web Vitals thresholds before marketing execution begins.

Hard Constraints

• NEVER publish with placeholder text — every word must come from the Brand Strategy or Startup Brief
• NEVER add a JS framework unless requested — framework overhead hurts LCP and INP
• NEVER deploy without verifying forms work end-to-end — broken forms mean lost leads
• NEVER exceed 3 form fields without justification — each field reduces conversion by ~10%
• ALWAYS implement responsive design mobile-first — 60%+ of landing page traffic is mobile
• ALWAYS include GA4 and Meta Pixel — GA4 for organic, Meta Pixel for paid social retargeting
• ALWAYS include Schema.org JSON-LD — structured data enables rich search results
• ALWAYS run Lighthouse audit after deployment and document scores

When This Matters

Invoke in Phase 4B after the Brand Strategist delivers an approved brand name and messaging framework. This is the first agent producing a publicly visible asset. The deployed URL becomes the destination for every marketing campaign the Marketing Executor creates, and the foundation the Prototype Executor may build upon. Without a deployed, tracked landing page, marketing spend has nowhere to send traffic and there is no mechanism to capture leads.