The Vet Visit That Made My Side Project Real

I built PawFormance for three reasons: Wick, Maya Rudolph, and Benny Hartz. My corgi, my Australian Shepherd, and my other corgi, respectively.

Like most side projects, it started with scratching my own itch. I had notebooks with scribbled dates, a Notes app full of "when did we last deworm?", scattered vet receipts, and that nagging feeling that I was forgetting something important about my dogs' health.

So I did what developers do. I built something.

The Technical Part (Spoiler: Not the Interesting Part)

The stack was straightforward. Next.js for the frontend, Supabase for the backend, Vercel for hosting. Built a CRUD app for pet health records—vaccines, vet visits, medications, weight tracking. Added some charts because data visualization makes everything feel more legitimate.

The build itself was unremarkable in the best way. Modern tooling is so good now that the actual construction of a pet health tracker is almost boring. Authentication? Solved. Database? Done. Responsive design? CSS Grid and Tailwind make it almost trivial.

I finished the MVP in a few weekends. Deployed it. Used it myself for a couple months. Felt good about actually shipping something instead of letting it rot in a private repo like so many other projects.

The Part I Didn't See Coming

Three months after launch, Wick started limping.

Not dramatically—just favoring his back left leg. At first I thought maybe he'd overdone it at the dog park. But it persisted. So I scheduled a vet appointment.

This is where PawFormance stopped being a side project and became... something else.

Sitting in the exam room, the vet asked when I first noticed the limp. I pulled up the app. I'd logged it four days ago, noting it was worse after walks. She asked about his weight trend. I had six months of weigh-ins charted. She asked when his last vaccination was and whether we'd had any recent medication changes. I had exact dates for everything.

The appointment went from "let's figure out what's happening" to "let's treat what's happening" about fifteen minutes faster than usual.

Wick's fine, by the way. Mild strain, some rest, good as new. But I sat in my car afterward and realized something I should have known but didn't really feel until that moment:

The value of what you build reveals itself in the quiet moments, not at launch.

What I Learned Building for My Own Dogs

When you're heads-down in code, you think about features. Edge cases. Performance optimization. Will the calendar component handle timezone differences? Should I add photo uploads? What about multi-pet households?

What you don't think about is the relief of having your dog's entire health history in your pocket when you need it. You don't think about the subtle confidence boost of being able to answer your vet's questions with precision instead of "uh, maybe March? Or was it April?"

You definitely don't think about how tracking your dog's weight over time will let you catch that gradual gain that indicates you've been a little too generous with the treats.

The technical problems are solvable. The emotional impact is unpredictable.

Still Just a CRUD App

I haven't raised funding. I'm not scaling to millions of users. PawFormance is still fundamentally a database with a nice interface. But it's useful. And it's used. Not just by me—other dog owners found it and started tracking their pets too.

Some sent me emails about their own vet visits going smoother. One person thanked me because they finally had all their dog's information organized before an emergency trip to the animal hospital. That one made me tear up a little.

This isn't a post about growth hacking or technical architecture. It's about the weird gap between shipping code and understanding what you actually built.

The product worked the day I deployed it. But I didn't understand its value until Wick limped and the data was just... there.

---

If you've got dogs (or cats, or both), and you've ever scrambled to remember dates during a vet visit: pawformance.app

Start Tracking Free — because the data you'll need is always the data you forgot to write down.