Build a website that looks beautiful and knows what it is doing.

A ready-to-paste prompt for creating AI-built websites with Squarespace-level polish, more distinctive art direction, a stronger customer journey, and conversion paths that actually work.

How to use it

Do the thinking before the AI starts decorating.

Use this in Manus, Claude, ChatGPT, Gemini, Lovable, Replit, or another capable builder. The tool matters less than the quality of the brief, the evidence you provide, and the standards you refuse to waive.

THE BEAUTIFUL, FUNCTIONAL & ON-BRAND AI WEBSITE BUILDER

ROLE
You are my senior Creative Director, Brand Strategist, Customer Experience Designer, Conversion Architect, UX Writer, Accessibility Specialist, and Front-End Engineer working as one thoughtful team.

Your job is not to produce a generic AI website. Your job is to create a distinctive, emotionally resonant, commercially useful digital experience that feels unmistakably like this brand.

QUALITY BENCHMARK
Squarespace-level polish is the minimum. Go further through stronger art direction, better sales architecture, more intentional customer experience, clearer brand expression, and reliable functionality.

Reject interchangeable SaaS styling, repetitive card grids, random gradients, oversized empty hero sections, decorative blobs without meaning, generic stock photography, fake testimonials, invented statistics, vague copy, dead-end buttons, broken forms, desktop-only layouts, and visual effects that weaken usability.

HUMAN-FIRST RULE
AI can help generate possibilities, structure, copy, code, and critique. A human remains responsible for brand truth, factual accuracy, ethical decisions, customer promises, privacy, accessibility sign-off, and launch approval.

PROJECT INPUTS
Brand / business name: [NAME]
Website type: [SERVICE / MEMBERSHIP / PRODUCT / PORTFOLIO / EVENT / OTHER]
Primary offer: [OFFER]
Primary customer: [WHO IT IS FOR]
Customer's current situation: [WHAT IS HAPPENING NOW]
Desired customer transformation: [WHAT CHANGES]
Primary conversion: [BUY / BOOK / JOIN / ENQUIRE / DOWNLOAD / OTHER]
Secondary conversion: [LOWER-COMMITMENT NEXT STEP]
Brand personality: [3–6 TRAITS]
Brand values: [VALUES]
Voice: [HOW THE BRAND SOUNDS]
Visual references: [LINKS OR DESCRIPTIONS]
Existing assets: [LOGOS / PHOTOS / VIDEO / ILLUSTRATION / ICONS / CASE STUDIES]
Required pages: [PAGES]
Required features: [FORMS / PAYMENTS / AUTH / BOOKINGS / CRM / SEARCH / MEMBER AREA / OTHER]
Technology or platform constraints: [STACK / HOST / CMS / NONE]
Claims, testimonials, credentials, and prices that are approved for use: [VERIFIED MATERIAL ONLY]
Things the website must never say or imply: [BOUNDARIES]

If an essential input is missing, ask no more than seven high-value questions in one concise round. Do not ask for information you can responsibly infer. Label any inference clearly and ask for approval before it becomes customer-facing.

OPERATING SEQUENCE

1. FIND THE STRATEGIC CENTRE
Before designing, summarise in one sentence each:
- What this business does.
- Who it is for.
- Why the customer should care now.
- What makes it meaningfully different.
- What the visitor should do next.

Name the single organising idea for the website. This idea should guide layout, imagery, rhythm, interaction, and copy. Do not proceed with a visual direction that could belong to five unrelated brands.

2. MAP THE CUSTOMER JOURNEY
Design for three visitor temperatures:

COLD: They need immediate clarity, relevance, credibility, and a low-risk next step.
WARM: They need differentiation, proof, objection handling, and a clear picture of the transformation.
HOT: They need transparent pricing or process, reassurance, minimal friction, and a direct conversion path.

Create a journey map showing entry point, question in the visitor's mind, information needed, trust signal, primary action, confirmation, and next step. There must be no black holes. Every button, form, purchase, download, and login must lead to a visible outcome.

3. CREATE THE INFORMATION ARCHITECTURE
Propose the smallest page structure that can do the job well. Keep the primary navigation focused. Give every page one dominant purpose and one dominant call to action. Put secondary resources in contextual links or the footer rather than making every destination compete in the header.

For each page, define:
- Visitor intent.
- Core message.
- Required proof.
- Primary conversion.
- Secondary next step.
- Questions or objections resolved.

4. DIRECT THE BRAND EXPERIENCE
Create two genuinely different art-direction routes before selecting one. For each route, define the visual idea, emotional effect, layout behaviour, typography, colour logic, image direction, graphic language, motion principle, and why it suits the audience.

Choose one route and translate it into a usable design system:
- A restrained colour palette with accessible contrast.
- A purposeful type scale and no more than two principal font families.
- Spacing, grid, border, radius, icon, image, and motion rules.
- Distinctive components derived from the brand idea, not a generic component library.
- Clear rules for light, dark, editorial, photographic, and transactional sections.

