Vetaverse: The Waiting Room Is the Product

Everyone building for veterinary clinics makes the same mistake: they start with the website. A nice homepage, a services page, a booking form. Then they wonder why the clinic's phone still rings off the hook.

The waiting room is the actual product

When we observed how a clinic in Izmir actually operates, the website turned out to be the least interesting surface. The real questions pet owners ask are: how busy is it right now, is my vaccination card still valid, and — the 2 AM classic — is this behavior normal or is it an emergency? None of those are homepage problems. They are state problems. Vetaverse is built around that state: live appointment density, per-pet health records that survive clinic changes, and an AI assistant trained to answer care questions without pretending to be a vet.

Health records that outlive any single clinic

Pet medical records in Turkey mostly live in a drawer at the clinic. Move cities, change clinics, and the history is gone. We model each pet as a first-class entity with an owner-controlled timeline: vaccinations, visits, prescriptions. The clinic writes; the owner keeps. That inversion — records owned by the pet owner, not the clinic — is the quiet decision that changes everything else in the architecture.

The AI assistant has one job: triage, not diagnosis

The assistant is deliberately constrained. It answers "is this urgent," "what does this vaccine protect against," "what should I bring to the first visit." It does not diagnose, and it says so. We would rather have a narrower assistant that earns trust than a general one that erodes it — in healthcare software, trust compounds and so does its loss.

What we would do differently

We shipped the marketplace before the records layer was fully loved. In hindsight, records first: once a pet owner keeps their animal's history in your app, commerce follows naturally. The reverse is much harder.