You are running a GLP-1 compound and it is working. Fat is coming off. But somewhere around week six or eight, a second question shows up: what else should I be running alongside this? The internet gives you a list of compounds. Nobody tells you which ones actually solve a problem you have, which ones fight each other for the same receptor, or when to introduce them. That is what this guide covers.
Every search for "what to stack with semaglutide" or "best peptides to take with tirzepatide" returns the same kind of page. A list of compound names, a vague claim that they "support" your protocol, and no logic connecting any of it. No sequencing. No conflict check. No explanation of when each addition makes sense versus when it is a waste of money or actively working against you.
This guide works differently. It walks through the stacking decision layer by layer, starting with the question that matters most: what specific problem is the next compound solving? If you cannot answer that clearly, you are not stacking. You are guessing.
The tool checks for receptor conflicts across your full stack and builds the sequencing for you. Answer a short intake about your research goal, current compounds, and foundations. It produces a layer by layer protocol framework with timing for every addition.
Free. No login. Run it as many times as you want.
If you want to understand the stacking logic yourself before running the tool, the rest of this post breaks down every layer, explains the two GH secretagogue options and why you pick one, covers the support compounds tied to specific problems, and shows you which combinations create receptor conflicts that most stacking guides never mention.
Researchers currently running semaglutide, tirzepatide, or retatrutide who want to know what support compounds make sense for their specific situation and in what order.
Researchers who have searched for "peptide stacking protocol" or "peptide stacking chart" and found lists of compounds without any logic connecting them to a specific problem.
Anyone who has been told to "add CJC and Ipa" or "throw in some BPC" without being told why, when, or what to watch for.
The Mistake That Starts Most Stacking Conversations
The most common stacking question is some version of "can I add tirzepatide to my retatrutide" or "should I stack semaglutide with tirzepatide." The answer is no, and the reason is receptor overlap.
Semaglutide targets one receptor called GLP-1R. Tirzepatide targets two receptors: GLP-1R and GIPR. Retatrutide targets three: GLP-1R, GIPR, and GcgR (the glucagon receptor). Every single one of these compounds already occupies GLP-1R. When you stack two of them together, both compounds are competing for the same binding site. The receptor does not produce a stronger signal because two compounds are hitting it. It is already occupied. You get receptor saturation with no additional benefit and a significant increase in side effect load.
This is the difference between stacking and doubling. Stacking means adding a compound that solves a different problem through a different mechanism. Doubling means pushing harder on a pathway that is already being fully driven. Every GLP-1 on GLP-1 combination is doubling.
| Compound | Class | Receptors |
|---|---|---|
| Semaglutide | Single agonist | GLP-1R |
| Tirzepatide | Dual agonist | GLP-1R + GIPR |
| Retatrutide | Triple agonist | GLP-1R + GIPR + GcgR |
| Cagrilintide | Amylin analog | Amylin receptors (CALCR/RAMP) |
Notice that cagrilintide is the only compound in the table that targets a completely different receptor system. That is why the CagriSema combination (cagrilintide paired with semaglutide) was studied in clinical trials. The two compounds drive satiety through independent pathways. Amylin and GLP-1 do not compete for the same receptor. That is what a legitimate stack looks like: two tools solving different problems through different mechanisms.
Good stacking solves different bottlenecks. Bad stacking pushes harder on the same one. Before adding any compound, ask: what specific problem is this solving that is not already being solved?
Layer 2: Protecting Lean Mass With GH Secretagogues
Layer 2 in the stacking framework is the lean mass and recovery pathway. This is the most common and most justified addition to a GLP-1 protocol, and the research supports it. A 2025 meta-analysis across 22 randomized controlled trials found that roughly 25% of weight lost on GLP-1 compounds is lean mass. That means for every four pounds lost, approximately one pound is muscle tissue. The faster the weight comes off and the less protein and training are in place, the higher that ratio climbs.
GH secretagogues are compounds that stimulate your body's own growth hormone production. They do not replace growth hormone externally. They work with the existing pituitary signaling system, which is why they carry a different profile than exogenous GH. The Protocol Builder presents Layer 2 as two options, not one. Both use the same pulse firing compound (Ipamorelin) paired with a different loading compound.
CJC-1295 No DAC is a short acting GHRH analog. It loads the pituitary gland (the gland that produces growth hormone) with a releasing signal. Ipamorelin works through a separate receptor called GHSR-1a and fires the pulse 15 to 30 minutes later. Together they produce significantly more GH output than either compound alone.
CJC-1295 has a short active window, which makes it the one GH secretagogue where bedtime injection is a rational choice. The pulse completes before the natural GH peak during deep sleep arrives intact.
Tesamorelin is also a GHRH analog but with the most extensive human clinical trial data of any GH secretagogue. It was FDA approved for a specific medical application, giving it a documented safety and efficacy profile no other secretagogue can match. Research data suggests it preserves lean mass during caloric restriction and supports visceral fat reduction.
Tesamorelin has a 2 to 3 hour active window. Bedtime injection is suboptimal because the signal fades before the natural overnight GH peak. Morning fasted injection is the standard.
The critical point is that CJC-1295 and Tesamorelin both target the same receptor: GHRHR. That is the growth hormone releasing hormone receptor on the pituitary. Running both at the same time is redundant signaling on the same binding site with no additional benefit. You pick one. The choice depends on whether clinical trial validation matters to you (Tesamorelin) or whether bedtime dosing convenience and a shorter active window fits your protocol better (CJC-1295 No DAC).
The GLP-1 timing interaction
Every GLP-1 compound slows gastric emptying. That means food stays in the stomach longer than it normally would. GH secretagogues require a fasted state to produce a full pulse because elevated insulin suppresses the GH signal. The standard recommendation for most people is to fast two hours before injecting a GH secretagogue. On an active GLP-1 protocol, that window is not long enough. The food is still there. The insulin is still active. Research suggests extending the fasted window to at least three hours, and some researchers report that four to five hours is the reliable threshold on higher GLP-1 doses.
This is not a conflict. It is a timing adjustment. The Protocol Builder flags this automatically for every GLP-1 and GH secretagogue combination.
When to add Layer 2
Lean mass support added at week four is prevention. Lean mass support added at week twelve when muscle loss is already visible is correction. Prevention is significantly easier. By the time lean mass loss shows up in the mirror or on the scale, weeks of tissue have already been lost that caloric restriction alone cannot replace.
The Protocol Builder recommends introducing the GH secretagogue pairing around week four to six if lean mass concern is present and foundation variables (sleep, protein, training) are in place. If foundations are not in place, the timeline pushes back until they are.
GH secretagogues require resistance training as the input signal. Without training, these compounds have nothing to amplify. The tool will not recommend a Layer 2 addition to someone who is not training.
Layer 3: Support Compounds Tied to Specific Problems
Layer 3 is the support and repair pathway. These compounds are not added preemptively and not added speculatively. They are added in response to a specific identified problem that has emerged during the protocol. The key differentiator from every stacking chart on the internet is that this guide tells you WHEN each addition makes sense, not just WHAT to add.
Three problems come up most often during a GLP-1 protocol: GI distress, energy decline, and injury or tissue repair. Each one has a specific compound or compound pairing that addresses it through a distinct mechanism.
GI sensitivity on a GLP-1 protocol has two common sources. The first is dose. If GI issues appeared at a specific dose, reducing by one titration step is always the first intervention. The second source is gut inflammatory response independent of dose. Published research (Dalmasso et al., 2008) confirmed that KPV inhibits NF-kB (a protein that drives inflammation) in colonic cells. KPV targets the MC1R receptor, which is a completely different system than any GLP-1 compound.
When to add it: only after confirming that the GI problem is not a dose issue. If reducing the GLP-1 dose resolves the symptoms, the compound was never needed. If GI persists at a tolerable dose, KPV becomes a reasonable Layer 3 addition.
Two compounds address energy, but they target two different failure patterns. Choosing the wrong one wastes time and money because the mechanism does not match the problem.
MOTS-c targets metabolic flexibility, which is the body's ability to switch between glucose and fat as fuel. It activates the AMPK pathway (a cellular energy sensor). Research suggests it is most relevant when energy drops during exercise or between meals, or when the body seems unable to access stored fuel efficiently. Energy that drops specifically during caloric restriction often fits this pattern.
SS-31 targets the inner mitochondrial membrane itself. It stabilizes the membrane structure called cardiolipin. Research suggests it is most relevant when fatigue is persistent and does not recover with rest, sleep, or nutrition. It is often the better fit when there is a history of prolonged caloric restriction, chronic stimulant use, or poor recovery capacity over months. SS-31 does not produce an acute felt sensation. The absence of immediate effect is the correct response, not a sign of failure.
If the pattern is unclear, MOTS-c is the less invasive starting point. Do not run both simultaneously.
These two compounds are a standard pairing because they cover different repair windows through complementary mechanisms. BPC-157 handles localized repair through nitric oxide pathways and angiogenesis (new blood vessel formation). It is most studied for gut, tendon, and ligament recovery. TB-500 handles systemic repair through actin regulation and cell migration to injury sites. Together they cover local and systemic repair without redundancy.
There is also a dimension most compound lists miss: BPC-157 functions as indirect cortisol management. Unresolved injuries keep cortisol chronically elevated. Resolving the injury through BPC-157's anti-inflammatory mechanism removes one of the most common invisible sources of cortisol elevation that silently caps fat loss results.
When to add it: only in response to a specific injury, gut issue that is not responding to dose adjustment, or documented connective tissue concern. Not preemptively. Not because someone on a forum told you to.
| Problem | Compound | Receptor / Pathway | When |
|---|---|---|---|
| GI distress | KPV | MC1R | After ruling out dose as the cause |
| Energy decline (metabolic) | MOTS-c | AMPK pathway | After fixing foundation variables |
| Energy decline (structural) | SS-31 | Cardiolipin | After fixing foundation variables |
| Injury / tissue repair | BPC-157 + TB-500 | NO synthase + Actin | In response to specific injury |
How to Check for Conflicts Across Your Stack
Every compound you add to a protocol interacts with every other compound already in the stack. Most stacking guides ignore this entirely. They give you a list and let you figure out whether two compounds are fighting each other for the same receptor. The Protocol Builder runs every compound against every other compound and checks for four types of interactions.
Two compounds target the same receptor. Running both saturates the binding site with no additive benefit. Choose one or stagger by sufficient washout. Example: Semaglutide and Tirzepatide both target GLP-1R. CJC-1295 and Tesamorelin both target GHRHR.
No receptor competition, but one compound interferes with the conditions the other requires. Most common: every 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 designed to work together through complementary mechanisms. CJC-1295 loads the pituitary, Ipamorelin fires the pulse. BPC-157 handles local repair, TB-500 handles systemic recovery. These are additive by design.
Not a conflict. The mechanisms are complementary or additive, but the combined effect should be tracked. Example: Cagrilintide combined with Retatrutide. Both suppress appetite through different receptor systems, but combined intake suppression may reduce calories beyond the intended range.
The most common conflicts researchers do not catch on their own: Ipamorelin and GHRP-6 both activate GHSR-1a (choose one, do not run both). Any two GLP-1 class compounds share GLP-1R (always a hard stop). CJC-1295 and Tesamorelin share GHRHR (redundant, pick one). These are not edge cases. They are the combinations that show up in half the "stacking protocols" shared on forums.
The Protocol Intelligence Tool maps every compound in your current stack to its receptor targets and flags where two compounds are competing for 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 ToolWhen to Add Each Layer
Stacking is not just about what to add. It is about when to add it. The wrong compound at the right time still works better than the right compound at the wrong time. The Protocol Builder produces a week by week timeline that adjusts based on your inputs, but the general framework for a fat loss protocol looks like this.
For experienced researchers switching between GLP-1 compounds, the timeline is different. You need to account for the washout period between compounds. Semaglutide and retatrutide both have long half lives, roughly 168 hours and 148 hours respectively. That means five to seven weeks of washout before the old compound clears and the new one can be evaluated cleanly. The Protocol Builder factors this into the timeline automatically.
What Not to Stack
Some combinations seem logical from a compound list perspective but fail the receptor data test. These are the stacks that show up constantly in forums and community groups that the research does not support.
| Combination | Why Not |
|---|---|
| Semaglutide + Tirzepatide | Both target GLP-1R. Receptor saturation with no additional signal. Choose one GLP-1 compound. |
| Retatrutide + Tirzepatide | Shared GLP-1R and GIPR. The only unique mechanism retatrutide adds over tirzepatide is glucagon receptor activity. Stacking both does not preserve that advantage. |
| Retatrutide + Semaglutide | Shared GLP-1R. Running both saturates the receptor. One compound should be active at a time. |
| CJC-1295 No DAC + Tesamorelin | Both target GHRHR. Redundant signaling on the same pituitary receptor. Pick one GHRH analog. |
| Ipamorelin + GHRP-6 | Both activate GHSR-1a. Running both simultaneously does not double the GH pulse. The receptor is already occupied by either compound. Choose one. |
The underlying principle is simple. If two compounds share a primary receptor target, running both at the same time produces no additive benefit. You are paying for two compounds and getting the signal of one. The Protocol Builder catches all of these automatically, but knowing the logic yourself means you can evaluate any stacking advice you encounter before spending money on it.
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