More insights.
Subscribe to our newsletter.
Deep dives into design thinking, creative process, and the intersection of business and aesthetics.
Rent the booking tool, but keep the website and the customer your own.
A hotel or clinic signs up to a booking platform such as Fresha, Mindbody or SynXis, and before long the booking engine is shaping the whole website. The service menu moves to the vendor's pages, and the question of how to win a customer gradually turns into the question of how to take their payment. We see this often in hospitality and service businesses.
A booking engine is a utility, closer to the card terminal on your reception desk than to anything that sells. You wouldn't let the card terminal decide how your lobby looks, and the booking vendor shouldn't decide how your brand looks online.
A booking engine won't do the selling for you
Booking platforms are built to work dependably for a great many businesses at once, which is why they all look alike. They aren't built to explain what's different about your treatment rooms, or why the walk from your hotel to the river matters. If the booking tool does most of the talking, you look like everyone else using it.
That job can't be handed to a software company that has never set foot on your premises. If customers spend more time on vendor-url.com than on your own domain, your marketing budget is building the vendor's brand.
The lock-in costs arrive after you've signed
If your services or room types are only described on the vendor's domain, that's where the search visibility builds up. You're paying for the tool and improving its rankings at the same time.
Then there's the customer record. Find out now who owns it, and whether your booking history leaves with you in a usable format if you switch provider. That's a harder conversation once you're already on your way out.
Booking widgets also tend to bring third-party scripts that slow pages down, which shows up in your Core Web Vitals and, more to the point, in how many people finish a booking.
Most of this only shows when the vendor changes its terms and you realise how much of the operation sits on land you don't own.
Persuade on your own domain, hand off at the last step
Everything that persuades (the photography, the room and treatment descriptions, the policies, the reasons to choose you) should sit on your own website, where you control how it looks and what it says. The booking engine takes over only once someone has decided to book. Depending on the platform, that means either building your own booking screens on the vendor's system or handing off cleanly to its hosted pages.
Done well, the customer barely notices the switch. The booking pages carry your fonts and colours, so nobody lands on a clunky grey form and wonders if they're in the right place.
Answer the doubts before the booking form
Every booking form adds friction, so put the effort into the pages before it: fewer steps, and doubts settled early. Explain cancellation and deposit policies before anyone starts, so nobody meets them for the first time on the payment screen and gives up.
Reassurance goes where people hesitate: a guest review beside the price, a plain note about secure payment just before the hand-off. A generic booking tool won't put those things there for you.
Track the booking across both domains
The hardest part to measure is the gap between your site and the booking engine, where analytics tends to lose people. Set up cross-domain tracking so you can see whether people drop out at the price list, the calendar, the account sign-up or the deposit screen. Once you know where they give up you can fix it, and that can recover bookings the business didn't know it was losing.
Four questions to put to a booking provider before you sign
Can the booking pages live on your own subdomain, such as
book.yoursite.com, instead of their address?Can you export your customer data easily, and in what format?
Can you set your own meta descriptions and schema on the booking pages?
If you leave, what does moving to another provider involve, and how long does it take?
Treat the booking engine as what it is, a supplier. A good one will answer those questions without much hesitation. If you've already signed, ask anyway: the answers tell you how much of your business you're renting, and what it would take to get it back.
Related Brainstorm services and work
Hospitality and tourism website design · The Red Hen website case study · Discuss a booking-led website
Updated 24 September 2026. Dave Curtin, founder and Creative Director of Brainstorm, leads website strategy, brand direction and technical delivery for Brainstorm clients.
Rent the booking tool, but keep the website and the customer your own.
A hotel or clinic signs up to a booking platform such as Fresha, Mindbody or SynXis, and before long the booking engine is shaping the whole website. The service menu moves to the vendor's pages, and the question of how to win a customer gradually turns into the question of how to take their payment. We see this often in hospitality and service businesses.
A booking engine is a utility, closer to the card terminal on your reception desk than to anything that sells. You wouldn't let the card terminal decide how your lobby looks, and the booking vendor shouldn't decide how your brand looks online.
A booking engine won't do the selling for you
Booking platforms are built to work dependably for a great many businesses at once, which is why they all look alike. They aren't built to explain what's different about your treatment rooms, or why the walk from your hotel to the river matters. If the booking tool does most of the talking, you look like everyone else using it.
That job can't be handed to a software company that has never set foot on your premises. If customers spend more time on vendor-url.com than on your own domain, your marketing budget is building the vendor's brand.
The lock-in costs arrive after you've signed
If your services or room types are only described on the vendor's domain, that's where the search visibility builds up. You're paying for the tool and improving its rankings at the same time.
Then there's the customer record. Find out now who owns it, and whether your booking history leaves with you in a usable format if you switch provider. That's a harder conversation once you're already on your way out.
Booking widgets also tend to bring third-party scripts that slow pages down, which shows up in your Core Web Vitals and, more to the point, in how many people finish a booking.
Most of this only shows when the vendor changes its terms and you realise how much of the operation sits on land you don't own.
Persuade on your own domain, hand off at the last step
Everything that persuades (the photography, the room and treatment descriptions, the policies, the reasons to choose you) should sit on your own website, where you control how it looks and what it says. The booking engine takes over only once someone has decided to book. Depending on the platform, that means either building your own booking screens on the vendor's system or handing off cleanly to its hosted pages.
Done well, the customer barely notices the switch. The booking pages carry your fonts and colours, so nobody lands on a clunky grey form and wonders if they're in the right place.
Answer the doubts before the booking form
Every booking form adds friction, so put the effort into the pages before it: fewer steps, and doubts settled early. Explain cancellation and deposit policies before anyone starts, so nobody meets them for the first time on the payment screen and gives up.
Reassurance goes where people hesitate: a guest review beside the price, a plain note about secure payment just before the hand-off. A generic booking tool won't put those things there for you.
Track the booking across both domains
The hardest part to measure is the gap between your site and the booking engine, where analytics tends to lose people. Set up cross-domain tracking so you can see whether people drop out at the price list, the calendar, the account sign-up or the deposit screen. Once you know where they give up you can fix it, and that can recover bookings the business didn't know it was losing.
Four questions to put to a booking provider before you sign
Can the booking pages live on your own subdomain, such as
book.yoursite.com, instead of their address?Can you export your customer data easily, and in what format?
Can you set your own meta descriptions and schema on the booking pages?
If you leave, what does moving to another provider involve, and how long does it take?
Treat the booking engine as what it is, a supplier. A good one will answer those questions without much hesitation. If you've already signed, ask anyway: the answers tell you how much of your business you're renting, and what it would take to get it back.
Related Brainstorm services and work
Hospitality and tourism website design · The Red Hen website case study · Discuss a booking-led website
Updated 24 September 2026. Dave Curtin, founder and Creative Director of Brainstorm, leads website strategy, brand direction and technical delivery for Brainstorm clients.