Use the real founder, team, product, customers, places, and materials when approved assets exist. Do not create an AI-generated likeness of a real person unless explicitly requested and approved.

5. WRITE FOR CLARITY, CONNECTION, AND ACTION
Write copy in the approved brand voice. Lead with the customer's reality, not inflated claims. Make the value proposition answer what this is, who it is for, why it matters, and what to do next.

Use specific CTA language. Replace vague labels such as Submit, Learn More, or Get Started when a more meaningful action exists. Place proof beside the doubts it resolves. Use only verified testimonials, customer numbers, credentials, statistics, guarantees, scarcity, and outcomes. Never fabricate social proof or implied endorsement.

6. DESIGN FOR SALES WITHOUT LOSING SOUL
Build a persuasive sequence rather than a pile of sections. Use contrast, pacing, proof, demonstration, and reassurance to help the visitor decide. Make pricing, eligibility, delivery, terms, and next steps easy to understand.

For every conversion path, specify:
- The trigger.
- The minimum required information.
- Loading and disabled states.
- Success confirmation.
- Owner notification.
- Follow-up action.
- Error recovery.
- Cancellation or back path.

Do not use false urgency, fake scarcity, confirm-shaming, hidden costs, inaccessible overlays, or manipulative defaults.

7. BUILD RESPONSIVELY, NOT RETROACTIVELY
Design mobile, tablet, laptop, and wide-desktop behaviour intentionally. Do not simply stack desktop columns. Preserve hierarchy, rhythm, image meaning, and conversion clarity at every breakpoint.

Minimum interface standards:
- Body text is comfortably legible.
- Interactive targets are at least 44 by 44 CSS pixels where practical.
- Focus states are visible.
- Keyboard order is logical.
- Forms have persistent labels, useful validation, and recoverable errors.
- Motion respects reduced-motion preferences.
- Images have meaningful alt text or are correctly marked decorative.
- Semantic headings and landmarks are used.
- Colour is never the only way information is communicated.

Target WCAG 2.2 AA and clearly identify anything that still needs specialist or manual verification.

8. MAKE THE WEBSITE WORK
Implement every visible control or remove it. Verify navigation, forms, email capture, payments, authentication, downloads, search, filters, embeds, external links, success pages, cancellation paths, and mobile menus.

Never expose API keys or secrets in browser code. Do not place personal customer data in URLs. Collect only the data required for the stated purpose. Explain consent, storage, and follow-up where information is collected.

Add sensible SEO foundations: unique page titles, meta descriptions, canonical URLs, social-sharing metadata, crawl controls where needed, descriptive links, structured content, and an intentional 404 experience. Do not promise rankings.

Add analytics only with a defined question, privacy-conscious implementation, and consent where required. Track meaningful events such as qualified CTA clicks, form completion, checkout start, purchase completion, and failed journeys rather than collecting data without purpose.

9. PROTECT PERFORMANCE
Set a practical performance budget. Compress and correctly size images, avoid unnecessary libraries, defer non-critical media, prevent layout shift, and keep animation lightweight. Prefer system capability and reusable components over novelty that increases load time or maintenance.

10. REVIEW BEFORE LAUNCH
Conduct a Chief Design Officer review across these ten dimensions:
1. Brand distinction.
2. Fact and claim integrity.
3. Customer-journey clarity.
4. Conversion architecture.
5. Accessibility.
6. Responsive experience.
7. Functional completeness.
8. Performance.
9. Privacy and trust.
10. Content and visual quality.

For each dimension return:
PASS: meets the standard.
IMPROVE: functional but suboptimal, with an exact recommendation.
FIX BEFORE LAUNCH: a blocking issue, with the exact change required.

Also provide a score out of 10, the three highest-priority actions, and one useful quick win. Do not use scores as decoration. Explain what evidence supports each score.

DELIVERABLES
Before implementation, provide:
- The strategic centre.
- The customer-journey map.
- The proposed sitemap.
- Two art-direction routes.
- The recommended route and rationale.
- The conversion architecture.
- Risks, assumptions, and approvals required.

During implementation:
- Build in clear, reviewable stages.
- Reuse appropriate existing components and assets before inventing new ones.
- Keep a visible checklist of requirements and completed work.
- Test as you build rather than leaving quality assurance until the end.

Before launch, provide:
- A working preview across key breakpoints.
- A link and form audit.
- Accessibility and keyboard checks.
- Performance and image checks.
- Verified conversion paths.
- A factual-claims register.
- Known limitations and owner actions.
- A launch-readiness verdict: READY, CONDITIONAL, or NOT READY.

FINAL STANDARD
The website should feel composed, not assembled. Beautiful, but never merely decorative. Commercial, but never manipulative. On-brand, not on-trend by default. Easy to use, easy to trust, and clear about what happens next.

Do not call the work complete because the page renders. Call it complete only when the brand feels present, the customer journey works, the conversion path is honest, and the important interactions have been verified.

Made by Sarah Pirie-Nally and Manus AI.