# Booking systems for service businesses | Plyo

> Off the shelf, embedded or built in: what each costs you in money and in control, and how to tell which your business actually needs.

Source: https://plyo.studio/blog/booking-systems-for-service-businesses

1.  [Home](/)
2.  [Blog](/blog)
3.  Booking systems for service businesses

# Booking systems for service businesses

Off the shelf, embedded or built in: what each costs you in money and in control, and how to tell which your business actually needs.

Plyo Studio 20 July 2026 8 min read

On this page

[Three routes](#three-routes)[When off the shelf is the right answer](#when-off-the-shelf-is-the-right-answer)[When to build](#when-to-build)[What a good booking flow has, whichever route you take](#what-a-good-booking-flow-has-whichever-route-you-take)[The parts people forget](#the-parts-people-forget) [Common questions](#common-questions)

Related service

[Application development](/services/app-development)

Taking bookings online removes the phone tag that costs you jobs. The question is not whether to do it, but how much of it to build.

## Three routes

**A hosted tool with its own page.** Calendly, Cal.com, Acuity. Fastest to set up, cheapest, and the booking happens on their domain under their branding. Good when the booking is simple and the volume is low.

**The same tool embedded in your site.** The visitor stays on your page; the booking logic is still theirs. The practical middle ground for most service businesses, and the one we recommend most often.

**Built into your site.** Your own form, your own availability rules, your own database. Right when the rules are specific enough that no tool fits, or when the booking has to touch something else you run.

## When off the shelf is the right answer

If a booking is one person, one duration, one location and a calendar invite, do not build anything. The tools are mature, they handle time zones and reminders properly, and they cost less per year than a day of development.

Embed it rather than linking away. A visitor sent to a different domain mid enquiry is a visitor you can lose.

## When to build

Build when the rules are yours:

-   **Resources, not just people.** A room, a machine and an operator all have to be free at once.
-   **Travel time between jobs.** A two hour buffer for a van crossing the city, but not for two jobs on the same street.
-   **Pricing that depends on the answers.** A quote that changes with access, materials or duration.
-   **Deposits that are conditional.** Taking a deposit only above a certain value.
-   **It has to talk to your other systems.** The booking creates a job in the system your team already uses.

If two or more of those apply, the configuration work to force a hosted tool into shape usually costs more than building the thing properly, and it stays fragile.

## What a good booking flow has, whichever route you take

-   Availability that reflects reality, fed by the calendar your team actually uses
-   A confirmation on screen and by email within seconds
-   A reminder a day before, by email and ideally SMS
-   A way to reschedule that does not require a phone call
-   A clear cancellation window stated before payment
-   Something sensible when it breaks: a phone number, not a blank page

## The parts people forget

**Time zones and daylight saving.** If you ever serve another region, store everything in UTC and render in the visitor’s zone. This is where homegrown systems fail first.

**Double booking.** Two people on the same slot at the same moment. Needs a real lock at the database level, not a check in the browser.

**Cancellations and no-shows.** Decide the policy before launch and put it on the page. Retrofitting it annoys people who already booked.

**Who owns the data.** If the tool holds your customer list and you later want to leave, check the export before you commit, not after.

## Keep reading.

[All posts](/blog)

-   [
    
    Apps & AI Practical AI automations for small businesses 7 min read](/blog/practical-ai-automations-for-small-businesses)
-   [
    
    Apps & AI Customer portals and dashboards: build or buy? 7 min read](/blog/customer-portals-and-dashboards-build-or-buy)
-   [
    
    Platforms Choosing a domain and setting up business email 7 min read](/blog/domain-names-and-business-email)

Updated 20 July 2026

FAQ

## Common questions

[Ask a question](/contact)

### How much does a custom booking system cost?

It depends entirely on the rules. A simple one tied to an existing calendar is a few days of work. Resource scheduling with travel time and conditional pricing is a project, not a feature.

### Can I take payment at the time of booking?

Yes, through Stripe or a similar provider, whether the booking is hosted or built. Take a deposit rather than the full amount for anything that needs a site visit to price.

### Will a booking form hurt my page speed?

An embedded third party widget adds weight, sometimes a lot. Load it only when the visitor opens it rather than on every page, and the cost disappears.

### Can bookings go into Google Calendar?

Yes. Two way sync is standard in hosted tools and straightforward to build, so staff availability stays accurate without anyone maintaining a second calendar.

### What happens if the booking system goes down?

Show a phone number and an email address on the same page. The failure case is the part most people skip, and it is the part customers remember.

About Plyo Studio

## Custom Astro websites. Built on Cloudflare.

Plyo Studio is an independent web studio that designs and builds fast, search-ready websites, web apps and interactive maps. Sites are custom-built in Astro and hosted on Cloudflare, so they load quickly and are easy for search engines and AI answer engines to read.

Founded by Chloe Nixon, a full stack developer and UI/UX designer from Australia, and Micky, a software engineer from New Zealand. Clients work directly with the founders from the first call to launch. Typical work: custom websites, migrations off Webflow, WordPress, Wix and Squarespace, web apps, and interactive maps and GIS. Projects are quoted at a fixed price before work starts.

[Start a project](/contact) [hello@plyo.studio](mailto:hello@plyo.studio) [About us](/about)

## Related pages

-   [Blog Read practical notes on designing, building and moving websites.](/blog)
-   [Application development Dashboards, portals and internal tools people use every day.](/services/app-development)

Start a conversation

## Ready for a website that works harder?

[Start a project](/contact) [Free website audit](/audit)
