Most service businesses should not build a booking engine. Rent one, embed it on a website you own, and keep the brand and the client list under your name. Custom only pays off when you book things a staff calendar cannot describe, or when bookings have to drive orders, stock or a CRM.
I build booking flows, online stores and internal systems at DodaCraft, so you might expect me to sell you a custom build. This post explains why I usually don't, and the specific cases where I would.
Short answer: should you build or buy a booking system?
Buy the booking engine and own the front door. If your bookings are "client picks a service, a staff member and a time", a booking SaaS already does that well for a monthly fee. Build only when the resource, payment or integration rules are specific enough that you would spend your days working around a SaaS tool.
What did Creative Hair Stories actually do?
Creative Hair Stories is a hair studio in Vilnius. It used to take bookings through a shared beauty-services marketplace. The marketplace handled the calendar fine, but the studio could not show its own style, collections or team there. Its old website was slow and in one language.
We did not write a booking engine. The new site runs on Next.js with Strapi as the content system, in several languages, and booking happens through Microsoft Bookings embedded on the studio's own website. The studio edits services, team members and photo collections itself, and analytics shows how visitors move through the booking step.
The calendar logic is rented. The brand, the content and the first impression belong to the studio. For a studio with staff calendars and a service menu, I think that is the right split.
What are the options, and who owns the client data?
There are four realistic setups. Prices below come from the vendors' own pricing pages at the time of writing.
| Option | Typical cost model | Who holds the client relationship | Fits |
|---|---|---|---|
| Marketplace platform (Fresha, Booksy, Treatwell) | Monthly fee per staff member, plus a fee on new clients found through the marketplace | The platform, under its terms | New businesses that need discovery more than brand |
| Booking SaaS embedded on your own site | Monthly subscription, sometimes bundled with tools you already pay for | You, through your account | Salons, clinics, consultants, studios |
| Booking SaaS plus integrations | Subscription plus a one-off integration build and some upkeep | You | Businesses that need bookings to reach a CRM, invoicing or email tool |
| Custom-built booking system | Large one-off build, hosting, ongoing maintenance | You, fully | Unusual resources, complex payments, bookings tied to orders or stock |
Some concrete numbers. Fresha's pricing page lists €12.95 per month for an independent professional and €8.95 per bookable team member per month on the Team plan, plus a one-time fee on brand-new clients who find you through the Fresha marketplace. The page does not state that fee clearly, so ask before you sign. Booksy's US pricing page lists $29.99 per month plus $20 per additional staff member, and its Boost feature charges a one-time 30% of a new client's first visit, capped at $100.
On the SaaS side, Microsoft's documentation lists Bookings as included in Microsoft 365 Business Basic, Business Standard and Business Premium, among other plans. If you already pay for Microsoft 365 for email, the booking engine may cost you nothing extra.
What does a real booking system have to handle?
People underestimate this list. A booking SaaS has spent years on it. A custom build has to get every item right before the first client books.
- Availability. Working hours, breaks, days off, holidays, and different hours per staff member or location.
- Buffers. Cleanup or travel time between appointments, and minimum notice before a booking.
- Double-booking prevention. Two clients clicking the same slot at the same second must not both succeed. This needs locking at the database level, not a check in the browser.
- Time zones and daylight saving. Your calendar, the client's phone and the server can all disagree, and the clock change in spring and autumn breaks naive code.
- Cancellations and rescheduling. Cut-off times, who may cancel, what happens to a deposit.
- Reminders. Email and SMS at the right moment, in the client's language.
- Deposits and payments. Taking money at booking, refunds, no-show fees, packages and memberships.
- Staff permissions. Who sees whose calendar, who can move appointments, who sees client notes.
- GDPR. Consent, data retention, export and deletion requests, and where the data is stored.
If your needs are covered by this list in its plain form, a SaaS tool already solves it. Custom work starts to make sense when one of these items has a rule that no tool supports.
When does a custom booking system make sense?
These are the cases where I would recommend building, or at least building part of it:
- You book resources other than people. Rooms, equipment, vehicles, delivery slots, each with its own capacity and rules. Most salon tools model staff calendars well and everything else poorly.
- Payments are more than "pay at the counter". Deposits that depend on the service, prepaid packages, memberships with monthly allowances.
- Several locations share staff or resources with rules about who works where and when.
- Bookings must drive other systems. A booking creates an order, reserves stock, updates a CRM record or triggers an invoice.
- Marketplace fees keep growing. If most new clients arrive through a marketplace that charges on each of them, add up a year of those fees and compare.
A related example from an online store: FlowerSweets, a flower shop in Dublin, needed same-day delivery and holiday days when no orders are accepted. Off-the-shelf platforms did not fit, so the date logic was built custom inside a Medusa.js store, and the store now blocks holiday days on its own. That is availability logic, but it lives inside an order flow, which is exactly where custom pays off.
Build vs buy checklist
Answer these honestly. If most of your answers point to "buy", embed a SaaS tool on your own site and spend the budget on the website.
- Is every booking "one client, one service, one staff member, one time slot"? If yes, buy.
- Do you book anything that is not a person's time? If yes, check whether a tool supports that resource before you consider building.
- Do you take deposits, sell packages or run memberships with rules a tool cannot express?
- Does a booking need to create or change something in another system, such as an order, stock level or CRM record?
- Do you run several locations with shared staff or rooms?
- Have you added up a year of marketplace fees per new client and compared it with a subscription?
- Can you export your client list today, in a format you could import elsewhere?
- Who will maintain a custom system in three years, and is that cost in your budget?
How much does a custom booking system cost?
Agency figures vary a lot because "booking system" covers a widget and a platform alike. Morningtrain, a Danish agency, quotes a range of DKK 10,000 to 1,000,000. Kolonell puts a custom booking platform at roughly €20,000 to €55,000 and 3 to 5 months of work. Those are their numbers, not mine, but they match the scale I would expect for a full platform with payments, admin and multiple locations.
Many businesses only need one piece. A delivery-slot rule inside a store, a resource calendar next to an existing booking tool, or an integration that pushes bookings into a CRM is a scoped job. My booking system work starts from €1,499, with the final quote and timeline in writing before work starts. A full platform with several locations and its own admin costs much more, and if a monthly subscription would do the job, I will say so on the first call.
If you are also weighing a spreadsheet against a custom admin system, I wrote about that in when to replace spreadsheets with an internal tool.
FAQ
How much does a custom booking system cost?
It depends on how much logic sits behind the calendar. A scoped tool that handles one specific booking rule next to an existing system starts from €1,499 with me, while a full booking platform with payments, multiple locations and its own admin is a five-figure project. Agencies publish ranges of roughly €20,000 to €55,000 for a custom platform.
Should a small salon or studio build its own booking system?
Almost never. A hair studio, clinic or consultant with staff calendars and a list of services is exactly what booking SaaS is built for. Put the money into your own website and embed the booking tool there.
Who owns client data on a beauty marketplace?
The marketplace holds the client records and the relationship, and its terms decide what you can export and when. On your own website with an embedded booking tool, the account and the client list sit under your business. Read the export terms before you commit either way.
Is Microsoft Bookings good enough for a small business?
For staff-and-service appointments it is a reasonable choice, and Microsoft lists it as included in Microsoft 365 Business Basic, Standard and Premium. It is weaker when you need rooms, equipment or complex payment rules. Creative Hair Stories uses it embedded on its own site.
When does a custom booking engine pay off?
When you book things a staff calendar cannot model, like rooms, vehicles or delivery slots, or when bookings must drive orders, stock or a CRM. Marketplace commissions on every new client can also tip the maths over a few years.
Tick what you need and see the starting price straight away.
Founder of DodaCraft, developer. I build websites, online stores and internal systems for businesses in Lithuania and abroad. I taught teenagers to programme for 7 years.
