Farrier Management Software

Farrier software for every horse on its own cycle, every barn in one round.

The appointment book lives in the truck, each horse runs on a different cycle, and the shoe setup for the tricky one lives in memory. We turn that round into one owned system that holds the cycle, the route, the record, and the invoice for every horse.

See our work

Bring one stuck farrier workflow. Leave with a buy, repair, or wait recommendation.

Trusted by

Perceptional logoMusgrave GroupUrShipper logoBrux Dental SolutionsBella Skin Institute LogoEnergia RewardsDraftly logoTuneClub LogoSekou LMS logoLogo of food order management app gulaSnelwegDealsGrubly logoPSi logoInstantor Rewards logologo of Mobile app for events, membership clubs, and communitiesAldiFest retail campaign logoVidmattic logoEMS Connect logoWorx Squad logologo of Online Web App For Making Intrologo of Referral and Viral Marketing PlatformConcurrences logoGE logoTicketstop logo

The brief

Start with what is not working.

Good software decisions begin with the constraint, not a list of features or a preferred technology.

01

Which horse needed the wedge pad? Nobody wrote it down, and the answer left with the last visit.

02

The appointment book lives in the truck, and owners get texted one by one to confirm the week.

03

The work is done on Friday and the invoices wait for Sunday night, again.

Plain answer

Farrier management software runs a farrier's own trade business in one place. Each horse carries its own shoeing cycle, shoe setup, and photos. The day is ordered barn by barn, the record works with no signal in the barn, and the invoice is finished at the barn instead of on Sunday night.

What to remember

  • Use this when cycles, shoe setups, routes, and invoices live apart and the gaps cost visits or unpaid work.
  • The first release should complete one path, such as one full round from due list to paid invoice, not collect disconnected features.
  • The horse is the record, not the owner: cycle, setup, and photos travel with the horse when it moves barns.
  • Quote the team's own screens as their own scope: the round list, the horse record, reminders, and invoicing are a second product, not a single admin-panel line.
  • Hire freelancers for one small, well-defined task; use one accountable agency party when the work needs coordination across cycles, routes, records, and billing.

The first decision is not what to build.

It is whether software is the right answer at all. We use four possible recommendations before discussing a development scope.

  • 01

    Buy

    Choose a maintained product when it handles the core workflow and the remaining gaps can be solved with configuration, a connector, or a small process change. Gatepost covers farrier scheduling, routing, and offline work, EQUINET covers horse records and invoicing, and FarrierIQ and Best Farrier cover the phone-first round. Compare them against your real round before paying for anything custom.

    Run the build-vs-buy numbers

  • 02

    Repair

    Keep the existing product when users still get value from it and the code can be understood safely. Start with evidence: where the code lives, how your data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live.

  • 03

    Build

    Own the system when the way you run the round shapes your margin, your evenings, and whether work gets billed at all. Start with one complete path, such as one full round from due list to paid invoice, and the system connections that path cannot work without.

  • 04

    Wait

    Do not turn a changing policy into permanent software. Stabilise the rules, name the workflow owner, and measure the cost of the current process before paying for a product.

Not sure which path is yours? Bring it to a 30-minute call. Leave with the answer in writing.

Fit

Farrier software should earn its maintenance burden.

A feature request is not enough. The case is real when the same constraint shows up in time, errors, margin, or customer experience.

A fit

Each horse runs on its own cycle, and the due list, the route, and the record live in different places.

A farrier or small team can name a workflow owner and what 'done' looks like for the first release.

Barn accounts, corrective setups, or pricing rules differ by horse and no maintained product holds them cleanly.

Not a fit

A maintained product fits with reasonable configuration and process change.

The team wants software to settle an unresolved operating policy.

The brief is a feature list with no horse, visit, or business result attached.

Not sure which side you are on? Use the first call to make that decision. A useful answer may be to buy, connect, repair, or wait.

Start with the round, not the software.

