Booking that is honest

The problem

When we read our own site the way a visitor would, the booking flow stood out. It showed a calendar of open times and, at the end, a six-digit confirmation code. The calendar was a picture of availability, not the real thing, and the code was never sent anywhere.

Nothing about it was meant to mislead. It was a placeholder that looked finished. But a visitor can't tell a placeholder from a promise.

How we defined it

A booking screen makes two promises: a time, and a confirmation. Ours had to keep both, or make neither.

How we solved it

First we made it honest: a plain request that said what would happen next, with no fake slots and no code. Then we kept both promises for real. The calendar now shows the open times from our actual calendar. Pick one and it is booked on the spot, and the invite reaches your inbox straight away.

• The times on screen are the times we are free.
• A booking is made the moment you confirm it, and the invite arrives by email, or by text if you ask.
• If a time is taken while you choose, the page says so and lets you pick another.

Our vision

Visitors know exactly what happens next. Every form, booking and sign-up we build now starts there: it says what it does, then does it.

A screen should never promise more than the system behind it can do.

It is tempting to make a flow look complete before it is. When the real thing isn't ready, a plain request that does exactly what it says earns more trust than a polished one that doesn't. Then build the real thing.

Read your own site like a stranger

We found this by reading every page as a first-time visitor, not as the people who built it. We now do that pass before anything we make goes live, for clients and for ourselves.

• 0Fake slots or codes left on the pageOur site, 2026-10-23
• InstantBooking and invite once you confirm a timeOur booking page, 2026-10-29