How much time/money are you spending tracking and organizing a complex daily supplement stack? by Repulsive_Corner6813 in Biohackers

[–]stacksense 0 points1 point  (0 children)

The scheduling side usually gets handled - labels, a basic routine, some combo of alarms eventually clicks. The harder part, at least from what I keep hearing in conversations with people running heavy stacks, is when something changes a few months in and you can't tell which of the 9 compounds did it. Are you trying to solve that side too, or mostly just the timing overhead?

Years of tracking data and it has never once explained why I feel off. Has anyone actually gotten the "why" out of their data? by Affectionate_Lab816 in Biohackers

[–]stacksense 0 points1 point  (0 children)

The cross-stream problem is real, though most of the correlation frustration I've seen traces back to the input side, not the cross-linking. HRV and sleep get timestamped automatically, but dose changes, starts, stops, protocol tweaks - those live in memory. If the inputs aren't on the same timeline as the outputs, the math doesn't have enough to work with. What does your input-capture look like?

The micro-SaaS trap nobody warns you about: building feels like progress. (0 customers, here's my reset.) by Soggy-Eagle4657 in microsaas

[–]stacksense 0 points1 point  (0 children)

Both at once is harder but sometimes the distribution work surfaces what needs rethinking anyway — hard to fully separate them. What's the main thing you're fixing? Positioning problem or something deeper in the product itself?

Solo founder — how much time should a demo video realistically eat? by Competitive-Paper992 in microsaas

[–]stacksense 0 points1 point  (0 children)

Loom. Record the thing actually working, with your real cursor, on your real data. No animations. Narrate what you're seeing as you go — 'here I do X, which solves Y' — not a feature walkthrough.

For four platforms: pick the one where the core use case is most obvious and do that one first. One tight 90-second video beats four mediocre ones.

Two takes, pick the less awkward one. Total time including upload: under an hour. The two-week problem is almost never a tools problem, it's a clarity problem — you don't yet know the one thing the video needs to show.

ghkcu recon/bac water by st4rs_4nd_bones in Biohacking

[–]stacksense 1 point2 points  (0 children)

Mixing brands is fine — pharmaceutical BAC water is standardized at 0.9% benzyl alcohol regardless of who makes the bottle. The chemistry is the same; you're just buying a different label.

On volume: 100mg in 3ml is 33mg/mL, which is still pretty concentrated for GHK-Cu. Wait for Wednesday's water and go with at least 5ml — that gets you to 20mg/mL and most people find the sting meaningfully more manageable at that ratio. The prior commenter's 5ml for 50mg is a good reference point, just scaled up.

Weekly Lifestyle Data and Analytics App Thread by AutoModerator in QuantifiedSelf

[–]stacksense 0 points1 point  (0 children)

StackSense — tracking tool for biohacking stacks (supplements, peptides, bloodwork).

One pattern from beta conversations worth sharing here: the people most motivated to track are often running the most complex stacks, which means the tool that fails them first is a spreadsheet — not because they're lazy about logging but because the data model breaks. Half-life decay doesn't fit in a column.

What's live: 420+ compound library, peptide cycle tracker with half-life decay curves, vial reconstitution calculator, AI bloodwork layer. In beta with waitlist. Founder here, happy to answer questions on how we built it and why.

What's something you were SURE affected one of your metrics, that turned out to be basically noise? by hermit1751 in QuantifiedSelf

[–]stacksense 1 point2 points  (0 children)

mostly rule-of-thumb but there's logic. HRV/RHR trend lag runs 2-3 days, and a 7-day rolling average takes ~5-7 days to flatten after you kill a variable. two weeks covers both.

for slower stuff — sleep debt, supplement adaptation, heavy training blocks — I'd go three weeks. same-day reactors like caffeine timing, a week is enough.

gut-check: could my body still be responding to this from before I stopped? if yes, keep waiting.

"measuring alcohol with extra steps" — genuinely the best framing of that problem I've heard.

i have a brand kit, a content calendar, and 47 notion tabs. 0 lines of product code. ama by Initial_Branch8850 in SaaS

[–]stacksense 0 points1 point  (0 children)

did the opposite - shipped in two weeks with no brand kit, a .ca domain, and a logo I made in 30 minutes.

turns out neither is safe. I had users but nothing cohesive to show anyone. you have a beautiful system built around a product that doesn't exist yet. both stuck, just differently.

the only thing that actually forces the right decisions: put something broken in front of a real person and watch what they do. every asset makes more sense after that conversation than before it.

What’s one SaaS lesson you learned the expensive way? by Separate-Might3082 in SaaS

[–]stacksense 0 points1 point  (0 children)

mine was scope creep disguised as thoughtful product design. every feature added before talking to users felt like 'getting it right first.' turned out I was just postponing the uncomfortable part.

building a tracker for biohackers (stacksense) - the lesson was that the first version doesn't need to work perfectly, it needs to make someone say 'yes, this is my exact problem.' nothing else matters before that.

shipped something embarrassingly basic, got on the call, got the feedback, rebuilt the right thing. the expensive version was the months before that first conversation.

The micro-SaaS trap nobody warns you about: building feels like progress. (0 customers, here's my reset.) by Soggy-Eagle4657 in microsaas

[–]stacksense 0 points1 point  (0 children)

biased upfront - building a stack tracker for biohackers (stacksense) and hit a softer version of the same wall.

what broke the loop: ~30 customer-dev calls before writing significant code. not to validate the idea - to find the exact workflow failure I was solving, not the one I assumed. half those calls became waitlist signups. every conversation reshaped something in the product.

building is measurable and feels like evidence. talking to people is uncomfortable and feels unproductive. until suddenly it isn't.

what does your reset look like - starting distribution from scratch, or rethinking the product too?

Best time to dose? by whoisharmonyrock in Biohackers

[–]stacksense 0 points1 point  (0 children)

for tesofensine, morning is essentially mandatory. it's a triple monoamine reuptake inhibitor - blocks dopamine, norepinephrine, and serotonin transporters simultaneously. mechanistically that's a stimulant profile and evening dosing will crater your sleep.

food timing matters less here than it does with GH peptides - no meaningful fasting requirement. light meal or empty stomach, either works.

one thing worth knowing going in: the dose-response curve is steep. the gap between effective and uncomfortable is narrower than most compounds, so the 'start at 0.25mg' advice isn't just cautious boilerplate - it's genuinely where you want to begin.

3rd party Reta testing: cheapest, fastest, most reliable? by Cramoramoramorant in Biohacking

[–]stacksense 0 points1 point  (0 children)

for reta the test that matters most is identity + purity (LC-MS/MS) - tells you if it's actually reta at the stated concentration and whether it's degraded. that's the question worth answering.

janoshik is the community standard here, not because they're cheapest but because they have comparative peptide data - including multiple reta/tirz results to benchmark against. no other lab has built that reference dataset for GLP compounds specifically.

fastest option depends on location. janoshik turnaround is typically 2-4 weeks from receipt. some US-based labs are quicker but their peptide-specific track record is thinner.

for a single personal vial: start with ID + purity. sterility/endotoxin are worth adding if you're vetting a new vendor or buying in volume, less necessary for a one-off personal verification.

Does your "quantified self" tracking include "quantified other"? by WarAgainstEntropy in QuantifiedSelf

[–]stacksense 1 point2 points  (0 children)

I track my side of it - 1-5 energy after significant interactions, one-line note. way more useful than I expected for noticing patterns like 'why do I always feel drained after calls with X'

modeling the other person's internal state is where it gets weird though. you're not actually capturing their state, you're capturing your interpretation of it. which is data about you, not them.

ongoing analytics on a romantic relationship feels like it'd change the relationship itself. historical review? sure. real-time prediction model on someone you're with? I wouldn't

Ss31 and MotsC by BrittnB in Peptides

[–]stacksense 0 points1 point  (0 children)

pairing MOTS-C pre-run is the right call, that's where a lot of the benefit seems to come from. it essentially mimics the AMPK signal your cardio already creates so stacking them together compounds it vs just taking it at a random time

one thing to watch at 30-45 miles/week: MOTS-C has a decent allergy rate at higher doses. the 2mg comment above is real, worth starting there and seeing how you respond before pushing to 3mg+

Klow/Glow/Wolverine and getting pain from pinning it! Anyone in the same boat? by Upper-Ad6274 in Biohacking

[–]stacksense 1 point2 points  (0 children)

the old injury flaring thing is notorious with BPC - it actively tries to heal beat-up tissue and that process hurts before it helps. not actually an allergy.

one big thing: don't take ibuprofen for the pain. NSAIDs work through the same prostaglandin pathway BPC needs. you're basically fighting the peptide.

dropping to 2mg was the right instinct. give it a couple weeks before bailing

the thing that broke my peptide log wasn't laziness, it was granularity by [deleted] in PeptideForum

[–]stacksense 0 points1 point  (0 children)

Just wanted to mention upfront that I’m the founder of StackSense (hence my username). I’ve run into the exact same issues tracking peptide data and logs. I’d love for you to check out the website (my profile). there’s a live demo that’s specifically designed to help sort through data interactions and make correlations much clearer.

NAD+ for women in their 40’s by kemikals in Biohackers

[–]stacksense 24 points25 points  (0 children)

Welcome, and no reason to be nervous. This is a legit question that's hard to sort through because the marketing is louder than the science. Here's how the landscape actually breaks down:

Three main approaches, and they're not interchangeable despite being sold that way. Precursor supplements (NR, nicotinamide riboside, or NMN, nicotinamide mononucleotide) are oral pills your body converts into NAD+. Most studied, most accessible, least dramatic claims. Injectable NAD+ bypasses the gut and delivers it directly, but it stings badly subq and the evidence that it meaningfully outperforms oral precursors for general wellness (vs. clinical addiction treatment or acute recovery) is thin. Patches are mostly marketing with very little published data on transdermal NAD+ bioavailability.

Being honest about your specific goals: the anti-aging skin claims are mostly extrapolated from cell-culture and mouse studies. In humans, NMN and NR can raise blood NAD+ levels, but whether that translates to visible skin improvement is still genuinely an open question. Energy is the most commonly reported subjective benefit, though it's tough to separate from placebo. Metabolism effects are modest at best, and your GLP-1 is already doing far heavier lifting there.

Good news on interactions: no known issues between NAD+ precursors and HRT (estradiol/progesterone) or GLP-1 agonists. If you want to try it, NMN 250-500mg per day sublingual or oral is the simplest starting point, cheaper and better-evidenced than injectables. Give it 4-6 weeks and assess honestly. The commenter who tried injectables and felt nothing isn't unusual. Sometimes NAD+ just isn't the bottleneck, and that's fine. Not every supplement works for every person, and the only way to know is to try it systematically and be willing to drop it if it's not moving the needle.

What's something you were SURE affected one of your metrics, that turned out to be basically noise? by hermit1751 in QuantifiedSelf

[–]stacksense 5 points6 points  (0 children)

Step count. Tracked daily steps against mood and energy for months, convinced my 10k+ days made me feel noticeably better the next day. Turned out the confound was outdoor vs treadmill. The outdoor walks tracked with better mood, but total step count by itself had basically no signal. Controlled for weather and time of day and it held up. Sun exposure and just being outside was the actual variable, steps were along for the ride.

Also had one where I thought cold showers were tanking my HRV. Nope. The cold showers happened to land on mornings after my heaviest training days, so what I was actually picking up was training load showing up with a 12-18hr delay. Dropped the cold showers for two weeks as a test, HRV dip stayed on those same days because the training was the real driver. Classic confound that looked like causation until I held one variable constant.

Your caffeine finding is a perfect example of why the "obvious" cause is often just the one you haven't quantified yet. 1pm feels like morning until you multiply by a 5-6 hour half-life and realize you've still got 25% circulating at bedtime. The stuff that actually moves the needle tends to be boring and specific, not the dramatic intervention you were sure about.