02 · Foundations

How PepStakk works.

PepStakk is built around a 6-verb journey: Decide, Build, Dose, Run, Resupply, Review. Each verb is a surface in the app. Here's what each one does and how they connect.

~6 min read Foundations · 02 of 03

The frame

Running a peptide protocol involves more moving parts than most tools acknowledge. You have to decide which peptides match your goal, build them into a coherent stakk, calculate the dose math, run the protocol day to day, keep yourself resupplied, and ideally have a clinician review what you're doing periodically.

Before PepStakk, that usually meant six different tools and a spreadsheet to glue them together. The 6-verb frame puts each function in its own surface — and connects them so what you decide flows into what you build, what you build informs how you dose, and what you log feeds your supply forecast and eventually your clinician review.

The Dashboard

The Dashboard is where you start each day. It's the heads-up view of your protocol — today's doses, your stakk overview, what's currently cycling vs tapering, your supply runway, and what needs attention.

If you're new and haven't built a stakk yet, the Dashboard shows a beginner state with primer links back to this site. Once you've built a stakk and have a schedule, the Dashboard becomes the daily landing — open the app, see what to take, log it, move on.

01 · Decide

The research surface. Two tools work together:

The Decide layer is also where the Featured Intelligence news lives — peptide research scored against your current stakk and recent Advisor queries, surfaced as the news feed that's actually relevant to your protocol.

02 · Build

Where you assemble your stakk. Once you've read about a peptide in the Library, you can add it to your stakk with a defined dose, cycle pattern, and goal context. Multiple peptides combine into a single multi-peptide stakk; the Advisor flags compatibility issues or known stack patterns as you build.

Build is also where you set the architecture: cycle length, taper plan, whether the peptide runs continuous or has defined on/off windows. The Schedule tab in Run honors whatever pattern you define in Build.

03 · Dose

The Calculator. Most peptides arrive as lyophilized powder in a vial; you mix them with BAC water to produce an injectable solution. The math — concentration, dose volume, syringe units — is where users most often make errors.

The Calculator handles reconstitution math, syringe profiles (insulin / U-100 / U-40), and shelf-life tracking. Input the peptide weight in the vial, the volume of BAC water you'll add, and the target per-dose amount; the Calculator returns the volume to draw on a U-100 insulin syringe. Save reconstitution profiles so you don't redo the math every cycle.

04 · Run

The Schedule. This is the daily-execution layer — Run tracks what you actually take on what day, not just what your protocol intends.

The Schedule generates day-by-day dose plans from your stakk's cycle definitions. Each scheduled dose can be marked drawn (logged) when you take it — that's the mark drawn action, named because peptide users literally draw doses into syringes. Adherence logging is on the roadmap; for now Run is dose-tracking + scheduling.

Run is also where the supply runway calculation lives — taking your schedule cadence and current inventory to forecast how many days of supply you have, which drives Resupply alerts.

05 · Resupply

The supply side of the platform. PepStakk's Resupply Stack covers four tiers:

The directory surfaces what each vendor has disclosed — third-party COAs, testing methodology, licensing, sourcing — and lets you pick suppliers based on the disclosure quality. Premium Auto-Restock (roadmap) will route reorders automatically when your supply runway hits the restock window.

06 · Review

The clinician layer. PepStakk's Clinician Network is a vetted directory of Reviewing Clinicians — licensed practitioners with peptide-protocol experience who provide async written feedback on Stakker protocols. The point is access on demand without forcing a clinical relationship: request a review, get written feedback within a defined window, use it to refine your protocol.

Reviews are informational, not a clinical relationship. They're a second set of eyes — useful when you're starting something new, adjusting doses, or want a peptide-literate clinician's view on what you're already doing. Async stakk reviews are on the roadmap and gated on the Premium tier launch.

How the verbs connect

The point of the 6-verb frame isn't that they're six separate apps — it's that they're connected. What you read in Decide informs what you Build. Your Build defines your Dose math and Run schedule. Your Run logging drives Resupply forecasting. Everything you've done across the five operational layers becomes context for a Reviewing Clinician in layer 06.

No competitor connects this many layers. Calculators handle Dose. Schedulers handle Run. Content sites handle Decide. Directories handle Resupply. Clinical platforms handle Review. PepStakk is the only platform that ties them together — which is why the integration is the moat.

The PepStakk voice. We're an intelligence and management platform. We provide the information. You decide. The Stakker is in charge of the protocol — PepStakk's job is to make the management easier, the sourcing more transparent, and clinician access available when you want it.