Seeker Paddock
Software — barn management
Not a brochure. A working application for running a boarding barn: who is in which stall, who owes what, and which horses need something done today.
This business is invented. It’s a concept build made to show how a site for this kind of business should work — not a real client, and not a real company.
The problem
Boarding barns run on a whiteboard, a phone, and one person's memory. Stall assignments, feed and medication instructions, farrier and vet dates, and who has paid this month all live in different places, and none of them are accessible to the person doing evening chores. The failure mode is not dramatic — it is a horse getting the wrong grain, a vet visit missed, or three months of unbilled board discovered in September.
What I built
- A stall roster that is the actual source of truth, filterable by barn and by what needs attention today.
- Per-horse records carrying feed, medication, turnout, and the notes that usually live on masking tape on a stall door.
- Care flags surfaced as a worklist rather than buried in records, so evening chores can be run off a phone.
- Board status per horse, so unbilled months are visible rather than discovered.
- An interface designed to be used one-handed, in a barn aisle, by someone wearing gloves.
What it does now
The whiteboard becomes a system that the barn manager, the evening help, and the owner can all see. Nothing about the work changes; it just stops depending on one person remembering.
What this shows
- That this is not a website-only business — this one has state, filtering, and a real interface.
- Designing an operational tool for its actual usage scene, which is standing up, in poor light, in a hurry.
- Restraint in a dense interface: scanability and state over expression.