About
Built by someone who runs the yard.
Who is behind Hesani, why it exists, and what is deliberately not being claimed.
Who
Built by someone who runs the yard, not just the software
Hesani is built by an operator who runs a working equestrian business in the UAE and who is the customer for this product. The problem it solves is a problem lived weekly: chasing payments after the lesson was taught, rebuilding last month from a notebook, and finding out on the day that a horse was booked twice.
That is the credential that matters here: the person building it is the person who has to live with it.
Why
Why this rather than an existing system
Most club software is built for gyms, salons or generic classes, then bent into an equestrian shape. It has no concept of a horse as a bookable resource with a welfare limit, or of a coach who is a schedulable record rather than a staff login, or of a junior rider whose guardian signs for them.
Those are not edge cases at a riding club. They are the ordinary week. Building around them from the first line is easier than retrofitting them later.
How it is being built
Slowly where it is load bearing
The parts that are expensive to get wrong are being built first and hardened before anything is layered on them: keeping one club's data structurally unable to reach another club's, and making an impossible schedule impossible to save. Those are not features that can be added later without a rewrite.
Everything decorative waits. If a navigation entry exists, the thing behind it works.
Early access
The first clubs decide what gets built first
A small group of clubs gets early access and shapes the order of the work. Two questions, and that is the whole form.