As of 13 August 2026, AI can design a landing page prototype.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Do it yourself

   Second choice

   A chat interface, chat-fluent skill, and roughly 30 minutes until you can act on the result.

   How to actually do it

   1. Open a document and gather the product description, target audience, main call to action, approved claims, brand guidance, required sections and any existing images or logos.
   2. Paste the gathered brief into the prompt, replacing every bracketed slot and leaving unknown information marked as [NEEDS INPUT].
   3. Run the prompt in a chatbot or paste the resulting structure into Relume to generate the landing page wireframe and section layout.
   4. Compare the drafted copy against your current product facts, approved pricing, feature list, testimonials and legal wording, replacing every unsupported statement.
   5. Open the prototype in desktop and mobile views and check the reading order, button destinations, form fields, text size, contrast, keyboard focus and missing states.
   6. Send the prototype to a colleague or a small group of representative users and ask them to complete the primary action, recording where they hesitate or misunderstand the page.
   7. Apply the agreed copy and layout changes, then export or publish the revised prototype for stakeholder approval.

   Prompt

   Design a landing page prototype for [PRODUCT OR SERVICE].
   
   Audience: [TARGET AUDIENCE]
   Primary goal: [SIGN-UP, BOOKING, ENQUIRY OR OTHER ACTION]
   Offer: [WHAT THE PRODUCT OR SERVICE DOES]
   Key benefit: [MAIN CUSTOMER BENEFIT]
   Required sections: [SECTIONS]
   Brand direction: [COLOURS, TYPE, TONE AND EXAMPLES]
   Required content: [FACTS, FEATURES, PROOF POINTS AND LEGAL COPY]
   Constraints: [MOBILE, DESKTOP, PLATFORM, ACCESSIBILITY OR TECHNICAL REQUIREMENTS]
   
   Create a clear, conversion-focused prototype with a header, hero section, primary call to action, supporting benefits, proof or trust section, explanation of how it works, objection handling and footer, adapting the structure when the brief requires it. Use only the facts supplied above. Mark missing content as [NEEDS INPUT] rather than inventing claims, testimonials, prices or statistics.
   
   Return:
   1. The page objective and one-sentence positioning.
   2. The proposed information architecture in order.
   3. The complete draft copy for every section.
   4. A desktop and mobile layout description, including hierarchy, spacing and responsive changes.
   5. Component and interaction notes for buttons, forms, navigation and states.
   6. A visual design direction with colour roles, typography roles and image guidance.
   7. An accessibility checklist covering contrast, headings, labels, focus states and keyboard use.
   8. A short list of assumptions and questions that must be answered before publishing.
   
   Keep the copy specific and plain. Give the primary call to action one clear label. Make the result detailed enough to build in Relume, Figma, Framer or HTML without guessing at the intended structure.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.

3. Use a tool built for this

   The distant third