Client comms in my voice
Owner explanations, discharge notes, and handouts written from a line of my shorthand, not from a template. It's the thing I use most.
DailyThe future of veterinary medicine is already running in a clinic in Houston.
I'm a solo vet in Houston. I started using ChatGPT to fix a Facebook post. Three years later I'm running an AI scribe in my exam rooms and building the tools myself. I didn't plan any of this. I just kept hitting problems AI could solve, and the distance from idea to working software kept shrinking.
Things I actually built and use
Not a demo reel. Tools I run in a working practice, plus a couple I built for fun.
An AI receptionist on the line
Call flows I wrote for emergencies, refills, and new clients. The real work was deciding what it should handle and when it hands off to a human.
In useA scribe in my exam rooms
I talk through the exam. It drafts the note and the discharge and puts them back in the record. Running on my own hardware.
Running dailyPractice data past the screens
Experiments pulling real clinic data through my practice software's API, instead of pasting text in. Still figuring out where it goes.
ExperimentsDadCaptions
A live-caption app I built in a weekend for my dad, who loses the thread in a loud cabin. Not veterinary, but it's proof the wall came down.
Built itA watcher on Telegram
A bot that watches the market and pings me when something moves. Not clinical either, but the skill transfers straight back into the clinic.
Built itSome of these are solid daily tools. Some are experiments I'm still poking at. I'll always tell you which is which.
Where this is going
If you've got a clinic website that's basically a page, your hours, and a phone number, that was the right call for a long time. Mine was the same. It worked because people searched, found you, and read it.
That's the part that's changing. More and more, people don't read your site at all. They ask an assistant, and it answers for them using whatever it can find about you. It's answering for your clinic right now, whether you helped it or not.
The phone is next. Most calls to a vet clinic are the same twelve questions, and a machine that never has a rough morning can handle a good number of them. I'm not predicting that. An AI already fields calls at my clinic, today.
None of this replaces the medicine, and it doesn't replace judgment. It replaces the typing, the phone tag, and the after-hours voicemail nobody calls back. The vet who learns these tools doesn't get replaced by AI. The vet who skips them just ends up competing with the one who didn't. That's the whole thesis. The rest of this site is how.
The honest part
Things AI still sucks at.
The demos are amazing. Tuesday afternoon is harder. If a site only shows you the wins, it's selling you something.
- Remembering everything correctly
- Knowing when its own answer is subtly wrong
- Understanding a workflow constraint you never said out loud
- Making a printable that's actually readable on the first try
- Staying out of generic marketing voice
- Producing code that works every single time
What's coming
The next builds, and what I'm sending you.
Agents with one job
Not one robot that does everything. A clinic-data agent, a records agent, a receptionist agent. Each does one thing well, and that's what I'm building now.
The playbook drops
The actual prompts, the actual builds, and the parts that broke. Sent as I write them. Not packaged into a course.
Open build logs
What I'm building this week, what failed, and what it cost. No highlight reel. Some of the failures are the useful part.