daybooked.io

The Challenge

A small business that teaches, coaches or rents things out sells three different shapes of time: seats in a group class, a private session with one person, and equipment by the hour or the day. Booking systems built around one of those tend to bend the other two to fit, and much of that software is priced per booking, as a cut of the business's sale or a fee added to the guest's total. Meanwhile the work around each booking (opening another class when one sells out, reminding tomorrow's guests) falls to people who would rather be teaching, and the software that could take it off their hands, a developer's script or an assistant acting for them, usually has no way in.

Our Solution

We built daybooked API-first and deliberately small. Classes, private sessions and rentals are three shapes of availability on one booking engine, and every booking goes through a single Postgres function that locks the offering and checks capacity, so the last seat only ever sells once. Each capability is written once, as an operation in a shared registry, and the dashboard, a REST API with its OpenAPI spec, and an MCP server all run those same operations with the same validation and the same errors. Guests book through a one-line widget on any website or a hosted booking page, and on Pro they pay by card straight into the business's own Stripe account. Every change becomes an event, delivered in order to signed webhooks. An ops agent comes with every account: it opens the next session when one fills, sends a morning brief and guest reminders, and each automation sits behind a dial (Off, Ask me, Do it and tell me, Do it quietly) inside guardrails the business sets.

Results