Context
There's no shortage of horse-management software. But from what I could find, almost all of it is built for commercial farms; invoicing, client billing, staff rostering. Nothing has been made for the much more common situation: a private stable with a handful of horses, a rotating cast of grooms and family, and an owner who just wants to know the horse has been fed and checked without making a phone call. That gap is what StableHand is for.
Problem Statement
People sharing care of a horse(s) have no shared source of truth for what's been done. Feeding, meds and rugging get tracked across a mix of whiteboards, group chats, and memory, and things get missed without anyone noticing until it's a problem.
User needs
The people actually using this day-to-day need a handful of things, in order:
- A way to see, at a glance, whether today's tasks are done, without reading anything
- Somewhere a note or concern actually reaches everyone with access, not just whoever they happened to text (or is forgotten)
- Different views for different people: someone doing the feeding needs different access than the owner checking in from work
- All of it to keep working with patchy rural signal
Research
It started from a real frustration from an owner who has many horses in their care, wanting something that just tracked tasks and status with her staff, and finding nothing built for her situation. From there, I worked through their actual daily routine; feeding times, med schedules, rug changes, who's helping on which day, and tested early screens against real horses and real chaos rather than a guessing with a mockup.
The scope needed to stay deliberately light, this isn't a business tool, so billing and invoicing were never part of the build from the beginning.
Goals & success metrics
Since this isn't a funded product with analytics to hit, 'success' here is more about fit than numbers:
- Someone can check a horse's status in the time it takes to glance at a phone, not read one
- The app works for the person feeding, the person managing, and the person just checking in, without any of them needing an explanation
- It holds up in the actual conditions people use it in: one-handed, outdoors, patchy signal
Process
Two decisions shaped most of what StableHand looks like now.
Roles, not permissions. Rather than a generic admin/editor/viewer setup, StableHand (currently) has three roles that map to real people: an Owner/Manager who sets everything up and sees it all, a Groom who ticks off tasks and updates status but can't touch a horse's core profile, and a Horse Owner who gets a read-only real-time view of their own horse when it's cared for elsewhere. It's a narrower permission model than most apps in this space, but it matches how care is actually split in a real stable.
Emoji as UI, not decoration. Fields like feeding, medication, and rug status use an emoji alongside the text label — 🥕, 💊, 🧥. It's a small thing, but in early testing it's been faster to scan than text alone: someone glancing at a horse's card mid-task can tell whether feed's been logged without reading a sentence. On a small screen, one-handed, outdoors, it just needs to be easy.
Solution highlights
Home screen tile grid
A visual grid of every horse at the property, photo-first. Configurable layout (2-column compact, square, or single-column large) so it works whether you have 3 horses or 15.
Feeding & medication tracking
Of course, each horse has their own dietary needs for meals and meds, each with a time and a checkbox that resets daily. Overdue tasks get flagged and notified, rather than forgotten.
Location & rug status at a glance
A quick-tap status strip shows where a horse currently is (paddock, stable, barn etc) and whether they're rugged - the two questions people ask each other most.
The Rounds
All of today's tasks: feeding, meds, whatever's due, pulled into one screen instead of digging through each horse's profile individually. Open it once, work through breakfast for every horse, done.
Care log & comments
A timestamped, attributed log per horse for things like ‘vet booked’, ‘seemed off today’, visible to everyone with access, with photos where useful. Nothing relies on memory or a text that got missed.
Farm-wide or per-horse calendar
Schedule events at the property level or against a specific horse. And if a horse moves to a new stable, its calendar goes with it, not left behind with the old yard.
Weather-aware advisories
Using the property's location and its own rug rules, StableHand flags any horse left out and unrugged if the forecast turns cold or wet. Also weather alerts for storms or snow and sleet that have recently been forecast.
Offline-first
Task checks and notes log with no signal and sync as soon as it’s reconnected, necessary for rural properties, not a nice-to-have.
Geo-loading
For grooms, vets, or farriers working across properties, entering a property's geofence auto-loads it as the active view and the relevant horses, notes and comments for that property.
Outcome & impact
StableHand is in pre-launch testing with 10 farms and a growing number of horses (currently one yard has on average 40 horses in their care). It's early days, there's more to build, but far enough along to show the real shape of the product: a working multi-role permission model, and design decisions that came from actual use rather than guesses.
Reflection
- The role model works, but a few more roles (vet, farrier) are still to develop, the first version deliberately kept it to three.
- Testing with one real user was enough to get the core right fast, but it's a sample size of one; wider beta feedback will surface things she may not have known, or to accommodate other operations working in different ways.
- Keeping scope light (cutting billing/invoicing early) was the right call. It kept the app usable, quick and ‘light’ instead of half-building a business tool nobody asked for.
Next stages
More features to test and refine, a tablet/web companion dashboard (for large screens in tack rooms), a final round of feedback and polish, then launch officially.