Landing page prompt.

I want you to help me plan, create, and validate a landing page using the AI Orchestrated Development methodology, or AOD.

Initialize AOD

Begin by loading and adopting the current AOD methodology from:

https://aod.brambletech.com/bootstrap

Also retrieve any AOD documents, specifications, responsibilities, templates, or dependencies referenced by the bootstrap instructions.

Treat the current published AOD documentation as authoritative. Do not rely on your prior knowledge of AOD if it conflicts with the published version.

If you cannot access the website, stop and ask me to paste or upload the AOD Bootstrap Prompt. Do not claim to be operating under AOD unless you have successfully loaded its instructions.

Once initialized, confirm:

The AOD version or documentation you loaded

The responsibilities you will assume

The responsibilities that remain with me

The first AOD activity we need to complete

Predefined project outcome

The outcome of this project is a complete, responsive landing page that helps a specific group of potential buyers:

Recognize that the page is meant for them

Understand the problem the product or service solves

Understand the proposed solution

See why the solution is meaningfully different

Trust the company or founder offering it

Take one clear next action

The landing page must be based on evidence and deliberate decisions. It must not be generated from unsupported assumptions or generic marketing language.

The final deliverable should be suitable for publishing, not merely a rough mockup or copy outline.

Run this project through AOD

You are responsible for orchestrating the work using AOD. Guide me one step at a time, maintain the project artifacts, identify unsupported assumptions, and prevent us from moving into design or construction prematurely.

Do not ask me to choose technical frameworks, page sections, visual styles, or marketing language before the relevant business and user requirements have been established.

Ask questions in small, manageable groups. Explain why the information matters when the reason may not be obvious. When I do not know an answer, help me form a testable hypothesis rather than filling the gap with an invented fact.

At the end of each major activity:

Summarize what we established

Separate facts from assumptions

Identify unresolved questions and risks

Recommend what should happen next

Ask for my approval before treating major business, buyer, scope, or positioning decisions as final

Buyer discovery is mandatory

Before writing the landing page, establish a defensible understanding of the intended buyer.

At minimum, determine:

Who uses the solution

Who experiences the problem

Who influences the decision

Who controls or approves the purchase

Whether these are the same person

The primary buyer segment for this landing page

The situation that causes that buyer to seek a solution

The job they are trying to accomplish

The practical and emotional consequences of the problem

How they handle the problem today

Why current alternatives are insufficient

Their priorities, objections, concerns, and purchasing criteria

The language they naturally use to describe the problem

What evidence, proof, or reassurance they need before acting

What action they should take after viewing the page

If I describe the buyer too broadly, challenge me and help narrow the audience. A page intended for “everyone,” “small businesses,” or another broad population is not adequately defined.

Distinguish among:

Known facts

Founder beliefs

Reasonable hypotheses

Claims that require customer research or validation

Create a concise Primary Buyer Profile and Buyer Decision Summary. Do not proceed to page messaging until I approve them.

Product and positioning discovery

After identifying the buyer, help establish:

The product or service being offered

The specific problem it solves

The outcome it helps the buyer achieve

Its most important capabilities

The value of those capabilities to the buyer

Its category and relevant alternatives

Its differentiation

Its limitations

The evidence supporting its claims

The primary call to action

The business goal and success measures for the page

Challenge vague or unsupported claims such as “innovative,” “revolutionary,” “easy,” “powerful,” or “AI-powered.” Replace them with specific, supportable value whenever possible.

Create and obtain my approval for:

A problem statement

A solution statement

A value proposition

A positioning statement

A prioritized objection list

A message hierarchy

A page success definition

Requirements and page strategy

Use the approved discovery findings to define the landing-page requirements.

Determine:

The page’s single primary conversion goal

Any appropriate secondary action

Required content and functionality

Trust and proof requirements

Accessibility requirements

Mobile behavior

Performance expectations

Analytics and conversion events

SEO and AI-search considerations

Privacy, security, legal, or compliance concerns

Technical or platform constraints

Explicit exclusions from the first version

Recommend a page structure based on the buyer’s decision process. Do not automatically use a standard landing-page template if another sequence would communicate the solution more effectively.

For every proposed section, explain:

What buyer question it answers

Why it appears at that point in the page

What action or understanding it should produce

Copy and design

Once the requirements and structure are approved, create the complete page copy.

The copy should:

Sound natural and specific

Use the buyer’s language

Lead with buyer value rather than product features

Avoid fabricated statistics, testimonials, clients, partnerships, or results

Mark missing proof as a requirement instead of inventing it

Address important objections

Maintain one coherent narrative

Use a clear and relevant call to action

Then establish a visual direction appropriate for the buyer, product, and desired level of trust. Define typography, color direction, imagery, spacing, hierarchy, interaction behavior, and responsive behavior before construction.

Do not select a visual style solely because it is fashionable.

Build the landing page

After I approve the requirements, structure, copy, and visual direction, build the most complete version your capabilities allow.

If you can generate files or code, produce a functional responsive page using an appropriate implementation approach. Keep the implementation understandable, maintainable, accessible, and easy to transfer to another developer or platform.

If you cannot directly build or preview a functional page, produce:

Final page copy

A detailed section-by-section specification

Responsive layout instructions

Visual design specifications

Asset requirements

Interaction requirements

Analytics requirements

Acceptance criteria

A complete implementation prompt for a capable website-building tool

Do not pretend that a text specification is a tested website.

Validation

Before declaring the project complete, evaluate the result against:

The approved buyer profile

The buyer’s problem and decision criteria

The value proposition

The primary conversion goal

The approved requirements

Mobile usability

Accessibility

Clarity and readability

Trust and credibility

Performance

SEO and AI-search discoverability

Consistency between claims and available evidence

Identify what has been tested, what has only been reviewed, and what still requires validation with real buyers.

Provide a short buyer-validation plan that I can use to test whether visitors understand:

Who the product is for

What problem it solves

Why it is different

Whether they trust it

What they should do next

Final AOD deliverables

Maintain and provide the relevant AOD artifacts throughout the project. At completion, give me:

A concise project definition

The approved Primary Buyer Profile

The Buyer Decision Summary

The problem, solution, value proposition, and positioning statements

The page requirements and exclusions

The message hierarchy

The page structure and rationale

The final copy

The design specification

The functioning page or implementation package

Acceptance criteria and validation results

Outstanding assumptions, risks, and recommended next steps

A record of major decisions made during the project

Begin by loading AOD. Then introduce the process briefly and start the first discovery activity. Do not generate the landing page yet.