As of 13 August 2026, AI can turn your brief into a website design.

What to actually do

1. Use a tool built for this

   The route this page recommends

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 for the design work and gather the brief, brand guidelines, logo files, existing copy, required pages, target audience, business goal, technical constraints and examples of websites you like or dislike.
   2. Paste the gathered information into the prompt, replacing each bracketed slot and removing any section that does not apply.
   3. Ask the chatbot to produce the sitemap, user journeys, page wireframes, visual direction, accessibility requirements and open questions in the requested order.
   4. Open the proposed sitemap beside the original brief and mark each requirement as covered, missing or assumed; correct the prompt and regenerate any section that misses a requirement.
   5. Turn the accepted wireframes into a clickable prototype in Relume, Figma or the design tool used by your team, adding the real navigation labels, content and brand assets.
   6. Ask at least one representative colleague or user to complete the main journey, then record where they hesitate and change the prototype before sending it to development.

   Prompt

   Turn the following website brief into a practical website design proposal.
   
   Brief:
   [PASTE THE BRIEF]
   
   Business or organisation:
   [NAME]
   Primary audience:
   [TARGET AUDIENCE]
   Main user need:
   [NEED]
   Business goal:
   [GOAL]
   Primary action users should take:
   [ACTION]
   Required pages or content:
   [PAGES AND CONTENT]
   Brand direction:
   [BRAND, TONE, COLOURS, TYPE, LOGO OR OTHER ASSETS]
   Technical constraints:
   [CMS, PLATFORM, INTEGRATIONS, ACCESSIBILITY, PERFORMANCE OR LEGAL REQUIREMENTS]
   参考 websites or disliked examples:
   [LINKS OR DESCRIPTIONS]
   
   Produce the result in this order:
   1. A short summary of the design strategy.
   2. The proposed sitemap, with the purpose of each page.
   3. The key user journeys, including the entry point, decisions and desired action.
   4. A page-by-page wireframe in plain text, showing the order of sections and the purpose of each section.
   5. Suggested navigation, calls to action and content hierarchy.
   6. A visual direction covering layout, spacing, colour use, typography, imagery and components, without inventing brand assets.
   7. Responsive and accessibility requirements, including keyboard use, focus states, colour contrast, headings, form labels and mobile layouts.
   8. Three design risks or assumptions that need confirmation.
   9. Five specific questions for me before this is treated as a final design.
   
   Use only information supplied in the brief. Mark missing information as an assumption or question rather than inventing it. Keep the design suitable for a UK audience where the brief requires that. Explain the reasoning behind important structural choices, but do not claim that the design has been validated unless user research or testing is provided.

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

3. Hand it to a person

   The distant third

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