EDAEquine Data Analytics
EdinburghSoftware & field recordsYards · studs · clubs · events

Records that keep pace with the yard.

Equine Data Analytics designs and builds mobile apps, web tools and websites for people whose working day starts in a stable. We turn whiteboards, diaries and device exports into software that riders actually fill in and owners can actually read.

Engraved-style illustration of a horse in five phases of a gallop, cream lines on deep green
Illustration generated for this site. The five phases below describe how we work, not the horse.
Listenat the yard, on the phone, or over video
Mapevery record, who writes it, who reads it
Sketchscreens tested with gloves and wet hands
Buildin fortnightly, visible increments
Settlesupport until the new habit sticks
What we are

An IT company with mud on its boots.

We are a software and digital services company. Our ordinary work is the same as any good studio: mobile apps, web applications, websites, interface design, publishing to the app stores and looking after what we ship. Our particular interest is the equestrian world, where information is often spread across a whiteboard in the tack room, three spreadsheets and somebody's memory.

We help organise that information, build tools around it and present it clearly. We do not offer betting or tipping services, and we do not interpret health data. Where your records touch veterinary matters, our software stores and displays what your professionals write; it never draws clinical conclusions.

The card

Six things we are commissioned to do

No.ServiceWhat you receiveTypically for
1Yard and stud web appsBrowser software for daily recordsSession logs, turnout and feed boards, per-horse history, exports to CSV, sign-in for staff.Training yards, livery, studs
2Mobile appsiOS and AndroidQuick-entry apps that work offline at the gallops and sync later, with large controls for cold hands.Riders, grooms, event stewards
3WebsitesClear, fast, maintainableSites for clubs, competitions, rehoming charities and equestrian businesses, with editing you can do yourself.Clubs, centres, organisers
4Interface designResearch, flows, prototypesClickable prototypes tested with the people who will use them, before code is written.Any of the above
5Data dashboardsReadable, honest chartsViews that summarise workload and history from your own records, with plain notes on what each chart can and cannot say.Yard managers, owners' updates
6Publishing and supportRelease and careApp Store and Google Play submissions, hosting set-up, updates, fixes and a named support route.Everything we build

Read the full description of apps and web work

Who it is for

Different gates, the same problem

Most equestrian organisations do not need a large platform. They need one dependable place for the records that matter and a way for the right people to see them. Scroll sideways for the settings we design around.

i

Training yards

Work programmes, session notes, who rode what, and the weekly view an owner asks for on Friday afternoon.

ii

Studs and breeders

Mare and foal records, covering calendars and document storage, with careful permissions for sensitive notes.

iii

Livery and riding centres

Turnout rotas, lesson bookings handled by your chosen provider, and notices that reach clients without a group chat.

iv

Clubs and societies

Membership websites, fixture lists, results pages and volunteer rotas that a new secretary can inherit.

v

Events and shows

Entry information, steward apps with offline timing notes, and results publishing that holds up on the day.

Try it

A two-minute look at your records

Before any meeting, it helps to know what material exists. This small check runs entirely in your browser. Nothing is sent to us.

Two more tools, a season record planner and a first-release sizer, are in the tack room.

Illustrative self-check

How ready are your yard records?

Tick what exists today, however untidy. The score only describes how much raw material there is to build from.

Records you already keep
0%

Watercolour illustration of a training gallop curving through misty hills with red marker posts
Illustration generated for this site, not a client location.
Mobile and web

Built for the gallops, not the boardroom

Field software fails in predictable ways: no signal on the hill, a phone in a glove, a rider with thirty seconds between lots. We design for those conditions first. Entry forms save locally and sync later. Buttons are large. Defaults are remembered so a session can be logged with three taps.

On the office side, web apps give the yard manager a fuller picture: filters, histories, exports and a printable week. Both sides share one data model, so nothing is entered twice.

How we approach mobile and web

Interface design

Design decided at the stable door

Watch the routine

We ask to shadow a morning, in person or by video, and note every time information is written down or asked for.

Prototype the smallest loop

A clickable prototype of one routine (logging a session, say) goes into real hands before anything else is designed.

Write the words properly

Labels use your yard's vocabulary. Charts carry plain captions explaining what they show and what they do not.

Our interface design process in full

Publishing

From test build to the stores

Getting an app published is its own small project. We prepare store listings, screenshots, privacy disclosures and age ratings, manage TestFlight and Google Play testing tracks, and answer reviewer questions. For websites, we set up hosting, domains, certificates and a sensible backup routine.

Apps are published under your organisation's own developer accounts wherever possible, so you always own the listing. We explain each account you need and why.

Publishing and release support

Delivery standards

Four commitments that hold for every job

  1. Every fortnightSomething to touchA working build or prototype, never only a status report.
  2. From day oneYour accountsCode, domains and store listings registered to you.
  3. Before launchAccessibility checkedKeyboard, contrast, screen reader and large-text passes.
  4. After launchPlain handoverA written guide for whoever looks after it next.

Read the full delivery standards

Honest charts

What a dashboard should not claim

Data from horses is noisy, partial and easily over-read. Our dashboards summarise what was recorded (distances, durations, workloads, notes) and say clearly what they cannot tell you. We do not build prediction tools for racing outcomes and we do not produce health assessments.

Every chart we design carries a caption with its source, its time window and its known gaps. That small discipline prevents most of the arguments a dashboard can otherwise start.

Before you write

Questions people ask first

More detail sits on the support and standards pages.

Do we need to be a large yard?

No. Some of the most useful projects are a single well-designed form and a weekly summary. We will say if a spreadsheet is still the right answer.

Can you work with our existing devices?

Often, if the device can export files such as CSV or GPX. We check a sample export early, before promising an import.

Do you work outside Scotland?

Yes. Most work happens remotely across the UK, with visits arranged where useful and agreed in advance.

Will you give advice on training or health?

No. We build software. Training and health decisions stay with you and your qualified professionals.

Winning post

Tell us about one routine.

The most useful first message describes a single routine that wastes time today: who does it, where, and what happens to the information afterwards. We reply from analytics@equinedataanalytics.fyi during working hours.

Monday to Friday, 09:00 to 18:00, Europe/London.