Built a free blood work tracker for TRT - need beta testers

LabTracker

Member
Like most of you, I've been tracking my blood work in spreadsheets for years. Every time I got labs back I'd manually type values into Excel, try to remember what protocol I was on at the time, and squint at charts trying to figure out if that hematocrit bump was because I went from 115mg to 120mg or because I switched from enanthate to cypionate.

After doing this for a while I got frustrated enough to build something better. LabTracker is a web app that lets you upload your lab PDF and immediately see your markers charted over time, tracked against your protocol changes.

01-darkmode.webp


Here's what it does:
  • Upload your lab PDF instead of typing everything by hand. It reads LabCorp, Quest, and most other standard lab formats. Scanned PDFs work too (it runs OCR in your browser).
  • Track protocols alongside markers. Log your compound, dose, and frequency. When you change protocol, the app shows what actually changed in your blood work. Before vs. after with percentage deltas for every marker.
  • Trend charts with clinical context. Reference ranges, TRT target zones, and trend direction for every marker. Supports both US and European units.
  • Alerts that flag when markers cross thresholds (hematocrit > 52%, PSA trending up, etc.) and project future trends based on your history.
  • Supplement timeline. Track your supplement stack separately from your protocol, with auto-matching to blood tests.
  • Wellbeing check-ins. Log energy, mood, sleep, libido, motivation on a simple scale. Builds a timeline you can compare against your labs.
Why this is different from just another chart viewer:

Most of us already track some of this stuff, but it's all over the place. Labs in a PDF folder, protocol history in your head or a forum post, supplements in a notes app, how you feel in... nowhere, usually. The problem isn't the individual pieces. It's that nothing connects them.

That's what I built this for. When everything lives in one place, you start seeing things you'd miss otherwise. You switch from enanthate to cypionate, did your estradiol actually change? You added NAC three months ago, what happened to your liver markers? You bumped your dose from 110 to 120 and logged feeling better two weeks later, does the blood work back that up?

That connected view across labs, protocol, supplements and symptoms is what I always wanted from a tracking tool and could never find anywhere.

Privacy, because this matters:

No account, no login, no email required. Your data stays in your browser's local storage. Nothing gets sent to a server.

The only exception is the AI analysis feature, which is off by default. If you choose to turn it on, it sends only your marker values (numbers and names) for analysis, not your name, DOB, lab info, or anything identifying. You get a consent prompt every time before anything leaves your device.

No ads, no affiliate links. I built this because I needed it myself.

Screenshots:

03-wellbeing.webp

05-alert.webp

04-doseimulator.webp

06-aianalysis.webp

02-lightmode.webp


Try it out:

You can play with the demo data here to get a feel for it: www.labtracker.app

When you're ready to use your own labs, click "Start fresh" and upload a PDF.



Where I really need your help​

The hardest part of this entire project isn't the charts or the protocol tracking. It's the PDF parsing. Every lab uses a different format, different layouts, different ways of writing reference ranges. I've tested against LabCorp, Quest, and a handful of European formats, but I know there are dozens more out there. Private labs, hospital systems, international formats, scanned copies from your doctor's office.

The more lab formats I can test against, the better the parser gets for everyone.

There are two ways you can help:

1. Upload and report. Just try uploading your PDF. If it works, great. If it doesn't parse correctly (wrong values, missing markers, broken date), hit the "Report a parsing issue" button in Settings. That sends me a description of what went wrong without the PDF itself.

2. Send me your actual PDF. This is honestly the most valuable thing anyone can do to help improve the tool. The parser is built and tested against real PDFs, and the more variety I have, the fewer edge cases slip through. If you're willing, you can email a PDF to [email protected]. Feel free to redact your name, DOB, SSN, whatever you want. I only need the marker table and layout.

I want to be upfront about what happens with PDFs you send me. I use them exclusively to test and improve the local parser, which is the code that runs in your browser. They don't get uploaded to any AI service, they don't get shared with anyone, and they don't leave my development machine. Once the parser handles your format correctly, the PDF has done its job. If you want me to delete it after, just say so and I will.

I realize that's a trust-based ask and you don't know me. So I'd say: start by trying the app with the demo data, look at the source code if you want (it's open source: [GitHub link]), and decide from there whether you're comfortable.



Other feedback I'd love to hear:
  • Does the protocol impact view match your real-world experience?
  • Are there markers or features you'd find useful that aren't there yet?
  • How does it handle your specific lab format?
  • Any general bugs, things that look broken or behave weird (this is a beta, still in development)
  • Anything that seems off in the calculations or logic. If a percentage change doesn't add up, or a trend direction doesn't match what you're seeing in your own numbers, I want to know about it