A farrier problem usually starts as a memory problem. The appointment book lives in the truck. Each horse runs on its own cycle, four weeks for one, six for the next, eight for the retired horse at the same barn. The setup for the horse with the wedge pad was decided two visits ago and written down nowhere, so it gets settled again from memory, under the horse. Owners are texted one by one to confirm the week, and the answers land in threads that scroll away.

The cost is spread across the week where nobody counts it. A horse missed off the due list is a visit that slips until the owner notices. A day ordered by habit instead of by barn burns fuel between stops. Work finished on Friday and invoiced on Sunday night is an evening gone, every week, and some of it never gets billed at all because the detail of what was fitted has faded by then.

The barn side of this work has its own view. A barn keeps its own record of the horses it houses, and our equine management and equine management software pages speak to that side. This page is the other side of the same visit: the farrier's own book, round, and billing. The two records meet at the horse, and neither one replaces the other. Where a vet directs the shoeing plan, the veterinary view holds the clinical side; the farrier's record holds what was fitted and when the horse is due again.

A second product hides inside the first. Owners see a visit and an invoice; you live in another set of screens: the due list, the round order, the horse record, reminders, stock, and a record of who did what. Quotes that squeeze all of that into an "admin panel" line item are where budgets most often break. On a real platform, your own screens are routinely the most underestimated part of the build, so we quote them as their own job, with their own users, from the start.

Farrier management software makes sense when one owned system can remove that constraint better than a product, connector, or process change. The first release should take one path, such as one full round from due list to paid invoice, from start to finish. It should not replace every tool at once.

We start where it hurts.

The interface is only one part of the job. The real scope includes the rules, the data, the connections to your other systems, what happens when things fail, who can see and change what, and who runs it after release.

One cycle per horse, one due list

Every horse carries its own cycle, four, six, or eight weeks, and finishing a visit sets the next due date from that cycle. The due list is the week, already worked out, instead of a book you re-read each night.

The day ordered barn by barn

The round groups horses by barn and orders the stops so the day runs as one loop. A barn stop with several owners still bills each owner separately, per horse, from the same visit.

The setup and the photos, on the horse

Shoe type and size, pads, packing, and changes from last time sit on the horse's record with photos of the feet. The wedge pad question is answered by the record, not by memory.

Work that keeps working with no signal

The round, the records, and the invoices live on the phone in the barn. You log the visit where the work happens and everything syncs when the signal returns, with the waiting items shown plainly.

The invoice finished at the barn

Rates set once price each visit as you complete it, and work with no rate is flagged instead of billed at nothing. Payment by card, cash, or check is recorded on the spot, so Sunday night is yours again.

Which one is yours?

Bring it to a 30-minute call. Leave with a buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

Workflows

One record from due date to paid invoice.

Some of this work only exists in one corner of the trade. The same rules apply: configure first, build only the part the maintained products cannot cover, and start with one complete path.

The solo round

One farrier, several barns, a book of horses on mixed cycles. The phone holds the day, the records, and the billing, so the truck stops being the office.

A small team on one book

Two or more farriers working the same clients need one shared due list and one record per horse, so a horse covered by a colleague keeps its setup and its history intact.

Corrective and vet-directed work

When a vet sets the plan, the record holds the instruction, what was fitted against it, and the photos that show the change over visits, ready to share back.

Barn accounts with several owners

One stop, many owners. Each horse is worked, recorded, and billed to its own owner, and the barn visit itself stays one entry on the round.

Proof

The fifth attempt became a product customers could keep using.

UrShipper had already worked with four development vendors. Its founder describes the communication and decisions during the recovery.

The case study documents a 14-week recovery, five carrier connections, a Shopify fulfilment workflow, and client-reported results. It is one comparable project, not a promise that every inherited codebase can follow the same plan.

Read the UrShipper case study

Which part of the round is costing you the most right now?

Bring it to a 30-minute call. Leave with a buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

How it works

Close one expensive risk before opening the next.

