Appearance
The Landing Page Lifecycle
A landing page is never "done" — it moves through predictable stages from initial brief to eventual retirement, with continuous optimization in between.
Why This Matters
- 💻 Dev: Understanding the lifecycle prevents the #1 dev frustration: building a "final" page that gets redesigned three times. When you know optimization is baked into the process, you build for iteration from day one — modular components, feature flags, and analytics hooks.
- 📋 PM: The lifecycle is your project plan. It tells you what happens when, who owns each stage, and how long each phase should take. Without it, landing page projects are chaos — no definition of done, no optimization cadence, no retirement criteria.
- 🎨 Designer: Design does not end at handoff. The lifecycle shows you that your initial design is a hypothesis, not a masterpiece. The best landing page designers stay involved through optimization, using data to refine their craft.
The Concept (Simple)
Think of a landing page like tending a garden.
You start by planning what to plant — choosing the right seeds for the season and soil (the brief and research). Then you prepare the bed — sketching out rows and spacing (wireframing). You plant the seeds (design and development) and water them (drive traffic).
But planting is not the end. You prune what is not working (optimize underperforming sections). You fertilize what is thriving (double down on high-converting elements). You harvest the results (measure conversions and ROI). And eventually, when the season changes, you replant — retiring the old page and starting fresh with new learnings.
The gardeners who treat planting as a one-time event get weeds. The ones who tend their garden continuously get abundance. Landing pages work the same way.
How It Works (Detailed)
The 11 Stages
A landing page moves through these stages over its lifetime:
┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐
│ 1. Brief │──▶│ 2.Research│──▶│ 3.Wire- │──▶│ 4. Visual │
│ & Goals │ │ │ │ frame │ │ Design │
└───────────┘ └───────────┘ └───────────┘ └───────────┘
│
┌───────────────────────────────────────────────┘
▼
┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐
│ 5. Dev & │──▶│ 6. QA & │──▶│ 7. Launch │──▶│ 8. Measure│
│ Build │ │ Review │ │ │ │ │
└───────────┘ └───────────┘ └───────────┘ └───────────┘
│
┌───────────────────────────────────────────────┘
▼
┌───────────┐ ┌───────────┐ ┌───────────┐
│ 9. Opti- │──▶│10. Iterate│──▶│11. Retire │
│ mize │◀──│ │ │ │
└───────────┘ └───────────┘ └───────────┘
▲ │
└───────────────┘
(continuous loop)Notice the loop between stages 9 and 10. This is where most of the page's lifetime is spent. The initial build (stages 1-7) might take 2-4 weeks. The optimization loop runs for months or even years.
Stage Details and Ownership
┌─────┬──────────────────┬────────────┬──────────────────────────────────────┐
│ # │ Stage │ Primary │ Key Activities │
│ │ │ Owner │ │
├─────┼──────────────────┼────────────┼──────────────────────────────────────┤
│ 1 │ Brief & Goals │ 📋 PM │ Define audience, traffic source, │
│ │ │ │ conversion goal, success metrics │
├─────┼──────────────────┼────────────┼──────────────────────────────────────┤
│ 2 │ Research │ 📋 PM + │ Competitor analysis, user language │
│ │ │ 🎨 Design │ mining, message-market fit │
├─────┼──────────────────┼────────────┼──────────────────────────────────────┤
│ 3 │ Wireframe │ 🎨 Design │ Layout structure, content hierarchy, │
│ │ │ │ section sequencing (per Ch. 02) │
├─────┼──────────────────┼────────────┼──────────────────────────────────────┤
│ 4 │ Visual Design │ 🎨 Design │ High-fidelity mockups, responsive │
│ │ │ │ variants, interaction states │
├─────┼──────────────────┼────────────┼──────────────────────────────────────┤
│ 5 │ Development │ 💻 Dev │ Build, integrate tracking, connect │
│ │ │ │ forms, optimize performance │
├─────┼──────────────────┼────────────┼──────────────────────────────────────┤
│ 6 │ QA & Review │ All three │ Cross-browser, mobile, copy review, │
│ │ │ │ tracking verification, speed audit │
├─────┼──────────────────┼────────────┼──────────────────────────────────────┤
│ 7 │ Launch │ 📋 PM │ Go live, connect traffic sources, │
│ │ │ │ verify tracking fires correctly │
├─────┼──────────────────┼────────────┼──────────────────────────────────────┤
│ 8 │ Measurement │ 📋 PM │ Collect baseline data (min 1-2 │
│ │ │ │ weeks), report initial results │
├─────┼──────────────────┼────────────┼──────────────────────────────────────┤
│ 9 │ Optimization │ All three │ Identify drop-off points, form A/B │
│ │ │ │ test hypotheses, prioritize tests │
├─────┼──────────────────┼────────────┼──────────────────────────────────────┤
│ 10 │ Iteration │ 🎨 Design │ Design variants, implement changes, │
│ │ │ + 💻 Dev │ run tests, analyze results │
├─────┼──────────────────┼────────────┼──────────────────────────────────────┤
│ 11 │ Retirement │ 📋 PM │ Archive learnings, redirect URL, │
│ │ │ │ document what worked │
└─────┴──────────────────┴────────────┴──────────────────────────────────────┘Typical Timelines
Not every landing page needs the same investment. Here is a realistic breakdown for three common scenarios:
┌─────────────────────┬────────────────┬────────────────┬────────────────┐
│ Stage │ Campaign Page │ Core Product │ High-Stakes │
│ │ (simple) │ Page (medium) │ Launch (large) │
├─────────────────────┼────────────────┼────────────────┼────────────────┤
│ Brief & Goals │ 1 day │ 2-3 days │ 1 week │
│ Research │ 1 day │ 3-5 days │ 1-2 weeks │
│ Wireframe │ 1 day │ 2-3 days │ 1 week │
│ Visual Design │ 2-3 days │ 1 week │ 2 weeks │
│ Development │ 2-3 days │ 1 week │ 2 weeks │
│ QA & Review │ 1 day │ 2-3 days │ 1 week │
│ Launch │ 1 day │ 1 day │ 1-2 days │
│ Measurement │ 1-2 weeks │ 2-4 weeks │ 4+ weeks │
│ Optimization loop │ 1-3 months │ 3-12 months │ 6-24 months │
├─────────────────────┼────────────────┼────────────────┼────────────────┤
│ Total build time │ ~1.5 weeks │ ~3-4 weeks │ ~6-8 weeks │
│ Total active life │ 1-4 months │ 6-18 months │ 1-3 years │
└─────────────────────┴────────────────┴────────────────┴────────────────┘The Optimization Loop in Detail
Stages 9 and 10 deserve special attention because this is where the real conversion gains happen. The initial build gets you to baseline. Optimization is what doubles or triples your conversion rate over time.
┌─────────────────────────────────────────────────┐
│ THE OPTIMIZATION LOOP │
│ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Analyze │───▶│Hypothe- │───▶│ Design │ │
│ │ Data │ │ size │ │ Variant │ │
│ └──────────┘ └──────────┘ └──────────┘ │
│ ▲ │ │
│ │ ▼ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Document │◀───│ Evaluate │◀───│ Run Test │ │
│ │ Learning │ │ Results │ │ (A/B) │ │
│ └──────────┘ └──────────┘ └──────────┘ │
│ │
└─────────────────────────────────────────────────┘Each loop should take 2-4 weeks depending on traffic volume. The key discipline is to test one thing at a time. If you change the headline, the hero image, and the CTA button color all at once, you will never know which change moved the needle.
When to Retire a Page
A landing page should be retired when:
- The campaign it supports has ended
- Conversion rates have plateaued despite multiple optimization cycles
- The product, offer, or brand positioning has fundamentally changed
- A complete redesign is more efficient than incremental fixes
- The page's traffic source has been discontinued
When you retire a page, do not just delete it. Archive the page, document what worked and what did not, redirect the URL, and carry the learnings forward into the next page.
In Practice
HubSpot: Campaign Lifecycle Management
HubSpot runs hundreds of landing pages simultaneously across their marketing campaigns. Their process illustrates disciplined lifecycle management:
- Brief stage: Every landing page starts with a campaign brief that specifies the offer, audience persona, traffic source, and target conversion rate. No brief, no page.
- Build stage: They use a template system with pre-built modules (hero, form, testimonials, FAQ) that designers customize for each campaign. This cuts build time from weeks to days.
- Measurement: They wait a minimum of two weeks and 1,000 visitors before drawing any conclusions about performance. Small sample sizes lead to bad decisions.
- Optimization: They run a structured A/B testing program with a prioritization framework (ICE scoring — Impact, Confidence, Ease). High-impact, high-confidence, easy-to-implement tests run first.
- Retirement: Campaign pages are archived after the campaign ends, but the URL redirects to a relevant evergreen page so inbound links are not wasted.
HubSpot's data shows that pages in their third or fourth optimization cycle convert 30-50% better than their initial launch versions. The lifecycle is not overhead — it is where the ROI lives.
Notion: Iterative Signup Pages
Notion has redesigned their primary signup page multiple times, but they approach it as evolution, not revolution. Each version builds on the previous one:
- Version 1 focused on the product's flexibility ("All-in-one workspace")
- Version 2 added social proof (company logos and user count)
- Version 3 introduced use-case segmentation (tabs for different team types)
- Version 4 simplified the hero and added an interactive demo
Each version was not a gut-feeling redesign. It was an informed iteration based on data from the previous version. They did not remove what was working — they built on it. This is the lifecycle in action: measure, learn, iterate, measure again.
The Biggest Lifecycle Mistake
The most common mistake teams make is treating the launch as the finish line. They spend 4 weeks building a page, launch it, check the conversion rate once, and move on to the next project. The page sits untouched for months, slowly decaying in performance.
The build is the starting line. The real work starts after launch.
Key Takeaways
- A landing page has a defined lifecycle: Brief, Research, Wireframe, Design, Dev, QA, Launch, Measure, Optimize, Iterate, Retire.
- The initial build (stages 1-7) typically takes 1-8 weeks depending on complexity. The optimization loop runs for months or years.
- Each stage has a primary owner, but QA and optimization require all three roles working together.
- The optimization loop (Analyze, Hypothesize, Design, Test, Evaluate, Document) is where the real conversion gains happen — often 30-50% improvement over the launch version.
- Never test more than one variable at a time. Multivariate changes make it impossible to isolate what worked.
- Retirement is a stage, not an accident. Archive learnings, redirect URLs, and carry insights forward.
- Launching the page is the starting line, not the finish line.
Action Items
┌──────────┬──────────────────────────────────────────────────────┐
│ 💻 Dev │ ☐ Build landing pages with modular components that │
│ │ can be swapped independently for A/B testing │
│ │ ☐ Implement feature flags or variant switching so │
│ │ test variants do not require redeployment │
│ │ ☐ Set up automated performance monitoring that │
│ │ alerts when page speed degrades over time │
│ │ ☐ Create a URL redirect process for retired pages │
├──────────┼──────────────────────────────────────────────────────┤
│ 📋 PM │ ☐ Create a landing page brief template covering: │
│ │ audience, source, goal, KPI, success threshold │
│ │ ☐ Establish a minimum data threshold before making │
│ │ optimization decisions (e.g., 1,000 visitors) │
│ │ ☐ Set up a bi-weekly optimization review cadence │
│ │ for all active landing pages │
│ │ ☐ Build a landing page archive with documented │
│ │ learnings from every retired page │
├──────────┼──────────────────────────────────────────────────────┤
│ 🎨 Design│ ☐ Design a modular component system that supports │
│ │ rapid variant creation for A/B tests │
│ │ ☐ Stay involved post-launch — review heatmaps and │
│ │ scroll depth data to inform design iterations │
│ │ ☐ Create a "design learnings" document that │
│ │ captures what visual patterns convert best │
│ │ ☐ Build wireframe templates for quick (1-day), │
│ │ medium (3-day), and full (1-week) page builds │
└──────────┴──────────────────────────────────────────────────────┘