Why I Built PeptideTrack

The $200 Mistake

It started with a ruined vial of BPC-157. I was doing the math in my head, got distracted, and drew way too much. By the time I realized my mistake, the vial was contaminated and I had to throw it out.

$200, gone in seconds.

I'm not bad at math. I'm a Lead 5G Core architect - I work with complex systems every day. But doing vial reconstitution math while tired, or distracted, or in a hurry? It's a recipe for expensive mistakes.

The Problem Nobody Was Solving

I looked for apps that could help. What I found was disappointing:

• Generic medication trackers that didn't understand vial math
• Calculators that required re-entering info every time
• Nothing that showed me what my dose actually looked like in a syringe

I knew I could build something better.

Building in Public

I decided to build PeptideTrack as a nights-and-weekends project, documenting everything along the way. No VC funding, no team - just me solving a problem I personally have.

The core features came from my own pain points:

• **Visual syringe rendering** because I wanted to SEE my dose before drawing
• **Error-proof vial math** because one mistake is one too many
• **Safety warnings** because high doses should require acknowledgment
• **Inventory tracking** because running out mid-protocol is frustrating

What's Next

I'm launching the iOS version first, with Android coming soon. The app is free for single-protocol tracking, with a Pro tier for those who need unlimited protocols and cloud sync.

I'm building this for people like me - people who want to track their protocols safely without the anxiety of manual calculations.

If that sounds useful to you, download PeptideTrack and let me know what you think. I read every piece of feedback.