Each stage answers a buyer question and leaves behind a decision you can inspect. The next stage only opens when the expensive uncertainty in the current one is small enough to accept.

  1. 01
    Understand

    Trace the real round

    Where is the cost or failure actually coming from?

    Follow one farrier and one full round from due list to paid invoice. Include the workarounds, manual judgement, duplicate entry, waiting, and failure paths that a tidy process diagram usually misses.

    Decision produced

    A map of the round, exceptions, owners, systems, and the baseline cost or delay worth changing.

    Risk closed

    Paying to automate the visible symptom while the expensive constraint remains.
  2. 02
    Shape

    Choose the first useful release

    What needs to exist together for one useful result to work?

    Choose the shape from the way the work happens, not from a preferred technology. Name the user, the device, the data, the system connections, who can access what, the exceptions, and the result the first release must complete.

    Decision produced

    The right mix of web, mobile, desktop, browser extension, connected device, wearable, or behind-the-scenes connection work, with the first-release boundary and a clear definition of done.

    Risk closed

    A small-looking feature list that quietly depends on several interfaces, systems, and owners.
  3. 03
    Prove

    Review working software

    Will it hold up outside a controlled demo?

    Review the product against the agreed workflow, not a tour of finished screens. Record changed assumptions and test what happens when data is missing, access is wrong, or a connected system fails.

    Decision produced

    Working checkpoints tested with realistic data, real user types, system connections, recovery plans, and the people who will use or run the system.

    Risk closed

    Discovering the important gaps during migration or after customers depend on the release.
  4. 04
    Transfer

    Release, measure, and hand over

    Did the new workflow improve the original constraint, and can another capable team operate it?

    Move a controlled set of horses or barns first. Compare time, errors, completion, or another agreed measure with the starting point before adding the next workflow.

    Decision produced

    A controlled release, comparison with the baseline, operating notes, account ownership map, and a recommendation for what should happen next.

    Risk closed

    Measuring development activity instead of the business result, or depending on the original vendor to keep the system running.

What stays out of the black box

These are operating conditions to put in the engagement, not claims to take on faith.

The scope names one complete workflow

The user, the trigger, the decisions, the data, the exceptions, and what 'done' looks like. A screen list is not enough.

Progress is visible in working software

Reviews against the product at agreed checkpoints, while there is still time to act. You see the round working, not a slide deck about it.

A scope change has a price before it has code

A new workflow or system connection shows its effect on cost and timing before anyone approves it.

Ownership exists throughout, not only at handover

Code, cloud, data, and provider access stay visible and under your control from day one.

You can judge the work without being technical

Checkpoints are working software you use yourself, reported in plain language. If a step fails, you see it fail in the product, not in a status report.

Farrier software and the neighbouring view.

The farrier's book is one side of the visit. The barn and the vet keep their own sides, and each page below speaks to one of them.

What it costs

Every project starts at $10000.

The first phase turns the costliest patched farrier workflow into a scoped build with written acceptance criteria.

Starting investment

Starts at $10000

Workflow complexity, systems to connect, data migration, and user roles set the scope. After a 30-minute call, you get a written buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.

Buy or own

Buy a maintained productOwn custom software
Best fitHandles your round with reasonable setup, and its pricing makes senseThe way you run the round is itself the advantage
Manual workConfiguration and process changes can remove the constraintRepeated manual work has a measurable cost
ConnectionsExisting connections work with reasonable setupA critical connection to your accounting or messaging system cannot be done cleanly any other way
Platform routeConfigure a maintained product when its cycle, route, and billing model fitsOwn custom software only when the differentiating process, barn accounts, or cost of constraint justifies build and support

Work with us

Bring one stuck farrier workflow. Leave with a decision.

In a 30-minute call, we will help you decide whether to buy, connect, repair, build, or wait. If custom software is not the sensible next move, that is still a useful answer.

  • One named workflow owner and one complete round scoped for the first phase.
  • Scope, price, what 'done' looks like, and exclusions agreed before paid work starts.
  • Code, cloud, data, and provider access remain under your control.
  • Post-launch warranty cover for defects in the agreed scope.

