What multi-location veterinary tech stacks actually look like in 2026.

Most consultants who write about veterinary technology have never set foot in a vet clinic. We haven't either. But what the consolidators are doing at scale — Mars Veterinary Health, National Veterinary Associates, Pathway Vet Alliance, AmeriVet Veterinary Partners, VetCor, PetVet Care Centers — is documented enough in industry filings, practice-management vendor release notes, and trade publications that we can answer three high-intent questions an operator at a PE-backed roll-up should be asking right now.

This is the landscape piece. The next two articles in this series score the actual vendors for each stack layer and walk through how one consolidator made its standardization decisions.

Question 1What does a multi-location veterinary group's tech stack actually look like in 2026?

Most write-ups of vet tech focus on the practice-management system (PMS) and stop there. That's not the stack. The actual operating reality of a multi-location veterinary group is four stacks running in parallel, each owned by a different decision-maker, often acquired in different decades, almost never standardized at the same time.

Layer 1 — Practice management software

The clinical core. Cornerstone (IDEXX) is the dominant PMS at the consolidator scale; the company's most recent IDEXX-published practice integration data shows Cornerstone running at more than half of the top 30 PE-backed roll-ups. AVImark (Covetrus) remains the most-installed PMS at the long tail of smaller acquisitions. ezyVet (IDEXX-owned, post-2021 acquisition) is the cloud-native option growing at multi-site groups that prioritize off-site access. Provet Cloud, Hippo Manager, and NaVetor appear at smaller scale. Each of these systems is the operating system of the clinic — schedule, medical records, billing, inventory, lab integration. None of them are vendors a consolidator buys; they're systems a consolidator inherits on acquisition.

Layer 2 — Phone systems and call routing

The most fragmented layer. Pre-acquisition, the typical single-location vet clinic runs whatever phone system was set up by the prior owner — sometimes a basic VoIP service from the local cable provider, sometimes an older on-premises PBX, occasionally a small-business UCaaS subscription. Post-acquisition, the consolidator faces a choice: standardize immediately and absorb the staff disruption, or defer and run 30 different phone vendors for two years. Most defer. The eventual standardization, when it happens, tends to converge on a mid-market UCaaS platform — the consolidator picks one and migrates clinic-by-clinic over 18–24 months. Contact center routing — distinct from the phone system itself — is the layer most groups under-invest in. We'll come back to this in Question 2.

Layer 3 — Connectivity and network

Each clinic has its own business-class broadband — typically a coax connection from Comcast Business, Spectrum, Cox, or whichever cable operator owns the regional footprint, with a few sites on fiber if they're near an enterprise carrier's network. The structural problem at scale is that radiography and ultrasound imaging files are large — a typical small-animal practice generates 5–50GB of imaging data per day — and these files frequently need to move to a centralized PACS or to a tele-radiology partner. Broadband alone can't prioritize that traffic against the rest of the clinic's needs. The consolidators that have done this well are overlaying their footprint with SD-WAN to apply application-aware QoS; the ones that haven't are dealing with imaging-handoff complaints from veterinarians.

Layer 4 — Security and managed services

The most under-resourced layer. Veterinary records aren't HIPAA-covered, which has historically been used as justification for skipping the security investment most healthcare-adjacent businesses make. That's changing. Most state veterinary medical boards now require breach notification under general consumer-protection law, and ransomware attacks on multi-location vet groups have become regular enough that PE acquirers are increasingly underwriting them as a risk in diligence. Most groups arrive at security only after the first incident; the consolidators doing this well are running managed detection-and-response with an MSSP partner from day one of standardization.

That accretion problem is the real story. When NVA acquires a 12-clinic regional group, NVA doesn't get to choose the tech stack — it inherits the stack. The work of consolidation isn't about picking the right vendor in a vacuum. It's about choosing which of the inherited systems to standardize on, which to migrate away from, and how fast to push that standardization through clinical staff who have been doing things their way for fifteen years.

Question 2Where do PE-backed veterinary roll-ups consistently get IT sourcing wrong?

Six structural mistakes show up across the roll-ups we've looked at. None of them are technology mistakes in isolation — they're operational mistakes about how technology decisions get made.

1 · Forcing PMS standardization too fast

The first instinct of an acquired group's new corporate parent is to standardize the PMS. The economics make sense in a spreadsheet — fewer vendor relationships, lower licensing cost, easier reporting roll-up. The reality is that practice managers and senior veterinarians have ten-to-fifteen-year workflows built around the existing PMS, and forcing migration in year one of acquisition predictably leads to practice-manager attrition, clinical workflow disruption, and slower productivity recovery post-close. The consolidators that handle this well — Mars Veterinary Health, NVA — defer standardization 18 to 24 months while clinical staff stabilize, then migrate clinics on a one-at-a-time cadence over multiple years.

2 · Defaulting to whatever phone vendor the HQ uses

A 30-clinic group whose HQ runs a basic UCaaS subscription will sometimes try to roll that vendor out to every acquired clinic on the assumption that scale is the only consideration. The trap: most small-business UCaaS platforms don't handle multi-site emergency call routing — they were designed for an office of 50 people, not for an after-hours emergency call that needs to route to whichever on-call vet is available across six time zones. Veterinary groups need either a UCaaS platform with multi-site call handling depth (RingCentral, Cisco Webex, NICE for the contact-center layer) or an explicit contact-center overlay on top of the basic phone system. Skipping this step means after-hours operations limp along on a single 24/7 answering service whose contract gets re-bid every year while the operational complexity grows.

3 · Under-investing in network for imaging traffic

