The most important user of veterinary software has no idea it exists

One of the things I like most about building veterinary software is that the most important user has no idea the software even exists.

The animal will never log in, click a button, complain about the interface or tell us whether a feature made its life better. Yet the quality of the software can still influence what happens to that animal, which makes veterinary product management quite different from most other software categories.

Most product teams naturally focus on two questions: does the person using the software like it, and does the product make the customer more successful?

In veterinary software there has to be a third question: does this improve what happens to the patient?

That gives us a useful way to think about whether a product, feature or workflow is actually worthwhile. Great veterinary technology should improve client engagement, improve practice profitability and, most importantly, improve animal outcomes.

Not every feature has to do all three, but the best ones often do.

Client engagement is only useful if it changes behaviour

Veterinary practices already communicate with clients constantly, so simply sending more messages is not much of a product strategy.

The interesting question is whether software makes it more likely that an owner does the right thing at the right time.

A vaccination reminder becomes much more useful if the client can immediately book the appointment. A discharge workflow is better if the practice can see whether the follow-up actually happened. Home monitoring becomes clinically useful when information submitted by the owner can create an action for the veterinary team rather than simply sitting in another app.

That is what I mean by better client engagement. It is not engagement as a vanity metric. It is using software to close the gap between what the practice recommends and what actually happens after the client leaves the building.

For veterinary care, that gap matters enormously.

Profitability matters too

There is sometimes a slightly strange reluctance to talk about profitability in veterinary technology, as if commercial outcomes and good animal care are somehow opposed.

They are not.

A healthy veterinary practice can invest in staff, equipment, training and better services. A practice that consistently loses revenue through missed charges, poor diary utilisation, inefficient administration or weak client retention eventually has less capacity to do any of those things.

Good software should help practices capture the value of work they are already doing, remove unnecessary administration and make it easier to grow sensibly.

That might mean automatic charge capture, better stock control, easier payments, fewer missed appointments, more effective pet-plan enrolment or simply giving staff back time that would otherwise disappear into manual processes.

Those are conventional product outcomes because they are relatively easy to measure. Time saved and revenue gained show up in a dashboard.

Animal outcomes are harder.

The patient cannot give us product feedback

This is where veterinary product management becomes unusual.

A vet can tell us a workflow is frustrating. A receptionist can tell us a booking process creates unnecessary work. A practice owner can tell us where money is being lost.

The patient cannot tell us anything.

There is no product interview with the dog and no NPS score from the cat, so somebody still has to represent that perspective when decisions are being made about what gets built.

That does not mean software companies should pretend to practise veterinary medicine or claim that every feature directly improves clinical outcomes. It means we should ask whether the system around the clinician makes good care easier to deliver.

• Does important information reach the right person earlier?
• Are follow-ups less likely to be missed?
• Can a deterioration be picked up between consultations?
• Does an owner understand what they need to do next?
• Is the clinical history easier to interpret when the vet actually needs it?

Those are product questions as much as workflow questions.

The most interesting products improve all three dimensions

Take something as simple as home monitoring.

Allowing a pet owner to enter a weight into an app is not particularly interesting on its own.

What becomes interesting is when that reading is connected to the rest of the practice.

An owner records the weight. The system identifies that the change is outside an expected range. A task reaches the clinical team. Somebody reviews it, contacts the owner and books a recheck if appropriate.

That single workflow can improve all three parts of the model.

The client becomes more involved in the animal's care. The practice creates legitimate clinical work and potentially retains that client more effectively. Most importantly, the animal may be reviewed earlier than it otherwise would have been.

That is a much stronger product than a standalone "weight tracking feature", because the value comes from what happens after the data is entered.

The same logic applies elsewhere.

A better vaccination reminder can improve compliance, fill an appointment slot and improve preventive care.

A clearer discharge process can reduce unnecessary calls, make the owner's responsibilities easier to understand and reduce the chance of an important follow-up being missed.

Automated charge capture may primarily improve profitability, while a medication safety warning may primarily improve patient outcomes. Both can still be valuable, because not every feature needs to score equally across all three areas.

The framework simply forces us to understand what problem we are solving.

It is also a useful filter for AI

The same test is useful when looking at AI, because it is very easy at the moment to build technology simply because AI makes something technically possible.

That is not enough.

If an AI consultation summary saves a vet five minutes, that may already be worthwhile. If it also produces a clearer clinical record and makes important information easier to retrieve later, it becomes more useful again.

If an AI communication tool reduces reception workload, that is good. If it also helps owners understand what they need to do next and makes follow-up more likely, it has started to affect another part of the system.

The question should not be where we can add AI. It should be what outcome changes because the feature exists.

That is a much harder test, but it is also a much better one.

A different definition of user experience

In most software businesses, user experience means the interaction between a person and the product.

Veterinary software has a more interesting version of UX because the person or animal who matters most may never touch the interface at all.

The animal experiences the consequences.

It experiences whether a vaccination happens on time, whether a deteriorating condition is noticed earlier, whether the owner follows the treatment plan and whether the practice has the information it needs when the animal comes back.

The software is invisible to that patient, but the effects do not have to be.

That is why I think great veterinary technology needs to be judged on three things at once: whether it creates better engagement with clients, whether it makes the veterinary practice stronger and whether it improves what happens to the animal.

The first two are familiar product-management territory.

The third is what makes building veterinary software different, and in my view much more interesting.