runpoint.home
Command Palette
Type to search. Press Enter for the top match.
← All case studies
Field-guide line illustration of a small-town vet clinic at dusk with a constellation of small dots above representing twenty clinic systems being unified

Veterinary care

A national operator of veterinary practices

Once the data lived in one place, the question changed from 'how do we know what's happening across our clinics' to 'which part of how the company runs should we rewire first?'

20+ → 1
Clinic-management systems unified into a single data layer
3+
Tools already stacking on the unified data layer

What we did, by area

OperationsUnified data platform. A data platform pulling in everything from more than 20 different clinic systems and document feeds. Cleaning, organizing, governance, the whole thing.
Built with
DatabricksDelta Live TablesUnity CatalogPySparkAzure DevOps
OperationsClinic staff workbench. Front-of-house workers at each clinic now use a single screen instead of jumping between systems.
Built with
ReactFastAPIDrizzle ORMLakebaseTwilioAzure
OperationsDoctor consult capture. When a doctor talks to a pet owner during a consult, we capture the conversation and reconcile it against what gets prescribed and billed afterwards.
Built with
WhisperClaudeNext.js
PeopleCross-clinic scheduling. Visibility into who's working where. In flight now.
Built with
ReactDrizzle ORMLakebaseExpressTanStack Query

Before

A national operator of veterinary practices, where each clinic ran on its own software and there were more than 20 different vendors in the mix. None of it talked to anything else. There was no single view of what was happening across the business, which meant there was also no leverage point for any single team to fix it.

The first bet

All the data, in one place

We built a data platform that pulls everything from all the clinic systems and document feeds into one model, with the cleaning, organizing, and governance done well enough that downstream tools could trust it. This is the work that paid for everything that came after.

What we noticed

Once the data was unified, the question changed. It went from 'how do we know what's going on across our clinics' to 'what should we build first now that we can see everything,' and that list keeps getting longer.

What we built next

01

A tool for clinic staff

Front-of-house workers at each clinic now use a single screen instead of jumping between systems, because all the systems they used to jump between are reading from the same data layer underneath.

02

Cross-clinic scheduling

Visibility into who's working where, in flight now, with the data already in place to make it possible.

03

Capturing the doctor's notes

When a doctor talks to a pet owner during a consult, we capture the conversation and reconcile it against what gets prescribed and billed afterwards, closing a gap that had been quietly costing the business money for a long time.

What's now possible

The foundation pays for itself by making the next ten projects cheaper. Each new tool the team wants to build sits on the same data layer, takes weeks instead of quarters to ship, and works on day one.

I can't even believe that we have something that will actually do the things that we've been wanting and dreaming about doing for a long time.

Client executive

These are real quotes from real clients. We anonymize on the site until each one says yes to being named. Most are in the queue. References available now.

Want this kind of work for your business?

SYSTEMS: NOMINAL
LATENCY: 12msRUNPOINT V2.0