Bookings that skip the marketplace

What it is

A marketplace booking is convenient and expensive: it arrives with a commission attached and a customer who belongs to the platform rather than the business.

Kora is the same transaction on the business's own site — booking, scheduling, payment, and the conversation afterwards.

How it is built

Booking, scheduling and payment as one flow

Availability, the reservation and the money in a single path, because splitting them across three tools is where double-bookings and unpaid holds come from.

Tax scoped on day one

Stripe Tax from the start rather than retrofitted. Sales tax added to a payment system after launch is a rebuild wearing the word 'update'.

Guest communications and a review pipeline

The messages before the visit and the review request after it, which is the half of a booking that marketplaces normally keep.

Kora grew out of TeeTimes, a multi-tenant tee-time booking proof of concept built to validate an engine-first architecture — Drizzle ORM, Auth.js v5, and background jobs on BullMQ and Redis. The PoC was never offered as a product; its booking and scheduling patterns became Kora's.

Our own software, not a client engagement. There are no business figures attached to it and none are claimed — the point of the link above is that you can check the work yourself.