Most peptide protocol tools on the internet hand you a list of compounds and call it a protocol. No sequencing. No conflict check. No foundation logic. The Protocol Builder works differently because it starts with the question most tools skip entirely: is your system ready to benefit from the compound you are considering?
The Protocol Builder is a free interactive tool that builds a research protocol framework from your specific inputs. It does not generate a generic stack. It asks what you are running, where you are in your research, and what problem you are actually trying to solve. Then it sequences compounds by priority, checks for receptor conflicts between everything in the stack, and produces a timing framework so you know when to introduce each layer and why.
This post walks through exactly how the tool works, what it asks, and what it produces. If you want to understand the logic before you run it, this is the reference.
Answer a short intake about your research goal, current compounds, dose, timeline, and foundations. The tool sequences compounds by layer, checks for receptor conflicts across the full stack, and builds a timing framework from your specific inputs.
Free. No login. Run it as many times as you want.
If you want to understand the logic behind the tool before you use it, keep reading. The rest of this post breaks down every step the tool runs, why it asks each question, how the conflict detection works, and what the output means.
Researchers who are considering their first peptide protocol and want to understand the decision logic before committing to a compound.
Researchers who are already running a GLP-1 compound and want to know what support compounds make sense for their specific situation, in what order, and what conflicts to watch for.
Anyone who has searched for "peptide protocol builder" or "peptide stacking chart" and found tools that hand out compound lists without explaining when each addition actually makes sense.
What the Tool Asks and Why
The Protocol Builder opens with a short intake. Each question narrows the recommendation. Nothing is random and nothing is filler. The tool asks about your primary research goal, where you are in your research timeline, which GLP-1 compound you are running if any, your current dose, how long you have been on it, and what other compounds are already in your stack.
It also asks about four foundation variables: sleep quality, daily protein intake, stimulant consumption, and whether you have a consistent training routine. These are not lifestyle questions. They are protocol prerequisites. The tool checks them because a compound added to a system that cannot support it does not produce the expected result. It amplifies the existing gap.
The reason for the dose and duration questions is steady state. Compounds with long half lives like retatrutide take multiple weeks to reach full circulating levels. If someone is three weeks into retatrutide at a starting dose and thinks it is not working, the tool needs to know that before recommending a change. The answer might be to hold, not to escalate or switch.
The Foundation Check
Before the tool recommends a single compound, it evaluates four inputs. If any of these are flagged, the tool tells you what to address and why. It does not block you from seeing the rest of the protocol. It tells you the protocol will underperform until the gap is fixed.
Foundation gaps do not mean you cannot start. They mean the protocol will underperform until addressed. Fix in parallel, not after failure.
The Three Layer System
The Protocol Builder organizes every compound into one of three layers. The layers are not categories for sorting. They are a sequencing framework. Layer 1 goes first because it creates the metabolic demand that determines what the rest of the protocol needs to support. Layer 2 responds to a predictable consequence of that demand. Layer 3 responds to specific problems that emerge during the protocol and cannot always be predicted in advance.
This is the difference between stacking and sequencing. Stacking is adding compounds. Sequencing is adding them in the right order, at the right time, in response to the right signal.
| Layer | Function | Compounds |
|---|---|---|
| Layer 1 | The intake suppression or thermogenic pathway. The GLP-1 class compound that drives the primary research objective. The choice within this class determines the metabolic demand the rest of the protocol must support. | Semaglutide, Tirzepatide, Retatrutide, Cagrilintide |
| Layer 2 | The lean mass and recovery pathway. GH secretagogue compounds that support growth hormone output. Added in response to lean mass loss or when loss is anticipated from the protocol design. Planning this layer from week 4 is prevention. Adding it at week 12 when muscle loss is visible is correction. | CJC-1295 no DAC + Ipamorelin, Tesamorelin + Ipamorelin, Sermorelin, GHRP-2, GHRP-6, HGH Fragment 176-191 |
| Layer 3 | The support and repair pathway. Compounds that address specific emerging bottlenecks: tissue repair, cellular energy, sleep architecture, immune support, hormonal maintenance. Added in response to a specific identified problem. Not preemptively. Not speculatively. | BPC-157, TB-500, MOTS-c, SS-31, KPV, Gonadorelin, Epithalon, Thymosin Alpha-1 |
The tool presents Layer 2 as two options, not one. Option A is CJC-1295 no DAC paired with Ipamorelin. Option B is Tesamorelin paired with Ipamorelin. Both use Ipamorelin to fire the growth hormone pulse. The difference is which compound loads the pituitary gland (the gland that produces growth hormone). CJC-1295 and Tesamorelin both target the same receptor, called GHRHR. That is why you pick one, not both. Running both at the same time is redundant signaling on the same receptor with no additional benefit.
How Conflict Detection Works
After the tool builds your protocol, it runs every compound in the stack against every other compound and checks for four types of interactions. This is the part most protocol tools skip entirely. They hand you a list and let you figure out whether two compounds are fighting each other for the same receptor.
The Protocol Builder does not just flag conflicts. It explains what the conflict means in plain language and what to do about it. Some conflicts are hard stops where you need to choose one compound or the other. Some are timing adjustments where you extend a fasted window or shift an injection day. Some are not conflicts at all but pairings that work better together than alone.
Two compounds target the same receptor. Running both simultaneously produces no additive benefit and may reduce signal from either. The tool flags this and tells you to choose one or stagger by sufficient washout. Example: Semaglutide and Tirzepatide both target GLP-1R. Running them together saturates the receptor.
No receptor competition, but one compound's mechanism interferes with the injection conditions required by the other. The most common example: any GLP-1 compound slows gastric emptying, which means the fasted window before a GH secretagogue injection needs to extend from two hours to at least three.
Two compounds that work through complementary mechanisms and are designed to be used together. Example: CJC-1295 loads the pituitary with a growth hormone releasing signal, and Ipamorelin fires the pulse 15 to 30 minutes later. BPC-157 handles localized repair while TB-500 provides systemic recovery support.
Not a true conflict. The mechanisms are complementary or additive, but the combined effect should be tracked. Often appropriate to run together with monitoring. Example: Cagrilintide combined with Retatrutide. Both suppress appetite through entirely separate receptor systems, but combined intake suppression may reduce caloric intake beyond the intended range.
When the tool finds no conflicts across the full stack, it displays a clean stack confirmation. That confirmation means every compound in the protocol is either additive or complementary with no receptor overlap and no timing interference that has not been accounted for.
The Protocol Intelligence Tool maps every compound in your current stack to its receptor targets and flags where two compounds are driving the same binding site. If you want to analyze what you are already running rather than build a new protocol from scratch, this is the tool built for that.
Run the Protocol Intelligence ToolThe Timing Framework
The last section of the output is a week by week timeline that tells you when to introduce each layer. This is not a fixed calendar. It adjusts based on your inputs. If you have foundation gaps, the timeline pushes compound introduction back by four to six weeks so you have time to address them first. If you are already running a stable GLP-1 protocol with solid foundations, the timeline moves Layer 2 and Layer 3 additions forward.
A typical timeline for a new researcher with no foundation flags might look like this: begin your Layer 1 compound at the lowest dose in week one. Evaluate the response at week four. Has the compound reached steady state? Is it tolerable? Titrate if indicated. Introduce the GH secretagogue pairing around week four to six if lean mass concern is present. Add Layer 3 support compounds after week six to eight, only in response to a specific identified problem. Full protocol review at week twelve where you evaluate all layers, foundation status, and what has changed.
For experienced researchers who are already running a multi compound stack and considering a compound change, the timeline adjusts differently. It factors in washout periods between GLP-1 compounds (typically five to seven weeks for receptor clearance), accounts for the steady state timeline of the new compound, and sequences any Layer 2 or Layer 3 adjustments around the transition.
Compounds the Tool Currently Covers
The Protocol Builder includes logic for the following compounds. Each one has specific dosing context, titration guidance, receptor data, and conflict mapping built into the tool. This list determines what the tool can evaluate. If a compound is not listed here, the tool does not currently include it in its recommendation engine.
| Compound | Class | Receptor Targets |
|---|---|---|
| Semaglutide | GLP-1 receptor agonist | GLP-1R |
| Tirzepatide | GLP-1 / GIP dual agonist | GLP-1R, GIPR |
| Retatrutide | GLP-1 / GIP / glucagon triple agonist | GLP-1R, GIPR, GcgR |
| Cagrilintide | Amylin analog | Amylin receptors (CALCR/RAMP) |
| Compound | Class | Receptor Targets |
|---|---|---|
| CJC-1295 no DAC | GHRH analog | GHRHR |
| Tesamorelin | GHRH analog | GHRHR |
| Sermorelin | GHRH analog | GHRHR |
| Ipamorelin | GH releasing peptide | GHSR-1a |
| GHRP-2 | GH releasing peptide | GHSR-1a |
| GHRP-6 | GH releasing peptide | GHSR-1a |
| HGH Fragment 176-191 | GH fragment | Lipolytic pathway (no GHR activation) |
| Compound | Category | Primary Application |
|---|---|---|
| BPC-157 | Tissue repair | Localized healing, gut repair, nitric oxide pathways |
| TB-500 | Systemic repair | Cell migration, systemic recovery signaling |
| MOTS-c | Mitochondrial peptide | Cellular energy, metabolic rate, AMPK activation |
| SS-31 | Mitochondrial peptide | Mitochondrial membrane stability, energy depletion |
| KPV | Anti-inflammatory | GI inflammation, gut barrier support |
| Gonadorelin | Hormonal support | HPG axis maintenance, LH/FSH signaling |
| Epithalon | Anti-aging | Telomere elongation, pineal function |
| Thymosin Alpha-1 | Immune modulation | Immune regulation, FDA orphan drug status for Hep B |
What the Tool Does Not Do
The Protocol Builder produces a research protocol framework. It is not a prescription. It does not replace bloodwork, and it does not account for individual medical history, hormonal status, or contraindications that only a qualified professional can evaluate.
The tool also has structural limits. It cannot assess why a specific compound is not producing results for a specific researcher when the framework says it should. It cannot evaluate whether a stall at week eight is a dose issue, a timing issue, a compound fit issue, or a foundation issue that the researcher did not accurately report. Those questions require a personalized analysis that maps every variable specific to the researcher's situation.
That is the difference between a framework and an audit. The Protocol Builder gives you the framework. The Protocol Audit gives you the personalized read.
Full stack visualizer with receptor overlap detection. Deep bottleneck analysis with compound-specific routing. 50+ research deep dives. The complete guide library. One membership.
See What Members GetFor educational and research purposes only | Not medical advice | Not for human use guidance | Project Theo