Fire your landing page builder and own your bookings

You spent a weekend on the Squarespace template. The hero photo is gorgeous. The fonts are good. There's a kind, well-written paragraph about your approach to vinyasa. At the bottom of the page, a confident button: Book a class.

Click it.

You're now on Eventbrite. Different colours, different fonts, a cookie banner, a sign-in nag, an upsell for a music festival in Bristol. By the time someone finds your actual class, half of them have closed the tab.

This is the most common booking setup I see for UK instructors, and it's almost always the single biggest leak in the funnel.

The handoff is where you lose people

Conversion isn't usually killed by a bad website. It's killed by the seam between websites. Every time you punt a visitor from one domain to another, you pay a tax:

• They lose trust — different branding feels like a different company
• They see new logins, new accounts, new privacy banners
• The booking platform's own funnel kicks in (their pricing, their suggested events, their sign-ups)
• Mobile becomes a coin-flip — half the time the redirect doesn't behave

A student who is 90% convinced on your beautiful page can become 40% convinced by the time the Eventbrite spinner finishes loading. And the 40% group doesn't book.

The pretty landing page isn't doing what you think. It's doing the warm-up. The booking page is doing the closing. If those two pages feel like different shops, you've lost.

"But I'm not a developer"

Fair. The reason this setup is everywhere is that Wix, Squarespace and friends made the marketing page trivial, while the booking page stayed hard. So everyone outsourced the hard bit and lived with the seam.

That trade-off made sense in 2018. It doesn't anymore. There are now booking tools that either run on your own domain or skin themselves so closely to your site that the seam disappears.

Here's what "owning your bookings" actually looks like in practice:

1. The "Book a class" button goes to a page on your domain — yourstudio.co.uk/book, not eventbrite.com/e/12345.
2. The colours, fonts, and copy match the rest of the site. No new login. No cookie banner from a third party.
3. The student picks a class, pays, and gets a confirmation email from you, not from a platform they've never heard of.
4. If they want to cancel or reschedule, they do it on your site too.

You don't need to build any of that. You need to pick a tool that defaults to it.

What to look for instead

A few practical things to check when you're shopping for a booking tool that doesn't break the seam:

• Custom domain or full white-label. Booking page lives at book.yourstudio.co.uk or as an embed on your existing site, not on the vendor's domain.
• No vendor branding in the confirmation email. Or at least, you can hide it. If "Powered by Eventbrite" goes out on every receipt, you're still in their funnel.
• A booking flow that fits on one screen. Pick class, enter card, done. Not a five-step wizard.
• Their checkout reads as yours. Even if it's a hosted Stripe page, the merchant name should be your business name, not the platform's.

If you can tick those four, the handoff disappears. Students stay in your world from first click to first class.

The smaller, related thing

Owning the bookings has a second benefit that nobody talks about until they switch: you stop paying the platform's per-ticket fees on top of Stripe's. Eventbrite, in particular, can take a meaningful slice on every booking once you add their service fee and payment processing. For a £15 yoga class, that's the margin you were going to spend on coffee.

The economics shift quickly. A flat monthly fee for owning the whole flow tends to undercut the per-booking model by the time you're doing more than about 40 bookings a month, and you keep the customer relationship.

If you'd like to see what owning your bookings looks like in the wild, Adminished runs the entire flow on your domain by default — students never see our brand unless you want them to.