Solutions: what changes when you build for a specific use case

A generic prompt produces a generic site. Ask any AI builder for "a website for my business" and you will get a hero, three feature cards, a testimonial strip and a contact form, because that shape is the statistical center of everything ever published. It is not wrong. It is just not built for what you do.

The differences between a site for a photographer and a site for a roofing contractor are not cosmetic. They are structural. A photographer is selling a body of work, so images are the content and the page exists to make them large, fast and uninterrupted; the conversion is an enquiry form that asks about dates. A roofing contractor is selling trust and urgency, so the phone number belongs in the header, the service area needs to be explicit, and the page has to answer "will you come to my street and can you come this week" above the fold. Same tool, different site, and no amount of restyling turns one into the other.

These pages exist to close that gap. Each one covers the page structure that actually converts for that audience, the sections worth asking the agent for by name, the settings that matter after the build, and the mistakes that show up repeatedly in that specific category. They are setup guides, not sales pages.

If you have not chosen a tool yet, start with the AI website builder guide instead — it covers the generation loop and the evaluation questions that apply regardless of who you are building for.

What actually changes between use cases

Five things vary, and everything else is more or less constant. Naming them makes it much easier to write a prompt that produces the right site the first time rather than the fourth.

Notice that only one of those five is about visual style. The reason use-case-specific setup matters is that the other four are structural decisions the model cannot infer from "make it look professional". Give it those four explicitly and the first generation lands much closer.

• The conversion action. Booking a call, submitting an enquiry, phoning immediately, buying, downloading, or applying. This decides the layout more than anything else.
• The proof that persuades. Photographs of work, credentials and licenses, named case studies, before-and-after pairs, or a client list. Different audiences trust completely different evidence.
• The content cadence. A portfolio changes a few times a year; a restaurant changes weekly; a consultancy publishing articles changes constantly. This determines whether you need blogs and how the site should be structured for editing.
• The backend requirement. Most marketing sites need none. Some need real accounts, stored records or file uploads, which is a different build with different plan requirements.
• The tone and visual register. Warm and hand-made, clinical and precise, cinematic and quiet, loud and energetic. This is the part everyone thinks about first and the part that matters least if the four above are wrong.

The twelve solution pages

Each page is written for people who already know their business and do not want a generic tutorial about websites. Pick the closest one — being roughly adjacent is usually enough, since the structural advice transfers between neighbors.

• Photographers — image-first structure, gallery performance, and enquiry forms that qualify a booking rather than just collecting an email.
• Restaurants — menus that stay current without a redesign, hours and location as first-class content, and reservations.
• Real estate agents — listing presentation, area pages, and the trust signals that make someone hand over a property.
• Local services — service-area clarity, quote requests, and getting a phone call from a first-time visitor on a phone.
• Agencies — case-study architecture, showing process without boring the reader, and pitching to people who evaluate sites for a living.
• Freelancers — a personal site that reads as a business, with a rate conversation the page starts for you.
• SaaS landing pages — positioning above the fold, a pricing table that survives contact with a buyer, and a page you can change weekly without breaking it.
• Consultants — authority-led structure, publishing cadence, and turning a reader into a scheduled call.
• Nonprofits — donation flows, program clarity, and reporting impact without overwhelming the visitor.
• Fitness coaches — program pricing, honest proof, and the delicate business of selling a personal relationship online.
• Ecommerce — product presentation, deciding what the site should own versus what a store platform should, and launch pages for a drop.
• Musicians — tour dates that stay current, embeds that do not wreck load time, and a press kit a booker can actually use.

How to get a better first generation

Whatever you are building, the same prompting discipline improves the result. The model is not reading your mind and it is not reading your market; it is filling in the parts you left blank with the most common answer it has seen.

A prompt with those five elements routinely produces a usable first draft. A prompt without them produces the statistical average of the internet, which is exactly what you are trying to avoid.

• State the business plainly, including the location if location matters to the customer.
• Name the single action a visitor should take, and say it is the priority.
• List the content you actually have — six photos, four services, two case studies — so the model builds a layout that fits real material rather than imaginary abundance.
• Give a tone in concrete terms. "Quiet and editorial, like a printed catalog" is directive; "modern and clean" is not.
• Name something to avoid. Constraints shape output far more efficiently than adjectives do.

The parts that stay the same whatever you build

Regardless of use case, the same machinery is underneath, and it is worth knowing what you can rely on before you start. Every build runs in a chat session with a live preview that updates while the agent edits, and a server-side auto-fix loop that repairs a preview the build has broken.

Every project is a real Next.js or Vite React and TypeScript codebase you can open in the built-in editor. Every plan, including Free, can publish to real production hosting. Site title, description, favicon and social share image are editable in settings for every site. Prebuilt sections and components can be inserted from a library and then restyled by the agent like any other file, and twenty-eight complete templates can be forked as a starting point.

The plan-gated pieces are the ones a business tends to need at launch rather than on day one: custom domains, visitor analytics, GitHub export and video generation on Pro and Max, blogs and repository access tokens on Max, and a managed backend for databases, auth and storage behind an explicit consent step on Pro and Max.

Last updated: 2026-08-16