The total cost of your veterinary PIMS: what practices forget to count

When you compare practice management systems (PIMS), the monthly subscription is the number that is easiest to put side by side. It is usually quoted per site, per user or both, and it tends to become the comparison.

The subscription is only one part of what a new system costs you. There are setup charges, the hours your team spends learning the system, usage fees for things like text messages and card payments, any hardware or network changes, and the terms that apply if you ever want to leave. Some of these arrive as invoices. Others show up as staff time or as appointments you choose not to book during the switch.

This guide sets out a method for adding all of that up over three years, so that two or three shortlisted systems, and the setup you run today, can be compared on the same terms.

How do you calculate the total cost of a PIMS?

This guide uses a three-year window. That is long enough to spread one-off setup costs across more than one year and to pick up any price changes during the contract. If you want a longer view, run a five-year version alongside it using the same assumptions.

Over that window, the calculation looks like this:

Three-year TCO = recurring PIMS costs + implementation costs + internal transition costs + usage and transaction costs + infrastructure costs + exit costs, minus the costs of tools and infrastructure the new system replaces.

Each of those lines is covered below. The point of writing it out is that every vendor gets measured against the same list, including the lines they did not put on their quote.

Why should your current setup be the starting point?

A practice is never choosing between a new system and nothing. You already pay for a PIMS license or server, and often for separate tools on top: a reminder or messaging platform, an AI scribe, a card terminal and gateway, reporting spreadsheets or add-ons.

So the most useful comparison has three columns rather than two:

With your current setup filled in, you can see whether each option adds cost, moves it from one line to another, or replaces something you are already paying for. Payment processing is a good example. You pay card fees today, so the relevant figure is the difference between your current rates and the new ones, not the full processing bill.

What belongs in the recurring cost?

Start with how each vendor calculates the subscription: per site, per user, per vet, a tier based on practice size, or a mix. Then check who counts as a user. Part-time staff, locums, reception cover and the practice manager can all change a per-user total.

Do not assume flat headcount for three years. If you expect to add two vets or open a second site, per-user and per-site models will diverge quickly. Use your current headcount for year one and your expected headcount for years two and three, and apply the same figures to every option.

Next, list which modules are in the subscription and which are extra. Ask specifically about any modules that matter to your practice, such as online booking, reminders, a client app, health plan administration, reporting and AI tools.

Finally, check how the price can change once you have signed. Ask whether the contract allows increases during the term, whether they are linked to an index such as CPI, and whether pricing can change at renewal. Put any expected increase into years two and three rather than leaving it as a surprise.

What does implementation cost?

Implementation covers data migration, configuration and training. Implementation pricing varies, so ask each vendor on your shortlist to quote migration, configuration and training against the same scope, in writing.

For migration, the fee matters less than the scope. Ask exactly what moves across: clinical notes, patient histories, financial records, outstanding balances, attachments, lab results, reminders and health plan data. If some of it stays behind, you may need to keep the old system running in read-only mode, and that license belongs in your calculation. Our guide to switching veterinary PIMS without disrupting your practice covers the migration process itself in more detail.

How should you cost staff time during the switch?

Training may be included in an implementation package or priced separately. Either way, the practice also carries an internal staff-time cost, and it is worth separating that into two parts.

The first is paid time. Multiply the training hours by the number of people and by a loaded hourly employment cost for each role. That means the hourly wage or salary plus employer's National Insurance and pension contributions. As an illustration, eight staff spending six hours each is 48 hours of paid time.

The second is lost capacity, and it only applies where training or the switch removes bookable work. Some training will happen in protected time that would not have been used for appointments anyway. Some will need cover. Some will mean fewer consults. Only the last of these should be valued as revenue, and only where the appointments cannot be recovered later.

The same applies to the first weeks after go-live. I could not identify robust published veterinary evidence for a standard productivity dip after a PIMS switch, so do not put a generic percentage into your model. Ask each vendor, and a couple of their recent reference customers, what reduction in the diary they planned for and for how long. Then build your own contingency.

If you do reduce the diary, record the effect as potential revenue displaced during the transition, on its own line. It is not the same as a cost. Some appointments move rather than disappear, and consult income is not the same as profit.

Which usage costs sit outside the subscription?

A feature being included in a PIMS does not mean using it is free. Messaging and payments are the main examples.

SMS is usually charged per message, and a long message can count as more than one. WhatsApp business messaging carries Meta's own charges, and those have changed several times. Meta moved template messages to per-message pricing in July 2025, and from 1 October 2026 it also charges for service replies and utility messages sent inside the 24-hour customer service window, with a monthly free allowance for service messages. Ask each vendor which Meta charges are passed through, and check the current rate card when you model usage.

For each option, ask:

• whether the communications module is included in the subscription
• what each SMS costs, and how longer messages are counted
• what WhatsApp or other platform fees apply, and who bills them
• whether email or client app messages are metered
• what the card-processing rates are, and whether terminal rental is separate
• whether integration fees are charged by the PIMS vendor, the third party, or both

Then compare each answer with what you pay now. A higher per-message rate may still cost less overall if the new system replaces a separate messaging platform with its own subscription.

Does hardware still matter with cloud software?

If you run a server-based system today, the server, backups, IT support contract and any remote-access setup are part of your current costs. Moving to cloud software may remove some or all of them, and those savings belong in the comparison. Our article on server-based or cloud PIMS explains the difference between the two.

Cloud software moves the dependency onto your internet connection and devices. A backup connection, reliable wifi across the building and enough working devices for consult rooms and reception all need checking. Price any upgrades you would need, and compare them with what you spend on infrastructure today.

What does it cost to leave?

Exit terms are easiest to check before you sign. For each option, find out:

• the minimum contract length and the notice period
• whether fees already paid are refunded if you leave early
• whether there is a charge to export your data, and in what format it comes
• whether the export includes attachments, financial history and audit information, or only basic client and patient records
• how long the vendor keeps your data available after the contract ends

An exit cost that is low on paper can still be high in practice if the export leaves out records you are required to keep.

How does Lupa price this?

Lupa publishes its pricing: $140 per month per site and $70 per user per month. Lupa Notes, the AI scribe, is listed at $35 per user per month and is currently offered at 100% off for a limited time. Training and data migration are available as optional one-time packages depending on what a practice needs. The full breakdown is on our pricing page.

Those figures are only one column of the calculation above. Usage charges, your own staff time and the tools you would stop paying for still need adding in, the same as for any other system on your shortlist.

What should the numbers tell you?

A three-year TCO puts the financial side of your shortlist on the same footing. It shows which option costs more, where the money goes and what you stop paying for.

It does not choose the system for you. A PIMS with a higher three-year figure can still be the right choice if it fits your workflows better, migrates your data more completely, comes with stronger support or saves more staff time than it costs. TCO belongs alongside workflow fit, migration quality, support, security and the functions your practice needs, rather than in place of them.

If you would like help filling in the Lupa column for your practice, including what migration and training would involve, book a demo.