Founders Round Economics — Landing Page Planning

Your Task

Help me develop the landing page for:

https://millennium-asset.biz/founders-round-economics/

First, determine what this landing page is intended to accomplish based
on the information available to you and anything I provide during our
conversation.

Then develop a complete recommendation for the page.

Do not limit your response to suggested marketing copy.
I need a practical specification that a web developer can use to build
the page.

1. Project Purpose

Explain:

• What the Founders Round Economics project is
• Why this landing page is being created
• What the page should accomplish
• Who the intended audience is
• What action we ultimately want visitors to take

If any of these are unknown, explicitly identify the missing information.

2. Recommended Page Structure

Recommend the complete structure of the page from top to bottom.

For each section, explain:

• The purpose of the section
• What information it should contain
• The recommended headline
• The recommended supporting copy
• Any call-to-action
• Any images, graphics, charts, diagrams, or other visual elements that would be useful

3. Proposed Copy

Write the actual proposed copy for the page.

This should include, where appropriate:

• Page headline
• Subheadline
• Introductory copy
• Section headings
• Body copy
• Calls to action
• Button text
• Supporting statements
• Disclaimer or qualification language if needed

Do not make unsupported claims. If a statement requires information
from Robert or Millennium Asset before it can be published, mark it
clearly as:

[CONFIRM BEFORE PUBLISHING]

4. Facts and Claims Requiring Verification

Create a separate list of every factual claim, statistic, number,
financial figure, performance claim, quotation, date, name, or other
potentially verifiable statement that should be confirmed before
publication.

For each item, explain what needs to be verified.

Do not assume that something is true merely because it would make
the landing page more persuasive.

5. Design and Layout Recommendations

Describe how the page should look and feel.

Consider:

• Overall visual style
• Page width and layout
• Typography
• Colors
• Use of images
• Use of charts or other financial visuals
• Section spacing
• Calls-to-action
• Mobile responsiveness
• Relationship to the existing Millennium Asset website

The recommendations should be practical for a web developer working
within the existing website rather than assuming that an entirely new
website will be built.

6. Technical / Implementation Requirements

Identify anything the developer will need to know to implement the page,
including:

• URL
• Forms
• Email addresses
• Links
• Downloads
• Tracking requirements
• Analytics
• Integrations
• Embeds
• Images or other assets
• Required plugins or third-party services
• SEO considerations
• Accessibility considerations

If you do not know whether something is required, say so.

7. Open Questions

Create a concise list of questions that Robert needs to answer before
the page can be finalized.

Do not hide uncertainties. If an important decision cannot be made from
the available information, identify it here.

Decision Rules

When making recommendations:

• Prioritize factual accuracy over persuasive language.
• Clearly distinguish known information from assumptions and recommendations.
• Never invent missing information.
• Do not fabricate financial data, investment performance, customer numbers, testimonials, partnerships, credentials, or regulatory claims.
• If the project involves financial or investment-related claims,
  identify claims that may require legal or compliance review before
  publication.
• If there are multiple reasonable approaches, explain the alternatives
  and their tradeoffs.
• Do not make a recommendation solely because it sounds more impressive.
• Keep the final proposed page practical and appropriate for Millennium
  Asset’s existing website.

Separate Known Information From Recommendations

At the end, clearly separate:

• APPROVED / KNOWN INFORMATION
• RECOMMENDED INFORMATION
• INFORMATION THAT MUST BE CONFIRMED

This distinction is important because the developer will use your
response to build the actual page.