People in small groups on a rooftop terrace at dusk, string lights and rooftops behind
Use cases

Four kinds of business.
Four different jobs.

Each of these is written against what the platform actually does for that kind of place: which modules carry the weight, and what the setup looks like on day one.

Where to start

Most sites here use two of the four.

Nothing has to be decided before you begin. Turn a module on the week you need it, and leave the rest switched off.

A cook at a stove in a dark kitchen, one warm pool of light
Restaurants

Covers booked while
the kitchen is running.

Tables are allocated from the party size, so two bookings never get the same table. Holds keep a slot while somebody is still typing, and a deposit can be taken before the slot is confirmed.

Runs onBookings, forms, visitor numbers
SetupA table for every real table, opening hours as weekly rules, closures as exceptions.
The trapA service with no table behind it draws a calendar with nothing in it.
Shops and makers

A shelf that keeps
selling overnight.

Physical, digital and subscription products in one catalogue. The listing on the page is a repeater you design once, so the shop looks like the rest of the site instead of a storefront you inherited.

Runs onSelling, payments, visitor numbers
SetupA product, a payment provider, and one test order you place yourself.
The moneyHosted checkout with Mollie or Stripe. Card details never reach your site.
Finished cups and bowls drying on a ceramics worktable
People in small groups on a rooftop terrace at dusk, string lights and rooftops behind
Events

Doors at eight.
The list is already at the door.

Generate a whole run of nights at once rather than making twelve events, then sell tiers into the same cart your products use.

An empty talk venue with pale timber seating angled toward a lit stage
Events and venues

Occurrences, tiers,
and a code that scans.

One event, a run of nights, and ticket types with their own prices and allocations. Check in is its own screen, and the door list is the same record as the sale.

Runs onTickets, selling, forms
SetupAn event, its occurrences, and one ticket type per price you charge.
LiveAvailability is fetched at runtime, so a cached page never oversells a night.
Studios and services

Enquiries that arrive
already sorted.

One form, validated twice, landing in the same inbox as everything else. Then a calendar for the call that follows, with buffers so the day is not booked end to end.

Runs onForms, bookings, visitor numbers
SetupOne form, one bookable service, one person behind it.
Nice to haveArticles, so the work has somewhere to live between enquiries.
A florist wrapping tulips in kraft paper on a steel counter
Yours is probably a mix

Turn one module on.
Then the next.

A site with one page and a working contact form is a finished thing. Everything else can wait until the week it earns its place.

Week oneA home page, a contact form, and your own domain.
Week twoThe calendar, or the shelf, whichever pays first.
LaterA second language, articles, and the numbers to tell you which pages people actually read.
Restaurants · Shops · Makers · Events · Venues · Studios · Services · Clinics · RentalsRestaurants · Shops · Makers · Events · Venues · Studios · Services · Clinics · Rentals
Start

Start with the one that pays first.

Nothing is published until you say so, and the domain is the very last step.

A barista working the machine in a small coffee bar, early morning, street beyond the glass