How it works

The easiest version is one universal booking engine with client-specific settings.

This page explains the operational model you should sell: a hosted booking and follow-up system that gets customized by the client’s onboarding answers, then embedded into their current site or shared as a direct booking link.

Client-facing model

What the client sees

  • Pays the setup fee and chooses their support plan
  • Fills out the onboarding form with service, hours, intake, and notification rules
  • Gets a hosted booking page and embed snippet
  • Shares that booking flow on their site and socials

Your backend model

What you manage

  • Store client configuration in one master data source
  • Run one booking automation engine in Make
  • Send notifications to the business based on their preferences
  • Push booking data to Sheets, email, and calendar workflows

Recommended stack

Fastest route to launch

  • Frontend: your hosted booking page and embed snippet
  • Automation: Make for routing, notifications, and follow-up
  • Storage: Google Sheets first, database later
  • Calendar connection: Google Calendar or the client’s booking tool if they already use one
  • Payments: Stripe links for setup and recurring billing

Why this is easier

Do this before trying to build a full SaaS app

  • You can launch faster with one static sales site and one automation backend.
  • Clients do not need to learn a complicated new dashboard right away.
  • Most service businesses only care that bookings come in and they get notified.
  • You can upgrade later into a full client portal once the process is proven.

Operational flow

What happens after a customer books

01

Customer submits the booking form

The hosted form collects the business-specific intake questions, desired service, and contact details.

02

Make routes the data

The automation identifies which client profile to use, logs the request, and triggers the proper business-side notification.

03

Follow-up logic runs automatically

Confirmation, reminders, and follow-up messages go out using the rules you saved from that client’s onboarding form.

Embed example

What you eventually give clients

<iframe
  src="https://yourdomain.com/book.html?client=bb-sample-spa"
  width="100%"
  height="880"
  style="border:0;border-radius:24px;overflow:hidden"
  loading="lazy">
</iframe>

For social media, the client can also use the direct hosted link instead of the iframe.

Important reality check

What still needs backend work beyond this website

  • This site now sells the offer and collects onboarding.
  • The universal booking flow itself should be your next build after this refresh.
  • You still need the Make scenarios, Sheets structure, and booking page implementation behind the scenes.
  • That is normal. The easier path is to sell the service first and power it with one backend engine.

Next page

Use the onboarding form to collect the exact client data this backend will need.

Open onboarding