Already covered above: consumer-grade broadband can't reliably move 50GB of imaging files per clinic per day while keeping voice quality acceptable on the same connection. The vendors who actually solve this are the SD-WAN providers with image-aware QoS — Cato Networks, Aryaka, Open Systems, and Bigleaf Networks all have veterinary-relevant deployments. Generic "we'll give you a faster connection" doesn't address the problem; the bottleneck is prioritization, not raw bandwidth.

4 · Treating security as IT's problem, not clinical operations'

Vet groups rarely have a CISO. Security ends up under the IT director, who reports to the CFO, who manages it as a cost. The right framing — and the framing the consolidators with mature security postures use — is that a ransomware event in a clinic shuts down clinical operations: appointments cancel, imaging stops, drug-cabinet inventory becomes inaccessible. That's an operational continuity problem, not an IT cost line. The fix is an MSSP relationship with clinical-operations escalation paths, not a thicker firewall. Trustwave, SilverSky, eSentire, Ontinue, and Level Blue are the managed security providers most commonly deployed at multi-site healthcare-adjacent operators.

5 · Skipping centralized after-hours emergency routing

This is the single most-overlooked operational improvement available to a multi-location vet group. Most clinics route after-hours to one of three options: a regional veterinary emergency hospital (which the consolidator may or may not own), a national answering service (PetCare USA, Vet Answer), or an on-call veterinarian's personal cell phone. At 5 clinics, this is manageable chaos. At 30 clinics, it's operational malpractice waiting for a Form 10-Q footnote. The fix is a real contact-center routing layer that handles after-hours call distribution, on-call vet escalation, regional emergency hospital routing, and post-call medical-record handoff to the clinic that owns the patient. The CCaaS platforms that do this at scale include NICE, Genesys Cloud, Five9, and Talkdesk — though the deployment patterns differ meaningfully between them, which we'll cover in next week's Shortlist piece.

6 · Letting practice managers retain vendor decision authority post-acquisition

When an acquisition closes, the existing practice manager often keeps making local IT decisions — phone vendor changes, broadband upgrades, software-renewal approvals — because the corporate parent hasn't yet built a centralized procurement function. The result a year later: 30 different phone vendors, 30 different broadband contracts, 30 different security postures, and a consolidated group that's worse-positioned to negotiate than it was as 30 independent practices. The fix is to centralize vendor authority for everything outside the PMS at the moment of acquisition, even if standardization doesn't happen for two years. The decision to not yet standardize a phone vendor is itself a centralized decision; it's just one that says "preserve optionality."

Question 3What three questions should a vet group operator ask before signing any phone, network, or security vendor?

Diligence questions are the cheapest filter available to a buyer. Three questions filter roughly 80% of vendors who don't actually understand veterinary operations from the ones who do.

Question one — practice management integration

"Show us your practice-management integration with Cornerstone, AVImark, or ezyVet, at three reference customers running ten or more locations."

A vendor that can't produce reference customers at the right scale is either selling a generic mid-market solution with no veterinary depth, or has a "we'll build the integration" pitch that translates to six months of professional services delay. The integration depth that matters is bidirectional — the phone system needs to know which patient is calling so it can pop the chart, and the PMS needs to know when a call ends so it can log communications. Vendors with strong vet PMS integration include RingCentral, NICE CXone, and Genesys Cloud; vendors that claim integration but rely on partner-built middleware should be treated with skepticism.

Question two — after-hours emergency routing

"Walk us through how your platform handles after-hours emergency call routing, on-call vet escalation across multiple clinics, and the handoff back to the patient's home clinic on the next business day."

This is the question that separates generic UCaaS vendors from real veterinary-capable platforms. The right answer involves time-of-day routing rules, geo-aware on-call schedules, escalation logic for when the primary on-call vet doesn't answer, and a defined process for logging the after-hours interaction back into the patient's clinic record. Vendors who answer with "we forward calls to a phone number" are not actually solving the problem. The CCaaS vendors with veterinary-relevant deployments include NICE CXone, Five9, Talkdesk, and Genesys Cloud.

Question three — network QoS for imaging

"What's your story for image-aware network QoS? We move 30 to 50 gigabytes of radiography and ultrasound files per clinic per day, much of it to a centralized PACS or to a tele-radiology partner."

The honest vendor will distinguish between "we sell SD-WAN" and "we sell SD-WAN with application-aware QoS that's been tuned for medical imaging workloads." Veterinary imaging is functionally similar to medical imaging traffic in human healthcare — large files, latency-tolerant but throughput-sensitive, occasionally needs to coexist with voice on the same connection. The SD-WAN and SASE vendors with relevant experience here are Cato Networks, Aryaka, Open Systems, and Bigleaf Networks. Most generic SD-WAN sales pitches will gloss over the QoS specificity; the test is whether the vendor can name the QoS profile they'd configure for your workload before the contract is signed.

None of these three questions require deep technical knowledge from the buyer. They require the buyer to ask the question and listen for whether the vendor has a substantive answer. The vendors who actually serve multi-location veterinary groups will have answers; the rest will produce sales material that doesn't engage with the substance.

If you're getting ready to source

Next Thursday's piece in this series is the vendor shortlist: which CCaaS vendors actually meet all three filters for a 20-to-40-location veterinary group, scored against the Cardinal Method rubric. The Thursday after that walks through a Cardinal Method engagement at a 34-location veterinary group — what we found at intake, what the scorecard produced, what was signed, what happened post-deployment.

If you'd rather not wait, the engagement page has three ways to start a conversation that don't require committing to anything.