Skip to content
Loom Design guide

Starting points

Pre-filled briefs for common kinds of site.

A starting point is not a file template — nothing is copied into your project. It is a set of decisions already made (this look, this palette, these sections, this voice) plus an opening instruction written the way someone who knew what they were doing would write it.

The [square brackets] are the parts to replace with your own details. Read one even if you do not use it — they are the clearest example of what a good brief looks like.

Local business

Restaurant or café

Warm hospitality · spacious · warm

Menu, hours, address and a table booking form.

Have ready

  • Your address and opening hours
  • A few dishes with prices
  • One or two photographs

Opening instruction

Build a site for [name], a [type of food] restaurant in [town]. We are open [days and hours] at [address], phone [number]. Show a short menu with these dishes and prices: [dish — price, dish — price, dish — price]. Include a table booking form that captures the date, time, number of people, name and phone number. The tone should sound like the people who cook the food, not a marketing agency.

Builds: nav → opening → services → gallery → hours → booking → footer

Trade or local service

Clinical trust · comfortable · plain

What you do, the area you cover, and a way to get a quote.

Have ready

  • The services you offer
  • The area you cover
  • Any certifications or insurance

Opening instruction

Build a site for [name], a [trade] business covering [area]. The services are: [list them]. We are [certifications, insurance, years in business]. Explain how a job works from first call to finished work in clear steps. Include a quote request form asking for the job type, address, and how to reach them. Be plain and factual — no salesmanship.

Builds: nav → opening → services → process → proof → hours → contact → footer

Clinic or practice

Clinical trust · comfortable · authoritative

Treatments, practitioners, and an appointment request.

Have ready

  • Treatments and prices
  • Practitioner names and registrations
  • Opening hours

Opening instruction

Build a site for [name], a [type] clinic in [town]. Treatments offered: [list with prices if you publish them]. Our practitioners are [names and registrations]. We are open [hours] at [address]. Include the questions patients always ask, answered directly. Add an appointment request form. The tone must be calm and credentialed — never urgent, never salesy.

Builds: nav → opening → services → team → faq → hours → booking → footer

Product

Software product

Technical precision · comfortable · technical

What it does, what it costs, and how to start.

Have ready

  • What the product does, in one sentence
  • Your pricing tiers
  • The main limits or specifications

Opening instruction

Build a landing page for [product], which [does what, for whom]. The capabilities are: [list them concretely — no benefit language]. Pricing: [tier — price — what is included, repeated]. Show real limits and numbers in a specification table rather than feature cards. Include an email signup for early access. Write for a technical reader who already understands the problem.

Builds: nav → opening → services → prices → faq → signup → footer

Open-source tool

Terminal native · compact · technical

Install command first, explanation second.

Have ready

  • The install command
  • A usage example
  • The repository link

Opening instruction

Build a page for [name], a [language] tool that [does what]. Install with: [command]. Show a real usage example with its actual output. List what it does and what it deliberately does not do. Link to the repository at [url]. Everything monospace, left-aligned, no marketing tone — describe it the way a README would.

Builds: nav → opening → services → process → footer

Personal

Portfolio

Archive quiet · comfortable · plain

An index of work, not a gallery of squares.

Have ready

  • Your projects with dates and clients
  • What you do and want more of

Opening instruction

Build a portfolio for [name], a [discipline] based in [place]. List this work as an index with years and clients: [project — year — client, repeated]. Write one honest paragraph about what I do and the work I want more of. Include a way to get in touch. Start with the work — no hero section, no tagline about passion.

Builds: nav → opening → gallery → about → contact → footer

Writing or newsletter

Editorial calm · spacious · plain

Built for reading, with a signup.

Have ready

  • What you write about
  • A few piece titles
  • How often you publish

Opening instruction

Build a site for [name], who writes about [subject]. List recent pieces: [title — date, repeated]. Say plainly what someone gets by subscribing and how often it arrives. Include an email signup. Optimize the whole page for reading — long measures, generous line spacing, nothing that competes with the text.

Builds: nav → opening → gallery → about → signup → footer

Professional

Studio or agency

Editorial calm · spacious · direct

Services, process and evidence.

Have ready

  • Your services
  • How you work, in stages
  • Clients or case studies you can name

Opening instruction

Build a site for [name], a [discipline] studio in [place]. We do: [services]. Our process is [stages]. We have worked with [clients you can actually name]. Include a short enquiry form asking about the project and its budget range. Be direct and confident — short sentences, no adjectives we cannot back up.

Builds: nav → opening → services → process → proof → team → contact → footer

Law or financial practice

Clinical trust · comfortable · authoritative

Credentials, areas of work, and a consultation request.

Have ready

  • Areas of practice
  • Regulatory registrations
  • Fee structure if you publish it

Opening instruction

Build a site for [firm], a [practice type] in [place]. Areas of work: [list them]. We are regulated by [body] under [number]. Our people are [names, qualifications]. Explain how fees work: [structure]. Include the questions clients ask before engaging, answered directly, and a consultation request form. Measured and precise throughout — no urgency, no superlatives.

Builds: nav → opening → services → team → proof → faq → contact → footer

Announcement

Event

Poster bold · comfortable · direct

Date, place, who is on, and how to come.

Have ready

  • Date, time and venue
  • The line-up or schedule
  • Ticket details

Opening instruction

Build a page for [event], on [date] at [venue, place]. The line-up or schedule is: [list with times]. Tickets are [price and where to get them]. Make the date and the name enormous — this should read like a poster. Include an email signup for people who miss it. Very short copy, all of it factual.

Builds: nav → opening → process → services → hours → signup → footer

Launch or waiting list

Poster bold · spacious · direct

One claim, one signup, nothing else.

Have ready

  • What you are launching
  • When
  • One reason to care

Opening instruction

Build a single-page announcement for [thing], arriving [when]. It [does what, in one sentence]. Give three concrete specifics — not benefits, specifics. Include an email signup with one honest line about what subscribers will receive. Keep the whole page under one screen and a half. No navigation, no footer links beyond the essentials.

Builds: opening → services → signup → footer

Catalog

Directory or listings

Utility dense · compact · plain

Many items, findable fast.

Have ready

  • The items with their details
  • How people want to filter them

Opening instruction

Build a listings site for [what is being listed] in [place or category]. Each entry has [fields: name, price, location, availability]. Here are the entries: [list them]. Lay them out as a dense table with visible filters for [the fields people search by]. Do not use a card grid — a table carries more and scans faster. Keep the header small so the listings start high on the page.

Builds: nav → opening → services → prices → faq → contact → footer

Next Why sites look AI-made →