Skip to main content

Use case

The equestrian centre, where every horse is a record and not a spreadsheet row

An equestrian centre runs three businesses at once: it stables horses, it teaches lessons, and it bills livery. Blueprint Maker generates the application that links YOUR horses, YOUR liveries and YOUR lessons, instead of three spreadsheets that never talk to each other.

Generate this application

The description is already written: free sign-up, then it's waiting for you in the composer.

Three activities, three spreadsheets, no link between them

The horse sits at the centre of everything, and that is precisely what a spreadsheet cannot represent. One horse belongs to an owner, occupies a stable under a livery package, works in certain lessons, and carries its own care calendar: vaccination, worming, farrier, dental visit.

As long as this lives in separate files, the simple question, “this horse, whose is it, how long is it paid up, and when was it last shod?”, means opening three documents and trusting your memory. Market software, meanwhile, is often built for large operations and priced accordingly.

Your horses, your liveries, your application

Describe your yard: “I have horses, each belongs to an owner and occupies a stable under a monthly livery package. I teach lessons with an instructor, a level and licensed riders. I want to track each horse's care, the liveries billed this month, and the week's schedule.”

The generated application links horses, owners, liveries, lessons and riders: a horse's record gathers its owner, its package, its care and its due dates, the schedule reads by day and by instructor, and the dashboard answers the morning questions: who's riding today, which liveries are due, which horse is coming up for a vaccination.

  • Horse records: owner, stable, breed, age, feed
  • Livery: package, monthly rate, payment status
  • Lessons: date, instructor, level, horses used
  • Riders: licence, level, lesson package
  • Care: vaccination, worming, shoeing, dentist, with their dates
  • Dashboard: today's schedule, month's livery, care due dates

Care due dates stop living in a paper diary

A missed vaccination means a horse that cannot compete. A late shoeing means lameness. Those dates are tracked today in a notebook or in someone's head, when they are exactly the kind of information a database holds effortlessly: each care entry carries a date, each horse carries its care, and whatever falls due surfaces on the dashboard by itself.

The application arrives with realistic demo data (horses, owners, livery packages, lessons at varied levels, care at different due dates) to judge it right away, and three generation levels (Sketch, Craft, Masterpiece) to raise the polish.

An owned tool, at subscription price

An equestrian centre's goodwill includes its owner base and its horses' history: that asset must stay with you. Code ZIP export, GitHub push, hosting wherever you want or the included dedicated URL, the application is yours.

Free Discovery plan for the first application; Pro (€25/month) and Max (€149/month) to iterate, with the cost shown before each generation.

Typical generated entities

  • Horse
  • Owner
  • Livery
  • Lesson
  • Rider
  • Care entry

Generated screens

  • Lesson schedule by day and instructor
  • Horse record: owner, livery, care
  • Livery and payments for the month
  • Riders and licences
  • Centre dashboard

Dashboard indicators

  • This week's lessons
  • Livery billed this month
  • Care coming due
  • Stables occupied

Frequently asked questions: equestrian centre management

Does the application handle riding-federation licences and competition entries?

It tracks what you describe: licence number, validity date, rider level, and surfaces licences coming up for renewal. The official formalities themselves (taking out a licence, entering a competition) stay on the federation's platforms: the application does not replace them.

Can vaccinations, shoeing and worming be tracked per horse?

Yes: describe the care to track and its dates, and it structures each horse's record. The dashboard surfaces what is coming due. The application displays those due dates; it does not send automatic reminders by SMS or email.

How is this different from pet-boarding software?

Pet boarding hosts animals for stays. An equestrian centre stables them year-round, teaches lessons, and follows a care calendar per horse: the horse is a lasting entity, linked to an owner, a livery package and the lessons it works in. The generated structure isn't the same.

Does the application produce livery invoices?

It tracks amounts, packages and statuses (to pay, paid), and gives you the month's total. Producing legally compliant invoices remains your invoicing tool's job.

Can it be used from the yard, on a phone?

It's a responsive web application: today's schedule and horse records read on a phone or tablet, at the yard as well as in the office, always current.

Related use cases

Describe your equestrian centre, walk away with the tool