Common questions

Farrier management software runs the farrier's own business in one place. Each horse carries its own cycle, shoe setup, and history. The day is ordered by barn, owners get reminders without one-by-one texts, and each visit turns into an invoice at the barn. It is the trade side of the work, not the barn's own record of the horses it keeps.

Every horse gets its own cycle, commonly four, six, or eight weeks, set by you for that horse. Finish a visit and the next due date comes from that horse's cycle, not from a shared calendar guess. A young horse, a horse in hard work, and a retired horse can sit at the same barn on three different cycles, and the due list still reads correctly.

The stop is the barn, and the work inside the stop is per horse and per owner. One visit can cover horses belonging to several owners, and each owner gets their own invoice for their own horses from that single stop. The route orders the barns for the day; the record keeps the billing separate.

The setup you fitted, foot by foot where it matters: shoe type and size, pads such as a wedge pad, packing, clips, and any change from last time. Photos of the feet sit on the same record, along with handling notes, such as which horse needs the owner holding it, and the notes a vet has asked you to follow. The record answers the wedge pad question before you unload the truck.

Yes, when offline work is part of the scope from the start. The round, the horse records, and the invoice screens live on the phone and keep working in a steel barn or a back field. Changes save on the device and sync when the signal returns, and you can see what has synced and what is still waiting.

The invoice is raised from the visits you just finished, priced from the rates you set once for a trim, a full set, a reset, or corrective work. Work with no rate set is flagged for you to price, never billed at nothing. Owners can pay by the ways farriers actually get paid, including card, cash, and check, and the payment is recorded against the horse and the visit before you leave.

The system sends the reminder for you: a notice before the visit is due and a confirmation request ahead of the day, tied to the horse and its cycle. Owners confirm or ask to move the visit, and the change lands on your round instead of in a text thread you have to re-read under a horse. You still handle the exceptions yourself; the routine chasing is what goes away.

The record travels with the horse. The cycle, the setups, the photos, and the visit history stay on the horse when it moves to a new barn or a new owner, because the shoeing history belongs to the animal, not to the billing relationship. The new owner starts from the real record instead of from a guess.

Yes, as part of the same record. Shoes, pads, and nails used on a visit are logged against the horse, so stock in the truck draws down as you work and the day shows what needs replacing before the next round. It will not order stock for you; it stops the mid-job discovery that the size you need is not on board.

Buy a maintained product when it handles your round with reasonable setup and its pricing makes sense. Gatepost covers scheduling, routing, and offline work for farriers, EQUINET covers horse records, appointments, and invoicing, and FarrierIQ and Best Farrier cover the phone-first round. Own custom software when your cycles, barn accounts, or pricing rules do not fit any maintained product, or when the way you run the round is itself the advantage. If the rules of the round are still changing every week, wait and settle them first.

For a small, well-defined task with someone technical managing it, freelancers are often cheaper. The pattern that goes wrong is a non-technical buyer coordinating several freelancers becoming the project manager, the tester, and the person who discovers the pieces do not fit. A farrier software company earns its fee when the work needs coordination across cycles, routes, records, and billing: one accountable party, one phase price, and checkpoints against the whole round. If your need is one screen or one fix, hire the freelancer.

The first paid phase may cover a bounded audit, a proof of concept, a recovery plan, or a small first release. The final price depends on how deep the workflow goes, how many kinds of users it serves, what it needs to connect to, whether data needs moving over, whether phones or tablets are involved, any compliance requirements, and the condition of existing code. The agreed phase is priced in writing before it starts.

You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the round agreed at the start. Progress is reported in plain language: what changed, what is next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads. Our job is to make the work checkable; your job is to check it against your business.

You own the code built for you and control where it lives, the cloud accounts, the data, analytics, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.

Every launch includes post-launch warranty cover for defects in the agreed scope, release support, and small screen corrections. After that, work can continue as another fixed phase or an ongoing product engagement. The code and accounts stay under your control either way.