One calendar the whole yard can trust.

The problem

Three resources that must never collide

A riding club runs on an instructor, an arena and a horse. Every lesson needs all three, free at the same time, and no two lessons can claim the same one. Most clubs coordinate that on a whiteboard, a WhatsApp group and one person's memory.

That works until the person who remembers takes a week off, or until two coaches book from two separate lists and a horse ends up working six times on a day it should have done three.

What it does

One schedule, one record, one page that says who paid

The schedule

Instructors, arenas and horses sit on a single calendar. A double booking is refused at the moment somebody tries to make it, not discovered on the yard afterwards.

Horse welfare

Each horse carries a daily session cap. The cap is enforced by the system when the booking is taken, counted in your club's own local day, so it holds no matter who is on the desk.

Records

Riders, guardians, horses, arenas, instructors and lesson types, in one place that outlives whoever set it up. Junior riders carry the guardian who signs and books for them.

The money trail

Lessons become invoices, and invoices give you a straight answer to who has paid and who owes, without reconstructing a month from a notebook.

Evidence

An append-only log of who changed what and when, readable by the club, so a disputed booking or balance has an answer.

How it is built

The rules are enforced by the database, not by good intentions

A warning message gets clicked through on a busy Saturday. So the scheduling rules are not warnings. Instructor, arena and horse conflicts, lesson capacity, and horse welfare caps are constraints inside the database itself, which means an impossible schedule physically cannot be saved, whatever the application or the person using it does.

No language model sits anywhere near a booking, a price or a payment. Those are ordinary deterministic code and database rules, so the same inputs give the same answer every time, and there is nothing to hallucinate.

Early access

The first clubs shape the order of the work

Hesani is in active development and the first group of clubs gets in early. What they tell us about their week decides what gets built next, which is a far better roadmap than guessing from the outside.

If your yard runs on a whiteboard and a WhatsApp thread, that is exactly the input worth having.