Skip to content

What you can build

Websites, client portals, booking systems, internal tools, directories, membership areas, and the sentence that starts each one.

Last updated September 17, 2026

On this page

Web Apps builds anything that is pages plus data plus people signing in. The builder designs each one for what it is, so a law firm's portal does not look like a bakery's ordering page. Here are the shapes that come up most, with a sentence that starts each one.

Websites and landing pages

A marketing site, a service page with a contact form, a launch page with a waitlist. Real photography is picked to match, and SEO is a switch away.

  • A website for my landscaping business with our services, before-and-after photos and a quote request form.
  • A landing page for our new app with a waitlist and a launch countdown.

Client portals

Customers sign in, see what is theirs and upload what you need from them. Each customer only ever sees their own rows.

  • A portal where customers log in, see their invoices, pay what is due and upload documents.
  • A client area for my accounting practice with a document checklist per client.

Booking and scheduling

  • A booking website for my studio with a class schedule, member sign-up and confirmation emails.
  • An appointment page for my clinic with available slots and a reminder the day before.

Internal tools and dashboards

Private apps for your own team: trackers, approvals, dashboards that update from your data every night.

  • An internal tool to track equipment, who has it and when it is due back.
  • A dashboard of our weekly numbers that pulls from our orders table every morning.

Directories and marketplaces

  • Property listings with photos, filters and a viewing request form.
  • A directory of local suppliers with reviews and a listing form for suppliers.

Membership and community

  • A members area with gated videos, a community feed and a monthly newsletter sign-up.
  • A course site with lessons, quizzes and a student login.

Ordering and payments

Menus, small shops, ticketing. For card payments the app uses your own payment provider: you paste your key as a secret and the builder writes the checkout around it. See Secrets.

  • A small online shop for my ceramics with pickup and shipping options.
  • An event page with tickets, seating and check-in.

Apps that talk to other services

Anything that needs to receive a webhook, call an outside API, or push data somewhere else is a backend function away. See Receiving webhooks and Backend functions.

Start smaller than you think. The best first message names the core thing the app manages and the first job someone does with it. Add the second and third jobs in follow-up messages once the first one works.
Was this page helpful?