A website used to mean a week of picking templates, wiring CMSs, and writing placeholder copy you hated. Now you describe the site you want and an AI builder like v0, Bolt, Lovable, or even ChatGPT Canvas generates it — code, copy, and layout in one shot. The difference between a generic template and a site you'd actually ship is the prompt.

We built 12 builder prompts that cover almost every site you'll ever need to make. Each takes variables like product, audience, pages, stack, and brand_colors so you control the output without writing it from scratch. Pick your type below, copy the prompt, fill the brackets, and paste into your builder.

For selling something

1. SaaS landing page — the conversion machine. Our Build a SaaS Landing Page prompt is the most used. Give it your product, audience, and key sections and it generates hero, features, pricing, social proof, and CTA in a stack you choose (Next.js + Tailwind or React + Tailwind):

Build a SaaS landing page for [product] aimed at [audience]. Pages: [pages]. Include sections: [hero, features, pricing, FAQ, CTA]. Stack: [stack]. Brand colors: [colors].

Best starting point if you have anything to launch. Pair it later with homepage hero and pricing copy prompts to tighten conversion.

2. E-commerce store — catalog that checks out. The Build an E-commerce Store prompt builds product listings, individual product pages, cart, and checkout flow:

Build an e-commerce store for [business_type] selling [products]. Pages: [pages], features: [features]. Data needs: [inventory, payments]. Stack: [stack].

Use it when you have real products. The prompt bakes in filtering, image galleries, and state — the parts that turn a pretty grid into a functioning store.

3. Waitlist / newsletter page — launch before you build. The Build a Waitlist or Newsletter Page prompt is for the focused single that captures emails:

Build a waitlist page for [product] for [audience]. Sections: [hero, benefits, social proof, email capture]. Stack: [stack].

Highest leverage if you're pre-launch. One good waitlist page plus a real incentive beats a full site you haven't validated.

4. Agency / consulting site — trust, not themes. The Build an Agency or Consulting Website prompt adds case studies, team bios, services, and contact — the proof that sells professional services:

Build an agency site for [business_type] offering [services]. Pages: [pages], sections: [content_sections]. Stack: [stack].

Swap "agency" for coach, studio, or firm — the structure (work → team → process → contact) is universal for selling expertise.

For showing your work

5. Portfolio — the freelancer's sales page. Build a Portfolio Website is built for showcasing work with case studies, about, and contact:

Build a portfolio for [business_type] featuring [portfolio pieces]. Pages: [pages], features: [filtering, lightbox]. Stack: [stack]. Brand: [colors].

Choose Plain HTML/CSS/JS if you want to host anywhere without a framework, or Next.js + Tailwind if you want image optimization and routing for free.

6. Personal resume / CV site — one page that gets interviews. The Build a Personal Resume Website prompt turns a PDF resume into a live URL with skills, experience, education, and contact:

Build a single-page resume site for [role]. Pages: [pages], features: [features]. Stack: [stack].

Recruiters open links faster than attachments. Host it on your name and link from LinkedIn — it compounds.

7. Blog / content site — publish, don't configure. Build a Blog or Content Site handles post listings, individual post pages, categories, and author bios:

Build a blog about [topic]. Pages: [pages], features: [search, categories, author bio]. Stack: [stack].

Pick Next.js + Tailwind for MDX and SEO, Plain HTML if you just need a clean reading experience without a build step.

For organizing knowledge

8. Documentation / knowledge base — the product's second interface. Our Build a Documentation Site prompt generates navigation, search, categorized articles, and code examples:

Build docs for [product]. Pages: [pages], features: [search, versioning, code blocks]. Stack: [stack].

If users ask the same question twice, you need docs. This prompt's IA is better than most hand-rolled wikis because it starts with navigation, not pages.

9. Event / conference site — schedule that doesn't confuse. Build an Event or Conference Website covers schedule, speakers, registration, tickets, and venue:

Build an event site for [business_type] with [features]. Pages: [pages]. Stack: [stack].

Reuse for meetups, workshops, webinars — anything with a date, lineup, and signup.

For local and mission-driven

10. Restaurant / local business — menu, hours, map. Build a Restaurant Website bakes in menu, hours, location, reservations, and reviews:

Build a site for [business_type] — a local business with [features]. Pages: [pages]. Stack: [stack].

Works for cafes, salons, gyms, dentists. The pattern (proof → offer → location → book) is the same — only the menu changes.

11. Nonprofit / donation site — story that moves money. The Build a Nonprofit Website prompt centers impact stories, donation forms, and volunteer CTAs:

Build a nonprofit site for [business_type] focused on [mission]. Pages: [pages], features: [donation, impact stories]. Stack: [stack].

Donor trust is the design constraint. This prompt leads with evidence, not decoration, and makes the donation form unavoidable without being aggressive.

For internal tools

12. Dashboard / admin panel — ship the tool, not the framework. Build a Dashboard or Admin Panel generates data tables, charts, filters, and user management:

Build a [site_type] dashboard with [features]. Data needs: [data_needs]. Pages: [pages]. Stack: [stack — React, Next.js, or Vue + Tailwind].

The only prompt offering Vue + Tailwind — useful if your team is already on Vue or you want the lightest SPA for an internal tool. Mark it Advanced for a reason: it scaffolds state and roles, not just layout.

How to use these without getting generic output

Three habits that separate a site you'd ship from a template:

  1. Fill the variables like a brief, not a form. "Audience: busy freelance designers who lose clients to slow proposals" beats "audience: designers." Specificity is the designer's instruction set.
  2. Pick the stack you can actually maintain. Plain HTML/CSS/JS ships fastest and hosts free. Next.js + Tailwind scales if you'll add a blog, auth, or API later. Don't pick the cool stack — pick the one you'll touch next month.
  3. Generate, then replace copy with proof. The prompt gives you plausible copy. Replace it with your real testimonials, pricing, and numbers before you publish. Copy from the builder is the scaffold — proof is the building.

Start with the type that matches your current problem, not your dream site. Launch the SaaS landing page before the docs. Ship the waitlist before the store. One focused site that goes live beats five perfect ones in Figma.

Browse all 12 in the Promptigo library — every builder prompt is free to copy with variables you can fill in. Try Build a SaaS Landing Page, Build a Portfolio Website, and Build a Documentation Site next.