Vet On Demand
Year
2015
Industry
Healthcare + Pet Care
North Star
Because pets don't wait for office hours
Pet telehealth had no benchmark. The product needed to solve distinct problems on both sides of the marketplace at the same time.
On the consumer side, millions of pet owners were googling symptoms at 11pm, trying to decide between an expensive emergency vet visit and waiting until morning. The anxiety was real, the information available online was unreliable, and the cost of guessing wrong could be the animal's life. The product had to feel as trustworthy as an office visit and simple enough for a worried pet owner at midnight.
On the provider side, veterinarians are a conservative profession. Most wanted nothing to do with diagnosing through a screen. The idea felt clinically reckless to them, and regulatory boards were cautious. We had to convince licensed professionals that they could practice good medicine remotely and that there was real income in doing so.
This wasn't just a UX problem. It was a credibility problem and a sales problem, and ultimately the regulatory problem that would define the entire category.
We started where any credible medical product should: with the practitioners. Before writing a line of code, we recruited a handful of veterinarians as an advisory board. These weren't consultants. They were equity partners with real skin in the game. They shaped everything: the compliance requirements for remote veterinary practice, the clinical workflows during a remote exam, what a vet needs to see and document during a video consultation, and which features would make them comfortable staking their license on a video call.
The most important feature came directly from the exam room. During the video call, the pet owner could flip their camera and point it at the animal. The vet could guide them: "hold the camera here," "can you press gently there." We built an interaction where the vet could tap a button to capture a still frame from the owner's live camera feed mid-call. A close-up of a scratch, a swollen joint, something caught in the teeth. The image saved directly to the patient record.
That feature came from our advisory vets describing how they document observations during a physical exam. They take notes, they take photos. We translated that clinical instinct into a digital interaction. It wasn't in any product spec or competitive analysis, because there were no competitors to analyze.
The advisory board solved the cold start problem too. When we launched, the vets who shaped the product became our first providers. The people who designed the clinical experience were the people delivering it. The supply side of the marketplace was bootstrapped before day one.
The hardest technical problem was reliability. In 2014 and 2015, 3G was still common and early 4G was inconsistent. When someone pays for a veterinary consultation, a dropped video connection isn't a minor UX issue. It's a broken promise, and it undermines the clinical credibility the entire product depends on.
The iOS app was built natively in Objective-C. The Android app was built natively in Java by a specialized development partner. We chose TokBox (OpenTok) for real-time video because it was the only viable option for mobile-native video at the time; WebRTC was still maturing. The backend ran on Ruby on Rails with PostgreSQL, Redis for background jobs and presence detection, Amazon S3 for file storage, and AWS infrastructure across the board.
TokBox gave us the video pipe. Everything else was on us. We built session persistence and reconnection logic to handle network drops gracefully, resuming the call rather than forcing the user to start over. We built cross-platform video routing from mobile devices through our servers to the vet's browser-based portal. We built quality management across network conditions that varied wildly between 3G, 4G, and WiFi. And we built a matching system with round-robin routing to available vets, powered by Redis presence detection tracking who was online and ready.
The entire platform was designed and built by a four-person team. No separate design team, no DevOps, no QA department. We filled all of those roles ourselves.
The consumer mobile apps on iOS and Android stripped onboarding to essentials: pet profile, symptom description, and straight to a live video call. In-call camera control let the owner flip to show the animal. Vet-initiated photo capture saved to the patient record. Push notifications handled confirmations and follow-ups.
The provider web platform was a browser-based clinical workspace with patient records and full consultation history, photo documentation from in-call captures, note-taking and annotation tools, data import from existing practice management systems, and availability management for the matching system.
The brand and visual identity had to balance two things that are usually in tension: clinical credibility and consumer warmth. The app needed to feel trustworthy enough for a medical interaction but approachable enough for a worried pet owner. I designed the logo, visual identity, and every screen on both the consumer and provider sides end-to-end.
The traction was real. Over 20,000 users within months of launch. Dozens of animals whose lives were saved by owners who got immediate care instead of waiting until morning. National press coverage. The first pet telehealth platform ever built and shipped.
What stopped us was veterinary law. In the United States, a preexisting physical relationship between the vet and the animal is required before medical advice can be delivered. It's called a VCPR, a Veterinarian-Client-Patient Relationship. Because all of our vets were remote and had never physically examined the animals, the consultations were operating in violation of that requirement.
The reasoning behind the law is sound. Animals can't self-report symptoms. They can't tell you where it hurts or what they ate. The physical exam gives the vet the baseline to make clinical judgments. Unlike human telemedicine, where the patient can describe their own symptoms, the veterinary case for requiring in-person exams is medically defensible.
Every pet telehealth platform that exists today is structured around the VCPR requirement. They're operated by brick-and-mortar veterinary practices offering remote consultations to their existing patients. The vet has already examined the animal in person, so the telemedicine follow-up is legally compliant.
We mapped the regulatory boundary that shaped how every successor in the category was built. The product worked, the technology worked, and the market wanted it. The regulatory environment wasn't ready, and we found the wall before anyone else did. The platforms that came after didn't have to discover it themselves.
We built pet telehealth before the category existed, reached 20,000 users, and saved dozens of animals' lives.