On pricing:

Everything is free during the beta. I'm planning to keep the core features (upload, charts, protocols, exports) free permanently and eventually add a paid tier for AI analysis and some advanced features. But right now it's all open. Use it, break it, tell me what needs fixing.
 
I'm the developer behind Himcules on the iOS App Store, and I respect what you're doing here. Manual tracking is genuinely painful, and the fact that you built something to solve it means you've felt the same friction I did.

One thing I'd push back on gently: web apps work, but most of us check our trends on mobile. I built Himcules as a native iOS app specifically because I was tired of pulling up a browser to log a dose or glance at my E2 trajectory. The native experience just feels different when you're doing it twice a week for years.

Your approach of parsing lab PDFs is solid. I went a different direction—manual entry with smart defaults and quick-add shortcuts—because I wanted to capture protocol context at injection time, not just numbers after the fact. That's where you learn whether a protocol tweak actually worked.

The beta tester thing is smart. Real feedback from guys actually running cycles will show you what matters. A few questions: are you planning to track injection protocol alongside labs, or keeping them separate? And how are you handling the fact that lab timing relative to injections massively affects what you're looking at?
 
I'm the developer behind Himcules on the iOS App Store, and I respect what you're doing here. Manual tracking is genuinely painful, and the fact that you built something to solve it means you've felt the same friction I did.

One thing I'd push back on gently: web apps work, but most of us check our trends on mobile. I built Himcules as a native iOS app specifically because I was tired of pulling up a browser to log a dose or glance at my E2 trajectory. The native experience just feels different when you're doing it twice a week for years.

Your approach of parsing lab PDFs is solid. I went a different direction—manual entry with smart defaults and quick-add shortcuts—because I wanted to capture protocol context at injection time, not just numbers after the fact. That's where you learn whether a protocol tweak actually worked.

The beta tester thing is smart. Real feedback from guys actually running cycles will show you what matters. A few questions: are you planning to track injection protocol alongside labs, or keeping them separate? And how are you handling the fact that lab timing relative to injections massively affects what you're looking at?
Appreciate the thoughtful response, and respect for building Himcules. It takes a certain kind of frustration to actually ship something instead of just complaining about spreadsheets.

On mobile: fair point, and I'll be honest about it. LabTracker is a web app, just go to labtracker.app, no install needed. The tradeoff is deliberate: no app store friction, works on any device, nothing to update. That said, the charts and trend views genuinely shine on a bigger screen. If you're doing a deep dive into your lab history, a desktop or tablet gives you a lot more to work with. For a quick check on your phone it works fine, but I'd be lying if I said it's optimized for mobile-first use the way a native app can be.

On your two questions:

Injection protocol tracking: it's already there. Every report has protocol context attached: compound, dose, frequency. There's a dedicated Protocol Impact view that shows before/after deltas for every marker when you change dose or compound. You can see what actually moved, with percentages, not just raw values next to each other.

Screenshot 2026-03-03 134312.webp


Screenshot 2026-03-03 134340.webp


Lab timing relative to injections: also already tracked. Sampling timing is a required context field per report, trough, mid-cycle, peak, or custom. The AI analysis uses it explicitly; a testosterone value means something different at trough vs. 24 hours post-injection, and the tool knows which it's looking at.

photo_2026-03-03_13-50-23.webp


Your injection-time logging is a different product category really, a dose journal that doesn't connect to labs. LabTracker works the other way around: labs are the primary data source, and protocol context exists to explain what you're seeing in the numbers. Different starting points, different use cases. Some people will want both.

To anyone else reading: the app is at labtracker.app, demo data can be preloaded, no login required. Would love to hear how it handles your lab format.
 

Attachments

  • Screenshot 2026-03-03 133518.webp
    Screenshot 2026-03-03 133518.webp
    43.6 KB · Views: 1
  • Screenshot 2026-03-03 133616.webp
    Screenshot 2026-03-03 133616.webp
    69.1 KB · Views: 1
  • Screenshot 2026-03-03 134340.webp
    Screenshot 2026-03-03 134340.webp
    47.7 KB · Views: 0
Last edited:

ExcelMale Newsletter Signup

Online statistics

Members online
4
Guests online
327
Total visitors
331

Latest posts

Beyond Testosterone Podcast

Back
Top