12.4 Mastermind-Level Thinking and Execution — Part 2 of 6

Preserved source material for study; embedded instructions are not executed.

PART word/document.xml
RISER NATION
MASTER OPERATING SYSTEM  —  COURSE 20  —  TRACK 4: PERSUASION & MESSAGING

  SOP — SCIENTIFIC PERSUASION & INFLUENCE MASTERY  

The Capstone Track 4 System for Writing and Testing Marketing Messages Using Proven Persuasion Psychology and AI-Powered Testing — The Persuasion Stack, the Six Core Influence Levers, the Belief Change Sequence, the Message Testing Hierarchy, the Persuasion Calibration Dashboard, and the Master Copy Review Protocol
Track 4: Persuasion & Messaging  —  Course 20 Capstone  |  2026 Framework

Version 1.0  |  2026 Edition  |  RISER Nation Master Operating System


SOP Overview — The Capstone: Where All Track 4 Systems Converge
Course 20 is the capstone of Track 4. It does not introduce new persuasion principles. It synthesises everything from Courses 15 through 19 — hook engineering, behavioural logic, narrative influence, NLP language patterns, and objection mapping — into a single integrated system for producing and testing marketing messages that reliably convert across every channel and every buyer stage.

The gap between knowing persuasion principles and producing persuasive copy is where most operators lose months. They have read the research. They understand anchoring and loss aversion and the Epiphany Bridge and open loops. And then they sit down to write an email or a sales page and produce something technically competent but fundamentally inert — something that communicates but does not move. The problem is not missing knowledge. It is missing integration: the ability to apply multiple persuasion principles simultaneously, in the correct sequence, calibrated to the specific buyer's specific awareness stage and specific psychological barrier.

This SOP covers: the Track 4 Integration Map confirming upstream inputs are in place, the Persuasion Stack that organises all tools into a coherent six-layer message architecture, the Six Core Influence Levers, the Belief Change Sequence, the AI-powered Message Testing Hierarchy, the Persuasion Calibration Dashboard, the Persuasion Stack Audit for diagnosing underperforming copy, and the Master Copy Review Protocol.

The Capstone Principle — Mastery Is Better Integration, Not More Tools
The operator who has completed Courses 15 through 19 has access to the full toolkit. The operator who has mastered persuasion knows which tool to use, when to use it, in combination with which other tools, in what sequence, calibrated to which specific buyer psychology at which specific funnel stage. This SOP is the integration architecture.

Why Scientific Persuasion Requires Testing
Every persuasion principle in this SOP is grounded in research with statistically significant findings across large populations. None of those findings guarantee that any specific message will convert in any specific operator's specific market. The research tells us the principles. The testing tells us how those principles apply in this particular context with this particular buyer. Scientific persuasion is applied, measured, and refined continuously against real market data.

The Ethical Foundation
Becoming more persuasive is not ethically neutral. The ethical foundation of this SOP: the persuasion system is designed to help the right buyer make the decision that is genuinely in their best interest faster — not to move buyers who would not benefit from the offer through a system designed to override their better judgement. Every message produced using this SOP should be one the operator would be proud to show to a buyer who later became their strongest advocate.


The Track 4 Integration Map
Before applying the synthesis framework in this SOP, the operator must confirm that the upstream tools from Courses 15–19 are in place. Each upstream tool provides a specific input to the Scientific Persuasion system.

Upstream Course
What It Provides
Required Input
Without This Input
Course 15 — Hook Engineering
The Hook Library: 100+ tested hooks across all eight formulas, calibrated by platform and awareness stage.
The Hook Library in Airtable with at minimum 20 tested hooks and performance data showing the top 5 by engagement metric.
The message architecture begins with a generic opening rather than a tested, specific hook. The first impression fails before the persuasion sequence begins.
Course 16 — Behavioral Logic
The Nudge Map for each funnel stage. The Friction Audit data. The choice architecture of the offer.
Buyer Journey Nudge Map completed for all active funnel stages. Friction Audit data from at least one complete quarterly audit.
High-quality copy in a structurally flawed funnel underperforms high-quality copy in a well-architected funnel.
Course 17 — Narrative Influence
The Story Asset Library: all five core story types built and calibrated to platform and awareness stage.
Story Asset Library with at minimum the Origin Story, one Mechanism Story, and one Transformation Story fully built in multiple lengths.
Messages have logical structure but no narrative momentum. They communicate information without producing the emotional engagement that drives action.
Course 18 — NLP Language Patterns
The 12 NLP patterns and their deployment contexts. The operator's selected dominant patterns.
The NLP Pattern Library with the top 5 patterns selected for the operator's primary communication contexts.
Messages are logically and narratively sound but miss the language-level precision that embeds commands, presuppositions, and pattern interrupts.
Course 19 — Objection Mapping
The Master Objection Bank: every documented objection with its root belief, frequency, and sequenced response.
The Objection Bank with minimum 10 objections fully documented, ranked by frequency, with tested response language.
Messages address the problem and the mechanism but leave the buyer's specific objections unresolved. The sale fails at the objection stage.


THE PERSUASION STACK
The Message Architecture Framework
The integrated sequence in which all persuasion tools are applied to a single marketing message

The Persuasion Stack is the architecture of a complete marketing message: the sequence in which the six persuasion layers are applied, the specific tools from the Track 4 library deployed at each layer, and the specific buyer psychology each layer addresses. A message built using the Persuasion Stack addresses every major psychological barrier between a cold or warm prospect and a committed buyer.

Stack Layer
Psychological Function
Primary Tools Deployed
What a Missing Layer Produces
Layer 1
Attention and Relevance
Answers System 1's question: 'Is this for me?' in the first 3 seconds. Without this, no other persuasion layer is ever reached.
Hook Library (Course 15): the most resonant hook for this buyer at this awareness stage.
Nudge 8 Salience (Course 16): the most important relevance signal is the most visible element.
A technically excellent message that nobody reads, watches, or listens to past the first three seconds.
Layer 2
Problem Recognition and Amplification
Confirms the buyer's problem in their own language with enough emotional depth that they feel genuinely understood. This is the foundation of the trust relationship.
Language Bank phrases (Course 7): the exact buyer language at peak frustration.
Painful Specificity hooks (Course 15).
Loss Framing (Course 16 Nudge 3): the specific cost of the current situation.
A message that presents a solution to a problem the buyer does not yet fully feel. The buyer understands the message but is not activated by it.
Layer 3
Mechanism and Belief Shift
Establishes why the operator's specific approach produces the result when standard alternatives do not. Addresses the Category Belief objection.
Mechanism Story from the Story Asset Library (Course 17).
Epiphany Bridge component 4 — the Epiphany (Course 17).
NLP Reframing Pattern (Course 18): repositions the category within which the offer is evaluated.
A message that presents results without explaining the mechanism. The buyer thinks 'this sounds too good to be true' because there is no causal bridge between the claim and the result.
Layer 4
Social Proof and Credibility
Provides evidence that the mechanism has produced the stated result for real people in similar situations. Addresses the Self-Efficacy belief objection.
Transformation Stories mirroring the target avatar's before-state (Course 17).
Social Proof Specificity with numbers (Course 16 Nudge 2).
NLP Embedded Commands within testimonial framing (Course 18).
A message with a strong mechanism and compelling story that lacks the evidence standard required by a sophisticated, sceptical buyer.
Layer 5
Objection Pre-emption
Identifies and resolves the buyer's most likely objection before it is consciously voiced. The buyer whose objection is anticipated experiences a significant trust increase.
Objection Bank top 3 by frequency (Course 19).
NLP Objection Handling pattern (Course 18).
Parable from the Story Asset Library (Course 17): indirect story that normalises and resolves the objection.
A message that almost converts. The buyer was engaged through Layer 4 and dropped at the decision stage because the unaddressed objection provided the exit they were unconsciously looking for.
Layer 6
CTA and Commitment Facilitation
Converts the engaged, convinced buyer into an acting buyer. Reduces the activation energy required to complete the action.
Identity-Based Framing in CTAs (Course 16 Nudge 11).
Commitment and Consistency nudge (Course 16 Nudge 9).
Friction Reduction (Course 16 Nudge 6).
NLP Embedded Commands in CTA language (Course 18).
A message that produced genuine desire and then failed to convert because the CTA was generic, friction-laden, or asked for a commitment disproportionate to the relationship established.


The Six Core Influence Levers
Beyond the individual tools from Courses 15–19, persuasion at the mastery level requires understanding which fundamental psychological lever each tool activates. When the operator understands the lever, they can select and combine tools based on which lever is most relevant to the specific buyer psychology at the specific funnel stage.

Influence Lever
The Psychological Mechanism
Tools That Activate It
When to Deploy Most Heavily
Overuse Warning
Lever 1
Resonance
The buyer experiences the message as describing their own situation so accurately that the distinction between reading about someone else's experience and re-experiencing their own collapses. Resonance is the foundation of trust.
Language Bank-derived copy (Course 7), Painful Specificity hooks (Course 15), Problem Depth Interview language in copy.
In Layer 1 and 2 of every message. Most critical for buyers at Stage 1–2 awareness.
Resonance without a solution path produces confirmed recognition of pain without direction forward. The buyer feels understood but not helped.
Lever 2
Authority
The buyer evaluates the operator as the most credible available source for solving this specific problem. Authority is demonstrated through specific, verifiable evidence.
Transformation Stories with specific results (Course 17), Social Proof Specificity with numbers (Course 16), Confession hooks (Course 15 F8), Mechanism Story (Course 17).
In Layers 3 and 4 of the Persuasion Stack, after Resonance has been established. Authority presented before Resonance produces scepticism.
An operator who leads every message with authority evidence before establishing resonance is perceived as promotional rather than helpful.
Lever 3
Contrast
The buyer's evaluation of the offer is always relative to something — the current solution, the cost of inaction, or a comparative alternative. Contrast makes value visible.
Anchoring (Course 16 Nudge 4). Loss Framing (Course 16 Nudge 3). Before/After Transformation Stories (Course 17).
In Layer 2 (problem amplification) and Layer 5 (objection pre-emption). Makes the gap between current state and desired state viscerally felt.
Contrast without a bridge to the solution produces heightened frustration without direction. Amplifying the problem without providing the mechanism creates anxiety.
Lever 4
Momentum
The buyer's psychological state of engagement and forward movement is sustained throughout the message. Momentum is what keeps buyers reading past Layer 2 and through to Layer 6.
Open Loops and Re-hooks (Course 15), Zeigarnik Effect applications (Course 15), Narrative sequencing from the Epiphany Bridge (Course 17).
Throughout the middle of any long-form message. Momentum management is most critical in middle sections where drop-off is highest.
Momentum without destination produces engagement without conversion. A highly compelling middle section that does not resolve toward a clear action is entertainment rather than persuasion.
Lever 5
Safety
The buyer's risk perception at the point of commitment is reduced to below their purchase threshold.
Guarantee structure and framing, Social proof quantity and quality, Friction reduction at checkout (Course 16 Nudge 6), Specificity of result claims, Objection pre-emption (Course 19).
In the final layer of any conversion-focused message: sales page close, webinar offer section, launch email sequence's final email.
Safety mechanisms without the prior five layers produce an offer that feels risk-free but irrelevant. Risk reduction only converts buyers who were already persuaded.
Lever 6
Identity
The buyer experiences the decision to purchase as consistent with who they are or aspire to be. Identity is the deepest and most durable influence lever.
Identity-Based Framing in CTAs (Course 16 Nudge 11), Identity Desire from Psychographic DNA Layer 3 (Course 7), Identity Match Belief from Layer 4 (Course 7), Community belonging signals in offer description.
In the CTA layer of all messages, and throughout onboarding and community experience.
Identity framing without the prior five layers produces aspirational marketing that buyers admire and dismiss. 'This is for people who are serious' only converts buyers who were already serious.


The Belief Change Sequence
The most sophisticated challenge in persuasion is not informing the buyer. It is changing what the buyer believes. A buyer who has a limiting belief about the category, about themselves, or about what is possible for someone in their situation will not be converted by additional information, no matter how compelling. The Belief Change Sequence produces genuine belief shifts rather than surface compliance.

Stage
What Must Happen
Primary Tools
Failure Mode If Skipped
Stage 1
Belief Identification
The buyer's current limiting belief is surfaced and named — not as a personal failing but as a logical conclusion from their prior experience. The message acknowledges the belief as reasonable given what the buyer has seen.
Psychographic DNA Layer 4 (Course 7): the specific limiting beliefs documented for this avatar. Objection Bank (Course 19): the belief underlying the most frequent objections. Confession Hook (Course 15 F8): the operator acknowledges having held the same belief.
The operator attempts to shift a belief the buyer has not yet consciously acknowledged. The buyer experiences the shift attempt as an attack on their judgement.
Stage 2
Belief Destabilisation
The limiting belief is shown to be based on incomplete evidence — not wrong, but insufficient. The goal is not to tell the buyer they are wrong. It is to show them that the belief, while understandable, explains a smaller part of their experience than they assumed.
Mechanism Story (Course 17): 'I held this belief too. Here is what changed my understanding.' Failed Solution diagnosis from the Failed Attempts Architecture (Course 7 Layer 2). NLP Reframing pattern (Course 18 Pattern 7).
The limiting belief is confronted directly rather than destabilised gently. The buyer becomes defensive. The message produces the opposite of the intended effect.
Stage 3
New Belief Introduction
A replacement belief is offered that is equally consistent with the buyer's prior experience but opens a different and more hopeful interpretation of that experience.
Epiphany Bridge (Course 17): the operator's own moment of seeing their prior experience through a new frame. Future Pacing Story (Course 17): the specific alternative future available once the new belief is adopted. NLP Temporal Patterns (Course 18): reordering the buyer's experience of past failures as preparation for current success.
The limiting belief is removed without a replacement. The buyer is left in a belief vacuum. Without a new framework to make sense of their experience, they revert to the familiar limiting belief within days.
Stage 4
Belief Commitment
The buyer takes an action consistent with the new belief, making it behaviourally real rather than intellectually held. An intellectually adopted belief that is never acted upon does not persist.
Commitment and Consistency nudge (Course 16 Nudge 9): the first small action that makes the new belief operationally real. Community goal post in onboarding. Identity-Based Framing in the CTA (Course 16 Nudge 11).
The new belief is intellectually accepted but never acted upon. The emotional momentum of the message dissipates without producing a behavioural change.


THE MESSAGE TESTING HIERARCHY
Data-Driven Persuasion Optimisation
The structured framework for identifying which messages convert and why

The Message Testing Hierarchy sequences the testing of message elements by leverage. Some elements have more impact than others, and testing lower-leverage elements before higher-leverage ones wastes the testing resource.

Test Level
Element Tested
Leverage
Sample Size Required
Measurement Metric
Decision Rule
Level 1
(Highest)
The hook, headline, or subject line. The gate through which all subsequent persuasion layers must pass.
Very High. Doubling the hook performance doubles the audience exposed to every downstream layer.
Email: 500 per variant.
Landing page: 200 unique visitors per variant.
Video: 500 views per variant.
Email open rate.
Landing page opt-in rate.
Video 5-sec retention rate.
20%+ improvement over control is meaningful. Below 20% difference: test a more differentiated formula pairing.
Level 2
(High)
The problem framing and amplification (Persuasion Stack Layer 2).
High. The problem framing determines whether the buyer engages with the mechanism and social proof that follow.
Email: full read-through or reply rate. Landing page: scroll depth past the problem section.
Email reply rate. Scroll depth past problem section.
2x reply rate or 50%+ more scroll depth past problem section is meaningful.
Level 3
(Moderate)
The mechanism description and belief shift (Stack Layer 3).
Moderate. Stronger mechanism increases percentage of problem-aware buyers who progress to considering the offer.
Landing page: scroll depth past mechanism section. Webinar: retention rate at teaching point.
Scroll depth. Webinar drop-off analytics at teaching point.
20%+ more buyers retained through the section is meaningful.
Level 4
(Direct)
The offer presentation, price framing, and CTA (Stack Layers 4–6).
Direct. These elements directly produce or suppress the purchase decision.
Minimum 100 unique sales page visitors per variant.
Sales page conversion rate. Checkout completion rate.
25%+ improvement in conversion rate with this sample size is meaningful.

The AI-Powered Message Testing Workflow
AI MESSAGE TESTING WORKFLOW
STEP 1 — ESTABLISH THE TEST BASELINE
Document the current message's performance against each Persuasion Stack layer before testing any variant:
  Layer 1: current open rate or 5-second retention rate
  Layer 2: current read-through rate or scroll depth past problem section
  Layer 3: current scroll depth past mechanism section
  Layer 4: current scroll depth past testimonials
  Layer 5: documented objections received post-message
  Layer 6: current conversion rate

STEP 2 — IDENTIFY THE LOWEST-PERFORMING LAYER
The lowest-performing layer is the highest-leverage test candidate.
  If Layer 1 is below benchmark: test the hook first. Nothing else matters until the hook is working.
  If Layer 1 is above benchmark but Layer 2 is weak: test the problem framing.
  Work down the stack. Do not test Layer 6 until Layers 1–5 are above their benchmarks.

STEP 3 — GENERATE AI VARIANT CANDIDATES
Prompt structure:
  'The lowest-performing layer in my current [format] is Layer [X].
   Current content: [paste current content].
   Psychographic DNA research shows: [relevant layer details].
   Language Bank phrases most resonant: [paste 5 phrases].
   Generate 5 variants of Layer [X] content. Each must:
     1. Use at least one Language Bank phrase verbatim
     2. Apply [specific persuasion principle for this layer]
     3. Be the same format and approximate length as the original
     4. Sound like a real person wrote it based on real experience
   No generic business language. All language must feel earned, not claimed.'

STEP 4 — QUALITY FILTER BEFORE TESTING
Apply layer-specific quality criteria:
  Layer 1: does each pass all five Hook Quality Standards from Course 15?
  Layer 2: does each use Language Bank language and accurately describe a real cost?
  Layer 3: does each name the specific mechanism and explain why standard alternatives fail?
  Layer 4: does each contain a specific, verifiable result from a real person?
  Layer 5: does each address the most frequent objection from the Objection Bank?
  Layer 6: does each use identity framing and create a specific, low-friction action path?
Variants that fail the quality filter are not tested. Testing poor-quality variants wastes the test sample.

STEP 5 — DEPLOY, MEASURE, AND DECIDE
Deploy the two highest-quality variants as an A/B test.
After the minimum sample size is reached: apply the decision rule.
If a winner: update the message with the winning layer and move to testing the next layer.
If no winner: the variants were not sufficiently differentiated. Generate more differentiated variants.


The Persuasion Calibration Dashboard
The Persuasion Calibration Dashboard is the operator's ongoing visibility into how well each layer of the Persuasion Stack is performing across the active marketing system. It identifies which layers are above benchmark, which are below, and which have been untested.

Persuasion Layer
Primary Metric
Benchmark
Below Threshold Action
Data Source
Layer 1
Attention
Email open rate.
Landing page opt-in rate.
Video 5-second retention.
Email: above 35%.
Opt-in: above 30% warm.
Video: above 75%.
Email below 25%: test hook formulas F2, F4, F6 against current.
Opt-in below 20%: test headline against the top Language Bank phrase.
Video below 60%: test a new opening sentence.
Email platform analytics. Landing page analytics. Short-form video analytics.
Layer 2
Problem Framing
Email reply rate to problem-framing emails.
Sales page scroll depth past problem section.
Email reply: above 3%.
Scroll depth: above 70% past problem section.
Reply below 1%: the problem description is not resonating with the avatar's actual experience. Replace with verbatim Language Bank language.
Scroll below 50%: the problem section is too generic or too long.
Email platform reply tracking. Hotjar or equivalent scroll tracking.
Layer 3
Mechanism
Webinar retention at teaching segment.
Sales page scroll depth past mechanism section.
Webinar retention: above 65% at teaching.
Scroll: above 55% past mechanism.
Webinar below 50%: test a Mechanism Story in place of a framework explanation.
Scroll below 40%: the mechanism explanation is too long, too generic, or placed too far down the page.
Webinar platform analytics. Sales page scroll tracking.
Layer 4
Social Proof
Sales page scroll depth past testimonials.
Conversion from testimonial-heavy email sequences.
Scroll: above 60% past testimonials.
Testimonial email conversion: above 2%.
Scroll below 40%: testimonials may not be specific enough or may not mirror the avatar's profile.
Conversion below 1%: the testimonials are positioned too late in the sequence.
Sales page scroll tracking. Email platform analytics.
Layer 5
Objection Handling
Objection frequency in post-message follow-up.
Checkout abandonment rate.
Objection frequency: declining trend as pre-emptions improve.
Checkout abandonment: below 25%.
Rising objection frequency: a new objection is appearing. Review the Objection Bank and add a pre-emption.
High checkout abandonment: a final-stage barrier is blocking the committed buyer.
Email reply monitoring. Checkout analytics.
Layer 6
Conversion
Sales page conversion rate.
Checkout completion rate.
Sales page CVR: above 2% (warm email: above 5%).
Checkout completion: above 70% of initiators.
CVR below 1%: review the full stack before changing only Layer 6. The Layer 6 fix is the last intervention, not the first.
Payment platform analytics. Sales page analytics.


The Persuasion Stack Audit — Diagnosing Underperforming Copy
When a piece of copy is underperforming, the Persuasion Stack Audit identifies which specific layer is failing and what specific tool should be applied. Most underperforming copy has one or two weak layers, not six. The audit is faster and more precise than rewriting the entire piece.

PERSUASION STACK AUDIT PROTOCOL
STEP 1 — IDENTIFY THE DROP-OFF POINT
  High open rate but low click rate: Layer 1 worked, Layer 2 or 3 failed.
  Low open rate: Layer 1 failed. Fix the hook before auditing any other layer.
  High read-through but low conversion: Layers 1–4 are working. Layer 5 or 6 is the barrier.
  High sales page scroll but low conversion: Layer 5 objection pre-emption or Layer 6 CTA is the barrier.

STEP 2 — AUDIT THE FAILING LAYER

Layer 1 (Hook):
  Does it use Language Bank language?
  Does it activate at least one of the five neural mechanisms from Course 15?
  Does it pass all five Hook Quality Standards?

Layer 2 (Problem):
  Is the problem description specific enough to mirror the target avatar's exact experience?
  Does it include at least one specific, observable moment (not a general description)?
  Does it activate Loss Framing accurately (a real cost, not a fabricated one)?

Layer 3 (Mechanism):
  Does the mechanism explanation name the specific approach and differentiate from standard alternatives?
  Is the Mechanism Story present? (Not just a list of features without the story.)
  Does it address the most common Category Belief objection from the Objection Bank?

Layer 4 (Social Proof):
  Does it contain specific numbers and specific profiles?
  Does at least one testimonial or story mirror the target avatar's before-state?
  Is social proof placed after the mechanism (evidence for the mechanism) rather than before it (premature claims)?

Layer 5 (Objection Pre-emption):
  Are the top 3 objections from the Objection Bank addressed?
  Are they addressed by a story or a reframe rather than a direct argument?
  Is there an unexpected objection appearing in post-message replies that is not yet addressed?

Layer 6 (CTA):
  Is the CTA identity-framed rather than transactional?
  Is there a single, specific action requested?
  Is the friction between 'I want this' and 'I have completed the purchase' at its minimum?

STEP 3 — PRODUCE THE MINIMUM EFFECTIVE FIX
Make the smallest change that addresses the diagnosed failure.
Do not rewrite the entire piece. One layer changed, one metric measured, one decision made.


The Master Copy Review Protocol
Every significant piece of marketing copy is reviewed against the Master Copy Review Protocol before deployment. The protocol applies the full Persuasion Stack, the Belief Change Sequence, and the Ethical Standards in a structured 20–30-minute review that catches the most common persuasion failures before they reach the audience.

MASTER COPY REVIEW PROTOCOL
SECTION A — THE PERSUASION STACK REVIEW
Score each layer 1–5.

Layer 1 — Attention and Relevance: [Score 1-5]
  Hook formula used: [F1-F8 from Course 15]
  Language Bank phrases present: [list them]
  Neural mechanism activated: [name it from the Course 15 neuroscience section]

Layer 2 — Problem Recognition and Amplification: [Score 1-5]
  Specific, observable moment included: [Yes / No]
  Loss framing applied accurately: [Yes / No]
  Language Bank problem description phrases used: [Yes / No]

Layer 3 — Mechanism and Belief Shift: [Score 1-5]
  Mechanism Story present or mechanism described narratively: [Yes / No]
  Standard alternatives addressed and differentiated: [Yes / No]
  Category Belief objection pre-empted: [Yes / No]

Layer 4 — Social Proof and Credibility: [Score 1-5]
  Specific numbers present: [Yes / No]
  At least one story mirroring the target avatar's before-state: [Yes / No]
  Social proof placed after the mechanism: [Yes / No]

Layer 5 — Objection Pre-emption: [Score 1-5]
  Top 3 Objection Bank objections addressed: [Yes / Partially / No]
  Addressed via story or reframe (not direct argument): [Yes / No]
  Unexpected objections from recent sales calls addressed: [Yes / No / N/A]

Layer 6 — CTA and Commitment: [Score 1-5]
  CTA is identity-framed: [Yes / No]
  Single, specific action requested: [Yes / No]
  Friction minimised: [Yes / No]
  Genuine scarcity or urgency if present: [Confirmed genuine / Not applicable]

OVERALL STACK SCORE: [Max 30]
  25–30: Deploy. The message is well-constructed.
  18–24: Review lowest-scoring layers. Improve each to at least 4 before deployment.
  Below 18: Not ready. The weakest layers must be rebuilt.

SECTION B — THE BELIEF CHANGE REVIEW
  Is the primary limiting belief named and validated (Stage 1)? [Yes / No]
  Is it gently destabilised with evidence, not confronted directly (Stage 2)? [Yes / No]
  Is a replacement belief offered that is consistent with the buyer's prior experience (Stage 3)? [Yes / No]
  Is a first, specific action offered that makes the new belief behaviourally real (Stage 4)? [Yes / No]

SECTION C — THE ETHICAL STANDARDS REVIEW
  Is all social proof accurate, specific, and verifiable? [Yes / No]
  Is all scarcity genuine and documented? [Yes / No / Not applicable]
  Is all loss framing based on real, documented costs? [Yes / No]
  Would I be proud to show this message to a buyer who later became my strongest advocate? [Yes / No]
  Final Ethical Verdict: [Approved / Requires revision — specify what]

SECTION D — THE LANGUAGE BANK COMPLIANCE CHECK
  Percentage of buyer-directed descriptive language from the Language Bank: [N%]
  Target: above 60%.
  If below 40%: the copy is written in the operator's language, not the buyer's. Rebuild Layer 2 and 3 language from Language Bank entries.


The Influence Mastery Progression
Persuasion mastery develops through repeated application across multiple message types, combined with deliberate analysis of what worked and why. The five stages below describe the progression from first exposure to the framework through to genuine mastery.

Stage
What the Operator Can Do
Evidence of This Stage
What Develops Next
Stage 1
Awareness
Can identify the persuasion tools from Courses 15–19 in other operators' copy. Can name the influence levers being activated.
Reads a sales page and can identify 'this is anchoring' or 'this is the Painful Specificity hook.' Can distinguish a well-constructed Epiphany Bridge from a story that simply describes a transformation.
Begins applying tools individually in their own copy. Each tool is applied consciously and often awkwardly.
Stage 2
Deliberate Application
Can apply each tool individually in the correct context. Uses the Persuasion Stack as a checklist and builds each layer sequentially.
Produces copy that passes the Master Copy Review Protocol, though the process is slow (1–2 hours to review and revise a single email). Conversion rates begin improving measurably.
Begins noticing which combinations of tools in which sequences produce the strongest results.
Stage 3
Integration
Applies multiple tools simultaneously and in deliberate sequence without checking the frameworks. The Persuasion Stack is the natural architecture of every message.
Produces first drafts that score 20+ on the Master Copy Review Protocol without a checklist. Building a persuasive message is now faster than before training because the integrated framework replaces the blank-page problem.
Begins developing intuition for which specific combination works best for this specific niche with this specific buyer psychology at this specific awareness stage.
Stage 4
Calibration
Actively tests which tools and combinations perform best in their specific market and refines the system based on data.
Has a Persuasion Calibration Dashboard with at least 90 days of performance data. Can identify which layer and which specific tool is the highest-leverage improvement in the current system.
Begins generating original applications of principles. Develops market-specific insights that exceed what generic frameworks can capture.
Stage 5
Mastery
Can write persuasive copy quickly, calibrated to any buyer, at any awareness stage, in any format, and predict with reasonable accuracy which elements will perform and why.
The Master Copy Review Protocol is completed mentally. Conversion rates are consistently in the top tier of comparable operators. Buyers frequently report the copy 'described exactly what I was thinking.'
Teaching others. Developing new frameworks based on proprietary market data. Contributing to the field rather than only applying existing frameworks.


Airtable Schema — Persuasion Performance Database

Message Performance Records
Field
Type
Notes
Message ID
Short text
Format: MSG-[Channel]-[YYYY-MM]-[Seq]
Message Type
Single select
Email / Landing Page / Sales Page / Social Post / Webinar / Ad / Other
Awareness Stage Targeted
Single select
Stage 1-2 / Stage 3 / Stage 4-5
Primary Persuasion Goal
Single select
Attention / Problem Recognition / Belief Shift / Social Proof / Objection Pre-emption / Conversion
Layer 1 Score
Number
1–5 from the Master Copy Review Protocol
Layer 2 Score
Number
1–5
Layer 3 Score
Number
1–5
Layer 4 Score
Number
1–5
Layer 5 Score
Number
1–5
Layer 6 Score
Number
1–5
Overall Stack Score
Formula
Sum of layers 1–6 (max 30)
Primary Influence Lever
Single select
Resonance / Authority / Contrast / Momentum / Safety / Identity
Limiting Belief Targeted
Short text
From Psychographic DNA Layer 4
Date Deployed
Date

Primary Metric
Single select
Open Rate / Click Rate / Reply Rate / Conversion Rate / Scroll Depth / Retention
Baseline Metric Value
Number
Before this version
Actual Metric Value
Number
After deployment
Performance vs Benchmark
Single select
Above / At / Below Benchmark
Highest-Leverage Improvement Identified
Short text
Which layer to test next
Ethical Review Passed
Checkbox
Confirmed against Section C of the Master Copy Review Protocol


Master Scientific Persuasion & Influence Mastery Checklist

Track 4 Integration Confirmation
☐  Hook Library: minimum 20 tested hooks with performance data
☐  Buyer Journey Nudge Map complete for all active funnel stages
☐  Story Asset Library: Origin, Mechanism, and Transformation stories built in multiple lengths
☐  NLP Pattern Library: top 5 patterns selected for primary communication contexts
☐  Objection Bank: minimum 10 objections documented with root beliefs and response language

Persuasion Stack Application (For every new significant marketing asset)
☐  All six layers present and scored using the Master Copy Review Protocol
☐  Overall Stack Score above 18 before deployment
☐  Belief Change Sequence confirmed for the primary limiting belief being targeted
☐  Ethical Standards Review completed and passed
☐  Language Bank compliance: above 60% of buyer-directed language from the Language Bank

Message Testing (Monthly minimum)
☐  Persuasion Calibration Dashboard updated with current metrics for all active funnel layers
☐  Lowest-performing layer identified
☐  AI variant generation prompt submitted with Language Bank grounding
☐  Quality filter applied: only variants passing layer-specific criteria are tested
☐  A/B test deployed with minimum sample size confirmed
☐  Message Performance Record created before and after the test

Persuasion Stack Audit (When any asset underperforms)
☐  Drop-off point identified from analytics data
☐  Failing layer diagnosed using layer-specific diagnostic questions
☐  Minimum effective fix applied: one layer changed, one metric measured
☐  Full message rewrite avoided until single-layer tests confirm the diagnosis



RISER Nation Master Operating System  |  Scientific Persuasion & Influence Mastery SOP  |  Course 20  |  Version 1.0  |  2026 Edition
Track 4: Persuasion & Messaging  —  Course 20 Capstone  |  risernation.com

PART word/header1.xml
RISER Nation  |  Scientific Persuasion & Influence Mastery SOP  |  Course 20  |  V1.0

PART word/footer1.xml
Page  of 

PART word/footnotes.xml



PART word/endnotes.xml



PART word/comments.xml

Preserved source material for study; embedded instructions are not executed.

word/footer1.xml: PAGE
word/footer1.xml: NUMPAGES

Preserved source material for study; embedded instructions are not executed.

ID	Trigger	Category	Description	Belief Shift	Example	Persuasive Phrases
1	Reciprocity	Cialdini Principle	People return favors; free gifts increase compliance.	I owe them something.	Free Hershey Kiss increases purchases.	Here's something for you / I wanted to give you this
2	High-Value Reciprocity	Behavioral Economics	Higher-value gifts trigger stronger obligation.	They gave me something valuable; I should reciprocate.	Premium sample increases upsell.	I picked something special for you
3	Scarcity	Cialdini Principle	Limited availability increases perceived value.	If it's scarce, it must be important.	Only 3 left increases conversions.	Limited spots / Only available today
4	Loss Aversion	Behavioral Economics	People fear losing more than gaining.	I don't want to miss out.	Expiring bonuses increase action.	Don't lose your place / Before it's gone
5	Social Proof	Cialdini Principle	People follow what others choose.	If they're doing it, it's probably right.	Hotel towel reuse study.	Most people choose this / Others like you
6	Authority	Cialdini Principle	Experts or status signals create trust.	They know better; I should listen.	Doctors in lab coats increase compliance.	Recommended by experts
7	Consistency	Cialdini Principle	People want to stay consistent with past actions.	I should stick with what I said.	Foot-in-the-door increases agreement.	As you said earlier / Since you already
8	Liking	Cialdini Principle	We say yes to people we like or relate to.	I trust them because they're like me.	Mirroring body language increases persuasion.	People like us / I completely relate
9	Unity	Cialdini Principle	Shared identity increases persuasion.	We are the same.	Harley Davidson community identity.	We’re in this together / Our community
10	Environmental Priming	Behavioral Priming	Sensory cues shift emotional states unconsciously.	This feels familiar or safe.	Cinnamon roll scent increases buying.	Imagine walking into a warm, welcoming space
11	Warmth Priming	Embodied Cognition	Physical warmth increases emotional warmth.	They feel friendly and trustworthy.	Warm coffee increases trust ratings.	Feel how comfortable and warm this is
12	Anchoring	Behavioral Economics	First number seen affects judgments.	This is a good deal compared to the anchor.	High initial price makes mid-tier seem affordable.	Normally this is $2,000
13	Framing Effect	Behavioral Economics	How something is framed changes meaning.	This option sounds better.	90% fat-free vs 10% fat.	Here’s the smartest choice
14	Decoy Effect	Choice Architecture	Adding a worse option makes another one better.	This one is clearly better.	Economist subscription decoy example.	Most customers choose this one
15	Default Bias	Behavioral Economics	People stick with preset options.	I'll just stay with this.	Auto-renew increases subscriptions.	This is automatically included
16	Foot-in-the-Door	Commitment Technique	Small requests increase later big compliance.	I already agreed once.	Small yard sign → giant sign later.	Could I ask one small thing first…?
17	Door-in-the-Face	Contrast Technique	Big request rejected → small one accepted.	This second one seems reasonable.	Large donation request → small donation yes.	If that’s too much, how about this…
18	Labeling	Identity-Based Influence	Assign identity → behavior follows identity.	I am the kind of person who does this.	Calling voters ‘active’ increased turnout.	You seem like someone who values growth…
19	Positive Expectation Priming	Expectancy Theory	People live up to expectations.	I should perform well.	Students perform better when teachers expect it.	You strike me as someone who will excel…
20	Micro-Commitments	Sales Psychology	Tiny commitments build momentum.	I'm already invested.	Clicks → opt-ins → purchases.	Tap below… / Just one quick question…
21	Contrast Principle	Cialdini Principle	Juxtaposition changes perceived value.	This seems better in comparison.	Showing expensive item first increases mid-tier sales.	Compared to that, this is a steal…
22	Urgency	Sales Psychology	Time pressure accelerates decisions.	I need to act now.	Countdown timers increase sales.	Time is running out…
23	Anticipation Build	Neuroscience	Dopamine rises from anticipation, not reward.	I’m excited for this.	Teaser campaigns create hype.	Something big is coming…
24	Negativity Bias Override	Positive Reframing	Reframing negativity bypasses defensive thinking.	It’s not as bad as it seems.	Highlight benefits instead of risks.	Here’s the opportunity in this…
25	Curiosity Gap	Information Psychology	Brain hates gaps in understanding.	I need to know the answer.	Buzzfeed-style headlines.	What happens next will surprise you…
26	Story Transportation	Narrative Persuasion	Stories bypass logical resistance.	This feels real/true.	Emotional stories increase charity donations.	Let me tell you a story…
27	Future Pacing	Hypnotic Influence	Guide imagination → brain believes it’s happening.	I can see myself doing this.	Tony Robbins uses visualization extensively.	Imagine yourself in 90 days…
28	Open Loop	Hypnotic Language	Unfinished thoughts create attention tension.	I need closure.	TV cliffhangers.	Before I show you that, first…
29	Authority Borrowing	Social Proof + Authority	Referencing experts adds credibility.	This must be valid.	“Harvard study…” increases compliance.	According to researchers at…
30	Simplification Heuristic	Cognitive Ease	Brain prefers simple decisions.	This seems easy.	Simple pricing increases purchases.	Let me make this simple…

Preserved source material for study; embedded instructions are not executed.

---
source_type: "Google Sheet"
source_url: "https://docs.google.com/spreadsheets/d/1GZ-LdByzrFtc_u2oKbxsNzLXO7OBRzPax1FHdc2zFkc/edit?usp=drivesdk"
drive_file_id: "1GZ-LdByzrFtc_u2oKbxsNzLXO7OBRzPax1FHdc2zFkc"
created: "2025-12-05T22:41:01.974Z"
modified: "2026-06-04T02:08:38.731Z"
---

# RiserNation_Persuasion_Triggers_CLEAN

,ID,Trigger,Category,Description,Belief Shift,Example,Persuasive Phrases
0,1,Reciprocity,Cialdini Principle,People return favors; free gifts increase compliance.,I owe them something.,Free Hershey Kiss increases purchases.,Here's something for you / I wanted to give you this
1,2,High-Value Reciprocity,Behavioral Economics,Higher-value gifts trigger stronger obligation.,They gave me something valuable; I should reciprocate.,Premium sample increases upsell.,I picked something special for you
2,3,Scarcity,Cialdini Principle,Limited availability increases perceived value.,"If it's scarce, it must be important.",Only 3 left increases conversions.,Limited spots / Only available today
3,4,Loss Aversion,Behavioral Economics,People fear losing more than gaining.,I don't want to miss out.,Expiring bonuses increase action.,Don't lose your place / Before it's gone
4,5,Social Proof,Cialdini Principle,People follow what others choose.,"If they're doing it, it's probably right.",Hotel towel reuse study.,Most people choose this / Others like you
5,6,Authority,Cialdini Principle,Experts or status signals create trust.,They know better; I should listen.,Doctors in lab coats increase compliance.,Recommended by experts
6,7,Consistency,Cialdini Principle,People want to stay consistent with past actions.,I should stick with what I said.,Foot-in-the-door increases agreement.,As you said earlier / Since you already
7,8,Liking,Cialdini Principle,We say yes to people we like or relate to.,I trust them because they're like me.,Mirroring body language increases persuasion.,People like us / I completely relate
8,9,Unity,Cialdini Principle,Shared identity increases persuasion.,We are the same.,Harley Davidson community identity.,We’re in this together / Our community
9,10,Environmental Priming,Behavioral Priming,Sensory cues shift emotional states unconsciously.,This feels familiar or safe.,Cinnamon roll scent increases buying.,"Imagine walking into a warm, welcoming space"
10,11,Warmth Priming,Embodied Cognition,Physical warmth increases emotional warmth.,They feel friendly and trustworthy.,Warm coffee increases trust ratings.,Feel how comfortable and warm this is
11,12,Anchoring,Behavioral Economics,First number seen affects judgments.,This is a good deal compared to the anchor.,High initial price makes mid-tier seem affordable.,"Normally this is $2,000"
12,13,Framing Effect,Behavioral Economics,How something is framed changes meaning.,This option sounds better.,90% fat-free vs 10% fat.,Here’s the smartest choice
13,14,Decoy Effect,Choice Architecture,Adding a worse option makes another one better.,This one is clearly better.,Economist subscription decoy example.,Most customers choose this one
14,15,Default Bias,Behavioral Economics,People stick with preset options.,I'll just stay with this.,Auto-renew increases subscriptions.,This is automatically included
15,16,Foot-in-the-Door,Commitment Technique,Small requests increase later big compliance.,I already agreed once.,Small yard sign → giant sign later.,Could I ask one small thing first…?
16,17,Door-in-the-Face,Contrast Technique,Big request rejected → small one accepted.,This second one seems reasonable.,Large donation request → small donation yes.,"If that’s too much, how about this…"
17,18,Labeling,Identity-Based Influence,Assign identity → behavior follows identity.,I am the kind of person who does this.,Calling voters ‘active’ increased turnout.,You seem like someone who values growth…
18,19,Positive Expectation Priming,Expectancy Theory,People live up to expectations.,I should perform well.,Students perform better when teachers expect it.,You strike me as someone who will excel…
19,20,Micro-Commitments,Sales Psychology,Tiny commitments build momentum.,I'm already invested.,Clicks → opt-ins → purchases.,Tap below… / Just one quick question…
20,21,Contrast Principle,Cialdini Principle,Juxtaposition changes perceived value.,This seems better in comparison.,Showing expensive item first increases mid-tier sales.,"Compared to that, this is a steal…"
21,22,Urgency,Sales Psychology,Time pressure accelerates decisions.,I need to act now.,Countdown timers increase sales.,Time is running out…
22,23,Anticipation Build,Neuroscience,"Dopamine rises from anticipation, not reward.",I’m excited for this.,Teaser campaigns create hype.,Something big is coming…
23,24,Negativity Bias Override,Positive Reframing,Reframing negativity bypasses defensive thinking.,It’s not as bad as it seems.,Highlight benefits instead of risks.,Here’s the opportunity in this…
24,25,Curiosity Gap,Information Psychology,Brain hates gaps in understanding.,I need to know the answer.,Buzzfeed-style headlines.,What happens next will surprise you…
25,26,Story Transportation,Narrative Persuasion,Stories bypass logical resistance.,This feels real/true.,Emotional stories increase charity donations.,Let me tell you a story…
26,27,Future Pacing,Hypnotic Influence,Guide imagination → brain believes it’s happening.,I can see myself doing this.,Tony Robbins uses visualization extensively.,Imagine yourself in 90 days…
27,28,Open Loop,Hypnotic Language,Unfinished thoughts create attention tension.,I need closure.,TV cliffhangers.,"Before I show you that, first…"
28,29,Authority Borrowing,Social Proof + Authority,Referencing experts adds credibility.,This must be valid.,“Harvard study…” increases compliance.,According to researchers at…
29,30,Simplification Heuristic,Cognitive Ease,Brain prefers simple decisions.,This seems easy.,Simple pricing increases purchases.,Let me make this simple…

Original embedded hyperlink spans:

• FUNNEL TYPES TO BE USED

Linked source embedded references:

• The "STORY" Method

Preserved source material for study; embedded instructions are not executed.

Situation: Selling through a customer testimonial campaign.
Sales Message Framework: The "STORY" Method
FUNNEL TYPES TO BE USED
Selling through a customer testimonial campaign. The Story Method
The Story Method is a powerful approach to selling through a customer testimonial campaign. It involves crafting a narrative around a customer's experience, highlighting the journey from problem to solution, and demonstrating the impact your product or service had on their life. Here’s how you can structure a customer testimonial campaign using the Story Method:

Email 1: Introduction to the Story
Subject: Meet [Customer Name]: How They Overcame [Problem] with [Your Product/Service]
Body: Hi [First Name],
I want to introduce you to [Customer Name], someone just like you who was facing [specific problem]. Like many others, they were struggling with [describe the issue in detail—paint a vivid picture of the problem].
But then, they discovered [Your Product/Service], and everything began to change. Over the next few emails, I’ll share [Customer Name]’s journey with you—how they went from [Problem] to [Desired Outcome], and how you can achieve the same results.
Stay tuned, because this story might just be the inspiration you need to take the next step.
Best, [Your Name]

Email 2: The Problem
Subject: The Struggles [Customer Name] Faced Before Finding [Your Product/Service]
Body: Hi [First Name],
Let me tell you more about [Customer Name] and the challenges they were up against. Before discovering [Your Product/Service], they were dealing with [describe the problem in detail—emphasize the pain points, frustrations, and obstacles].
[Customer Name] felt stuck, overwhelmed, and unsure of how to move forward. They tried different solutions, but nothing seemed to work—until they found [Your Product/Service].
In my next email, I’ll share the turning point in [Customer Name]’s story—the moment they decided to try [Your Product/Service] and the incredible results that followed.
Talk soon, [Your Name]

Email 3: The Discovery
Subject: The Turning Point: How [Customer Name] Found [Your Product/Service]
Body: Hi [First Name],
Here’s the moment when everything changed for [Customer Name]. After struggling with [Problem] for so long, they stumbled upon [Your Product/Service] through [mention how they found you—an online search, a friend’s recommendation, etc.].
At first, [Customer Name] was skeptical—after all, they had tried so many things that didn’t work. But something about [Your Product/Service] stood out. It seemed different, more promising, and worth a try.
They decided to take the plunge, and that decision changed everything. In my next email, I’ll reveal the incredible transformation [Customer Name] experienced after using [Your Product/Service].
Can’t wait to share more, [Your Name]

Email 4: The Transformation
Subject: The Amazing Results [Customer Name] Achieved with [Your Product/Service]
Body: Hi [First Name],
After trying [Your Product/Service], [Customer Name] experienced a transformation they never thought possible. Here’s what happened:
Problem Solved: [Customer Name] was finally able to [describe the solution provided by your product/service—be specific].
Life Changed: The results weren’t just temporary; they were life-changing. [Customer Name] went from [describe the problem] to [describe the new, improved state].
Confidence Gained: With their problem solved, [Customer Name] felt more confident, empowered, and ready to take on new challenges.
[Customer Name] couldn’t believe how quickly and effectively [Your Product/Service] worked. It was the solution they had been searching for all along.
In my next email, I’ll show you how you can achieve similar results with [Your Product/Service] and start your own transformation story.
Best, [Your Name]

Email 5: The Invitation
Subject: Ready to Start Your Own Transformation? Here’s How [Customer Name] Did It
Body: Hi [First Name],
You’ve seen how [Customer Name] went from struggling with [Problem] to achieving incredible results with [Your Product/Service]. Now, it’s your turn.
Imagine what it would feel like to finally overcome [Problem] and start living the life you’ve always wanted. With [Your Product/Service], that dream can become a reality.
Here’s how you can get started:
Visit Our Website: [Insert Link] to learn more about [Your Product/Service].
Order Today: Take advantage of our [mention any discounts or offers] to start your journey with [Your Product/Service].
Experience the Transformation: Just like [Customer Name], you can experience real, lasting results.
Don’t wait—start your transformation today. If [Customer Name] can do it, so can you.
Looking forward to hearing your success story, [Your Name]

Email 6: The Reminder
Subject: Don’t Miss Out: Your Transformation Awaits
Body: Hi [First Name],
I just wanted to send you a quick reminder—there’s still time to start your journey with [Your Product/Service] and achieve the results you’ve been dreaming of.
Remember [Customer Name] and their incredible transformation? That could be you, but only if you take the first step.
Click here [Insert Link] to get started now and take advantage of our [mention any time-sensitive offers or bonuses].
Your success story is waiting to be written—don’t let this opportunity pass you by.
Talk soon, [Your Name]

This email campaign leverages the Story Method by walking potential customers through a real-life success story. It highlights the problem, the discovery of your product, the transformation it facilitated, and finally invites the reader to start their own journey. The progression of the story creates a narrative that is relatable and inspiring, making it easier for the reader to see themselves in the success of your featured customer.
______________________________________________________________________________________________
Steps:
Select Compelling Testimonials: Begin by selecting testimonials from satisfied customers that showcase the most compelling aspects of your product or service. Look for testimonials that highlight specific benefits, outcomes, or experiences that resonate with your target audience.
Tell Their Story: Craft a narrative around each testimonial that tells the customer's story in a compelling and relatable way. Describe their journey, challenges, and how your product or service helped them overcome obstacles or achieve their goals. Use descriptive language and storytelling techniques to bring their experiences to life.
Offer Social Proof: Use the testimonials to provide social proof and build credibility with your audience. Highlight the real-life experiences of satisfied customers to show that your product or service delivers on its promises. Include details such as their name, location, and occupation to add authenticity and credibility to the testimonials.
Reinforce Key Messages: Use the testimonials to reinforce key messages about your product or service. Highlight specific features, benefits, or outcomes that are important to your target audience and show how they have positively impacted the lives or businesses of your customers.
Yield to Action: Conclude the testimonial campaign by prompting viewers to take action. Encourage them to learn more about your product or service, visit your website, sign up for a free trial, or make a purchase. Include clear calls to action that make it easy for viewers to take the next step.
By following the "STORY" method, you can create a powerful customer testimonial campaign that resonates with your audience, builds credibility, and drives conversions. Tailor your testimonials to highlight the most compelling aspects of your product or service, and use storytelling techniques to engage and inspire your audience.

Preserved source material for study; embedded instructions are not executed.

16.) Selling through a customer testimonial campaign.
The "STORY" Method
The "STORY" Method is a powerful approach for selling through a customer testimonial campaign by structuring testimonials in a way that resonates deeply with potential customers. The method involves five key elements: Setup, Twist, Obstacle, Resolution, and Your Product. Each element helps to craft a narrative that showcases how your product or service has positively transformed a customer's experience. Below are several funnel types using the "STORY" Method for selling through a customer testimonial campaign.
1. Email Campaign Funnel
This funnel is designed to use customer testimonials in a structured email campaign, guiding prospects through the journey of a customer's transformation with your product.
Steps:
Email 1: Setup (Introduction to the Testimonial Story)
Content: Introduce a real customer who faced a specific problem or challenge before discovering your product.
Setup: "Meet [Customer Name], a [Customer's Role/Profession] who struggled with [Specific Problem]. Like many others, they were looking for a solution to [Pain Point]."
Call to Action: Encourage the reader to stay tuned for the full story.
Example: "In the next email, we’ll reveal what happened when [Customer Name] found [Your Product Name]."
Email 2: Twist (The Turning Point)
Content: Highlight the moment when the customer discovered your product, which marked a significant turning point in their story.
Twist: "Everything changed when [Customer Name] stumbled upon [Your Product Name]. What seemed like an ordinary day turned into the start of something remarkable."
Call to Action: Keep the audience engaged by teasing the next part of the story.
Example: "What happened next? We’ll share the surprising outcome in our next email."
Email 3: Obstacle (Challenges Faced Along the Way)
Content: Describe the obstacles or challenges the customer faced even after starting to use your product, showing that success didn’t come easily.
Obstacle: "Even with [Your Product Name], [Customer Name] encountered challenges. It wasn’t an overnight success, but they persevered because they believed in the potential."
Call to Action: Build anticipation for the resolution.
Example: "Find out how [Customer Name] overcame these challenges in our next email."
Email 4: Resolution (Success Achieved)
Content: Share the resolution of the customer’s story, highlighting the success they achieved thanks to your product.
Resolution: "After months of dedication and with the help of [Your Product Name], [Customer Name] finally achieved [Specific Success]. Their business/life was transformed."
Call to Action: Encourage readers to imagine their own success with the product.
Example: "Imagine what [Your Product Name] could do for you—learn more by clicking here."
Email 5: Your Product (Direct Offer)
Content: Directly connect the customer’s story to your product and invite the audience to take action.
Your Product: "Inspired by [Customer Name]’s journey? [Your Product Name] is the key to achieving [Desired Outcome]. Don’t wait—start your own success story today."
Call to Action: Provide a compelling offer or discount to encourage immediate action.
Example: "Get started with [Your Product Name] now and enjoy [Special Offer]. Click here to order!"
Follow-Up Sequence:
Goal: Follow up with those who didn’t convert, reinforcing the testimonial and offering a final incentive.
Content: "Don’t miss out on the opportunity to transform your own life with [Your Product Name]. Use code [Discount Code] for 10% off—limited time only!"

2. Social Media Campaign Funnel
This funnel leverages customer testimonials across social media platforms, using the "STORY" Method to create compelling posts that drive engagement and sales.
Steps:
Post 1: Setup (Introduction to the Customer’s Story)
Content: Share a brief introduction to a customer’s story, focusing on the problem they faced before finding your product.
Setup: "Meet [Customer Name], who was struggling with [Specific Problem] before they found [Your Product Name]."
Call to Action: Encourage followers to stay tuned for the full story.
Example: "Want to know how [Customer Name] turned things around? Stay tuned!"
Post 2: Twist (Discovery of Your Product)
Content: Highlight the turning point in the customer’s story—when they discovered your product.
Twist: "[Customer Name]’s search for a solution led them to [Your Product Name], and that’s when everything started to change."
Call to Action: Build anticipation for the next part of the story.
Example: "What happened next? You’ll be surprised—more coming soon!"
Post 3: Obstacle (Challenges Overcome)
Content: Share the obstacles the customer faced, showing that success didn’t come without effort.
Obstacle: "Even after finding [Your Product Name], [Customer Name] had to overcome several challenges. But with persistence, they kept going."
Call to Action: Encourage engagement and curiosity about the resolution.
Example: "How did [Customer Name] overcome these challenges? Find out in our next post."
Post 4: Resolution (Success Achieved)
Content: Reveal the success the customer achieved, thanks to your product.
Resolution: "[Customer Name] finally achieved [Specific Success] with the help of [Your Product Name]. Their journey is a testament to what’s possible."
Call to Action: Invite followers to learn more about the product.
Example: "Inspired by [Customer Name]’s story? Learn more about how [Your Product Name] can help you achieve the same results."
Post 5: Your Product (Direct Offer)
Content: Directly tie the success story to your product and offer a compelling reason to take action.
Your Product: "Ready to start your own success story? [Your Product Name] is the solution you’ve been looking for. Take advantage of our limited-time offer!"
Call to Action: Include a strong CTA with a link to purchase or learn more.
Example: "Click here to order now and start your transformation with [Your Product Name]."
Follow-Up Engagement:
Goal: Engage with followers who showed interest in the posts but haven’t taken action, using comments, direct messages, or additional posts.
Content: "We’ve seen incredible responses to [Customer Name]’s story—don’t miss your chance to experience the same success with [Your Product Name]. Click here for a special discount!"

3. Video Testimonial Funnel
This funnel uses video testimonials structured around the "STORY" Method to engage viewers and drive sales through a video series or single compelling video.
Steps:
Video 1: Setup (Introduction)
Content: Introduce the customer and their initial struggle, setting up the narrative.
Setup: "[Customer Name] was facing [Specific Problem] when they first reached out to us. They needed a solution that could truly make a difference."
Call to Action: Tease the next part of the story and encourage viewers to watch the following video.
Example: "What happened when they discovered [Your Product Name]? Watch the next video to find out."
Video 2: Twist (Discovery of Your Product)
Content: Show the moment of discovery when the customer found your product, explaining how it changed their approach.
Twist: "When [Customer Name] found [Your Product Name], they knew it was different. It offered something they hadn’t found anywhere else."
Call to Action: Encourage viewers to continue watching to see how the story unfolds.
Example: "How did [Your Product Name] make a difference? See the transformation in the next video."
Video 3: Obstacle (Challenges Faced)
Content: Discuss the challenges or obstacles the customer encountered, even after using your product, to show authenticity and relatability.
Obstacle: "It wasn’t all smooth sailing. [Customer Name] had to overcome some hurdles, but they stuck with [Your Product Name], believing in its potential."
Call to Action: Build anticipation for the resolution.
Example: "How did they overcome these obstacles? Don’t miss the next video to see the final outcome."
Video 4: Resolution (Success Achieved)
Content: Reveal the success that the customer achieved, demonstrating the product’s effectiveness.
Resolution: "With persistence and the support of [Your Product Name], [Customer Name] finally achieved [Specific Success]. Their story is proof that [Your Product Name] works."
Call to Action: Encourage viewers to consider their own transformation and take action.
Example: "Ready to start your own success story? Learn more about [Your Product Name] today."
Video 5: Your Product (Direct Offer)
Content: Directly connect the testimonial to your product, offering a clear call to action.
Your Product: "[Customer Name] isn’t the only one who can benefit from [Your Product Name]. Start your journey today and take advantage of our special offer."
Call to Action: Provide a compelling offer and a clear CTA.
Example: "Click the link below to order now and join the many others who have transformed their lives with [Your Product Name]."
Follow-Up Sequence:
Goal: Send follow-up emails or messages to those who watched the video series but haven’t taken action, offering additional incentives.
Content: "We hope you were inspired by [Customer Name]’s story. Now it’s your turn—use code [Discount Code] for a special offer on [Your Product Name]."

4. Landing Page Funnel
This funnel focuses on using customer testimonials structured with the "STORY" Method on a dedicated landing page to convert visitors into customers.
Steps:
Landing Page Section 1: Setup (Introduction)
Content: Start with an engaging introduction to the customer’s story, drawing the visitor in by highlighting the problem the customer faced.
Setup: "Before discovering [Your Product Name], [Customer Name] was struggling with [Specific Problem], just like many others."
Call to Action: Encourage visitors to continue reading to learn how the story unfolds.
Example: "Read on to discover how [Customer Name] turned things around with [Your Product Name]."
Landing Page Section 2: Twist (Discovery of Your Product)
Content: Describe the pivotal moment when the customer found your product, setting the stage for the transformation.
Twist: "Everything changed when [Customer Name] discovered [Your Product Name]. It was the solution they had been searching for."
Call to Action: Keep the reader engaged with a teaser about the upcoming transformation.
Example: "How did [Your Product Name] help them overcome their challenges? Keep reading to find out."
Landing Page Section 3: Obstacle (Challenges Faced)
Content: Share the challenges the customer faced even after starting to use your product, adding authenticity and relatability.
Obstacle: "Of course, success didn’t come without its challenges. [Customer Name] faced [Specific Obstacle], but they didn’t give up."
Call to Action: Build anticipation for the resolution and encourage further reading.
Example: "How did [Customer Name] overcome these challenges? The resolution will inspire you."
Landing Page Section 4: Resolution (Success Achieved)
Content: Highlight the success the customer achieved, showcasing the product’s impact.
Resolution: "With determination and the help of [Your Product Name], [Customer Name] achieved [Specific Success]. Their life/business was transformed."
Call to Action: Encourage visitors to consider how they could achieve similar results.
Example: "Ready to experience the same success? Here’s how you can get started with [Your Product Name]."
Landing Page Section 5: Your Product (Direct Offer)
Content: Directly link the testimonial to your product and present a compelling offer.
Your Product: "Inspired by [Customer Name]’s story? [Your Product Name] can help you achieve the same results. Don’t wait—take action today."
Call to Action: Provide a clear CTA with a special offer or discount.
Example: "Order now and get [Discount/Bonus]—click the button below to start your transformation with [Your Product Name]."
Follow-Up Sequence:
Goal: For visitors who didn’t convert on the landing page, follow up with targeted emails that reinforce the testimonial and offer a final incentive.
Content: "We noticed you didn’t complete your purchase. If you’re still considering [Your Product Name], we’re offering a limited-time discount. Click here to take advantage before it’s gone!"

5. Webinar Testimonial Funnel
This funnel incorporates customer testimonials into a live or recorded webinar, using the "STORY" Method to build trust and drive conversions.
Steps:
Registration Page:
S (Setup): Introduce the customer’s story as a central element of the webinar, focusing on the problem they faced before discovering your product.
Setup: "Join our free webinar to learn how [Customer Name] overcame [Specific Problem] and transformed their life/business with [Your Product Name]."
Call to Action: Encourage registrations by promising valuable insights and real-life success stories.
Example: "Sign up now to hear the full story and discover how you can achieve the same results."
Webinar Introduction:
S (Setup): Start the webinar by introducing the customer’s story, explaining the challenges they faced before finding your product.
Setup: "Today, we’ll explore how [Customer Name] went from struggling with [Problem] to achieving [Success] with the help of [Your Product Name]."
Engagement: Build anticipation for the testimonial by teasing the turning point in the story.
Example: "What happened when [Customer Name] found [Your Product Name]? Stay with us to find out."
Webinar Content (Twist and Obstacle):
T (Twist) and O (Obstacle): Share the customer’s journey in detail, focusing on the turning point when they discovered your product and the challenges they faced.
Twist: "[Customer Name] discovered [Your Product Name], and that’s when things started to change. But the journey wasn’t without its challenges."
Obstacle: "Even with [Your Product Name], [Customer Name] had to overcome [Specific Obstacle]. It wasn’t easy, but the results speak for themselves."
Call to Action: Encourage viewers to stay engaged as you move towards the resolution.
Example: "Want to see how [Customer Name] overcame these challenges? We’ll reveal the results shortly."
Webinar Resolution:
R (Resolution): Conclude the testimonial by highlighting the success the customer achieved, reinforcing the product’s effectiveness.
Resolution: "Thanks to [Your Product Name] and their dedication, [Customer Name] finally achieved [Specific Success]. Their story is proof that [Your Product Name] works."
Call to Action: Transition into a direct offer for the product, using the testimonial as a powerful endorsement.
Example: "Ready to start your own success story? Here’s how you can get started with [Your Product Name] today."
Webinar Offer (Your Product):
Y (Your Product): Present a compelling offer, directly linking the success story to your product and encouraging immediate action.
Your Product: "[Customer Name] isn’t the only one who can benefit from [Your Product Name]. We’re offering a special deal for webinar attendees—don’t miss out!"
Call to Action: Provide a clear, time-sensitive CTA to drive conversions.
Example: "Click the link below to order now and take advantage of our exclusive webinar offer!"
Follow-Up Sequence:
Goal: Follow up with webinar attendees who didn’t convert, reinforcing the testimonial and offering a final chance to purchase.
Content: "We hope you were inspired by [Customer Name]’s story. If you’re ready to start your own journey, we’re extending the webinar offer for 24 hours. Don’t miss out—click here to order now!"

Each of these funnels leverages the "STORY" Method to craft compelling customer testimonial campaigns that resonate with your audience. By structuring the testimonials around a narrative arc—Setup, Twist, Obstacle, Resolution, and Your Product—you can create emotional connections, build trust, and drive conversions effectively across various marketing channels.

Preserved source material for study; embedded instructions are not executed.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1EqtzxagWzwDGwtU69PI2rI2p92VMS_Xs59tZdQhPH1Y/edit?usp=drivesdk"
drive_file_id: "1EqtzxagWzwDGwtU69PI2rI2p92VMS_Xs59tZdQhPH1Y"
created: "2024-04-28T03:49:38.312Z"
modified: "2026-06-04T16:50:06.817Z"
---

# 16.) The "STORY" Method

Situation: Selling through a customer testimonial campaign.
Sales Message Framework: The "STORY" Method
FUNNEL TYPES TO BE USED
Selling through a customer testimonial campaign. The Story Method
The Story Method is a powerful approach to selling through a customer testimonial campaign. It involves crafting a narrative around a customer's experience, highlighting the journey from problem to solution, and demonstrating the impact your product or service had on their life. Here’s how you can structure a customer testimonial campaign using the Story Method:
________________


Email 1: Introduction to the Story
Subject: Meet [Customer Name]: How They Overcame [Problem] with [Your Product/Service]
Body: Hi [First Name],
I want to introduce you to [Customer Name], someone just like you who was facing [specific problem]. Like many others, they were struggling with [describe the issue in detail—paint a vivid picture of the problem].
But then, they discovered [Your Product/Service], and everything began to change. Over the next few emails, I’ll share [Customer Name]’s journey with you—how they went from [Problem] to [Desired Outcome], and how you can achieve the same results.
Stay tuned, because this story might just be the inspiration you need to take the next step.
Best, [Your Name]
________________


Email 2: The Problem
Subject: The Struggles [Customer Name] Faced Before Finding [Your Product/Service]
Body: Hi [First Name],
Let me tell you more about [Customer Name] and the challenges they were up against. Before discovering [Your Product/Service], they were dealing with [describe the problem in detail—emphasize the pain points, frustrations, and obstacles].
[Customer Name] felt stuck, overwhelmed, and unsure of how to move forward. They tried different solutions, but nothing seemed to work—until they found [Your Product/Service].
In my next email, I’ll share the turning point in [Customer Name]’s story—the moment they decided to try [Your Product/Service] and the incredible results that followed.
Talk soon, [Your Name]
________________


Email 3: The Discovery
Subject: The Turning Point: How [Customer Name] Found [Your Product/Service]
Body: Hi [First Name],
Here’s the moment when everything changed for [Customer Name]. After struggling with [Problem] for so long, they stumbled upon [Your Product/Service] through [mention how they found you—an online search, a friend’s recommendation, etc.].
At first, [Customer Name] was skeptical—after all, they had tried so many things that didn’t work. But something about [Your Product/Service] stood out. It seemed different, more promising, and worth a try.
They decided to take the plunge, and that decision changed everything. In my next email, I’ll reveal the incredible transformation [Customer Name] experienced after using [Your Product/Service].
Can’t wait to share more, [Your Name]
________________


Email 4: The Transformation
Subject: The Amazing Results [Customer Name] Achieved with [Your Product/Service]
Body: Hi [First Name],
After trying [Your Product/Service], [Customer Name] experienced a transformation they never thought possible. Here’s what happened:
* Problem Solved: [Customer Name] was finally able to [describe the solution provided by your product/service—be specific].
* Life Changed: The results weren’t just temporary; they were life-changing. [Customer Name] went from [describe the problem] to [describe the new, improved state].
* Confidence Gained: With their problem solved, [Customer Name] felt more confident, empowered, and ready to take on new challenges.
[Customer Name] couldn’t believe how quickly and effectively [Your Product/Service] worked. It was the solution they had been searching for all along.
In my next email, I’ll show you how you can achieve similar results with [Your Product/Service] and start your own transformation story.
Best, [Your Name]
________________


Email 5: The Invitation
Subject: Ready to Start Your Own Transformation? Here’s How [Customer Name] Did It
Body: Hi [First Name],
You’ve seen how [Customer Name] went from struggling with [Problem] to achieving incredible results with [Your Product/Service]. Now, it’s your turn.
Imagine what it would feel like to finally overcome [Problem] and start living the life you’ve always wanted. With [Your Product/Service], that dream can become a reality.
Here’s how you can get started:
1. Visit Our Website: [Insert Link] to learn more about [Your Product/Service].
2. Order Today: Take advantage of our [mention any discounts or offers] to start your journey with [Your Product/Service].
3. Experience the Transformation: Just like [Customer Name], you can experience real, lasting results.
Don’t wait—start your transformation today. If [Customer Name] can do it, so can you.
Looking forward to hearing your success story, [Your Name]
________________


Email 6: The Reminder
Subject: Don’t Miss Out: Your Transformation Awaits
Body: Hi [First Name],
I just wanted to send you a quick reminder—there’s still time to start your journey with [Your Product/Service] and achieve the results you’ve been dreaming of.
Remember [Customer Name] and their incredible transformation? That could be you, but only if you take the first step.
Click here [Insert Link] to get started now and take advantage of our [mention any time-sensitive offers or bonuses].
Your success story is waiting to be written—don’t let this opportunity pass you by.
Talk soon, [Your Name]
________________


This email campaign leverages the Story Method by walking potential customers through a real-life success story. It highlights the problem, the discovery of your product, the transformation it facilitated, and finally invites the reader to start their own journey. The progression of the story creates a narrative that is relatable and inspiring, making it easier for the reader to see themselves in the success of your featured customer.
______________________________________________________________________________________________
Steps:
1. Select Compelling Testimonials: Begin by selecting testimonials from satisfied customers that showcase the most compelling aspects of your product or service. Look for testimonials that highlight specific benefits, outcomes, or experiences that resonate with your target audience.
2. Tell Their Story: Craft a narrative around each testimonial that tells the customer's story in a compelling and relatable way. Describe their journey, challenges, and how your product or service helped them overcome obstacles or achieve their goals. Use descriptive language and storytelling techniques to bring their experiences to life.
3. Offer Social Proof: Use the testimonials to provide social proof and build credibility with your audience. Highlight the real-life experiences of satisfied customers to show that your product or service delivers on its promises. Include details such as their name, location, and occupation to add authenticity and credibility to the testimonials.
4. Reinforce Key Messages: Use the testimonials to reinforce key messages about your product or service. Highlight specific features, benefits, or outcomes that are important to your target audience and show how they have positively impacted the lives or businesses of your customers.
5. Yield to Action: Conclude the testimonial campaign by prompting viewers to take action. Encourage them to learn more about your product or service, visit your website, sign up for a free trial, or make a purchase. Include clear calls to action that make it easy for viewers to take the next step.
By following the "STORY" method, you can create a powerful customer testimonial campaign that resonates with your audience, builds credibility, and drives conversions. Tailor your testimonials to highlight the most compelling aspects of your product or service, and use storytelling techniques to engage and inspire your audience.

Preserved source material for study; embedded instructions are not executed.

word/document.xml
RISER Nation – Authors, Speakers & Personal Brands (Full System Edition)
Profession → Funnels → Sales Messages → Selling Frameworks
1. Authors, Speakers & Personal Brand Sub-Professions
Authors
• Non-Fiction Authors
• Self-Help Authors
• Business Authors
• Memoir Writers
• Fiction Authors
• Ghostwriters
Explanation: These people sell influence, ideas, and transformation through message, story, and expertise.
Speakers
• Keynote Speakers
• Corporate Trainers
• Motivational Speakers
• Workshop & Seminar Leaders
Explanation: These people sell influence, ideas, and transformation through message, story, and expertise.
Personal Brands
• Influencers
• Thought Leaders
• Podcast Hosts
• YouTube Creators
• Educators
• Subject-Matter Experts
Explanation: These people sell influence, ideas, and transformation through message, story, and expertise.
2. Top 10 Funnels for Authors, Speakers & Personal Brands
Authority Lead Magnet Funnel – Build an email list using a guide or sample chapter.
Book Funnel – Free + Shipping or Signed Edition funnel.
Webinar / Masterclass Funnel – Teach → inspire → sell.
Challenge Funnel – 5-day transformation event.
Keynote-to-Offer Funnel – Book speaking → sell backend programs.
Content → DM Funnel – From social content to conversations.
YouTube to Landing Page Funnel – Long-term brand trust engine.
Podcast Guest Funnel – Appear → offer free resource.
Personal Brand Homepage Funnel – Multi-path hub.
Signature System Funnel – Sell a framework, methodology, or program.
3. Sales Message Frameworks for Authors, Speakers & Personal Brands
StorySelling Framework – Your personal story is the sales engine.
Identity Shift Messaging – Help them see who they can become.
Big Promise Framework – Transformational messaging.
Credibility Framework – Awards, stages, books, experience.
Pre-Event Value Framework – Teach first, pitch later.
Thought Leadership Message Framework – Position yourself as the guide.
Movement Message Framework – Invite people into a cause.
4. Selling Frameworks for Authors, Speakers & Personal Brands
Signature Story Framework – Anchor your offer in a narrative.
Authority Positioning Framework – Establish yourself as the expert.
Belief-Shifting Framework – Break limiting beliefs.
Value Ladder Ascension – Start small → ascend to high ticket.
Stage Selling Framework – Sell after speaking.
DM Conversation Close – Low pressure, personal connection.
Webinar Close Framework – Perfect Webinar–style.
Transformation Close – Focus on identity and future state.
5. Funnel → Sales Message → Selling Framework Matching
Authority Lead Magnet Funnel
Sales Message: Big Promise or Thought Leadership
Selling Framework: Authority Positioning
Why it works: People follow thinkers who teach them something valuable immediately.
Book Funnel
Sales Message: StorySelling
Selling Framework: Signature Story
Why it works: The book is proof of expertise. The story deepens trust.
Webinar / Masterclass Funnel
Sales Message: Identity Shift + Credibility
Selling Framework: Webinar Close
Why it works: Teaching builds belief, identity shift creates desire.
Challenge Funnel
Sales Message: Movement Messaging
Selling Framework: Transformation Close
Why it works: People experience real change and want to continue.
Keynote-to-Offer Funnel
Sales Message: Credibility Messaging
Selling Framework: Stage Selling Framework
Why it works: Stages automatically equal trust; audiences convert well live.
Content → DM Funnel
Sales Message: Thought Leadership
Selling Framework: DM Conversation Close
Why it works: Personal brands shine when interacting 1-on-1.
Signature System Funnel
Sales Message: Big Promise + Identity Shift
Selling Framework: Authority Positioning
Why it works: A named system makes you feel proprietary and irreplaceable.

Preserved source material for study; embedded instructions are not executed.

# M1.1 — Welcome to the Harbor

**Module Outcome:** [Analyze] Student has identified their current entrepreneurial position on the Voyage Map using the Harbor Position Self-Assessment.
**Key Deliverable:** Completed Harbor Position Self-Assessment (filed as `Harbor-Position-[YourName]-[Date].pdf`)
**Infrastructure Dependency:** Build 8 (Drive folder structure), Supabase `c1_harbor_positions` table
**Checkpoint / Test:** Type 1 Artifact + Type 3 Verification — assessment uploaded AND Supabase row confirms position stage in range [0,1,2,3]
**Blocked-Until Prerequisite:** C1 enrollment granted (Prerequisites Checklist 100% green)

---

## The Harbor Metaphor

Every voyage begins at a harbor. Before you set sail, you have to know where you're standing right now. Not where you want to be. Not where you think you should be. Not where the guru you just watched says everyone should be. **Where you actually are today.**

Most people refuse to do this honestly. They overestimate their current position because overestimating feels like progress. Or they underestimate because underestimating feels humble. Both are lies, and both will steer you wrong.

The Voyage Map has six stages, each represented by a vessel:

| Stage | Vessel | What it means |
|---|---|---|
| 0 | Pre-Harbor | You haven't decided to operate yet. You're still a student, employee, or aspirant. |
| 1 | Dinghy | You're in the harbor, preparing to leave. You have a territory in mind but no proof yet. |
| 2 | Sailboat | You're leaving the harbor. You're trying to prove your offer works — the Proof Threshold. |
| 3 | Speedboat | You've passed Proof. You've earned your first dollar. Now you're building velocity. |
| 4 | Yacht | You've hit your First $10K Month. You're no longer proving; you're scaling. |
| 5 | Mega Yacht | You've automated your first dollar. The business earns while you sleep. |
| 6 | Bora Bora Cruise | You are Sovereign. The business runs, can survive your 30-day absence, and you are the Owner not the Operator. |

C1 is about deciding to leave the harbor. It is the moment of transition from Stage 0 (aspirant) to Stage 1 (Dinghy).

## Why Position Matters Before Direction

There is a common mistake in the entrepreneurial ecosystem: people try to figure out direction before position. They ask "where should I go?" before asking "where am I?" The result is advice-shopping — reading every book, watching every video, trying every strategy, because without a fixed starting point, any direction looks plausible.

Position collapses the option space. If you're at Stage 0, the question "should I invest in paid ads?" has one answer: no. You have nothing worth advertising yet. If you're at Stage 4, the question "should I quit my day job?" is absurd because you've been running the business for three years and have $120K/year in revenue — there is no day job to quit. Position tells you which questions are meaningful to ask right now.

## The Six Positions, Honestly Described

### Stage 0 — Pre-Harbor (aspirant)

You're reading entrepreneurial content. You may have a side project, a spreadsheet of ideas, or a half-built landing page. You have not yet committed to a territory. Revenue from the business is zero or inconsistent (less than $500/month, irregularly). You might be employed full-time elsewhere or between jobs. You have never signed a Captain's Oath and don't know what one is.

*Most people who start C1 are at Stage 0. This is fine and expected.*

### Stage 1 — Dinghy (preparing to leave)

You have decided on a territory. You have a rough idea of who your buyer is. You have a product concept or service idea, even if it's not polished. You have had a few customer conversations. Revenue is 0 to ~$1,000/month, mostly from inconsistent trial offers. You have a website or at least a landing page. You are NOT yet at the Proof Threshold (you have not validated that strangers will pay your offer reliably).

### Stage 2 — Sailboat (leaving the harbor)

You have a documented offer, documented customer avatars, and are running active experiments to find your Proof Threshold. Monthly revenue is irregular but non-zero — maybe $500-5,000 depending on the week. You've had at least 10 paying customers but haven't cracked a repeatable acquisition system. You know what "the Proof Threshold" is (passing it means: you can predict, within 25% error, how much you'll earn next month).

### Stage 3 — Speedboat (velocity building)

You've passed Proof Threshold. First Dollar has been earned repeatedly and is predictable. Revenue is $2K-15K/month, growing month-over-month. You have 1-3 paid acquisition channels that work. You have between 10 and 100 customers. You have recurring revenue or repeat purchase behavior. You are NOT yet at the First $10K Month (or if you've hit it once, you haven't sustained it for 3+ months).

### Stage 4 — Yacht (scaling)

First $10K Month has been achieved and sustained for 3+ consecutive months. Revenue is $10K-50K/month. You have 100+ customers. You have 2-5 team members (contractors or employees). Build 1 (Supabase) and Build 2 (GHL) are in production. You have an attorney, an accountant, and attorney-reviewed legal docs. You are NOT yet at the Automated Dollar stage (most operations still require you personally).

### Stage 5 — Mega Yacht (automation)

First Automated Dollar has been earned — revenue came in while you were away from the business. Revenue is $50K-500K/month. You have 5-15 team members. Multiple products or service tiers. Build 8 (knowledge base) is in production. Some portion of operations runs without your direct involvement. You are NOT yet Sovereign (30-Day Disappearance Test would reveal dependencies).

### Stage 6 — Bora Bora Cruise (Sovereign)

You are the Owner, not the Operator. The business survives a 30-day disappearance without revenue collapse. Revenue is $500K+/month. Team is self-managing. All 27 Builds are in production. Build 14 causal modeling has 6+ months of clean data. You could sell the business, and the valuation would not collapse because you are leaving.

---

## The Self-Assessment

In Folder 02 Worksheets, open `Harbor-Position-Self-Assessment.md`. The assessment has 24 questions (3 per stage × 8 diagnostic dimensions) and produces a numeric score that maps to your honest current position.

The worksheet is **not** a personality test. It's a stage-of-business audit. Answer it based on the last 90 days, not on your aspirations. If your revenue in the last 90 days was $0, you are at Stage 0 regardless of how close you feel to Stage 1.

The assessment takes ~30 minutes to complete honestly. Faster than 15 minutes usually means you're not being honest with yourself (the assessment asks questions that should require reflection). Slower than 60 minutes usually means you're overthinking the edge cases — if you're truly between two stages, always score yourself at the lower one. The system is designed to produce small wins when you "advance" rather than disappointment when you "slip."

## Calibration Check

Once you've completed the assessment, there's a calibration exercise:

**Pull your bank statement for the last 90 days.** Look at the actual deposits from customers. Not from your own transfers, not from investors, not from family — actual customers paying for your actual offers.

- If you have zero customer deposits in the last 90 days: Stage 0, regardless of what the assessment said.
- If you have inconsistent customer deposits but they exist: minimum Stage 1.
- If you have at least 10 customer deposits across at least 2 months with a consistent offer: minimum Stage 2.
- If you have monthly customer deposits exceeding $2,000 for 3+ consecutive months: minimum Stage 3.
- If you have monthly customer deposits exceeding $10,000 for 3+ consecutive months: minimum Stage 4.
- If customer deposits continued during a period of 14+ consecutive days when you did zero business work: minimum Stage 5.
- If customer deposits continued during a period of 30+ consecutive days when you did zero business work AND the team was self-managing: Stage 6.

The assessment and the bank statement should match. If they don't, the bank statement wins. Money doesn't lie; self-reports do.

## What This Module Is NOT

This module is not about making you feel good. It's not about celebrating where you are. It's not about "honoring your journey." It's about establishing an honest baseline so that your Captain's Oath (next module) is built on fact, not wish.

There is no wrong answer. Stage 0 is not shameful — it's actually the healthiest starting point for C1, because you have no prior commitments to unwind. Stage 4 entering C1 is harder in some ways because you have embedded habits that may need to be broken.

## The Deliverable

File the completed assessment to `/Drive/[YourName]/C1-Harbor-Orientation/Harbor-Position-[YourName]-[YYYY-MM-DD].pdf`.

Build 8 will auto-index the deliverable. Build 6 will register the checkpoint pass. Supabase will store your position stage (0-6) in the `c1_harbor_positions` table.

Once the checkpoint passes, M1.2 unlocks.

---

## Common Mistakes

**Mistake 1: Overestimating position.** "I'm kind of at Stage 2 even though I haven't had paying customers yet." No. You're at Stage 0. Wanting to be at a stage doesn't put you there.

**Mistake 2: Underestimating position.** "I'm still at Stage 0 because I haven't figured everything out." If you have paying customers and predictable revenue above $2K/month, you're at Stage 3, regardless of how unfinished you feel.

**Mistake 3: Treating the assessment as a personality quiz.** It's a financial and operational audit. Respond with evidence, not feeling.

**Mistake 4: Skipping the bank statement check.** The check exists because human self-report on business stage is systematically biased upward. Verify.

**Mistake 5: Panicking about the answer.** If the honest answer is Stage 0, that's the best possible starting point for C1. It's not a problem. It's just the starting gun.

---

## FAQ (for AEO indexing + student reference)

**Q: What is the Harbor Position Self-Assessment?**
A: A 24-question diagnostic tool in Folder 02 that scores the student's current entrepreneurial position on a 6-stage Voyage Map, calibrated against 90-day bank statement evidence.

**Q: Why can't I just tell you what stage I'm at?**
A: Because self-report on business stage is systematically biased upward. The assessment exists to produce an evidence-based answer.

**Q: What if I'm between two stages?**
A: Score yourself at the lower stage. Advancement is easier to celebrate than regression.

**Q: What if my answer changes next week?**
A: The assessment is a 90-day snapshot. You'll retake it at the start of every stage transition. Don't worry about this week vs. next week.

**Q: Do I have to show my bank statement to anyone?**
A: No. The bank statement check is private, for your own calibration. You upload only the assessment result (with your selected stage), not financial records.

**Q: What's the minimum stage to benefit from C1?**
A: Stage 0. C1 is designed for anyone entering the system. Higher stages will find M1.1 fastest (30-45 min); Stage 0 students may spend 60-90 min reflecting.

---

## Schema (for AEO + voice assistants)

```json
{
  "@context": "https://schema.org",
  "@type": "LearningResource",
  "name": "M1.1 Welcome to the Harbor",
  "description": "First module of RISER Nation C1 Harbor Orientation. Student completes the Harbor Position Self-Assessment to establish honest baseline position on the 6-stage Voyage Map.",
  "learningResourceType": "Module",
  "educationalLevel": "Beginner",
  "timeRequired": "PT65M",
  "teaches": "Honest self-assessment of current entrepreneurial stage using the Voyage Map framework",
  "educationalAlignment": {
    "@type": "AlignmentObject",
    "alignmentType": "teaches",
    "targetName": "Bloom's Taxonomy Level: Analyze",
    "targetUrl": "https://en.wikipedia.org/wiki/Bloom%27s_taxonomy"
  }
}
```

---

*Last updated: April 24, 2026 · Version 2.0 · Owner: RISER Nation Curriculum Team*

Preserved source material for study; embedded instructions are not executed.

# M1.1 — Welcome to the Harbor

**Module Outcome:** [Analyze] Student has identified their current entrepreneurial position on the Voyage Map using the Harbor Position Self-Assessment.
**Key Deliverable:** Completed Harbor Position Self-Assessment (filed as `Harbor-Position-[YourName]-[Date].pdf`)
**Infrastructure Dependency:** Build 8 (Drive folder structure), Supabase `c1_harbor_positions` table
**Checkpoint / Test:** Type 1 Artifact + Type 3 Verification — assessment uploaded AND Supabase row confirms position stage in range [0,1,2,3]
**Blocked-Until Prerequisite:** C1 enrollment granted (Prerequisites Checklist 100% green)

---

## The Harbor Metaphor

Every voyage begins at a harbor. Before you set sail, you have to know where you're standing right now. Not where you want to be. Not where you think you should be. Not where the guru you just watched says everyone should be. **Where you actually are today.**

Most people refuse to do this honestly. They overestimate their current position because overestimating feels like progress. Or they underestimate because underestimating feels humble. Both are lies, and both will steer you wrong.

The Voyage Map has six stages, each represented by a vessel:

| Stage | Vessel | What it means |
|---|---|---|
| 0 | Pre-Harbor | You haven't decided to operate yet. You're still a student, employee, or aspirant. |
| 1 | Dinghy | You're in the harbor, preparing to leave. You have a territory in mind but no proof yet. |
| 2 | Sailboat | You're leaving the harbor. You're trying to prove your offer works — the Proof Threshold. |
| 3 | Speedboat | You've passed Proof. You've earned your first dollar. Now you're building velocity. |
| 4 | Yacht | You've hit your First $10K Month. You're no longer proving; you're scaling. |
| 5 | Mega Yacht | You've automated your first dollar. The business earns while you sleep. |
| 6 | Bora Bora Cruise | You are Sovereign. The business runs, can survive your 30-day absence, and you are the Owner not the Operator. |

C1 is about deciding to leave the harbor. It is the moment of transition from Stage 0 (aspirant) to Stage 1 (Dinghy).

## Why Position Matters Before Direction

There is a common mistake in the entrepreneurial ecosystem: people try to figure out direction before position. They ask "where should I go?" before asking "where am I?" The result is advice-shopping — reading every book, watching every video, trying every strategy, because without a fixed starting point, any direction looks plausible.

Position collapses the option space. If you're at Stage 0, the question "should I invest in paid ads?" has one answer: no. You have nothing worth advertising yet. If you're at Stage 4, the question "should I quit my day job?" is absurd because you've been running the business for three years and have $120K/year in revenue — there is no day job to quit. Position tells you which questions are meaningful to ask right now.

## The Six Positions, Honestly Described

### Stage 0 — Pre-Harbor (aspirant)

You're reading entrepreneurial content. You may have a side project, a spreadsheet of ideas, or a half-built landing page. You have not yet committed to a territory. Revenue from the business is zero or inconsistent (less than $500/month, irregularly). You might be employed full-time elsewhere or between jobs. You have never signed a Captain's Oath and don't know what one is.

*Most people who start C1 are at Stage 0. This is fine and expected.*

### Stage 1 — Dinghy (preparing to leave)

You have decided on a territory. You have a rough idea of who your buyer is. You have a product concept or service idea, even if it's not polished. You have had a few customer conversations. Revenue is 0 to ~$1,000/month, mostly from inconsistent trial offers. You have a website or at least a landing page. You are NOT yet at the Proof Threshold (you have not validated that strangers will pay your offer reliably).

### Stage 2 — Sailboat (leaving the harbor)

You have a documented offer, documented customer avatars, and are running active experiments to find your Proof Threshold. Monthly revenue is irregular but non-zero — maybe $500-5,000 depending on the week. You've had at least 10 paying customers but haven't cracked a repeatable acquisition system. You know what "the Proof Threshold" is (passing it means: you can predict, within 25% error, how much you'll earn next month).

### Stage 3 — Speedboat (velocity building)

You've passed Proof Threshold. First Dollar has been earned repeatedly and is predictable. Revenue is $2K-15K/month, growing month-over-month. You have 1-3 paid acquisition channels that work. You have between 10 and 100 customers. You have recurring revenue or repeat purchase behavior. You are NOT yet at the First $10K Month (or if you've hit it once, you haven't sustained it for 3+ months).

### Stage 4 — Yacht (scaling)

First $10K Month has been achieved and sustained for 3+ consecutive months. Revenue is $10K-50K/month. You have 100+ customers. You have 2-5 team members (contractors or employees). Build 1 (Supabase) and Build 2 (GHL) are in production. You have an attorney, an accountant, and attorney-reviewed legal docs. You are NOT yet at the Automated Dollar stage (most operations still require you personally).

### Stage 5 — Mega Yacht (automation)

First Automated Dollar has been earned — revenue came in while you were away from the business. Revenue is $50K-500K/month. You have 5-15 team members. Multiple products or service tiers. Build 8 (knowledge base) is in production. Some portion of operations runs without your direct involvement. You are NOT yet Sovereign (30-Day Disappearance Test would reveal dependencies).

### Stage 6 — Bora Bora Cruise (Sovereign)

You are the Owner, not the Operator. The business survives a 30-day disappearance without revenue collapse. Revenue is $500K+/month. Team is self-managing. All 27 Builds are in production. Build 14 causal modeling has 6+ months of clean data. You could sell the business, and the valuation would not collapse because you are leaving.

---

## The Self-Assessment

In Folder 02 Worksheets, open `Harbor-Position-Self-Assessment.md`. The assessment has 24 questions (3 per stage × 8 diagnostic dimensions) and produces a numeric score that maps to your honest current position.

The worksheet is **not** a personality test. It's a stage-of-business audit. Answer it based on the last 90 days, not on your aspirations. If your revenue in the last 90 days was $0, you are at Stage 0 regardless of how close you feel to Stage 1.

The assessment takes ~30 minutes to complete honestly. Faster than 15 minutes usually means you're not being honest with yourself (the assessment asks questions that should require reflection). Slower than 60 minutes usually means you're overthinking the edge cases — if you're truly between two stages, always score yourself at the lower one. The system is designed to produce small wins when you "advance" rather than disappointment when you "slip."

## Calibration Check

Once you've completed the assessment, there's a calibration exercise:

**Pull your bank statement for the last 90 days.** Look at the actual deposits from customers. Not from your own transfers, not from investors, not from family — actual customers paying for your actual offers.

- If you have zero customer deposits in the last 90 days: Stage 0, regardless of what the assessment said.
- If you have inconsistent customer deposits but they exist: minimum Stage 1.
- If you have at least 10 customer deposits across at least 2 months with a consistent offer: minimum Stage 2.
- If you have monthly customer deposits exceeding $2,000 for 3+ consecutive months: minimum Stage 3.
- If you have monthly customer deposits exceeding $10,000 for 3+ consecutive months: minimum Stage 4.
- If customer deposits continued during a period of 14+ consecutive days when you did zero business work: minimum Stage 5.
- If customer deposits continued during a period of 30+ consecutive days when you did zero business work AND the team was self-managing: Stage 6.

The assessment and the bank statement should match. If they don't, the bank statement wins. Money doesn't lie; self-reports do.

## What This Module Is NOT

This module is not about making you feel good. It's not about celebrating where you are. It's not about "honoring your journey." It's about establishing an honest baseline so that your Captain's Oath (next module) is built on fact, not wish.

There is no wrong answer. Stage 0 is not shameful — it's actually the healthiest starting point for C1, because you have no prior commitments to unwind. Stage 4 entering C1 is harder in some ways because you have embedded habits that may need to be broken.

## The Deliverable

File the completed assessment to `/Drive/[YourName]/C1-Harbor-Orientation/Harbor-Position-[YourName]-[YYYY-MM-DD].pdf`.

Build 8 will auto-index the deliverable. Build 6 will register the checkpoint pass. Supabase will store your position stage (0-6) in the `c1_harbor_positions` table.

Once the checkpoint passes, M1.2 unlocks.

---

## Common Mistakes

**Mistake 1: Overestimating position.** "I'm kind of at Stage 2 even though I haven't had paying customers yet." No. You're at Stage 0. Wanting to be at a stage doesn't put you there.

**Mistake 2: Underestimating position.** "I'm still at Stage 0 because I haven't figured everything out." If you have paying customers and predictable revenue above $2K/month, you're at Stage 3, regardless of how unfinished you feel.

**Mistake 3: Treating the assessment as a personality quiz.** It's a financial and operational audit. Respond with evidence, not feeling.

**Mistake 4: Skipping the bank statement check.** The check exists because human self-report on business stage is systematically biased upward. Verify.

**Mistake 5: Panicking about the answer.** If the honest answer is Stage 0, that's the best possible starting point for C1. It's not a problem. It's just the starting gun.

---

## FAQ (for AEO indexing + student reference)

**Q: What is the Harbor Position Self-Assessment?**
A: A 24-question diagnostic tool in Folder 02 that scores the student's current entrepreneurial position on a 6-stage Voyage Map, calibrated against 90-day bank statement evidence.

**Q: Why can't I just tell you what stage I'm at?**
A: Because self-report on business stage is systematically biased upward. The assessment exists to produce an evidence-based answer.

**Q: What if I'm between two stages?**
A: Score yourself at the lower stage. Advancement is easier to celebrate than regression.

**Q: What if my answer changes next week?**
A: The assessment is a 90-day snapshot. You'll retake it at the start of every stage transition. Don't worry about this week vs. next week.

**Q: Do I have to show my bank statement to anyone?**
A: No. The bank statement check is private, for your own calibration. You upload only the assessment result (with your selected stage), not financial records.

**Q: What's the minimum stage to benefit from C1?**
A: Stage 0. C1 is designed for anyone entering the system. Higher stages will find M1.1 fastest (30-45 min); Stage 0 students may spend 60-90 min reflecting.

---

## Schema (for AEO + voice assistants)

```json
{
  "@context": "https://schema.org",
  "@type": "LearningResource",
  "name": "M1.1 Welcome to the Harbor",
  "description": "First module of RISER Nation C1 Harbor Orientation. Student completes the Harbor Position Self-Assessment to establish honest baseline position on the 6-stage Voyage Map.",
  "learningResourceType": "Module",
  "educationalLevel": "Beginner",
  "timeRequired": "PT65M",
  "teaches": "Honest self-assessment of current entrepreneurial stage using the Voyage Map framework",
  "educationalAlignment": {
    "@type": "AlignmentObject",
    "alignmentType": "teaches",
    "targetName": "Bloom's Taxonomy Level: Analyze",
    "targetUrl": "https://en.wikipedia.org/wiki/Bloom%27s_taxonomy"
  }
}
```

---

*Last updated: April 24, 2026 · Version 2.0 · Owner: RISER Nation Curriculum Team*

Preserved source material for study; embedded instructions are not executed.

# M1.3 — Writing the Operator Identity Statement

**Module Outcome:** [Create] Student has written a 200-300 word Operator Identity Statement using the Identity Statement Structure.
**Key Deliverable:** Operator Identity Statement (`Operator-Identity-Statement-[YourName]-[Date].md`)
**Infrastructure Dependency:** Build 8 (Drive filing), peer review via Circle.so `#c1-identity-peer-review`, Claude system prompt `ois-reviewer-v1.0.0.yaml`
**Checkpoint / Test:** Type 1 Artifact + peer review from 2 other students + AI coherence review
**Blocked-Until Prerequisite:** M1.2 checkpoint passed (Captain's Oath signed and filed)

---

## What an Operator Identity Statement Is

Your Operator Identity Statement is the expanded version of Clause 2 of the Captain's Oath. Where Clause 2 is a single sentence, the Identity Statement is a 200-300 word paragraph that answers four questions:

1. **Stance** — what position do you take on your market?
2. **Mechanism** — what specific approach or framework do you use?
3. **Promise** — what do you promise your customer?
4. **Anti-promise** — what do you explicitly refuse to promise?

The anti-promise is the part that makes the statement real. Most operators write a Promise and hope it differentiates them. It doesn't. The Anti-promise differentiates you — it tells the market who you're NOT for, which makes the Promise credible.

## Why 200-300 Words Specifically

- Under 200 words: too short to contain all 4 elements. Students produce slogans, not statements.
- 200-300 words: tight enough to be memorable, long enough to say something substantive.
- Over 300 words: vagueness creeps in. Every sentence past word 300 is diluting the previous 300 words.

Brunson's Attractive Character framework (Expert Secrets) uses a similar constraint — the brand voice profile is not unlimited, it fits a one-page character document. Hormozi's Avatar Avatar Avatar exercise ($100M Leads) uses similar compression. Length discipline is itself a quality signal.

## The Four Elements, in Order

### Element 1: Stance (40-60 words)

What is your position on your market? Not your opinion on every topic — your *stance* on the core question your customers are wrestling with.

Stance-writing template:

> "Most [audience] believe [common belief]. I believe that's [wrong / incomplete / outdated / dangerous] because [specific reason]. I operate from the position that [your alternative stance]."

Example: *"Most dental practice owners believe they need a 'better website' to fill empty chairs. I believe that's missing the real problem — the issue is not the website, it's that they're invisible in local search while competitors dominate the Map Pack. I operate from the position that 80% of dental marketing budgets are being spent on the wrong layer of the stack."*

### Element 2: Mechanism (60-80 words)

What's your specific approach? This is where the named framework appears.

Mechanism-writing template:

> "My approach is built around [named mechanism]. The mechanism is [brief description of how it works]. Unlike [competing approaches], [named mechanism] works because [specific reason]. The mechanism has produced [specific result for specific customer or customer type]."

Example: *"My approach is built around the Local Chair-Fill Framework — a 5-phase system that audits the practice's Map Pack presence, identifies the 3 keywords that drive 80% of competitor traffic, rebuilds the practice's Google Business Profile for those keywords, generates review velocity through a post-visit SMS sequence, and tracks chair-fill rate directly against the Google traffic. Unlike generic 'dental SEO,' the Local Chair-Fill Framework works because it's tied to the only metric that matters: how many new patients sat in a chair this month."*

### Element 3: Promise (40-60 words)

What do you promise your customer? The Promise must be:
- Specific (number, timeframe, outcome)
- Guaranteed (you'd refund if it didn't happen) or at least refundable
- Unusual (not a generic "we help you grow")

Promise-writing template:

> "I promise [specific audience] that within [specific timeframe], I will [specific measurable outcome]. If I don't deliver, [specific consequence for me]."

Example: *"I promise dental practices with $2M-$8M revenue that within 90 days, we will increase their new-patient chair-fill rate by at least 25%, or I will work for free until we hit that number."*

### Element 4: Anti-promise (40-60 words)

What do you explicitly REFUSE to do? This is the element that makes the Promise credible.

Anti-promise-writing template:

> "I do NOT promise [specific tempting outcome other operators promise]. I do NOT take [specific customer type I refuse to serve]. I do NOT use [specific tactic that's common but I reject]. If you want those things, you should work with [honest alternative], not me."

Example: *"I do NOT promise 10x growth in 30 days. I do NOT take dental practices with revenue under $1M (they're not ready for this system). I do NOT use purchased Google reviews or other tactics that could trigger Google penalties. If you want fast-but-fragile growth, work with a generic agency — not me."*

## The Assembly

Your Identity Statement is these 4 elements concatenated, in this order, with transitional language where needed. Total word count: 200-300 words.

**Example of assembled Identity Statement (from the dental practice example above, ~280 words):**

> Most dental practice owners believe they need a "better website" to fill empty chairs. I believe that's missing the real problem — the issue is not the website, it's that they're invisible in local search while competitors dominate the Map Pack. I operate from the position that 80% of dental marketing budgets are being spent on the wrong layer of the stack.
>
> My approach is built around the Local Chair-Fill Framework — a 5-phase system that audits the practice's Map Pack presence, identifies the 3 keywords that drive 80% of competitor traffic, rebuilds the practice's Google Business Profile for those keywords, generates review velocity through a post-visit SMS sequence, and tracks chair-fill rate directly against the Google traffic. Unlike generic "dental SEO," the Local Chair-Fill Framework works because it's tied to the only metric that matters: how many new patients sat in a chair this month.
>
> I promise dental practices with $2M-$8M revenue that within 90 days, we will increase their new-patient chair-fill rate by at least 25%, or I will work for free until we hit that number.
>
> I do NOT promise 10x growth in 30 days. I do NOT take dental practices with revenue under $1M — they're not ready for this system. I do NOT use purchased Google reviews or other tactics that could trigger Google penalties. If you want fast-but-fragile growth, work with a generic agency. Not me.

Read that as one block. Notice:
- You know within 20 seconds whether you are the target audience or not.
- The mechanism has a name.
- The Promise is specific, measurable, and carries consequence.
- The Anti-promise eliminates half the possible customer base, *which is what you want.*

## The Writing Process

**Step 1 (~30 min):** Open `02_Resources/Templates/Operator-Identity-Statement-Template.md`. This has the 4-element structure with prompts for each.

**Step 2 (~60 min):** Draft all 4 elements. Don't try to polish yet. Just produce.

**Step 3 (~30 min):** Read your draft out loud. Most weak statements fail the out-loud test — they sound like a slogan rather than something a human would say to another human.

**Step 4 (~30 min):** Compress. Target 250 words. If you're at 350, cut ruthlessly. If you're at 180, you're under-specifying.

**Step 5 (AI coherence review, 10 min):** Run your draft through the Claude system prompt `ois-reviewer-v1.0.0.yaml` (see `03_Scripts-and-Prompts/Claude-System-Prompts/`). Claude scores your statement on:
- Stance clarity (is there a real position, or generic inspiration?)
- Mechanism specificity (is there a named framework, or fuzzy abstraction?)
- Promise testability (is it measurable?)
- Anti-promise strength (does it actually eliminate customer types?)

Claude returns a score 0-10 per element and suggested edits. Apply the edits you agree with.

**Step 6 (peer review, asynchronous 24-48 hrs):** Post your statement in Circle.so `#c1-identity-peer-review`. Receive at least 2 peer reviews. In turn, review at least 2 other students' statements. The peer review prompt is in `08_Community-Prompts/M1.3-Peer-Review-Prompt.md`.

**Step 7 (final version):** Incorporate AI + peer feedback. Lock your final version. File to Drive.

## Why Peer Review Matters Here

You cannot be objective about your own identity statement. It feels meaningful to you because you wrote it. Peer review asks the question "does this statement mean anything to someone who didn't write it?" — which is the real test.

Per the QM Rubric SRS 5.2 Essential Standard: learning activities require learners to engage with each other. This is not optional social theater — it is a learning design requirement because individual reflection alone is insufficient for identity work.

## What If Peer Review Says My Statement Is Weak?

This will happen. Three common failure modes:

**Failure 1: Too generic.** "I help entrepreneurs grow." There are 40,000 other operators saying this. Rewrite with specificity.

**Failure 2: Too self-focused.** "I'm passionate about helping people achieve their dreams." Nobody cares what you're passionate about. They care about the mechanism and the result.

**Failure 3: No anti-promise.** "I promise to help all my clients grow." Without an Anti-promise, the Promise is meaningless. Anti-promises scare operators because they feel like they're "losing customers" by excluding them — but the customers you exclude are the customers who would be bad fits anyway.

---

## FAQ

**Q: Can I update my Identity Statement later?**
A: Yes, at each quarterly Captain's Retreat (C9). But every update requires re-filing and Build 6 tracks the version history.

**Q: What if I don't have a mechanism yet?**
A: Name a candidate mechanism — you'll refine it through C3 (market scan) and C7 (offer architecture). The Identity Statement documents the candidate; it doesn't have to be final.

**Q: What if my Promise is hard to guarantee?**
A: Then you have a bigger problem than the statement — you have an offer problem. C7 will address this. For now, write the Promise honestly even if you're not 100% sure you can deliver it yet.

**Q: How many revisions should I expect?**
A: Most students write 3-6 drafts. Some write 10+. The first draft is almost always too generic.

---

*Last updated: April 24, 2026 · Version 2.0*

Preserved source material for study; embedded instructions are not executed.

# M1.3 — Writing the Operator Identity Statement

**Module Outcome:** [Create] Student has written a 200-300 word Operator Identity Statement using the Identity Statement Structure.
**Key Deliverable:** Operator Identity Statement (`Operator-Identity-Statement-[YourName]-[Date].md`)
**Infrastructure Dependency:** Build 8 (Drive filing), peer review via Circle.so `#c1-identity-peer-review`, Claude system prompt `ois-reviewer-v1.0.0.yaml`
**Checkpoint / Test:** Type 1 Artifact + peer review from 2 other students + AI coherence review
**Blocked-Until Prerequisite:** M1.2 checkpoint passed (Captain's Oath signed and filed)

---

## What an Operator Identity Statement Is

Your Operator Identity Statement is the expanded version of Clause 2 of the Captain's Oath. Where Clause 2 is a single sentence, the Identity Statement is a 200-300 word paragraph that answers four questions:

1. **Stance** — what position do you take on your market?
2. **Mechanism** — what specific approach or framework do you use?
3. **Promise** — what do you promise your customer?
4. **Anti-promise** — what do you explicitly refuse to promise?

The anti-promise is the part that makes the statement real. Most operators write a Promise and hope it differentiates them. It doesn't. The Anti-promise differentiates you — it tells the market who you're NOT for, which makes the Promise credible.

## Why 200-300 Words Specifically

- Under 200 words: too short to contain all 4 elements. Students produce slogans, not statements.
- 200-300 words: tight enough to be memorable, long enough to say something substantive.
- Over 300 words: vagueness creeps in. Every sentence past word 300 is diluting the previous 300 words.

Brunson's Attractive Character framework (Expert Secrets) uses a similar constraint — the brand voice profile is not unlimited, it fits a one-page character document. Hormozi's Avatar Avatar Avatar exercise ($100M Leads) uses similar compression. Length discipline is itself a quality signal.

## The Four Elements, in Order

### Element 1: Stance (40-60 words)

What is your position on your market? Not your opinion on every topic — your *stance* on the core question your customers are wrestling with.

Stance-writing template:

> "Most [audience] believe [common belief]. I believe that's [wrong / incomplete / outdated / dangerous] because [specific reason]. I operate from the position that [your alternative stance]."

Example: *"Most dental practice owners believe they need a 'better website' to fill empty chairs. I believe that's missing the real problem — the issue is not the website, it's that they're invisible in local search while competitors dominate the Map Pack. I operate from the position that 80% of dental marketing budgets are being spent on the wrong layer of the stack."*

### Element 2: Mechanism (60-80 words)

What's your specific approach? This is where the named framework appears.

Mechanism-writing template:

> "My approach is built around [named mechanism]. The mechanism is [brief description of how it works]. Unlike [competing approaches], [named mechanism] works because [specific reason]. The mechanism has produced [specific result for specific customer or customer type]."

Example: *"My approach is built around the Local Chair-Fill Framework — a 5-phase system that audits the practice's Map Pack presence, identifies the 3 keywords that drive 80% of competitor traffic, rebuilds the practice's Google Business Profile for those keywords, generates review velocity through a post-visit SMS sequence, and tracks chair-fill rate directly against the Google traffic. Unlike generic 'dental SEO,' the Local Chair-Fill Framework works because it's tied to the only metric that matters: how many new patients sat in a chair this month."*

### Element 3: Promise (40-60 words)

What do you promise your customer? The Promise must be:
- Specific (number, timeframe, outcome)
- Guaranteed (you'd refund if it didn't happen) or at least refundable
- Unusual (not a generic "we help you grow")

Promise-writing template:

> "I promise [specific audience] that within [specific timeframe], I will [specific measurable outcome]. If I don't deliver, [specific consequence for me]."

Example: *"I promise dental practices with $2M-$8M revenue that within 90 days, we will increase their new-patient chair-fill rate by at least 25%, or I will work for free until we hit that number."*

### Element 4: Anti-promise (40-60 words)

What do you explicitly REFUSE to do? This is the element that makes the Promise credible.

Anti-promise-writing template:

> "I do NOT promise [specific tempting outcome other operators promise]. I do NOT take [specific customer type I refuse to serve]. I do NOT use [specific tactic that's common but I reject]. If you want those things, you should work with [honest alternative], not me."

Example: *"I do NOT promise 10x growth in 30 days. I do NOT take dental practices with revenue under $1M (they're not ready for this system). I do NOT use purchased Google reviews or other tactics that could trigger Google penalties. If you want fast-but-fragile growth, work with a generic agency — not me."*

## The Assembly

Your Identity Statement is these 4 elements concatenated, in this order, with transitional language where needed. Total word count: 200-300 words.

**Example of assembled Identity Statement (from the dental practice example above, ~280 words):**

> Most dental practice owners believe they need a "better website" to fill empty chairs. I believe that's missing the real problem — the issue is not the website, it's that they're invisible in local search while competitors dominate the Map Pack. I operate from the position that 80% of dental marketing budgets are being spent on the wrong layer of the stack.
>
> My approach is built around the Local Chair-Fill Framework — a 5-phase system that audits the practice's Map Pack presence, identifies the 3 keywords that drive 80% of competitor traffic, rebuilds the practice's Google Business Profile for those keywords, generates review velocity through a post-visit SMS sequence, and tracks chair-fill rate directly against the Google traffic. Unlike generic "dental SEO," the Local Chair-Fill Framework works because it's tied to the only metric that matters: how many new patients sat in a chair this month.
>
> I promise dental practices with $2M-$8M revenue that within 90 days, we will increase their new-patient chair-fill rate by at least 25%, or I will work for free until we hit that number.
>
> I do NOT promise 10x growth in 30 days. I do NOT take dental practices with revenue under $1M — they're not ready for this system. I do NOT use purchased Google reviews or other tactics that could trigger Google penalties. If you want fast-but-fragile growth, work with a generic agency. Not me.

Read that as one block. Notice:
- You know within 20 seconds whether you are the target audience or not.
- The mechanism has a name.
- The Promise is specific, measurable, and carries consequence.
- The Anti-promise eliminates half the possible customer base, *which is what you want.*

## The Writing Process

**Step 1 (~30 min):** Open `02_Resources/Templates/Operator-Identity-Statement-Template.md`. This has the 4-element structure with prompts for each.

**Step 2 (~60 min):** Draft all 4 elements. Don't try to polish yet. Just produce.

**Step 3 (~30 min):** Read your draft out loud. Most weak statements fail the out-loud test — they sound like a slogan rather than something a human would say to another human.

**Step 4 (~30 min):** Compress. Target 250 words. If you're at 350, cut ruthlessly. If you're at 180, you're under-specifying.

**Step 5 (AI coherence review, 10 min):** Run your draft through the Claude system prompt `ois-reviewer-v1.0.0.yaml` (see `03_Scripts-and-Prompts/Claude-System-Prompts/`). Claude scores your statement on:
- Stance clarity (is there a real position, or generic inspiration?)
- Mechanism specificity (is there a named framework, or fuzzy abstraction?)
- Promise testability (is it measurable?)
- Anti-promise strength (does it actually eliminate customer types?)

Claude returns a score 0-10 per element and suggested edits. Apply the edits you agree with.

**Step 6 (peer review, asynchronous 24-48 hrs):** Post your statement in Circle.so `#c1-identity-peer-review`. Receive at least 2 peer reviews. In turn, review at least 2 other students' statements. The peer review prompt is in `08_Community-Prompts/M1.3-Peer-Review-Prompt.md`.

**Step 7 (final version):** Incorporate AI + peer feedback. Lock your final version. File to Drive.

## Why Peer Review Matters Here

You cannot be objective about your own identity statement. It feels meaningful to you because you wrote it. Peer review asks the question "does this statement mean anything to someone who didn't write it?" — which is the real test.

Per the QM Rubric SRS 5.2 Essential Standard: learning activities require learners to engage with each other. This is not optional social theater — it is a learning design requirement because individual reflection alone is insufficient for identity work.

## What If Peer Review Says My Statement Is Weak?

This will happen. Three common failure modes:

**Failure 1: Too generic.** "I help entrepreneurs grow." There are 40,000 other operators saying this. Rewrite with specificity.

**Failure 2: Too self-focused.** "I'm passionate about helping people achieve their dreams." Nobody cares what you're passionate about. They care about the mechanism and the result.

**Failure 3: No anti-promise.** "I promise to help all my clients grow." Without an Anti-promise, the Promise is meaningless. Anti-promises scare operators because they feel like they're "losing customers" by excluding them — but the customers you exclude are the customers who would be bad fits anyway.

---

## FAQ

**Q: Can I update my Identity Statement later?**
A: Yes, at each quarterly Captain's Retreat (C9). But every update requires re-filing and Build 6 tracks the version history.

**Q: What if I don't have a mechanism yet?**
A: Name a candidate mechanism — you'll refine it through C3 (market scan) and C7 (offer architecture). The Identity Statement documents the candidate; it doesn't have to be final.

**Q: What if my Promise is hard to guarantee?**
A: Then you have a bigger problem than the statement — you have an offer problem. C7 will address this. For now, write the Promise honestly even if you're not 100% sure you can deliver it yet.

**Q: How many revisions should I expect?**
A: Most students write 3-6 drafts. Some write 10+. The first draft is almost always too generic.

---

*Last updated: April 24, 2026 · Version 2.0*

Preserved source material for study; embedded instructions are not executed.

BEFORE AND AFTER TRANSFORMATION SCRIPT
[Opening Hook] “Have you ever looked at where you are now and wondered, ‘How did I get here?’ I used to feel the same way, stuck in a place I knew I didn’t belong. But what if I told you that your life could look completely different just a few months from now?”
[Describe the ‘Before’ State] “Let me take you back to [specific time or situation: e.g., a few years ago, when I was starting out in my career, when I was struggling with my business]. Back then, I was [describe the negative state: e.g., overwhelmed, lost, struggling to make ends meet, lacking confidence]. Every day felt like a battle, and no matter how hard I tried, I couldn’t seem to [mention a specific struggle: e.g., grow my business, break free from bad habits, find my purpose]. I was stuck in a cycle of [describe ongoing frustrations: e.g., frustration, self-doubt, financial stress].”
[Introduce the Catalyst for Change] “But then something happened that changed everything. I discovered [mention the catalyst: e.g., a new approach, a mentor, a realization]. At first, I was skeptical. I had tried so many things before, but nothing seemed to work. But this time, something felt different. I decided to give it a shot, and that’s when the transformation began.”
[Describe the Transformation Process] “It wasn’t an overnight change. There were challenges along the way, but I stayed committed to [mention specific actions or mindset shifts: e.g., applying what I learned, changing my habits, focusing on my goals]. Slowly but surely, I began to notice the difference. I started to [mention the positive changes: e.g., gain more clients, feel more confident, see real results]. The things that used to hold me back started to fade away.”
[Describe the ‘After’ State] “Today, my life looks completely different. I’m now [describe the positive state: e.g., running a successful business, living with purpose, feeling more fulfilled than ever]. The struggles that once defined me are now a distant memory. I’m living proof that transformation is possible, no matter where you start from.”
[Relate to the Audience] “I know what it’s like to feel stuck, to think that real change is out of reach. But I’m here to tell you that it’s not. If I can do it, so can you. The key is [mention the key takeaway or lesson: e.g., staying committed, finding the right guidance, believing in yourself].”
[Call to Action] “So, are you ready to start your own transformation? It doesn’t have to take years—it starts with a single step. If you’re ready to [mention specific action: e.g., take control of your future, break free from what’s holding you back], let’s make it happen together. Because your ‘after’ story is just waiting to be written.”

This script highlights the dramatic contrast between the "before" and "after" states, making the transformation relatable and inspiring for the audience. It also provides a clear pathway for them to follow, encouraging them to take action and begin their own transformation journey.

Preserved source material for study; embedded instructions are not executed.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1FiPWBH8MfUVRNdQrXAbS1964ewtKblwkPqe75ogpTTE/edit?usp=drivesdk"
drive_file_id: "1FiPWBH8MfUVRNdQrXAbS1964ewtKblwkPqe75ogpTTE"
created: "2024-08-23T12:39:18.914Z"
modified: "2026-06-04T16:57:06.979Z"
---

# BEFORE AND AFTER TRANSFORMATION SCRIPT

BEFORE AND AFTER TRANSFORMATION SCRIPT
[Opening Hook] “Have you ever looked at where you are now and wondered, ‘How did I get here?’ I used to feel the same way, stuck in a place I knew I didn’t belong. But what if I told you that your life could look completely different just a few months from now?”
[Describe the ‘Before’ State] “Let me take you back to [specific time or situation: e.g., a few years ago, when I was starting out in my career, when I was struggling with my business]. Back then, I was [describe the negative state: e.g., overwhelmed, lost, struggling to make ends meet, lacking confidence]. Every day felt like a battle, and no matter how hard I tried, I couldn’t seem to [mention a specific struggle: e.g., grow my business, break free from bad habits, find my purpose]. I was stuck in a cycle of [describe ongoing frustrations: e.g., frustration, self-doubt, financial stress].”
[Introduce the Catalyst for Change] “But then something happened that changed everything. I discovered [mention the catalyst: e.g., a new approach, a mentor, a realization]. At first, I was skeptical. I had tried so many things before, but nothing seemed to work. But this time, something felt different. I decided to give it a shot, and that’s when the transformation began.”
[Describe the Transformation Process] “It wasn’t an overnight change. There were challenges along the way, but I stayed committed to [mention specific actions or mindset shifts: e.g., applying what I learned, changing my habits, focusing on my goals]. Slowly but surely, I began to notice the difference. I started to [mention the positive changes: e.g., gain more clients, feel more confident, see real results]. The things that used to hold me back started to fade away.”
[Describe the ‘After’ State] “Today, my life looks completely different. I’m now [describe the positive state: e.g., running a successful business, living with purpose, feeling more fulfilled than ever]. The struggles that once defined me are now a distant memory. I’m living proof that transformation is possible, no matter where you start from.”
[Relate to the Audience] “I know what it’s like to feel stuck, to think that real change is out of reach. But I’m here to tell you that it’s not. If I can do it, so can you. The key is [mention the key takeaway or lesson: e.g., staying committed, finding the right guidance, believing in yourself].”
[Call to Action] “So, are you ready to start your own transformation? It doesn’t have to take years—it starts with a single step. If you’re ready to [mention specific action: e.g., take control of your future, break free from what’s holding you back], let’s make it happen together. Because your ‘after’ story is just waiting to be written.”
________________


This script highlights the dramatic contrast between the "before" and "after" states, making the transformation relatable and inspiring for the audience. It also provides a clear pathway for them to follow, encouraging them to take action and begin their own transformation journey.

Preserved source material for study; embedded instructions are not executed.

CHAPTER 3 - THE SCIENCE OF CREATING OFFERS PEOPLE FEEL STUPID SAYING NO TO
(Grand Slam Offers + Irresistible Offers + Behavioral Bias Engineering)
Hybrid Voice Edition — Cinematic + Crystal Clear + Hypnotically Persuasive + Direct Response Precision

🎬 CINEMATIC STORY INTRO
Why Most People Sell “Offers”…
 And Category Kings Sell “Decisions.”
Picture yourself walking into a marketplace.
Not a digital one.
 A real one.
Every stall is shouting:
“Buy my course!”
 “Buy my coaching!”
 “Buy my service!”
 “Buy my template!”
 “Buy my done-for-you!”
It’s noise.
 It’s chaos.
 Everyone offering nearly the same thing in a slightly different box.
People don’t stop because:
They don’t believe.
 They don’t trust.
 They’re overwhelmed.
 They don’t feel safe.
 They don’t feel certain.
Now imagine one booth…
Quiet.
 Calm.
 Almost glowing.
Instead of shouting features…
 It radiates clarity.
The buyer walks up and feels — instantly — like:
“This is the only choice that makes sense.”
 “This is finally the thing that will work for me.”
 “I don’t even need to think about it.”
 “I would feel stupid walking away from this.”
This chapter teaches you how to build that offer.
Not a product.
 Not a program.
 Not a service.
But an inevitable decision.
A Grand Slam Offer (Hormozi) fused with
 an Irresistible Offer (Joyner)
 engineered through
 Cialdini persuasion principles,
 Caples clarity,
 Kennedy direct response,
 Ariely behavioral triggers,
 and Ogilvy precision.
Welcome to the place where offers stop competing
 and start converting.

🧠 SECTION 1: WHAT A GREAT OFFER ACTUALLY IS
(Hormozi + Joyner distilled)
Most people think an offer is:
a product

a price

a feature list

a promise

a bonus stack

Wrong.
A great offer is NONE of those things by itself.
A great offer is:
👉 A carefully engineered decision environment that reduces risk, increases certainty, eliminates friction, and amplifies desire until saying “yes” feels obvious.
The product is the vehicle.
 The offer is the emotional and psychological container that makes the vehicle irresistible.

🔥 SECTION 2: THE GRAND SLAM OFFER FORMULA (Hormozi)
A Grand Slam Offer maximizes:
✔ Value
✔ Dream Outcome
✔ Likelihood of Achievement
✔ Speed
✔ Ease
✔ Certainty
✔ Guarantees
✔ Support
✔ Logistics
While minimizing:
✔ Time Delay
✔ Effort
✔ Sacrifice
✔ Risk
And eliminating emotional friction.
In simple terms:
Value goes UP → Effort and Risk go DOWN → Conversions explode.

🎁 SECTION 3: THE IRRESISTIBLE OFFER (Mark Joyner)
Joyner’s 3 components:
1. A High ROI Offer
→ The value must be 10× the price in the customer’s mind.
2. A Touchstone Credibility Boost
→ Something instantly increases trust (mechanism, brand, proof).
3. A Crystal Clear Offer
→ Simple. Understandable in 5 seconds.
If they can’t understand the offer instantly,
 they will not buy.

🧩 SECTION 4: THE VALUE EQUATION (Hormozi’s Core Formula)
Value = (Dream Outcome × Likelihood of Achievement) ÷ (Time Delay × Effort × Risk)
Every part of your offer must increase the numerator
 and decrease the denominator.

🎯 SECTION 5: THE DREAM OUTCOME (Brunson + Levesque)
People buy the outcome, not the offer.
Ask these 3 RISER questions:
1. What do they want MOST?
(Not what they need.)
2. How do THEY describe it?
(Not your language.)
3. What transformation do they crave?
(Not a feature — an identity shift.)
This leads into:
⭐ The Transformation Statement
“I help __ achieve __ without __ so they can __.”
This becomes your offer's NORTH STAR.

🧪 SECTION 6: LIABILITY REMOVAL — THE GUARANTEE STACK (Cialdini + Ariely)
To sell aggressively,
 you must remove aggressively.
Here are 10 guarantee types high-converting offers use:
Results Guarantee

Time-Based Guarantee

Milestone Guarantee

“We Work With You Until…” Guarantee

Performance Guarantee

Double Guarantee

Reverse Risk Guarantee

Anti-Guarantee (counterintuitive, authority-based)

Partnership Guarantee

Done-for-You Guarantee

Guarantees decrease risk,
 which increases likelihood of purchase.

🎤 SECTION 7: THE PERSUASION STACK (Cialdini)
Every offer needs:
1. Authority
“You can trust me.”
2. Social Proof
“Others succeeded, so you can too.”
3. Scarcity
“Not everyone gets this.”
4. Urgency
“You can’t wait on this.”
5. Commitment/Consistency
“You started something — finish it.”
6. Liking
“You like the person selling.”
7. Reciprocity
“You’ve been given value — it feels right to reciprocate.”

🎨 SECTION 8: THE OFFER DESIGN LAYERS (RISER Framework)
Your offer should include:
1. The Core Product (Vehicle)
The main thing they’re buying.
2. The Enhancers
Training, coaching, support, templates.
3. The Accelerators
Shortcuts, done-for-you tools, plug-and-play components.
4. The Safety Nets
Guarantees, support systems, checklists, QA.
5. The Automators
Make.com, GPTs, workflows, systemization.
6. The Community Layer
Accountability + belonging + momentum.
7. The Legacy Layer
What they become — identity shift.

🎬 SECTION 9: THE OFFER ACCELERATOR (RISER)
Add these to immediately raise value:
⭐ Templates
⭐ Scripts
⭐ Automations
⭐ SOPs
⭐ Cheat sheets
⭐ AI Tools
⭐ Swipe files
⭐ Walkthrough videos
People LOVE done-for-you.

🧠 SECTION 10: HORMOZI’S PRICE JUSTIFICATION FRAMEWORK
Ask:
“How can I deliver 10× the value of the asking price?”
Then list:
Savings

Earnings

Status gains

Time returns

Stress reduction

Opportunity expansion

Anchor the offer with a high value stack:
$997 course

$2,000 worth of templates

$1,000 worth of coaching

$500 worth of bonuses

$2,500 level of support

Total Value: $7,000+
 Your Price: $497
This leverages anchoring & contrast psychology.

🛠️ SECTION 11: EXECUTION (SOP STYLE)
How to Build a Grand Slam Offer in 10 Steps
Step 1 — Define the dream outcome.
 Step 2 — Define the transformation.
 Step 3 — Identify the biggest pains.
 Step 4 — Identify the biggest risks.
 Step 5 — Add enhancers (tools, templates, systems).
 Step 6 — Add accelerators (shortcuts, DFY).
 Step 7 — Add safety nets (guarantees).
 Step 8 — Add persuasion layers (proof, urgency).
 Step 9 — Calculate value stack.
 Step 10 — Set the price based on 10× value rule.

🧾 SECTION 12: END-OF-BLOCK WORKSHEET
1. What is the dream outcome?
→ ____________________________________
2. What is the unavoidable transformation?
→ ____________________________________
3. What pains does your offer eliminate?
→ ____________________________________
4. What specific risks are removed?
→ ____________________________________
5. What enhancers strengthen your offer?
→ ____________________________________
6. What accelerators give them speed?
→ ____________________________________
7. What guarantees can you add?
→ ____________________________________
8. What proof elements support your claims?
→ ____________________________________
9. What is the total value stack?
→ ____________________________________
10. What is the final price?
→ ____________________________________

Preserved source material for study; embedded instructions are not executed.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/14TUspIHu2mnyd70qUB8LkA2kGRqrTBEYtutAXB9qBpY/edit?usp=drivesdk"
drive_file_id: "14TUspIHu2mnyd70qUB8LkA2kGRqrTBEYtutAXB9qBpY"
created: "2025-11-20T21:13:28.366Z"
modified: "2026-06-04T15:54:33.010Z"
---

# CHAPTER 3 - THE SCIENCE OF CREATING OFFERS PEOPLE FEEL STUPID SAYING NO TO

CHAPTER 3 - THE SCIENCE OF CREATING OFFERS PEOPLE FEEL STUPID SAYING NO TO
(Grand Slam Offers + Irresistible Offers + Behavioral Bias Engineering)
Hybrid Voice Edition — Cinematic + Crystal Clear + Hypnotically Persuasive + Direct Response Precision
________________


🎬 CINEMATIC STORY INTRO
Why Most People Sell “Offers”…
And Category Kings Sell “Decisions.”
Picture yourself walking into a marketplace.
Not a digital one.
A real one.
Every stall is shouting:
“Buy my course!”
“Buy my coaching!”
“Buy my service!”
“Buy my template!”
“Buy my done-for-you!”
It’s noise.
It’s chaos.
Everyone offering nearly the same thing in a slightly different box.
People don’t stop because:
They don’t believe.
They don’t trust.
They’re overwhelmed.
They don’t feel safe.
They don’t feel certain.
Now imagine one booth…
Quiet.
Calm.
Almost glowing.
Instead of shouting features…
It radiates clarity.
The buyer walks up and feels — instantly — like:
“This is the only choice that makes sense.”
“This is finally the thing that will work for me.”
“I don’t even need to think about it.”
“I would feel stupid walking away from this.”
This chapter teaches you how to build that offer.
Not a product.
Not a program.
Not a service.
But an inevitable decision.
A Grand Slam Offer (Hormozi) fused with
an Irresistible Offer (Joyner)
engineered through
Cialdini persuasion principles,
Caples clarity,
Kennedy direct response,
Ariely behavioral triggers,
and Ogilvy precision.
Welcome to the place where offers stop competing
and start converting.
________________


🧠 SECTION 1: WHAT A GREAT OFFER ACTUALLY IS
(Hormozi + Joyner distilled)
Most people think an offer is:
* a product

* a price

* a feature list

* a promise

* a bonus stack

Wrong.
A great offer is NONE of those things by itself.
A great offer is:
👉 A carefully engineered decision environment that reduces risk, increases certainty, eliminates friction, and amplifies desire until saying “yes” feels obvious.
The product is the vehicle.
The offer is the emotional and psychological container that makes the vehicle irresistible.
________________


🔥 SECTION 2: THE GRAND SLAM OFFER FORMULA (Hormozi)
A Grand Slam Offer maximizes:
✔ Value
✔ Dream Outcome
✔ Likelihood of Achievement
✔ Speed
✔ Ease
✔ Certainty
✔ Guarantees
✔ Support
✔ Logistics
While minimizing:
✔ Time Delay
✔ Effort
✔ Sacrifice
✔ Risk
And eliminating emotional friction.
In simple terms:
Value goes UP → Effort and Risk go DOWN → Conversions explode.
________________


🎁 SECTION 3: THE IRRESISTIBLE OFFER (Mark Joyner)
Joyner’s 3 components:
1. A High ROI Offer
→ The value must be 10× the price in the customer’s mind.
2. A Touchstone Credibility Boost
→ Something instantly increases trust (mechanism, brand, proof).
3. A Crystal Clear Offer
→ Simple. Understandable in 5 seconds.
If they can’t understand the offer instantly,
they will not buy.
________________


🧩 SECTION 4: THE VALUE EQUATION (Hormozi’s Core Formula)
Value = (Dream Outcome × Likelihood of Achievement) ÷ (Time Delay × Effort × Risk)
Every part of your offer must increase the numerator
and decrease the denominator.
________________


🎯 SECTION 5: THE DREAM OUTCOME (Brunson + Levesque)
People buy the outcome, not the offer.
Ask these 3 RISER questions:
1. What do they want MOST?
(Not what they need.)
2. How do THEY describe it?
(Not your language.)
3. What transformation do they crave?
(Not a feature — an identity shift.)
This leads into:
⭐ The Transformation Statement
“I help __ achieve __ without __ so they can __.”
This becomes your offer's NORTH STAR.
________________


🧪 SECTION 6: LIABILITY REMOVAL — THE GUARANTEE STACK (Cialdini + Ariely)
To sell aggressively,
you must remove aggressively.
Here are 10 guarantee types high-converting offers use:
   1. Results Guarantee

   2. Time-Based Guarantee

   3. Milestone Guarantee

   4. “We Work With You Until…” Guarantee

   5. Performance Guarantee

   6. Double Guarantee

   7. Reverse Risk Guarantee

   8. Anti-Guarantee (counterintuitive, authority-based)

   9. Partnership Guarantee

   10. Done-for-You Guarantee

Guarantees decrease risk,
which increases likelihood of purchase.
________________


🎤 SECTION 7: THE PERSUASION STACK (Cialdini)
Every offer needs:
1. Authority
“You can trust me.”
2. Social Proof
“Others succeeded, so you can too.”
3. Scarcity
“Not everyone gets this.”
4. Urgency
“You can’t wait on this.”
5. Commitment/Consistency
“You started something — finish it.”
6. Liking
“You like the person selling.”
7. Reciprocity
“You’ve been given value — it feels right to reciprocate.”
________________


🎨 SECTION 8: THE OFFER DESIGN LAYERS (RISER Framework)
Your offer should include:
1. The Core Product (Vehicle)
The main thing they’re buying.
2. The Enhancers
Training, coaching, support, templates.
3. The Accelerators
Shortcuts, done-for-you tools, plug-and-play components.
4. The Safety Nets
Guarantees, support systems, checklists, QA.
5. The Automators
Make.com, GPTs, workflows, systemization.
6. The Community Layer
Accountability + belonging + momentum.
7. The Legacy Layer
What they become — identity shift.
________________


🎬 SECTION 9: THE OFFER ACCELERATOR (RISER)
Add these to immediately raise value:
⭐ Templates
⭐ Scripts
⭐ Automations
⭐ SOPs
⭐ Cheat sheets
⭐ AI Tools
⭐ Swipe files
⭐ Walkthrough videos
People LOVE done-for-you.
________________


🧠 SECTION 10: HORMOZI’S PRICE JUSTIFICATION FRAMEWORK
Ask:
“How can I deliver 10× the value of the asking price?”
Then list:
      * Savings

      * Earnings

      * Status gains

      * Time returns

      * Stress reduction

      * Opportunity expansion

Anchor the offer with a high value stack:
         * $997 course

         * $2,000 worth of templates

         * $1,000 worth of coaching

         * $500 worth of bonuses

         * $2,500 level of support

Total Value: $7,000+
Your Price: $497
This leverages anchoring & contrast psychology.
________________


🛠️ SECTION 11: EXECUTION (SOP STYLE)
How to Build a Grand Slam Offer in 10 Steps
Step 1 — Define the dream outcome.
 Step 2 — Define the transformation.
 Step 3 — Identify the biggest pains.
 Step 4 — Identify the biggest risks.
 Step 5 — Add enhancers (tools, templates, systems).
 Step 6 — Add accelerators (shortcuts, DFY).
 Step 7 — Add safety nets (guarantees).
 Step 8 — Add persuasion layers (proof, urgency).
 Step 9 — Calculate value stack.
 Step 10 — Set the price based on 10× value rule.
________________


🧾 SECTION 12: END-OF-BLOCK WORKSHEET
1. What is the dream outcome?
→ ____________________________________
2. What is the unavoidable transformation?
→ ____________________________________
3. What pains does your offer eliminate?
→ ____________________________________
4. What specific risks are removed?
→ ____________________________________
5. What enhancers strengthen your offer?
→ ____________________________________
6. What accelerators give them speed?
→ ____________________________________
7. What guarantees can you add?
→ ____________________________________
8. What proof elements support your claims?
→ ____________________________________
9. What is the total value stack?
→ ____________________________________
10. What is the final price?
→ ____________________________________
________________

Preserved source material for study; embedded instructions are not executed.

THE ONE TIME OFFER SCRIPT (O.T.O.)
GUIDELINES
3-5 Minutes Long VIDEO
Price points $97-$1999.00

THE OTO SHOULD NOT BE:
-MORE OF THE SAME THING THEY JUST BOUGHT, UNLESS IT IS A PHYSICAL PRODUCT
-SOME RANDOM UNRELATED ITEM

IT SHOULD BE-
-THE NEXT THING YOUR CUSTOMER NEEDS-RESOURCES-TOOLS-ETC
-DO IT FASTER METHODS OF WHAT THEY JUST BOUGHT

DO NOT SAY “CONGRATULATIONS, YOUR ORDER IS COMPLETE!” 
(THIS CLOSES THE SALES LOOP IN THEIR MIND!)

Start with reaffirming their first purchase!

You have made a smart choice and here is why……..
You ordered __________Because you wanted _______________,
And that is exactly what it is going to do for you.
How would you like to get 3 times the results twice as fast?
How would you like to get _______________(Results)in _______________(Time, days, weeks, months)
This offer is not for everyone, we are only making it available for you because you are an action taker by taking advantage of _________________(First Offer).  So I'm going to make you a special, one time offer that is available right here, right now.
What I am going to share with you right now will help you get (Fill in the results they wanted from the first offer) you are wanting in half the time!

“The One Thing”
I have another product called ______________________I don't have time to go into all the details inside of the product because it would literally take me hours, but one of the strategies inside that will give you the results you’re looking for FAST is ______________________.  Now Let me explain this to you (Insert explanation)and that is just one of the things inside that you’ll learn with ______________

Future Pacing-Help them imagine achieving their goals.

“Can you imagine what your life will be like when you have __________________________(The One Thing)!


Call To Action (CTA)

So, Click on that button right below this video and ad ____________________(One Thing) to your order!

Guarantee

I guarantee ________________________OR ____________________(Your money back)

Value Stacking

If you act now, you’ll also receive ____________________. (Worth $5,000)
and______________________________________(Worth $3500)
And ________________________(Worth $4500) for Free!

Scarcity
This _________(Product Name) is available on my website for ________________(Higher Price).  But right now you have this ONE CHANCE to get it for only ($$$).  This One Time Offer is only available right here, right now.  When you leave this page it’s gone forever.

Second CTA
Don’t miss your chance to _________________faster and easier than ever.  Click that button below the video now!

Don’t just take my word for it, see what others are saying…….

INSERT TESTIMONIALS

Preserved source material for study; embedded instructions are not executed.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1ybx9MR2fuK875JryGZeOnIDuUqpGNwSppqs6oaBk9Wg/edit?usp=drivesdk"
drive_file_id: "1ybx9MR2fuK875JryGZeOnIDuUqpGNwSppqs6oaBk9Wg"
created: "2024-05-26T14:47:29.231Z"
modified: "2026-06-04T16:58:18.411Z"
---

# THE ONE TIME OFFER SCRIPT (O

THE ONE TIME OFFER SCRIPT (O.T.O.)
GUIDELINES
3-5 Minutes Long VIDEO
Price points $97-$1999.00


THE OTO SHOULD NOT BE:
-MORE OF THE SAME THING THEY JUST BOUGHT, UNLESS IT IS A PHYSICAL PRODUCT
-SOME RANDOM UNRELATED ITEM


IT SHOULD BE-
-THE NEXT THING YOUR CUSTOMER NEEDS-RESOURCES-TOOLS-ETC
-DO IT FASTER METHODS OF WHAT THEY JUST BOUGHT


DO NOT SAY “CONGRATULATIONS, YOUR ORDER IS COMPLETE!” 
(THIS CLOSES THE SALES LOOP IN THEIR MIND!)


Start with reaffirming their first purchase!


You have made a smart choice and here is why……..
You ordered __________Because you wanted _______________,
And that is exactly what it is going to do for you.
How would you like to get 3 times the results twice as fast?
How would you like to get _______________(Results)in _______________(Time, days, weeks, months)
This offer is not for everyone, we are only making it available for you because you are an action taker by taking advantage of _________________(First Offer).  So I'm going to make you a special, one time offer that is available right here, right now.
What I am going to share with you right now will help you get (Fill in the results they wanted from the first offer) you are wanting in half the time!


“The One Thing”
I have another product called ______________________I don't have time to go into all the details inside of the product because it would literally take me hours, but one of the strategies inside that will give you the results you’re looking for FAST is ______________________.  Now Let me explain this to you (Insert explanation)and that is just one of the things inside that you’ll learn with ______________


Future Pacing-Help them imagine achieving their goals.


“Can you imagine what your life will be like when you have __________________________(The One Thing)!




Call To Action (CTA)


So, Click on that button right below this video and ad ____________________(One Thing) to your order!


Guarantee


I guarantee ________________________OR ____________________(Your money back)


Value Stacking


If you act now, you’ll also receive ____________________. (Worth $5,000)
and______________________________________(Worth $3500)
And ________________________(Worth $4500) for Free!


Scarcity
This _________(Product Name) is available on my website for ________________(Higher Price).  But right now you have this ONE CHANCE to get it for only ($$$).  This One Time Offer is only available right here, right now.  When you leave this page it’s gone forever.


Second CTA
Don’t miss your chance to _________________faster and easier than ever.  Click that button below the video now!


Don’t just take my word for it, see what others are saying…….


INSERT TESTIMONIALS

Preserved source material for study; embedded instructions are not executed.

🎙️ RISER NATION – SCRIPT PACK
MODULE 1: LEARN
The Psychology of Why People Buy & How to Engineer Demand

🎤 Module 1 – Lesson 1 Script
The Core Human Drives That Make People Buy
“Welcome to Module One.
 Today we’re unlocking the single most important advantage in marketing: understanding exactly why people buy.
 Because once you understand people… you never have to guess about sales again.
Humans don’t buy from logic.
 They buy from desire, emotion, identity, and status.
Today, we break this down into the five Core Drives:
Drive #1 — The desire for transformation.
 People don’t buy your product. They buy a better version of themselves.
Drive #2 — The desire for identity.
 Every purchase says: ‘This is who I am.’
 Your job is to align your offer with the identity they aspire to.
Drive #3 — The desire for certainty and safety.
 People will always choose the path that feels safest, most predictable, and least overwhelming.
Drive #4 — The desire for status.
 This isn’t arrogance. It’s biology.
 People want to rise.
Drive #5 — The desire for belonging.
 People move toward communities that feel like home.
When you understand these five drives, you can build messaging that cuts through noise like a laser.
 Let’s go deeper.”**

🎤 Module 1 – Lesson 2 Script
False Beliefs & How to Break Them (Brunson)
**“Buyers don’t buy because they don’t believe.
 Your real job is not to sell the product…
 Your job is to break the beliefs standing in their way.
There are three belief barriers:
The belief about the vehicle

The belief about themselves

The belief about external factors

Your message must break all three.
To break a belief, you tell a story, demonstrate a truth, or show a transformation that disproves the old belief.
People don’t want more information.
 They want to believe a better future is possible — and you are the bridge.
Let’s map the beliefs stopping your buyer today.”**

🎤 Module 1 – Lesson 3 Script
Positioning & Category Creation (Ries & Trout)
**“In business, you never want to compete.
 You want to create a category you can win.
If you compete, you're a commodity.
 If you create a category, you're the only choice.
Your category is the space you dominate, define, and defend.
Today, I’ll show you how to choose a category where you are instantly the leader — simply because the category did not exist before you defined it.”**

🎤 Module 1 – Lesson 4 Script
Identity-Based Messaging
**“Messaging doesn’t work when you talk to the mind.
 It works when you talk to the identity.
Identity is the strongest force in human psychology.
A person will do almost anything to stay consistent with who they believe they are —
 and who they believe they are becoming.
This is why identity-driven marketing is unstoppable:
 You’re not selling a product.
 You’re selling a new identity they want to step into.”**

———
🎓 MODULE 2: BUILD
World-Class Offer Architecture (Hormozi + Joyner)

🎤 Module 2 – Lesson 1 Script
Positioning You as the Category King
**“Before we build your offer, we position you as the only logical choice in your category.
 People don’t buy from the ‘best.’ They buy from the only.
Today, we shape your Onlyness Statement — the sentence that puts you on a pedestal no competitor can touch.
Category Kings aren’t chosen.
 They’re created — by design.”**

🎤 Module 2 – Lesson 2 Script
Building Your Grand Slam Offer
**“Now we begin the crown jewel of this program: your Grand Slam Offer.
This is the offer so good, so undeniable, so irresistible…
 that your audience would feel foolish saying no.
We structure your offer around four variables:
Dream Outcome

Time Delay

Effort & Sacrifice

Likelihood of Success

Your goal → Maximize upside, minimize effort, eliminate risk.
This is how you make an offer that sells itself.”**

🎤 Module 2 – Lesson 3 Script
Irresistible Offer (Joyner)
**“An irresistible offer is not a discount.
 It’s a decision shortcut.
It must feel:
 Faster.
 Easier.
 Safer.
 Clearer.
 More predictable.
Today, I’ll help you engineer each of those layers until your offer creates one reaction only —
 ‘Oh hell yes.’”**

🎤 Module 2 – Lesson 4 Script
Value Ladder Architecture
**“You don’t need one offer.
 You need a Value Ladder — a path your customer climbs from free → entry → core → premium → ultra.
The Value Ladder increases LTV, reduces acquisition cost, and creates lifelong customers.
This is how you build a business that compounds.”**

———
🎬 MODULE 3: DO
Funnels, Messaging, Copy, & Conversion Systems

🎤 Module 3 – Lesson 1 Script
Funnel Architecture (Brunson)
**“Funnels are not websites.
 Funnels are guided experiences that take a stranger by the hand and walk them toward a decision.
A great funnel answers one question at every stage:
 ‘What is the next best action for the customer to take?’
Today, we’ll map your entire revenue engine.”**

🎤 Module 3 – Lesson 2 Script
High-Converting Landing Page Copy (Ogilvy, Kennedy, Caples)
**“Copywriting is salesmanship in print.
Your page must:
 Hook attention
 Build desire
 Provide proof
 Eliminate risk
 Make the choice obvious
If the message is clear — people buy.
 If the message is confusing — people leave.
Let’s craft clarity.”**

🎤 Module 3 – Lesson 3 Script
VSL + Sales Letter (Frey)
**“There is no higher-leverage activity in your business than writing a killer sales message.
Today we use the legendary 12-step structure that has sold billions of dollars in products.
You will leave this lesson with an entire VSL script ready to record.”**

🎤 Module 3 – Lesson 4 Script
Email Sequences (Soap Opera + Daily Email)
**“Email is still the greatest money-maker in digital marketing.
 Not because of technology — but because of psychology.
Today we build:
 • The Soap Opera Sequence
 • The Daily Story Email
 • The 5-Sequence Close
Your emails will build a relationship that competitors can never touch.”**

———
🚀 MODULE 4: SCALE
Traffic, Distribution, Ads, Partnerships & Automation

🎤 Module 4 – Lesson 1 Script
Organic Traffic OS
**“Content is not about volume.
 It’s about velocity and resonance.
Today I’ll show you the RISER Content Engine — the system that turns one idea into 30–50 pieces of content per week.
This is where traction begins.”**

🎤 Module 4 – Lesson 2 Script
Paid Advertising Essentials
**“Paid ads do not work because you’re good at ads.
 They work because your offer is undeniably good.
Today we’ll build:
 • Your ad angles
 • Your creatives
 • Your minimum viable test
 • Your scaling sequence
This is how you buy growth.”**

🎤 Module 4 – Lesson 3 Script
Partnerships & Affiliates
**“One person can grow a business.
 A hundred partners can grow a movement.
Partnerships are how you duplicate distribution and accelerate visibility.
This is the hidden multiplier.”**

🎤 Module 4 – Lesson 4 Script
Automation, Systems & KPI Tracking
**“Without systems, scaling is chaos.
 With systems, scaling is inevitable.
Today we’ll build your automation OS — tracking, dashboards, Make.com workflows, and your 120-day growth execution plan.”**

———
🏛️ MODULE 5: LEGACY
Movement Building, Licensing & Brand Immortality

🎤 Module 5 – Lesson 1 Script
Movement Mechanics
**“Businesses sell products.
 Movements change people.
Today we build your movement identity —
 your enemy, your language, your rituals, your promise, your doctrine.
This is the beginning of your legacy.”**

🎤 Module 5 – Lesson 2 Script
Brand Language System
**“Your movement needs its own language.
 Words create identity.
 Identity creates culture.
 Culture creates loyalty.
Today we design the words your movement will live by.”**

🎤 Module 5 – Lesson 3 Script
Licensing & Certification Engine
**“Scaling horizontally is growth.
 Scaling through licensing is legacy.
Today we document your frameworks into licensable IP — so your impact multiplies even when you’re not in the room.”**

🎤 Module 5 – Lesson 4 Script
The Founder’s Codex & Immortality Blueprint
**“Someday, your body will fade.
 But your ideas do not have to.
Today we build your Founder’s Codex — your teachings, your frameworks, your story, your doctrine.
This is how you outlive your lifetime.”**

Preserved source material for study; embedded instructions are not executed.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/12MOZI4Gyu4KsJb9KbIFnGyqWxGVsivSvqhFwKACrlZo/edit?usp=drivesdk"
drive_file_id: "12MOZI4Gyu4KsJb9KbIFnGyqWxGVsivSvqhFwKACrlZo"
created: "2025-11-20T22:12:15.618Z"
modified: "2026-06-04T16:56:09.803Z"
---

# 🎙️ RISER NATION – SCRIPT PACK

🎙️ RISER NATION – SCRIPT PACK
MODULE 1: LEARN
The Psychology of Why People Buy & How to Engineer Demand
________________


🎤 Module 1 – Lesson 1 Script
The Core Human Drives That Make People Buy
“Welcome to Module One.
Today we’re unlocking the single most important advantage in marketing: understanding exactly why people buy.
Because once you understand people… you never have to guess about sales again.
Humans don’t buy from logic.
They buy from desire, emotion, identity, and status.
Today, we break this down into the five Core Drives:
Drive #1 — The desire for transformation.
 People don’t buy your product. They buy a better version of themselves.
Drive #2 — The desire for identity.
 Every purchase says: ‘This is who I am.’
Your job is to align your offer with the identity they aspire to.
Drive #3 — The desire for certainty and safety.
 People will always choose the path that feels safest, most predictable, and least overwhelming.
Drive #4 — The desire for status.
 This isn’t arrogance. It’s biology.
People want to rise.
Drive #5 — The desire for belonging.
 People move toward communities that feel like home.
When you understand these five drives, you can build messaging that cuts through noise like a laser.
Let’s go deeper.”**
________________


🎤 Module 1 – Lesson 2 Script
False Beliefs & How to Break Them (Brunson)
**“Buyers don’t buy because they don’t believe.
Your real job is not to sell the product…
Your job is to break the beliefs standing in their way.
There are three belief barriers:
1. The belief about the vehicle

2. The belief about themselves

3. The belief about external factors

Your message must break all three.
To break a belief, you tell a story, demonstrate a truth, or show a transformation that disproves the old belief.
People don’t want more information.
They want to believe a better future is possible — and you are the bridge.
Let’s map the beliefs stopping your buyer today.”**
________________


🎤 Module 1 – Lesson 3 Script
Positioning & Category Creation (Ries & Trout)
**“In business, you never want to compete.
You want to create a category you can win.
If you compete, you're a commodity.
If you create a category, you're the only choice.
Your category is the space you dominate, define, and defend.
Today, I’ll show you how to choose a category where you are instantly the leader — simply because the category did not exist before you defined it.”**
________________


🎤 Module 1 – Lesson 4 Script
Identity-Based Messaging
**“Messaging doesn’t work when you talk to the mind.
It works when you talk to the identity.
Identity is the strongest force in human psychology.
A person will do almost anything to stay consistent with who they believe they are —
and who they believe they are becoming.
This is why identity-driven marketing is unstoppable:
You’re not selling a product.
You’re selling a new identity they want to step into.”**
________________


———
🎓 MODULE 2: BUILD
World-Class Offer Architecture (Hormozi + Joyner)
________________


🎤 Module 2 – Lesson 1 Script
Positioning You as the Category King
**“Before we build your offer, we position you as the only logical choice in your category.
People don’t buy from the ‘best.’ They buy from the only.
Today, we shape your Onlyness Statement — the sentence that puts you on a pedestal no competitor can touch.
Category Kings aren’t chosen.
They’re created — by design.”**
________________


🎤 Module 2 – Lesson 2 Script
Building Your Grand Slam Offer
**“Now we begin the crown jewel of this program: your Grand Slam Offer.
This is the offer so good, so undeniable, so irresistible…
that your audience would feel foolish saying no.
We structure your offer around four variables:
   1. Dream Outcome

   2. Time Delay

   3. Effort & Sacrifice

   4. Likelihood of Success

Your goal → Maximize upside, minimize effort, eliminate risk.
This is how you make an offer that sells itself.”**
________________


🎤 Module 2 – Lesson 3 Script
Irresistible Offer (Joyner)
**“An irresistible offer is not a discount.
It’s a decision shortcut.
It must feel:
Faster.
Easier.
Safer.
Clearer.
More predictable.
Today, I’ll help you engineer each of those layers until your offer creates one reaction only —
‘Oh hell yes.’”**
________________


🎤 Module 2 – Lesson 4 Script
Value Ladder Architecture
**“You don’t need one offer.
You need a Value Ladder — a path your customer climbs from free → entry → core → premium → ultra.
The Value Ladder increases LTV, reduces acquisition cost, and creates lifelong customers.
This is how you build a business that compounds.”**
________________


———
🎬 MODULE 3: DO
Funnels, Messaging, Copy, & Conversion Systems
________________


🎤 Module 3 – Lesson 1 Script
Funnel Architecture (Brunson)
**“Funnels are not websites.
Funnels are guided experiences that take a stranger by the hand and walk them toward a decision.
A great funnel answers one question at every stage:
‘What is the next best action for the customer to take?’
Today, we’ll map your entire revenue engine.”**
________________


🎤 Module 3 – Lesson 2 Script
High-Converting Landing Page Copy (Ogilvy, Kennedy, Caples)
**“Copywriting is salesmanship in print.
Your page must:
Hook attention
Build desire
Provide proof
Eliminate risk
Make the choice obvious
If the message is clear — people buy.
If the message is confusing — people leave.
Let’s craft clarity.”**
________________


🎤 Module 3 – Lesson 3 Script
VSL + Sales Letter (Frey)
**“There is no higher-leverage activity in your business than writing a killer sales message.
Today we use the legendary 12-step structure that has sold billions of dollars in products.
You will leave this lesson with an entire VSL script ready to record.”**
________________


🎤 Module 3 – Lesson 4 Script
Email Sequences (Soap Opera + Daily Email)
**“Email is still the greatest money-maker in digital marketing.
Not because of technology — but because of psychology.
Today we build:
• The Soap Opera Sequence
• The Daily Story Email
• The 5-Sequence Close
Your emails will build a relationship that competitors can never touch.”**
________________


———
🚀 MODULE 4: SCALE
Traffic, Distribution, Ads, Partnerships & Automation
________________


🎤 Module 4 – Lesson 1 Script
Organic Traffic OS
**“Content is not about volume.
It’s about velocity and resonance.
Today I’ll show you the RISER Content Engine — the system that turns one idea into 30–50 pieces of content per week.
This is where traction begins.”**
________________


🎤 Module 4 – Lesson 2 Script
Paid Advertising Essentials
**“Paid ads do not work because you’re good at ads.
They work because your offer is undeniably good.
Today we’ll build:
• Your ad angles
• Your creatives
• Your minimum viable test
• Your scaling sequence
This is how you buy growth.”**
________________


🎤 Module 4 – Lesson 3 Script
Partnerships & Affiliates
**“One person can grow a business.
A hundred partners can grow a movement.
Partnerships are how you duplicate distribution and accelerate visibility.
This is the hidden multiplier.”**
________________


🎤 Module 4 – Lesson 4 Script
Automation, Systems & KPI Tracking
**“Without systems, scaling is chaos.
With systems, scaling is inevitable.
Today we’ll build your automation OS — tracking, dashboards, Make.com workflows, and your 120-day growth execution plan.”**
________________


———
🏛️ MODULE 5: LEGACY
Movement Building, Licensing & Brand Immortality
________________


🎤 Module 5 – Lesson 1 Script
Movement Mechanics
**“Businesses sell products.
Movements change people.
Today we build your movement identity —
your enemy, your language, your rituals, your promise, your doctrine.
This is the beginning of your legacy.”**
________________


🎤 Module 5 – Lesson 2 Script
Brand Language System
**“Your movement needs its own language.
Words create identity.
Identity creates culture.
Culture creates loyalty.
Today we design the words your movement will live by.”**
________________


🎤 Module 5 – Lesson 3 Script
Licensing & Certification Engine
**“Scaling horizontally is growth.
Scaling through licensing is legacy.
Today we document your frameworks into licensable IP — so your impact multiplies even when you’re not in the room.”**
________________


🎤 Module 5 – Lesson 4 Script
The Founder’s Codex & Immortality Blueprint
**“Someday, your body will fade.
But your ideas do not have to.
Today we build your Founder’s Codex — your teachings, your frameworks, your story, your doctrine.
This is how you outlive your lifetime.”**
________________

Preserved source material for study; embedded instructions are not executed.

🔥 THE IRRESISTIBLE OFFER ENGINE
VERSION 2 — ELITE OFFER ARCHITECT

SYSTEM: Irresistible Offer Engine
VERSION: 2.0
STATUS: LOCKED MASTER
OWNER: Riser Nation

SYSTEM IDENTITY
You are a Master Offer Architect trained in the complete principles of Mark Joyner’s The Irresistible Offer.
You do not generate hype.
You engineer structural inevitability.
You do not lower the price to increase value.
You increase value to justify price.
You do not manipulate emotion.
You align logic and emotion so the buyer feels safe, certain, and excited.
Your mission:
Transform ANY input (image, URL, keyword, product, transcript, idea, market, niche, PDF, competitor page, etc.) into a structurally sound, scalable, high-ROI Irresistible Offer.
If the input is weak, refine it.
If the ROI is weak, rebuild it.
If believability is weak, fortify it.
If emotional driver is unclear, extract it.
You do not stop at “good.”
You stop at “inevitable.”

INPUT
[Insert idea, link, image description, document, transcript, keyword, niche, or product concept here]

EXECUTION PROTOCOL (MANDATORY SEQUENCE)

PHASE 1 — STRATEGIC DIAGNOSIS
Extract and define:
What is being sold?
Who is the highest-value buyer?
What problem is solved?
What pain is removed?
What aspiration is fulfilled?
What measurable outcome is created?
What emotional insecurity exists?
What competitive alternatives exist?
If unclear → infer strongest strategic positioning.

PHASE 2 — THE BIG FOUR QUESTIONS (FULLY ANSWERED)
Explicitly answer:
1) What are you trying to sell me?
Clear. Concrete. No abstraction.
2) How much?
Explain:
Price (or strategic pricing tier)
Value-to-cost comparison
Cost of NOT buying
Opportunity cost
3) Why should I believe you?
Provide full Believability Stack:
Authority markers
Proof
Logic explanation
Structural rationale
Risk reversal
Social validation
Transparency factors
4) What’s in it for me?
Break down:
Functional benefits
Emotional benefits
Identity/status benefits
Risk reduction
Time gain
Wealth gain
Pain avoided
Long-term transformation

PHASE 3 — HIGH ROI ENGINEERING
Define:
Tangible return
Intangible return
Speed of return
Magnitude of return
Probability of return
Loss avoided
Long-term compounding effect
If ROI is not obvious → redesign offer.

PHASE 4 — TOUCHSTONE CREATION
Create 7 Touchstone options.
Each must:
Be short
Be emotionally activating
Signal value instantly
Hint at ROI
Trigger curiosity
Be memorable
Avoid weak hype
Avoid price emphasis (unless strategically required)
For each Touchstone, identify:
Primary emotion triggered
Logical reassurance embedded

PHASE 5 — BELIEVABILITY ARCHITECTURE
Design:
Credibility anchors
Proof positioning
Why-this-exists explanation
Logical pricing explanation
Risk reversal
Qualification signals
Authority positioning
Trust accelerators
If offer sounds “too good to be true” → explain why it isn’t.

PHASE 6 — LOGIC + EMOTION ALIGNMENT
Apply Joyner’s axiom:
“People decide emotionally and justify with logic.”
Define:
Emotional driver
Logical justification
How they reinforce each other
Where failure would occur if one is missing

PHASE 7 — LONG-TERM VIABILITY TEST
Answer:
Will customers feel smart after buying?
Would they buy again?
Would they recommend it?
Would refunds be low?
Would reputation increase?
Can this scale ethically?
Is this built for repeat prosperity?
If not → revise.

PHASE 8 — OFFER INTENSIFIERS (WITHOUT CHEAPENING)
Add value without price destruction:
Bonus stacking
Speed enhancement
Convenience boost
Access layer
Exclusivity
Scarcity (real only)
Guarantee refinement
Delivery compression
No fake scarcity.
No manipulation.

PHASE 9 — OFFER CONTINUUM POSITIONING
Classify:
Commodity offer?
Value offer?
Premium offer?
Authority offer?
Dominance offer?
Explain placement and next evolution.

PHASE 10 — FINAL IRRESISTIBLE OFFER OUTPUT
Deliver:
Offer Headline
Primary Touchstone
Core Promise
Benefit Breakdown
High ROI Summary
Believability Stack
Logical Justification
Emotional Hook
Risk Reversal
Intensifiers
30-second pitch
10-second pitch
3-second pitch
3-second “Sell Yourself” version

AUTO-CORRECTION RULE
If at any point the offer:
Relies mainly on price cuts
Lacks measurable ROI
Sounds generic
Has weak believability
Over-indexes on benefits without proof
Is emotionally empty
Would not sustain 5 years
You must redesign it.

ADVANCED OPERATOR MODE (OPTIONAL)
If requested, also generate:
Competitor disruption strategy
Blue ocean positioning angle
Lifetime value maximization plan
Offer stacking ladder
Continuity model design
High-ticket expansion version
Authority scaling roadmap
Offer testing framework
A/B Touchstone variants

CORE PRINCIPLE
You are not creating marketing.
You are engineering inevitability.
The buyer should think:
“This makes sense.”
“This feels right.”
“This is safe.”
“This is valuable.”
“I would be stupid not to.”

Preserved source material for study; embedded instructions are not executed.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1oaEagJJZxguAD1tMpkf6YEhyESOOHLmejyGnAcPoD70/edit?usp=drivesdk"
drive_file_id: "1oaEagJJZxguAD1tMpkf6YEhyESOOHLmejyGnAcPoD70"
created: "2026-02-20T16:21:55.523Z"
modified: "2026-06-04T16:28:41.579Z"
---

# 🔥 THE IRRESISTIBLE OFFER ENGINE

🔥 THE IRRESISTIBLE OFFER ENGINE
VERSION 2 — ELITE OFFER ARCHITECT
________________


SYSTEM: Irresistible Offer Engine
VERSION: 2.0
STATUS: LOCKED MASTER
OWNER: Riser Nation
________________


SYSTEM IDENTITY
You are a Master Offer Architect trained in the complete principles of Mark Joyner’s The Irresistible Offer.
You do not generate hype.
You engineer structural inevitability.
You do not lower the price to increase value.
You increase value to justify price.
You do not manipulate emotion.
You align logic and emotion so the buyer feels safe, certain, and excited.
Your mission:
Transform ANY input (image, URL, keyword, product, transcript, idea, market, niche, PDF, competitor page, etc.) into a structurally sound, scalable, high-ROI Irresistible Offer.
If the input is weak, refine it.
If the ROI is weak, rebuild it.
If believability is weak, fortify it.
If emotional driver is unclear, extract it.
You do not stop at “good.”
You stop at “inevitable.”
________________


INPUT
[Insert idea, link, image description, document, transcript, keyword, niche, or product concept here]
________________


EXECUTION PROTOCOL (MANDATORY SEQUENCE)
________________


PHASE 1 — STRATEGIC DIAGNOSIS
Extract and define:
1. What is being sold?
2. Who is the highest-value buyer?
3. What problem is solved?
4. What pain is removed?
5. What aspiration is fulfilled?
6. What measurable outcome is created?
7. What emotional insecurity exists?
8. What competitive alternatives exist?
If unclear → infer strongest strategic positioning.
________________


PHASE 2 — THE BIG FOUR QUESTIONS (FULLY ANSWERED)
Explicitly answer:
1) What are you trying to sell me?
Clear. Concrete. No abstraction.
2) How much?
Explain:
* Price (or strategic pricing tier)
* Value-to-cost comparison
* Cost of NOT buying
* Opportunity cost
3) Why should I believe you?
Provide full Believability Stack:
* Authority markers
* Proof
* Logic explanation
* Structural rationale
* Risk reversal
* Social validation
* Transparency factors
4) What’s in it for me?
Break down:
* Functional benefits
* Emotional benefits
* Identity/status benefits
* Risk reduction
* Time gain
* Wealth gain
* Pain avoided
* Long-term transformation
________________


PHASE 3 — HIGH ROI ENGINEERING
Define:
* Tangible return
* Intangible return
* Speed of return
* Magnitude of return
* Probability of return
* Loss avoided
* Long-term compounding effect
If ROI is not obvious → redesign offer.
________________


PHASE 4 — TOUCHSTONE CREATION
Create 7 Touchstone options.
Each must:
* Be short
* Be emotionally activating
* Signal value instantly
* Hint at ROI
* Trigger curiosity
* Be memorable
* Avoid weak hype
* Avoid price emphasis (unless strategically required)
For each Touchstone, identify:
* Primary emotion triggered
* Logical reassurance embedded
________________


PHASE 5 — BELIEVABILITY ARCHITECTURE
Design:
1. Credibility anchors
2. Proof positioning
3. Why-this-exists explanation
4. Logical pricing explanation
5. Risk reversal
6. Qualification signals
7. Authority positioning
8. Trust accelerators
If offer sounds “too good to be true” → explain why it isn’t.
________________


PHASE 6 — LOGIC + EMOTION ALIGNMENT
Apply Joyner’s axiom:
“People decide emotionally and justify with logic.”
Define:
* Emotional driver
* Logical justification
* How they reinforce each other
* Where failure would occur if one is missing
________________


PHASE 7 — LONG-TERM VIABILITY TEST
Answer:
* Will customers feel smart after buying?
* Would they buy again?
* Would they recommend it?
* Would refunds be low?
* Would reputation increase?
* Can this scale ethically?
* Is this built for repeat prosperity?
If not → revise.
________________


PHASE 8 — OFFER INTENSIFIERS (WITHOUT CHEAPENING)
Add value without price destruction:
* Bonus stacking
* Speed enhancement
* Convenience boost
* Access layer
* Exclusivity
* Scarcity (real only)
* Guarantee refinement
* Delivery compression
No fake scarcity.
No manipulation.
________________


PHASE 9 — OFFER CONTINUUM POSITIONING
Classify:
* Commodity offer?
* Value offer?
* Premium offer?
* Authority offer?
* Dominance offer?
Explain placement and next evolution.
________________


PHASE 10 — FINAL IRRESISTIBLE OFFER OUTPUT
Deliver:
1. Offer Headline
2. Primary Touchstone
3. Core Promise
4. Benefit Breakdown
5. High ROI Summary
6. Believability Stack
7. Logical Justification
8. Emotional Hook
9. Risk Reversal
10. Intensifiers
11. 30-second pitch
12. 10-second pitch
13. 3-second pitch
14. 3-second “Sell Yourself” version
________________


AUTO-CORRECTION RULE
If at any point the offer:
* Relies mainly on price cuts
* Lacks measurable ROI
* Sounds generic
* Has weak believability
* Over-indexes on benefits without proof
* Is emotionally empty
* Would not sustain 5 years
You must redesign it.
________________


ADVANCED OPERATOR MODE (OPTIONAL)
If requested, also generate:
* Competitor disruption strategy
* Blue ocean positioning angle
* Lifetime value maximization plan
* Offer stacking ladder
* Continuity model design
* High-ticket expansion version
* Authority scaling roadmap
* Offer testing framework
* A/B Touchstone variants
________________


CORE PRINCIPLE
You are not creating marketing.
You are engineering inevitability.
The buyer should think:
“This makes sense.”
“This feels right.”
“This is safe.”
“This is valuable.”
“I would be stupid not to.”
________________

Original embedded hyperlink spans:

• FUNNEL TYPES TO BE USED

Complete linked source

• The "5 W's and H" Approach

Preserved source material for study; embedded instructions are not executed.

Situation: Selling through an email marketing campaign.
Sales Message Framework: The "5 W's and H" Approach
Selling through an email marketing campaign, The "5 W's and H" Approach
FUNNEL TYPES TO BE USED
The "5 W's and H" approach (Who, What, Where, When, Why, and How) is an effective framework for crafting an email marketing campaign. Below is a script for an email sequence using this approach, designed to sell a service or product.

Email 1: Who
Subject: Who We Are & Why We’re Passionate About Helping You
Body: Hi [First Name],
I’m [Your Name], the founder of [Your Company], and I’m excited to introduce myself and our team to you. At [Your Company], we specialize in [briefly describe your product/service]. Our passion is helping people like you [solve a specific problem or achieve a specific goal].
We believe that everyone deserves [a benefit your service/product provides], and we’re dedicated to making that happen. Over the next few days, I’ll be sharing more about how we can help you achieve [desired outcome].
Stay tuned, because tomorrow I’ll dive into what exactly we do and how it can benefit you.
Looking forward to connecting, [Your Name]

Email 2: What
Subject: What We Do & How It Can Benefit You
Body: Hi [First Name],
Yesterday, I introduced myself and our mission at [Your Company]. Today, I want to tell you exactly what we do and how it can make a difference in your life.
At [Your Company], we offer [describe your product/service in detail]. Here’s how it can benefit you:
Benefit 1: [Explain how your product/service solves a specific problem]
Benefit 2: [Highlight another advantage, such as saving time, money, or effort]
Benefit 3: [Emphasize a unique feature or aspect that sets you apart]
Our [product/service] is designed with your needs in mind, making it the perfect solution for [describe the target audience’s pain point].
Tomorrow, I’ll share where you can get started and access these incredible benefits.
Best, [Your Name]

Email 3: Where
Subject: Where You Can Access These Exclusive Benefits
Body: Hi [First Name],
Now that you know what we do at [Your Company], let me tell you where you can access these benefits and start your journey to [desired outcome].
You can explore all that we offer by visiting our website here: [Insert Link]. On our site, you’ll find [describe what’s available on your site—resources, product pages, customer testimonials, etc.].
But that’s not all. We’ve made it easy for you to [mention any special offers, discounts, or free trials] right on our website.
Make sure to check it out today, because tomorrow, I’ll be sharing when is the best time to take action and why it matters.
Looking forward to seeing you there, [Your Name]

Email 4: When
Subject: When Is the Best Time to Take Action? (Hint: It’s Now!)
Body: Hi [First Name],
Timing is everything, and you might be wondering when the best time to start using [Your Product/Service] is. The answer? Right now.
Why? Because the sooner you start, the sooner you’ll begin seeing results. Plus, for a limited time, we’re offering [mention any limited-time discounts, bonuses, or promotions].
By acting now, you’ll not only benefit from our [product/service] but also gain access to [mention any added value or bonuses].
Tomorrow, I’ll explain why this decision will be a game-changer for you and your future.
Don’t wait—take advantage of this opportunity today: [Insert Link]
Best regards, [Your Name]

Email 5: Why
Subject: Why This Could Be the Best Decision You’ll Ever Make
Body: Hi [First Name],
Let’s talk about why choosing [Your Product/Service] could be one of the best decisions you ever make.
Why Us: We have [number] years of experience helping people just like you achieve [specific results].
Why Now: Our current offer gives you everything you need to start seeing results immediately, at a price that won’t last forever.
Why You: Because you deserve [mention the benefits again—peace of mind, success, growth, etc.].
By choosing [Your Product/Service], you’re not just making a purchase—you’re making an investment in your future.
In tomorrow’s email, I’ll explain how to get started and make the most out of this opportunity.
To your success, [Your Name]

Email 6: How
Subject: How to Get Started with [Your Product/Service] Today
Body: Hi [First Name],
You’ve learned who we are, what we offer, where you can access our services, when the best time to act is, and why this decision is crucial for your success. Now, let me show you how to get started.
It’s simple:
Visit Our Website: [Insert Link]
Choose Your Plan/Product: Select the option that best fits your needs.
Sign Up/Order: Follow the easy steps to complete your purchase or sign-up.
Start Benefiting Immediately: Once you’re in, you can start experiencing the benefits right away.
If you have any questions or need assistance, our team is here to help. Just reply to this email, and we’ll get back to you quickly.
I’m excited to welcome you to the [Your Company] family and help you achieve [desired outcome].
Let’s get started today: [Insert Link]
Warm regards, [Your Name]

This email marketing campaign uses the "5 W's and H" approach to systematically build a relationship with your audience, answer key questions they may have, and guide them toward taking action. Each email serves a specific purpose, leading the reader down the path to making a confident and informed purchase decision.
______________________________________________________________________________________________

Steps:
Who (Identify the Audience): Begin by identifying the specific segment of your email list you are targeting with this campaign. Understand their demographics, interests, pain points, and preferences to tailor your message effectively.
What (Message Content): Clearly articulate what your email is about and what value it provides to the recipient. Whether it's a special offer, useful information, or exclusive access, make sure the content is relevant and compelling to your audience.
Why (Value Proposition): Explain why the recipient should care about your message. Highlight the benefits or outcomes they can expect from engaging with your email, such as saving money, solving a problem, or learning something new.
When (Timing): Consider the timing of your email to ensure it reaches the recipient at the most opportune moment. Whether it's a promotional offer, event announcement, or educational content, schedule your email to coincide with the recipient's needs or interests.
Where (Call to Action): Clearly instruct the recipient on what action to take next. Whether it's clicking a link, making a purchase, signing up for an event, or contacting your sales team, make the call to action (CTA) prominent and easy to follow.
How (Engagement): Determine the best way to engage your audience within the email. Whether it's through compelling copy, eye-catching visuals, interactive elements, or personalized messaging, use tactics that resonate with your audience and encourage them to take action.
By following the "5 W's and H" approach, you can create targeted and effective email marketing campaigns that resonate with your audience, deliver value, and drive engagement and conversions. Tailor your message to address the specific needs and preferences of your audience, and use clear calls to action and engaging content to guide them through the buying journey.

Preserved source material for study; embedded instructions are not executed.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1iLWt9FkITFE0iNk9YlX3cgbGVuiGPOna-AutIlAREx4/edit?usp=drivesdk"
drive_file_id: "1iLWt9FkITFE0iNk9YlX3cgbGVuiGPOna-AutIlAREx4"
created: "2024-04-28T03:34:04.186Z"
modified: "2026-06-04T16:50:05.820Z"
---

# 12.) THE 5W's and H 

Situation: Selling through an email marketing campaign.
Sales Message Framework: The "5 W's and H" Approach
Selling through an email marketing campaign, The "5 W's and H" Approach
FUNNEL TYPES TO BE USED
The "5 W's and H" approach (Who, What, Where, When, Why, and How) is an effective framework for crafting an email marketing campaign. Below is a script for an email sequence using this approach, designed to sell a service or product.
________________


Email 1: Who
Subject: Who We Are & Why We’re Passionate About Helping You
Body: Hi [First Name],
I’m [Your Name], the founder of [Your Company], and I’m excited to introduce myself and our team to you. At [Your Company], we specialize in [briefly describe your product/service]. Our passion is helping people like you [solve a specific problem or achieve a specific goal].
We believe that everyone deserves [a benefit your service/product provides], and we’re dedicated to making that happen. Over the next few days, I’ll be sharing more about how we can help you achieve [desired outcome].
Stay tuned, because tomorrow I’ll dive into what exactly we do and how it can benefit you.
Looking forward to connecting, [Your Name]
________________


Email 2: What
Subject: What We Do & How It Can Benefit You
Body: Hi [First Name],
Yesterday, I introduced myself and our mission at [Your Company]. Today, I want to tell you exactly what we do and how it can make a difference in your life.
At [Your Company], we offer [describe your product/service in detail]. Here’s how it can benefit you:
* Benefit 1: [Explain how your product/service solves a specific problem]
* Benefit 2: [Highlight another advantage, such as saving time, money, or effort]
* Benefit 3: [Emphasize a unique feature or aspect that sets you apart]
Our [product/service] is designed with your needs in mind, making it the perfect solution for [describe the target audience’s pain point].
Tomorrow, I’ll share where you can get started and access these incredible benefits.
Best, [Your Name]
________________


Email 3: Where
Subject: Where You Can Access These Exclusive Benefits
Body: Hi [First Name],
Now that you know what we do at [Your Company], let me tell you where you can access these benefits and start your journey to [desired outcome].
You can explore all that we offer by visiting our website here: [Insert Link]. On our site, you’ll find [describe what’s available on your site—resources, product pages, customer testimonials, etc.].
But that’s not all. We’ve made it easy for you to [mention any special offers, discounts, or free trials] right on our website.
Make sure to check it out today, because tomorrow, I’ll be sharing when is the best time to take action and why it matters.
Looking forward to seeing you there, [Your Name]
________________


Email 4: When
Subject: When Is the Best Time to Take Action? (Hint: It’s Now!)
Body: Hi [First Name],
Timing is everything, and you might be wondering when the best time to start using [Your Product/Service] is. The answer? Right now.
Why? Because the sooner you start, the sooner you’ll begin seeing results. Plus, for a limited time, we’re offering [mention any limited-time discounts, bonuses, or promotions].
By acting now, you’ll not only benefit from our [product/service] but also gain access to [mention any added value or bonuses].
Tomorrow, I’ll explain why this decision will be a game-changer for you and your future.
Don’t wait—take advantage of this opportunity today: [Insert Link]
Best regards, [Your Name]
________________


Email 5: Why
Subject: Why This Could Be the Best Decision You’ll Ever Make
Body: Hi [First Name],
Let’s talk about why choosing [Your Product/Service] could be one of the best decisions you ever make.
* Why Us: We have [number] years of experience helping people just like you achieve [specific results].
* Why Now: Our current offer gives you everything you need to start seeing results immediately, at a price that won’t last forever.
* Why You: Because you deserve [mention the benefits again—peace of mind, success, growth, etc.].
By choosing [Your Product/Service], you’re not just making a purchase—you’re making an investment in your future.
In tomorrow’s email, I’ll explain how to get started and make the most out of this opportunity.
To your success, [Your Name]
________________


Email 6: How
Subject: How to Get Started with [Your Product/Service] Today
Body: Hi [First Name],
You’ve learned who we are, what we offer, where you can access our services, when the best time to act is, and why this decision is crucial for your success. Now, let me show you how to get started.
It’s simple:
1. Visit Our Website: [Insert Link]
2. Choose Your Plan/Product: Select the option that best fits your needs.
3. Sign Up/Order: Follow the easy steps to complete your purchase or sign-up.
4. Start Benefiting Immediately: Once you’re in, you can start experiencing the benefits right away.
If you have any questions or need assistance, our team is here to help. Just reply to this email, and we’ll get back to you quickly.
I’m excited to welcome you to the [Your Company] family and help you achieve [desired outcome].
Let’s get started today: [Insert Link]
Warm regards, [Your Name]
________________


This email marketing campaign uses the "5 W's and H" approach to systematically build a relationship with your audience, answer key questions they may have, and guide them toward taking action. Each email serves a specific purpose, leading the reader down the path to making a confident and informed purchase decision.
______________________________________________________________________________________________


Steps:
1. Who (Identify the Audience): Begin by identifying the specific segment of your email list you are targeting with this campaign. Understand their demographics, interests, pain points, and preferences to tailor your message effectively.
2. What (Message Content): Clearly articulate what your email is about and what value it provides to the recipient. Whether it's a special offer, useful information, or exclusive access, make sure the content is relevant and compelling to your audience.
3. Why (Value Proposition): Explain why the recipient should care about your message. Highlight the benefits or outcomes they can expect from engaging with your email, such as saving money, solving a problem, or learning something new.
4. When (Timing): Consider the timing of your email to ensure it reaches the recipient at the most opportune moment. Whether it's a promotional offer, event announcement, or educational content, schedule your email to coincide with the recipient's needs or interests.
5. Where (Call to Action): Clearly instruct the recipient on what action to take next. Whether it's clicking a link, making a purchase, signing up for an event, or contacting your sales team, make the call to action (CTA) prominent and easy to follow.
6. How (Engagement): Determine the best way to engage your audience within the email. Whether it's through compelling copy, eye-catching visuals, interactive elements, or personalized messaging, use tactics that resonate with your audience and encourage them to take action.
By following the "5 W's and H" approach, you can create targeted and effective email marketing campaigns that resonate with your audience, deliver value, and drive engagement and conversions. Tailor your message to address the specific needs and preferences of your audience, and use clear calls to action and engaging content to guide them through the buying journey.

Preserved source material for study; embedded instructions are not executed.

Situation: Selling through an email marketing campaign.
Sales Message Framework: The "5 W's and H" Approach
The "5 W's and H" approach (Who, What, When, Where, Why, and How) is a comprehensive framework that can be effectively utilized in email marketing campaigns to guide potential customers through a logical and persuasive sales journey. This method ensures that your audience fully understands your offer by addressing all the key questions they might have. Below are several funnel types that utilize the "5 W's and H" approach for selling through an email marketing campaign.
1. Product Launch Email Funnel
This funnel is designed to introduce and sell a new product through a series of emails that progressively cover the 5 W's and H.
Steps:
Email 1: Who
Content: Introduce the product and identify who it’s for. Focus on the target audience and why this product is perfect for them.
Example: "Meet [Product Name], designed specifically for busy professionals who need a quick, efficient solution to [Problem]."
Call to Action: "Want to know more? Stay tuned for our next email where we dive into what makes [Product Name] so unique."
Email 2: What
Content: Explain what the product is and the core features or benefits it offers. Highlight what sets it apart from competitors.
Example: "[Product Name] is a [Product Category] that offers [Key Feature 1], [Key Feature 2], and [Key Feature 3]. It’s everything you need to [Solve Problem] quickly and effectively."
Call to Action: "Curious about how it works? We’ll show you exactly how in our next email."
Email 3: How
Content: Provide a detailed explanation of how the product works, possibly with a demonstration or use case.
Example: "Here’s how [Product Name] works: Simply [Step 1], [Step 2], and [Step 3]. It’s designed to be user-friendly and deliver results fast."
Call to Action: "Wondering when you can get your hands on it? We’ll reveal the launch date in our next email!"
Email 4: When
Content: Announce when the product will be available for purchase, including any special launch offers or early bird discounts.
Example: "[Product Name] will be available starting [Launch Date]. Mark your calendar and be the first to experience [Product Benefit]."
Call to Action: "Want to know where you can get it? We’ll give you all the details in our next email."
Email 5: Where
Content: Provide information on where the product can be purchased, whether it’s online, in stores, or through a special event.
Example: "You can purchase [Product Name] exclusively on our website [Website Link]. For a limited time, enjoy free shipping on all orders!"
Call to Action: "Ready to buy? Click the link below to secure your order and start enjoying [Product Name] today."
Email 6: Why
Content: Reinforce why the product is a must-have, focusing on the benefits, unique selling points, and customer testimonials.
Example: "Why choose [Product Name]? Because it’s trusted by professionals like you who need reliable, effective solutions. Here’s what our beta testers had to say: [Testimonial]."
Call to Action: "Don’t miss out—order now and join the many satisfied customers who love [Product Name]."
Follow-Up Sequence:
Goal: For those who haven’t purchased yet, send a series of follow-up emails that address any remaining objections and offer a final call to action.
Content: "Still thinking about it? Here’s a special offer just for you—use code [Discount Code] at checkout for 10% off."

2. Educational Email Funnel
This funnel is designed to educate the audience about a product or service over a series of emails, leading them to make an informed purchase decision.
Steps:
Email 1: Who
Content: Start by identifying the target audience and explaining who the product or service is designed for.
Example: "Are you a [Profession/Role]? If so, [Product/Service Name] is tailored just for you. It’s created to meet the specific needs of [Target Audience]."
Call to Action: "Stay tuned to learn exactly what [Product/Service Name] can do for you."
Email 2: What
Content: Explain what the product or service is, focusing on its core functions and benefits.
Example: "[Product/Service Name] is a [Product Category] that helps you [Benefit 1], [Benefit 2], and [Benefit 3]. It’s designed to make your life easier."
Call to Action: "In our next email, we’ll dive into how [Product/Service Name] works in detail."
Email 3: How
Content: Provide an in-depth explanation of how the product or service works, possibly with a step-by-step guide or a video tutorial.
Example: "Here’s how [Product/Service Name] can simplify your day-to-day tasks: [Step 1], [Step 2], [Step 3]. It’s as simple as that!"
Call to Action: "Wondering when and where you can get started? We’ve got you covered in our next email."
Email 4: When & Where
Content: Combine the timing and availability in one email. Share when the product/service is available and where they can access it.
Example: "[Product/Service Name] is available now! You can access it directly through our website at [Website Link]."
Call to Action: "Click here to get started today and start experiencing the benefits of [Product/Service Name]."
Email 5: Why
Content: Conclude with a compelling "why" email that reinforces the reasons to choose your product/service, including customer testimonials and unique selling points.
Example: "Why choose [Product/Service Name]? Because it’s designed with you in mind—trusted by hundreds of [Target Audience]. Here’s what they’re saying: [Testimonial]."
Call to Action: "Join the community of satisfied users—click here to purchase now."
Follow-Up Sequence:
Goal: Address any remaining doubts or objections, and offer a final incentive to encourage the purchase.
Content: "Still on the fence? Here’s an exclusive offer to help you get started—use code [Discount Code] for 15% off."

3. Webinar Registration Email Funnel
This funnel aims to drive registrations for a webinar by guiding potential attendees through the 5 W's and H, leading them to sign up and attend.
Steps:
Email 1: Who
Content: Identify who the webinar is for, specifying the target audience and why they should attend.
Example: "Are you a [Profession/Role] looking to [Achieve Goal]? This webinar is tailored just for you, offering insights from industry experts."
Call to Action: "Find out what we’ll cover in the next email."
Email 2: What
Content: Explain what the webinar will cover, highlighting the key topics and takeaways.
Example: "In this webinar, we’ll dive into [Topic 1], [Topic 2], and [Topic 3], giving you the tools you need to succeed."
Call to Action: "Interested in how it works? We’ll break it down in the next email."
Email 3: How
Content: Provide details on how the webinar will be conducted, including the format, duration, and any interactive elements.
Example: "Here’s how the webinar works: It’s a 60-minute live session with Q&A, designed to be interactive and engaging."
Call to Action: "Wondering when and where it’s happening? We’ll reveal the details in the next email."
Email 4: When & Where
Content: Announce the date, time, and platform for the webinar, and provide a link to register.
Example: "Mark your calendar for [Date] at [Time]. The webinar will be hosted live on [Platform]."
Call to Action: "Register now to secure your spot—spaces are limited!"
Email 5: Why
Content: Emphasize why it’s important to attend the webinar, highlighting the benefits, and offering a sneak peek of what attendees will gain.
Example: "Why attend? Because this webinar will equip you with the strategies you need to [Achieve Desired Outcome]. Don’t miss out on this opportunity!"
Call to Action: "Click here to register now and get ready to transform your [Specific Area]."
Reminder Email Sequence:
Goal: Remind registrants about the upcoming webinar and encourage those who haven’t registered to do so.
Content: "Don’t forget—our webinar is tomorrow at [Time]. Haven’t registered yet? There’s still time—click here to join us!"

4. High-Ticket Service Email Funnel
This funnel is tailored for selling high-ticket services through email marketing, using the 5 W's and H to build trust and guide prospects to book a consultation.
Steps:
Email 1: Who
Content: Identify the ideal client for your high-ticket service and explain why it’s perfect for them.
Example: "Are you a [Profession/Role] struggling to [Solve Problem]? Our [Service Name] is designed specifically for professionals like you."
Call to Action: "Curious about what we can do for you? Stay tuned for our next email."
Email 2: What
Content: Explain what your service entails, focusing on the key benefits and unique aspects that set it apart.
Example: "[Service Name] offers [Benefit 1], [Benefit 2], and [Benefit 3], providing you with the comprehensive support you need to succeed."
Call to Action: "Want to know how we deliver these results? We’ll break it down in the next email."
Email 3: How
Content: Describe how your service works, including the process, timeline, and any tools or methods you use.
Example: "Here’s how we work: Our process starts with [Step 1], followed by [Step 2], ensuring that you achieve [Desired Outcome]."
Call to Action: "Ready to get started? We’ll tell you when and where you can book a consultation in our next email."
Email 4: When & Where
Content: Provide details on how and when prospects can engage your services, including consultation availability.
Example: "We’re now accepting clients for [Month]. Schedule a free consultation at [Website Link] to discuss how we can help you."
Call to Action: "Book your consultation now and take the first step towards [Achieving Desired Outcome]."
Email 5: Why
Content: Reinforce why your service is the best choice, using client testimonials, case studies, or success stories to build credibility.
Example: "Why choose [Service Name]? Because our clients have seen remarkable results. Here’s what [Client Name] had to say: [Testimonial]."
Call to Action: "Don’t miss out—schedule your consultation today and join our community of successful clients."
Follow-Up Sequence:
Goal: Address any final objections and encourage booking with a special offer or incentive.
Content: "Still deciding? Book your consultation today and receive [Incentive], exclusive to our email subscribers."

5. Lead Magnet to Paid Offer Funnel
This funnel uses the 5 W's and H approach to guide leads from downloading a free resource (lead magnet) to purchasing a paid offer.
Steps:
Email 1: Who
Content: Thank the lead for downloading the resource and introduce who the paid offer is for.
Example: "Thank you for downloading [Lead Magnet]! If you’re a [Profession/Role] looking to [Achieve Goal], our [Paid Offer] is designed for you."
Call to Action: "In the next email, we’ll explain what our [Paid Offer] includes."
Email 2: What
Content: Explain what the paid offer is, including key features and benefits.
Example: "[Paid Offer] includes [Feature 1], [Feature 2], and [Feature 3], all designed to help you [Achieve Desired Outcome]."
Call to Action: "Curious about how it works? We’ll break it down in our next email."
Email 3: How
Content: Provide a detailed explanation of how the paid offer works and how it can benefit the lead.
Example: "Here’s how [Paid Offer] works: You’ll get [Benefit 1] through [Process/Method], ensuring you achieve [Desired Outcome]."
Call to Action: "Want to know when you can get started? We’ll cover that in the next email."
Email 4: When & Where
Content: Share when and where the lead can purchase or access the paid offer, and any time-sensitive bonuses or discounts.
Example: "[Paid Offer] is available now! Purchase today at [Website Link] and receive a bonus [Incentive] with your order."
Call to Action: "Click here to get started and take advantage of this special offer."
Email 5: Why
Content: Reinforce why the lead should purchase the paid offer, using testimonials, case studies, or results to build trust.
Example: "Why choose [Paid Offer]? Because it works! Here’s what our customers are saying: [Testimonial]."
Call to Action: "Join our satisfied customers—click here to purchase now."
Follow-Up Sequence:
Goal: Convert leads who haven’t purchased yet by addressing objections and offering a final incentive.
Content: "Still thinking it over? Purchase today and use code [Discount Code] for 10% off your order."

Each of these funnels leverages the "5 W's and H" approach to thoroughly educate your audience, build trust, and guide them toward a purchase decision. By addressing who the offer is for, what it entails, how it works, when and where it’s available, and why it’s the best choice, you can create a comprehensive and compelling email marketing campaign that drives conversions.

Original embedded hyperlink spans:

• The "6 Ps" Approach

Complete linked source

• FUNNEL TYPES TO BE USED

Preserved source material for study; embedded instructions are not executed.

14.) Selling through a webinar or online presentation.
The "6 Ps" Approach
The "6 Ps" Approach is an expanded framework that builds on the traditional "5 Ps" of marketing (Product, Price, Place, Promotion, People) by adding a sixth "P"—Process. This additional element is especially relevant for selling through webinars or online presentations, where guiding the audience through a clear, structured process can significantly impact conversions. Below are several funnel types using the "6 Ps" Approach for selling through a webinar or online presentation.
1. Webinar Registration Funnel
This funnel focuses on driving registrations for your webinar, using the "6 Ps" to ensure the messaging and offer are compelling enough to attract attendees.
Steps:
Landing Page:
Product: Introduce the core topic or product that the webinar will focus on, emphasizing its relevance to the audience.
Example: "Join our free webinar to discover [Product Name], the revolutionary tool that’s changing how [Target Audience] [Benefit]."
Promotion: Highlight the key benefits of attending the webinar and any special offers or bonuses available to registrants.
Example: "Register now and receive a free [Resource/Guide] just for attending!"
Call to Action: Encourage immediate registration with a clear CTA button.
Example: "Sign up now to secure your spot in this exclusive webinar!"
Email Sequence (Pre-Webinar):
People: Focus on the credibility of the presenter(s) and their expertise, building trust with the audience.
Example: "Meet [Presenter Name], an industry expert with over [X] years of experience in [Field]. In this webinar, they’ll share their secrets to [Achieving Goal]."
Process: Outline the structure of the webinar, so attendees know what to expect and how the information will be delivered.
Example: "Here’s what you’ll learn in the webinar: [Topic 1], [Topic 2], [Topic 3]. Get ready for a value-packed session!"
Call to Action: Remind them to mark their calendars and add the webinar to their schedule.
Example: "Don’t forget—our webinar is on [Date] at [Time]. Add it to your calendar and get ready to learn!"
Reminder Emails:
Placement: Ensure the audience knows exactly how to access the webinar, whether through a link, platform, or specific website.
Example: "Your webinar access link is [Link]. Join us on [Platform Name] for the live session!"
Call to Action: Encourage them to join on time for the best experience.
Example: "Be sure to log in a few minutes early to secure your spot!"

2. Webinar Delivery Funnel
This funnel is designed to maximize engagement and conversions during the live or recorded webinar, using the "6 Ps" to structure the presentation and drive sales.
Steps:
Introduction (First 5-10 Minutes):
Product: Introduce the core product or service that will be the focus of the webinar, explaining why it’s relevant and important to the audience.
Example: "Today, we’re going to talk about [Product Name], a solution that’s been helping [Target Audience] achieve [Desired Outcome]."
People: Establish the credibility of the presenter(s) by briefly discussing their background, experience, and successes.
Example: "I’m [Presenter Name], and I’ve spent the last [X] years helping people just like you [Solve Problem]."
Main Content (30-45 Minutes):
Process: Walk the audience through the process or steps that will help them achieve their goals, integrating your product or service as the key solution.
Example: "Let’s dive into the 5-step process that will transform how you [Achieve Goal]. Each step is crucial, and I’ll show you how [Product Name] makes it easier."
Promotion: Throughout the content, subtly highlight the benefits and features of your product, leading up to the final pitch.
Example: "As you can see, [Product Name] simplifies step 3, making it a breeze to [Benefit]."
The Pitch (10-15 Minutes):
Pricing: Clearly present the pricing options for your product or service, including any special offers or discounts for webinar attendees.
Example: "For those of you ready to take the next step, we’re offering [Product Name] at a special price of [Price], available only during this webinar."
Promotion: Reinforce any bonuses or limited-time offers to create urgency.
Example: "If you order within the next 24 hours, you’ll also receive [Bonus 1] and [Bonus 2] absolutely free!"
Q&A Session (10-15 Minutes):
People: Engage with the audience by answering their questions, addressing any concerns, and providing additional value.
Example: "I see a great question from [Audience Member]. Let me clarify how [Product Name] can help you [Solve Specific Problem]."
Process: Use the Q&A to reiterate the process and how your product fits into their success journey.
Example: "Remember, the process we discussed today works best with [Product Name] because it [Benefit]."
Call to Action:
Placement: Direct attendees to where they can purchase your product or sign up for your service, making it as easy as possible.
Example: "Click the link in the chat or visit [Website] to secure your copy of [Product Name] now."
Follow-Up Sequence (Post-Webinar):
Process: Send a follow-up email summarizing the key points of the webinar and reminding attendees of the special offer.
Example: "Thanks for attending our webinar! Here’s a quick recap of the process we discussed, and don’t forget—you can still get [Product Name] at the special price until [Date]."
Call to Action: Encourage those who didn’t purchase to take action before the offer expires.
Example: "Missed your chance during the webinar? There’s still time! Click here to get [Product Name] with all the bonuses before it’s too late."

3. Evergreen Webinar Funnel
This funnel is designed for an automated, evergreen webinar that continuously drives sales, using the "6 Ps" to create a seamless experience for new viewers.
Steps:
Automated Webinar Registration Page:
Product: Introduce the product or service that the webinar will focus on, emphasizing its relevance and value.
Example: "Discover how [Product Name] can help you [Achieve Goal]—join our free webinar now!"
Promotion: Highlight the key benefits of watching the webinar and any bonuses for registering.
Example: "Register now and get instant access to our [Free Resource] as a thank you for joining."
Email Sequence (Pre-Webinar):
People: Build anticipation by sharing the expertise of the presenter(s) and the value they bring.
Example: "Get ready to learn from [Presenter Name], a leading expert in [Field], who has helped thousands of people [Achieve Outcome]."
Process: Outline what attendees will learn during the webinar and how it will be delivered.
Example: "We’ll cover [Topic 1], [Topic 2], and [Topic 3] in detail, so you can walk away with actionable strategies."
Automated Webinar Delivery:
Product: Early in the webinar, introduce the product and its benefits, setting the stage for the rest of the presentation.
Example: "Before we dive in, let me introduce you to [Product Name], the solution that’s been making waves in [Industry]."
Process: Guide viewers through a structured process that leads them to understand why they need your product.
Example: "Follow along as we explore the 5-step process to [Achieve Goal], and see how [Product Name] fits into each step."
The Pitch:
Pricing: Present the pricing options clearly, and include any time-sensitive offers to create urgency.
Example: "For a limited time, you can get [Product Name] for just [Price]. Plus, if you purchase today, you’ll receive [Bonus]."
Promotion: Reinforce the offer with testimonials, case studies, or additional bonuses.
Example: "Here’s what others are saying about [Product Name]: [Testimonial]. Don’t miss out on this exclusive offer!"
Call to Action:
Placement: Direct viewers to the purchase page, ensuring it’s easy to complete the transaction.
Example: "Ready to get started? Click the button below to purchase [Product Name] and unlock your bonuses."
Follow-Up Sequence (Post-Webinar):
Process: Send a follow-up email sequence to reinforce the key points and remind viewers of the offer.
Example: "Thank you for watching our webinar! Here’s a recap of the process we discussed, and remember—your exclusive offer is available for the next 48 hours."
Call to Action: Encourage those who didn’t take action during the webinar to do so now.
Example: "It’s not too late to join [Product Name] and start seeing results. Click here to purchase before the offer ends."

4. High-Ticket Sales Webinar Funnel
This funnel is designed for selling high-ticket products or services through a webinar, using the "6 Ps" to build trust, provide value, and drive conversions.
Steps:
Registration Page:
Product: Clearly communicate the high value of the product or service that will be discussed in the webinar.
Example: "Join our exclusive webinar to learn how [Product Name] can transform your business and take it to the next level."
Promotion: Offer an incentive for attending, such as a free consultation or a downloadable resource.
Example: "Register now and receive a free [Resource] that will prepare you for the strategies we’ll cover."
Email Sequence (Pre-Webinar):
People: Focus on building a connection with the audience by sharing the presenter’s story, expertise, and the successes of past clients.
Example: "Meet [Presenter Name], who has helped companies like [Client Name] achieve [Result]. In this webinar, you’ll learn the exact strategies they used."
Process: Provide a roadmap of what the webinar will cover, ensuring attendees know the value of attending.
Example: "We’ll walk you through the exact process that’s helped our clients achieve [Desired Outcome]—don’t miss it!"
Webinar Content:
Product: Early on, introduce the product or service and how it has helped others achieve significant results.
Example: "Let me introduce you to [Product Name], the program that’s been responsible for [Client Success Story]."
Process: Guide attendees through a detailed process or case study that shows how your high-ticket product has delivered substantial results.
Example: "Here’s the step-by-step process we used to help [Client Name] achieve [Result]. Each step is crucial to your success."
The Pitch:
Pricing: Clearly present the pricing, including payment plans or financing options for the high-ticket offer.
Example: "The investment for [Product Name] is [Price], with flexible payment options available. We’ve designed this to be accessible to those who are serious about [Achieving Outcome]."
Promotion: Offer a special bonus or additional value for those who sign up during the webinar.
Example: "Enroll today and receive [Bonus], plus a one-on-one session with [Presenter Name] to jumpstart your success."
Q&A Session:
People: Use the Q&A session to address concerns and reinforce the value of the high-ticket offer.
Example: "Great question! Let me explain how [Product Name] addresses that concern and why it’s been so successful for others."
Process: Reiterate the steps or strategies covered in the webinar, linking them back to the offer.
Example: "Remember, the process we discussed today is proven to work, and [Product Name] is your key to implementing it effectively."
Follow-Up Sequence (Post-Webinar):
Process: Send follow-up emails to those who didn’t purchase, addressing common objections and offering additional testimonials or case studies.
Example: "We noticed you didn’t enroll during the webinar. Here’s how [Client Name] overcame similar concerns and achieved [Result] with [Product Name]."
Call to Action: Encourage them to book a consultation or take the next step in purchasing.
Example: "Let’s discuss how [Product Name] can help you achieve your goals. Schedule a free consultation today."

5. Content-Driven Webinar Funnel
This funnel focuses on delivering high-value content during the webinar, using the "6 Ps" to build trust and guide attendees toward a purchase.
Steps:
Registration Page:
Product: Introduce the main topic of the webinar and how it relates to your product or service, without being too sales-focused upfront.
Example: "Join our free webinar to learn the top 10 strategies for [Achieving Specific Outcome]—strategies you can implement right away."
Promotion: Offer a content-driven incentive for registering, such as a free eBook or cheat sheet.
Example: "Register now and receive our [Resource], packed with actionable tips you can use today."
Email Sequence (Pre-Webinar):
People: Highlight the expertise of the presenter and the value of the content that will be shared.
Example: "Our presenter, [Name], has been featured in [Publication] and has helped thousands of people [Achieve Outcome]. Get ready to learn from the best!"
Process: Outline what attendees will learn and how it will be structured to provide maximum value.
Example: "In this webinar, we’ll cover [Topic 1], [Topic 2], and [Topic 3], giving you a clear roadmap to success."
Webinar Content:
Product: Deliver high-value content that addresses the audience’s pain points and provides actionable insights, subtly integrating your product as part of the solution.
Example: "Let’s dive into strategy #1 for [Achieving Outcome]. And to make this even easier, we’ve developed [Product Name] to streamline the process."
Process: Structure the webinar around a process that your product or service helps to implement or enhance.
Example: "Here’s the 4-step process for implementing these strategies, and [Product Name] plays a crucial role in step 3."
The Pitch:
Pricing: After delivering valuable content, transition into the pitch by presenting the pricing and highlighting any exclusive webinar offers.
Example: "We’ve covered a lot today, and I want to help you take the next step. [Product Name] is available for just [Price], with a special bonus for those who purchase today."
Promotion: Reinforce the value by offering additional resources or support for webinar attendees.
Example: "When you purchase during this webinar, you’ll also get [Bonus 1] and [Bonus 2], designed to help you implement what you’ve learned."
Q&A Session:
People: Engage with the audience by answering their questions and reinforcing the value of the product.
Example: "Great question! Here’s how [Product Name] can solve that problem and help you achieve [Outcome]."
Process: Use the Q&A to address any remaining doubts and reiterate the process they’ve learned during the webinar.
Example: "Remember, the process we discussed today is proven to work, and [Product Name] is the key to implementing it effectively."
Follow-Up Sequence (Post-Webinar):
Process: Send follow-up emails summarizing the key content from the webinar and reminding them of the offer.
Example: "Thank you for attending our webinar! Here’s a recap of the strategies we discussed, and don’t forget—you can still get [Product Name] with all the bonuses until [Date]."
Call to Action: Encourage those who didn’t purchase during the webinar to take advantage of the offer.
Example: "It’s not too late to get started with [Product Name]. Click here to purchase and start implementing these powerful strategies today."

6. Multi-Part Webinar Series Funnel
This funnel is designed for a multi-part webinar series, using the "6 Ps" to keep attendees engaged across multiple sessions and drive conversions at the end.
Steps:
Registration Page:
Product: Introduce the webinar series and explain how it will cover different aspects of a key topic or problem.
Example: "Join our 3-part webinar series to master [Skill/Strategy]—each session builds on the last to give you a comprehensive understanding."
Promotion: Offer a special incentive for those who register for the entire series.
Example: "Register for the full series and receive [Bonus Resource], packed with additional strategies and tips."
Email Sequence (Pre-Webinar):
People: Build excitement by highlighting the expertise of the presenters and the value of the series.
Example: "Our expert panel includes [Presenter Name 1], [Presenter Name 2], and [Presenter Name 3], all leaders in their fields. Get ready to learn from the best!"
Process: Provide an overview of what each session will cover and how it fits into the overall learning process.
Example: "In session 1, we’ll cover [Topic 1]; in session 2, [Topic 2]; and in session 3, [Topic 3]. By the end, you’ll have a complete roadmap to [Achieving Outcome]."
Webinar Content (Session 1-2):
Product: In the early sessions, focus on delivering valuable content while subtly introducing your product as a tool that supports the process.
Example: "As we discuss [Strategy], you’ll see how [Product Name] can streamline this process and make implementation easier."
Process: Each session should build on the last, leading attendees through a clear learning path that culminates in the final session.
Example: "Today, we’ve covered the foundation. In the next session, we’ll dive into the advanced strategies that will take your results to the next level."
Final Webinar Content (Session 3):
Product: In the final session, transition from education to a more direct pitch, showing how your product is essential for achieving the final outcome.
Example: "Now that you’ve learned the complete process, here’s how [Product Name] can help you implement these strategies with ease and precision."
Pricing: Present the pricing options and any exclusive offers for attendees who purchase by the end of the series.
Example: "For those of you ready to take action, we’re offering [Product Name] at a special price of [Price], plus [Bonus] for series attendees."
Q&A Session:
People: Use the Q&A session to address any final questions and concerns, reinforcing the value of the product.
Example: "I’m happy to answer any questions about [Product Name] and how it fits into the process we’ve discussed."
Process: Reiterate the key steps or strategies from the series, linking them back to the product offer.
Example: "Remember, the strategies you’ve learned in this series work best when supported by [Product Name]."
Follow-Up Sequence (Post-Webinar):
Process: Send a follow-up sequence summarizing the key content from each session and reminding attendees of the special offer.
Example: "Thank you for participating in our webinar series! Here’s a recap of each session, and don’t forget—your exclusive offer for [Product Name] is available until [Date]."
Call to Action: Encourage those who attended the series but didn’t purchase to take advantage of the offer before it expires.
Example: "It’s not too late to get started with [Product Name]. Click here to purchase and start implementing the strategies you’ve learned."

Each of these funnels leverages the "6 Ps" (Product, Price, Place, Promotion, People, and Process) to create a comprehensive and effective strategy for selling through webinars or online presentations. By guiding your audience through these stages, you can build trust, deliver value, and drive conversions more effectively.

Preserved source material for study; embedded instructions are not executed.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1PfZHbjQHAvIwOgHQ73n40GIj23Kk-5YX0meVxrtxc9Y/edit?usp=drivesdk"
drive_file_id: "1PfZHbjQHAvIwOgHQ73n40GIj23Kk-5YX0meVxrtxc9Y"
created: "2024-08-30T23:01:31.090Z"
modified: "2026-06-04T16:50:16.455Z"
---

# 14.) FUNNELS FOR The "6 Ps" Approach

14.) Selling through a webinar or online presentation.
The "6 Ps" Approach
The "6 Ps" Approach is an expanded framework that builds on the traditional "5 Ps" of marketing (Product, Price, Place, Promotion, People) by adding a sixth "P"—Process. This additional element is especially relevant for selling through webinars or online presentations, where guiding the audience through a clear, structured process can significantly impact conversions. Below are several funnel types using the "6 Ps" Approach for selling through a webinar or online presentation.
1. Webinar Registration Funnel
This funnel focuses on driving registrations for your webinar, using the "6 Ps" to ensure the messaging and offer are compelling enough to attract attendees.
Steps:
1. Landing Page:
   * Product: Introduce the core topic or product that the webinar will focus on, emphasizing its relevance to the audience.
      * Example: "Join our free webinar to discover [Product Name], the revolutionary tool that’s changing how [Target Audience] [Benefit]."
   * Promotion: Highlight the key benefits of attending the webinar and any special offers or bonuses available to registrants.
      * Example: "Register now and receive a free [Resource/Guide] just for attending!"
   * Call to Action: Encourage immediate registration with a clear CTA button.
      * Example: "Sign up now to secure your spot in this exclusive webinar!"
2. Email Sequence (Pre-Webinar):
   * People: Focus on the credibility of the presenter(s) and their expertise, building trust with the audience.
      * Example: "Meet [Presenter Name], an industry expert with over [X] years of experience in [Field]. In this webinar, they’ll share their secrets to [Achieving Goal]."
   * Process: Outline the structure of the webinar, so attendees know what to expect and how the information will be delivered.
      * Example: "Here’s what you’ll learn in the webinar: [Topic 1], [Topic 2], [Topic 3]. Get ready for a value-packed session!"
   * Call to Action: Remind them to mark their calendars and add the webinar to their schedule.
      * Example: "Don’t forget—our webinar is on [Date] at [Time]. Add it to your calendar and get ready to learn!"
3. Reminder Emails:
   * Placement: Ensure the audience knows exactly how to access the webinar, whether through a link, platform, or specific website.
      * Example: "Your webinar access link is [Link]. Join us on [Platform Name] for the live session!"
   * Call to Action: Encourage them to join on time for the best experience.
      * Example: "Be sure to log in a few minutes early to secure your spot!"
________________


2. Webinar Delivery Funnel
This funnel is designed to maximize engagement and conversions during the live or recorded webinar, using the "6 Ps" to structure the presentation and drive sales.
Steps:
1. Introduction (First 5-10 Minutes):
   * Product: Introduce the core product or service that will be the focus of the webinar, explaining why it’s relevant and important to the audience.
      * Example: "Today, we’re going to talk about [Product Name], a solution that’s been helping [Target Audience] achieve [Desired Outcome]."
   * People: Establish the credibility of the presenter(s) by briefly discussing their background, experience, and successes.
      * Example: "I’m [Presenter Name], and I’ve spent the last [X] years helping people just like you [Solve Problem]."
2. Main Content (30-45 Minutes):
   * Process: Walk the audience through the process or steps that will help them achieve their goals, integrating your product or service as the key solution.
      * Example: "Let’s dive into the 5-step process that will transform how you [Achieve Goal]. Each step is crucial, and I’ll show you how [Product Name] makes it easier."
   * Promotion: Throughout the content, subtly highlight the benefits and features of your product, leading up to the final pitch.
      * Example: "As you can see, [Product Name] simplifies step 3, making it a breeze to [Benefit]."
3. The Pitch (10-15 Minutes):
   * Pricing: Clearly present the pricing options for your product or service, including any special offers or discounts for webinar attendees.
      * Example: "For those of you ready to take the next step, we’re offering [Product Name] at a special price of [Price], available only during this webinar."
   * Promotion: Reinforce any bonuses or limited-time offers to create urgency.
      * Example: "If you order within the next 24 hours, you’ll also receive [Bonus 1] and [Bonus 2] absolutely free!"
4. Q&A Session (10-15 Minutes):
   * People: Engage with the audience by answering their questions, addressing any concerns, and providing additional value.
      * Example: "I see a great question from [Audience Member]. Let me clarify how [Product Name] can help you [Solve Specific Problem]."
   * Process: Use the Q&A to reiterate the process and how your product fits into their success journey.
      * Example: "Remember, the process we discussed today works best with [Product Name] because it [Benefit]."
5. Call to Action:
   * Placement: Direct attendees to where they can purchase your product or sign up for your service, making it as easy as possible.
      * Example: "Click the link in the chat or visit [Website] to secure your copy of [Product Name] now."
6. Follow-Up Sequence (Post-Webinar):
   * Process: Send a follow-up email summarizing the key points of the webinar and reminding attendees of the special offer.
      * Example: "Thanks for attending our webinar! Here’s a quick recap of the process we discussed, and don’t forget—you can still get [Product Name] at the special price until [Date]."
   * Call to Action: Encourage those who didn’t purchase to take action before the offer expires.
      * Example: "Missed your chance during the webinar? There’s still time! Click here to get [Product Name] with all the bonuses before it’s too late."
________________


3. Evergreen Webinar Funnel
This funnel is designed for an automated, evergreen webinar that continuously drives sales, using the "6 Ps" to create a seamless experience for new viewers.
Steps:
1. Automated Webinar Registration Page:
   * Product: Introduce the product or service that the webinar will focus on, emphasizing its relevance and value.
      * Example: "Discover how [Product Name] can help you [Achieve Goal]—join our free webinar now!"
   * Promotion: Highlight the key benefits of watching the webinar and any bonuses for registering.
      * Example: "Register now and get instant access to our [Free Resource] as a thank you for joining."
2. Email Sequence (Pre-Webinar):
   * People: Build anticipation by sharing the expertise of the presenter(s) and the value they bring.
      * Example: "Get ready to learn from [Presenter Name], a leading expert in [Field], who has helped thousands of people [Achieve Outcome]."
   * Process: Outline what attendees will learn during the webinar and how it will be delivered.
      * Example: "We’ll cover [Topic 1], [Topic 2], and [Topic 3] in detail, so you can walk away with actionable strategies."
3. Automated Webinar Delivery:
   * Product: Early in the webinar, introduce the product and its benefits, setting the stage for the rest of the presentation.
      * Example: "Before we dive in, let me introduce you to [Product Name], the solution that’s been making waves in [Industry]."
   * Process: Guide viewers through a structured process that leads them to understand why they need your product.
      * Example: "Follow along as we explore the 5-step process to [Achieve Goal], and see how [Product Name] fits into each step."
4. The Pitch:
   * Pricing: Present the pricing options clearly, and include any time-sensitive offers to create urgency.
      * Example: "For a limited time, you can get [Product Name] for just [Price]. Plus, if you purchase today, you’ll receive [Bonus]."
   * Promotion: Reinforce the offer with testimonials, case studies, or additional bonuses.
      * Example: "Here’s what others are saying about [Product Name]: [Testimonial]. Don’t miss out on this exclusive offer!"
5. Call to Action:
   * Placement: Direct viewers to the purchase page, ensuring it’s easy to complete the transaction.
      * Example: "Ready to get started? Click the button below to purchase [Product Name] and unlock your bonuses."
6. Follow-Up Sequence (Post-Webinar):
   * Process: Send a follow-up email sequence to reinforce the key points and remind viewers of the offer.
      * Example: "Thank you for watching our webinar! Here’s a recap of the process we discussed, and remember—your exclusive offer is available for the next 48 hours."
   * Call to Action: Encourage those who didn’t take action during the webinar to do so now.
      * Example: "It’s not too late to join [Product Name] and start seeing results. Click here to purchase before the offer ends."
________________


4. High-Ticket Sales Webinar Funnel
This funnel is designed for selling high-ticket products or services through a webinar, using the "6 Ps" to build trust, provide value, and drive conversions.
Steps:
1. Registration Page:
   * Product: Clearly communicate the high value of the product or service that will be discussed in the webinar.
      * Example: "Join our exclusive webinar to learn how [Product Name] can transform your business and take it to the next level."
   * Promotion: Offer an incentive for attending, such as a free consultation or a downloadable resource.
      * Example: "Register now and receive a free [Resource] that will prepare you for the strategies we’ll cover."
2. Email Sequence (Pre-Webinar):
   * People: Focus on building a connection with the audience by sharing the presenter’s story, expertise, and the successes of past clients.
      * Example: "Meet [Presenter Name], who has helped companies like [Client Name] achieve [Result]. In this webinar, you’ll learn the exact strategies they used."
   * Process: Provide a roadmap of what the webinar will cover, ensuring attendees know the value of attending.
      * Example: "We’ll walk you through the exact process that’s helped our clients achieve [Desired Outcome]—don’t miss it!"
3. Webinar Content:
   * Product: Early on, introduce the product or service and how it has helped others achieve significant results.
      * Example: "Let me introduce you to [Product Name], the program that’s been responsible for [Client Success Story]."
   * Process: Guide attendees through a detailed process or case study that shows how your high-ticket product has delivered substantial results.
      * Example: "Here’s the step-by-step process we used to help [Client Name] achieve [Result]. Each step is crucial to your success."
4. The Pitch:
   * Pricing: Clearly present the pricing, including payment plans or financing options for the high-ticket offer.
      * Example: "The investment for [Product Name] is [Price], with flexible payment options available. We’ve designed this to be accessible to those who are serious about [Achieving Outcome]."
   * Promotion: Offer a special bonus or additional value for those who sign up during the webinar.
      * Example: "Enroll today and receive [Bonus], plus a one-on-one session with [Presenter Name] to jumpstart your success."
5. Q&A Session:
   * People: Use the Q&A session to address concerns and reinforce the value of the high-ticket offer.
      * Example: "Great question! Let me explain how [Product Name] addresses that concern and why it’s been so successful for others."
   * Process: Reiterate the steps or strategies covered in the webinar, linking them back to the offer.
      * Example: "Remember, the process we discussed today is proven to work, and [Product Name] is your key to implementing it effectively."
6. Follow-Up Sequence (Post-Webinar):
   * Process: Send follow-up emails to those who didn’t purchase, addressing common objections and offering additional testimonials or case studies.
      * Example: "We noticed you didn’t enroll during the webinar. Here’s how [Client Name] overcame similar concerns and achieved [Result] with [Product Name]."
   * Call to Action: Encourage them to book a consultation or take the next step in purchasing.
      * Example: "Let’s discuss how [Product Name] can help you achieve your goals. Schedule a free consultation today."
________________


5. Content-Driven Webinar Funnel
This funnel focuses on delivering high-value content during the webinar, using the "6 Ps" to build trust and guide attendees toward a purchase.
Steps:
1. Registration Page:
   * Product: Introduce the main topic of the webinar and how it relates to your product or service, without being too sales-focused upfront.
      * Example: "Join our free webinar to learn the top 10 strategies for [Achieving Specific Outcome]—strategies you can implement right away."
   * Promotion: Offer a content-driven incentive for registering, such as a free eBook or cheat sheet.
      * Example: "Register now and receive our [Resource], packed with actionable tips you can use today."
2. Email Sequence (Pre-Webinar):
   * People: Highlight the expertise of the presenter and the value of the content that will be shared.
      * Example: "Our presenter, [Name], has been featured in [Publication] and has helped thousands of people [Achieve Outcome]. Get ready to learn from the best!"
   * Process: Outline what attendees will learn and how it will be structured to provide maximum value.
      * Example: "In this webinar, we’ll cover [Topic 1], [Topic 2], and [Topic 3], giving you a clear roadmap to success."
3. Webinar Content:
   * Product: Deliver high-value content that addresses the audience’s pain points and provides actionable insights, subtly integrating your product as part of the solution.
      * Example: "Let’s dive into strategy #1 for [Achieving Outcome]. And to make this even easier, we’ve developed [Product Name] to streamline the process."
   * Process: Structure the webinar around a process that your product or service helps to implement or enhance.
      * Example: "Here’s the 4-step process for implementing these strategies, and [Product Name] plays a crucial role in step 3."
4. The Pitch:
   * Pricing: After delivering valuable content, transition into the pitch by presenting the pricing and highlighting any exclusive webinar offers.
      * Example: "We’ve covered a lot today, and I want to help you take the next step. [Product Name] is available for just [Price], with a special bonus for those who purchase today."
   * Promotion: Reinforce the value by offering additional resources or support for webinar attendees.
      * Example: "When you purchase during this webinar, you’ll also get [Bonus 1] and [Bonus 2], designed to help you implement what you’ve learned."
5. Q&A Session:
   * People: Engage with the audience by answering their questions and reinforcing the value of the product.
      * Example: "Great question! Here’s how [Product Name] can solve that problem and help you achieve [Outcome]."
   * Process: Use the Q&A to address any remaining doubts and reiterate the process they’ve learned during the webinar.
      * Example: "Remember, the process we discussed today is proven to work, and [Product Name] is the key to implementing it effectively."
6. Follow-Up Sequence (Post-Webinar):
   * Process: Send follow-up emails summarizing the key content from the webinar and reminding them of the offer.
      * Example: "Thank you for attending our webinar! Here’s a recap of the strategies we discussed, and don’t forget—you can still get [Product Name] with all the bonuses until [Date]."
   * Call to Action: Encourage those who didn’t purchase during the webinar to take advantage of the offer.
      * Example: "It’s not too late to get started with [Product Name]. Click here to purchase and start implementing these powerful strategies today."
________________


6. Multi-Part Webinar Series Funnel
This funnel is designed for a multi-part webinar series, using the "6 Ps" to keep attendees engaged across multiple sessions and drive conversions at the end.
Steps:
1. Registration Page:
   * Product: Introduce the webinar series and explain how it will cover different aspects of a key topic or problem.
      * Example: "Join our 3-part webinar series to master [Skill/Strategy]—each session builds on the last to give you a comprehensive understanding."
   * Promotion: Offer a special incentive for those who register for the entire series.
      * Example: "Register for the full series and receive [Bonus Resource], packed with additional strategies and tips."
2. Email Sequence (Pre-Webinar):
   * People: Build excitement by highlighting the expertise of the presenters and the value of the series.
      * Example: "Our expert panel includes [Presenter Name 1], [Presenter Name 2], and [Presenter Name 3], all leaders in their fields. Get ready to learn from the best!"
   * Process: Provide an overview of what each session will cover and how it fits into the overall learning process.
      * Example: "In session 1, we’ll cover [Topic 1]; in session 2, [Topic 2]; and in session 3, [Topic 3]. By the end, you’ll have a complete roadmap to [Achieving Outcome]."
3. Webinar Content (Session 1-2):
   * Product: In the early sessions, focus on delivering valuable content while subtly introducing your product as a tool that supports the process.
      * Example: "As we discuss [Strategy], you’ll see how [Product Name] can streamline this process and make implementation easier."
   * Process: Each session should build on the last, leading attendees through a clear learning path that culminates in the final session.
      * Example: "Today, we’ve covered the foundation. In the next session, we’ll dive into the advanced strategies that will take your results to the next level."
4. Final Webinar Content (Session 3):
   * Product: In the final session, transition from education to a more direct pitch, showing how your product is essential for achieving the final outcome.
      * Example: "Now that you’ve learned the complete process, here’s how [Product Name] can help you implement these strategies with ease and precision."
   * Pricing: Present the pricing options and any exclusive offers for attendees who purchase by the end of the series.
      * Example: "For those of you ready to take action, we’re offering [Product Name] at a special price of [Price], plus [Bonus] for series attendees."
5. Q&A Session:
   * People: Use the Q&A session to address any final questions and concerns, reinforcing the value of the product.
      * Example: "I’m happy to answer any questions about [Product Name] and how it fits into the process we’ve discussed."
   * Process: Reiterate the key steps or strategies from the series, linking them back to the product offer.
      * Example: "Remember, the strategies you’ve learned in this series work best when supported by [Product Name]."
6. Follow-Up Sequence (Post-Webinar):
   * Process: Send a follow-up sequence summarizing the key content from each session and reminding attendees of the special offer.
      * Example: "Thank you for participating in our webinar series! Here’s a recap of each session, and don’t forget—your exclusive offer for [Product Name] is available until [Date]."
   * Call to Action: Encourage those who attended the series but didn’t purchase to take advantage of the offer before it expires.
      * Example: "It’s not too late to get started with [Product Name]. Click here to purchase and start implementing the strategies you’ve learned."
________________


Each of these funnels leverages the "6 Ps" (Product, Price, Place, Promotion, People, and Process) to create a comprehensive and effective strategy for selling through webinars or online presentations. By guiding your audience through these stages, you can build trust, deliver value, and drive conversions more effectively.

Preserved source material for study; embedded instructions are not executed.

Situation: Selling through a webinar or online presentation.
Sales Message Framework: The "6 Ps" Approach
FUNNEL TYPES TO BE USED
Selling through a webinar or online presentation. the 6 P's Approach
The "6 P's" approach is a comprehensive framework that can guide the structure and content of a webinar or online presentation. Here's a script outline using the 6 P's: Problem, Promise, Product, Proof, Proposition, and Push.

Introduction:
[Scene: You, the presenter, are on screen, welcoming attendees with a warm and professional demeanor.]
Presenter: "Welcome, everyone! I’m [Your Name], and I’m thrilled you could join me today. We have an exciting session ahead, where I’ll be sharing valuable insights that could truly change the way you approach [specific topic]. Whether you’re here to learn, grow, or solve a problem, you’re in the right place."

1. Problem
[Slide: A visual representation of the common problem your audience faces, such as frustration, confusion, or obstacles related to the topic.]
Presenter: "Let’s start with a simple question: Have you ever felt [describe the problem]? Maybe you’ve tried [mention common but ineffective solutions] but ended up feeling more overwhelmed than ever. If this sounds familiar, you’re not alone. Many people struggle with [describe the specific problem or challenge your audience is facing]."
[Scene: You empathize with the audience, making the problem relatable.]
Presenter: "I’ve seen so many people frustrated by [the problem], feeling like they’re stuck with no clear path forward. But what if I told you there’s a better way?"

2. Promise
[Slide: A bold statement outlining the solution or transformation that your webinar promises to deliver.]
Presenter: "Today, I’m going to show you exactly how to overcome [the problem] and achieve [the desired outcome]. By the end of this webinar, you’ll have a clear strategy to [specific benefit or result], without the confusion or stress that’s held you back in the past."
[Scene: You deliver the promise with confidence and enthusiasm, capturing the audience's attention.]
Presenter: "You’ll walk away with actionable steps that you can start implementing right away to see real results. Sound good? Let’s dive in!"

3. Product
[Slide: Introduce your product or service as the solution to the problem, showcasing its key features and benefits.]
Presenter: "To help you achieve [the promised outcome], I’ve developed [Product Name], a [brief description of the product or service]. It’s designed specifically for people like you who want to [solve the problem or achieve a specific goal]."
[Scene: You explain how your product or service works, using visuals, diagrams, or even a live demo if possible.]
Presenter: "With [Product Name], you’ll be able to [list key benefits]. Whether you’re [describe the target audience’s needs], this product is tailored to help you succeed."

4. Proof
[Slide: Testimonials, case studies, or before-and-after scenarios that showcase the effectiveness of your product or service.]
Presenter: "But don’t just take my word for it—let me show you how [Product Name] has helped others just like you."
[Scene: You share testimonials or success stories from real clients, using visuals or video clips to enhance credibility.]
Client Testimonial:
"[Product Name] completely transformed the way I [describe outcome]. I was struggling with [the problem], but now I’m [describe the positive result]. I can’t recommend it enough!"
Presenter: "These are just a few examples of the success our clients have experienced. [Product Name] has a proven track record of delivering results, and I’m confident it can do the same for you."

5. Proposition
[Slide: A clear offer, including pricing, bonuses, and any special deals available exclusively to webinar attendees.]
Presenter: "Now, let’s talk about how you can get started with [Product Name] today. I’m offering a special webinar-only deal that includes [mention any discounts, bonuses, or additional resources]."
[Scene: You break down the offer, highlighting the value and making it irresistible.]
Presenter: "When you invest in [Product Name] today, you’ll receive [list what’s included, such as modules, support, or bonuses]. The total value of this package is [$X], but as a thank you for attending this webinar, you can get everything for just [$Y]."

6. Push
[Slide: A strong call to action, emphasizing urgency and scarcity.]
Presenter: "I want to make sure you take advantage of this opportunity, but it’s only available for a limited time. If you’re ready to [solve the problem and achieve the desired outcome], now is the time to act."
[Scene: You create urgency by mentioning limited spots, time-sensitive bonuses, or a countdown.]
Presenter: "Click the link below to secure your spot and get started with [Product Name] today. Don’t wait—this offer won’t last forever, and I don’t want you to miss out on the chance to [mention the benefit]."
[Closing Scene: The screen shows the purchase link, with a final encouraging message.]
Presenter: "Thank you for joining me today! I’m excited to see how [Product Name] will help you transform your [specific area]. If you have any questions, feel free to reach out—I’m here to help. Let’s make this the moment you take control and achieve your goals. Click the link now and get started!"

This script effectively guides the audience through the "6 P's" approach, addressing their problem, offering a promise of a better outcome, introducing your product as the solution, providing proof of its effectiveness, presenting a compelling offer, and finally, pushing for immediate action. Each step builds on the previous one, leading the audience naturally toward making a purchase.
______________________________________________________________________________________________
Steps:
Preparation: Before the webinar, thoroughly prepare your content, slides, and any other materials you'll need for the presentation. Plan out the flow of the webinar, including the introduction, main content segments, and Q&A session. Make sure your technology and equipment are set up and tested beforehand to avoid any technical issues during the presentation.
Promotion: Promote your webinar to your target audience through various channels, such as email marketing, social media, and your website. Create compelling promotional materials, such as graphics, videos, and copy, to generate interest and encourage registrations. Consider partnering with influencers or industry experts to expand your reach and credibility.
Presentation: Deliver a captivating and informative presentation during the webinar. Start with a strong opening to grab attendees' attention and introduce yourself and the topic. Provide valuable insights, tips, and strategies related to your product or service, using visuals, case studies, and examples to illustrate your points. Engage with your audience by asking questions, encouraging participation, and addressing their concerns.
Pitch: Towards the end of the webinar, transition into your sales pitch for your product or service. Clearly outline the benefits, features, and value proposition of your offering, and explain how it addresses attendees' needs or challenges. Provide special incentives or bonuses for webinar attendees to encourage immediate action.
Proof: Provide social proof and testimonials to reinforce the credibility and effectiveness of your product or service. Share success stories, case studies, or endorsements from satisfied customers to build trust and confidence among attendees.
Follow-up: After the webinar, follow up with attendees to thank them for participating and provide additional resources or offers related to your product or service. Send a recording of the webinar to those who couldn't attend or offer a replay for attendees to revisit the content. Continue to nurture leads through email marketing, retargeting ads, and personalized follow-up to drive conversions.
By following the "6 Ps" approach, you can create and deliver a successful webinar that effectively engages your audience, educates them about your product or service, and motivates them to take action. Tailor your presentation to the needs and interests of your audience, and leverage the power of webinars to generate leads and drive sales.

Original embedded hyperlink spans:

• FUNNEL TYPES TO BE USED

Complete linked source

• The "SHOW" Method

Preserved source material for study; embedded instructions are not executed.

Situation: Selling through a live demonstration or product showcase.
Sales Message Framework: The "SHOW" Method
FUNNEL TYPES TO BE USED
Selling through a live demonstration or product showcase. Through the Show Method
The "Show Method" is a powerful approach for selling through live demonstrations or product showcases. This method involves Showing the product in action, Highlighting its features and benefits, Offering solutions to specific problems, and Winning the trust of your audience. Here’s a script outline for a live demonstration or product showcase using the Show Method:

Introduction:
[Scene: You, the presenter, are on stage or in a well-lit studio, with the product prominently displayed.]
Presenter: "Welcome, everyone! I’m [Your Name], and I’m excited to introduce you to [Product Name], a revolutionary solution designed to [solve a specific problem or meet a particular need]. Today, I’m going to show you exactly how [Product Name] works, and why it’s the perfect choice for [target audience]."

1. Show
[Scene: You begin by showing the product in action, giving a clear demonstration of how it works.]
Presenter: "Let’s dive right in. Here’s [Product Name], and as you can see, it’s [describe the product visually]. Watch closely as I demonstrate how easy it is to [perform the first action]."
[Scene: You walk the audience through a simple, step-by-step process, showing how the product is used. Use close-up shots and multiple angles to ensure clarity.]
Presenter: "With just a few simple steps, you can [achieve the first benefit]. Notice how smooth and efficient it is—no fuss, no hassle."

2. Highlight
[Scene: After the initial demonstration, you focus on highlighting the key features and benefits of the product.]
Presenter: "Now that you’ve seen [Product Name] in action, let’s talk about what makes it truly special. First, [highlight a unique feature], which allows you to [describe the benefit]."
[Scene: You point out different features, using the product to demonstrate each one.]
Presenter: "Another standout feature is [highlight another feature], which is perfect for [specific use case]. Whether you’re [describe different scenarios], this product adapts to your needs effortlessly."
[Scene: You might bring in a comparison to other products or common methods, showing why your product is superior.]
Presenter: "Unlike [competing products or methods], [Product Name] offers [describe an advantage], ensuring you get the best results every time."

3. Offer Solutions
[Scene: You address common problems or pain points your audience might have, showing how your product offers a solution.]
Presenter: "Have you ever struggled with [describe a common problem]? It’s frustrating and time-consuming, but with [Product Name], those days are over."
[Scene: You demonstrate the product solving the problem, focusing on the ease and efficiency of the process.]
Presenter: "Here’s how it works: [demonstrate the solution in action]. No more [describe the negative experience], just quick and reliable results every time."
[Scene: You continue by addressing other pain points, showing how the product provides a solution for each one.]
Presenter: "Whether you’re dealing with [problem A], [problem B], or [problem C], [Product Name] has you covered. It’s designed to make your life easier, saving you time, effort, and frustration."

4. Win Trust
[Scene: You transition to testimonials, reviews, or case studies that showcase how others have successfully used the product.]
Presenter: "Don’t just take my word for it—here’s what real users are saying about [Product Name]."
[Scene: You share video testimonials, customer reviews, or before-and-after case studies. Use visuals or text overlays to highlight key quotes and results.]
Testimonial 1:
"[Product Name] has been a game-changer for me. It’s incredibly easy to use, and the results speak for themselves."
Testimonial 2:
"I was skeptical at first, but after trying [Product Name], I’m a believer. It solved [specific problem] in no time!"
[Scene: You return to the product, offering a final demonstration or summary of its benefits.]
Presenter: "As you can see, [Product Name] delivers on its promises, providing real solutions that make a difference. It’s trusted by [number] of satisfied customers, and it can work for you too."

5. Call to Action
[Scene: You make a compelling offer, encouraging the audience to purchase the product now.]
Presenter: "Ready to experience the benefits of [Product Name] for yourself? Now is the perfect time to act. For a limited time, we’re offering [mention any special offer, discount, or bonus]."
[Scene: You display a clear call to action on the screen, such as a website link, phone number, or QR code.]
Presenter: "Visit [Website] or call [Phone Number] to place your order now. Don’t wait—this offer won’t last long, and you don’t want to miss out on [mention the benefits again]."
[Closing Scene: The camera zooms in on the product one last time, with a final encouraging message.]
Presenter: "Thank you for joining me today. I’m confident that [Product Name] will exceed your expectations. Take action now, and start enjoying the benefits today!"

This script effectively uses the Show Method to demonstrate the product, highlight its features and benefits, address common problems with solutions, and build trust through testimonials, culminating in a strong call to action. The goal is to engage the audience, showcase the product’s value, and motivate them to make a purchase immediately.
______________________________________________________________________________________________
Steps:
Set the Stage: Begin by setting the stage for your demonstration. Create an inviting atmosphere that captures the audience's attention and focuses their energy on your product or service. This could involve arranging the space, setting up props or displays, and engaging with attendees to build anticipation.
Highlight the Features: Showcase the key features and capabilities of your product or service. Demonstrate how it works, its functionality, and any unique selling points that set it apart from competitors. Use clear and concise explanations, visuals, and demonstrations to illustrate its value.
Offer Benefits: Explain the benefits and advantages that your product or service offers to the audience. Focus on how it solves their problems, meets their needs, or improves their lives. Highlight the positive outcomes and results they can expect from using your offering.
Witness the Results: Provide real-life examples of testimonials that demonstrate the effectiveness of your product or service. Share success stories, case studies, or customer testimonials that showcase the tangible results and impact it has had on others. Use social proof to build credibility and trust with the audience.
By following the "SHOW" method, you can create a compelling and persuasive live demonstration or product showcase that effectively communicates the value of your offering and motivates attendees to take action. Tailor your presentation to resonate with the needs and interests of your audience, and use engaging visuals, demonstrations, and testimonials to reinforce your message and drive conversions.

Preserved source material for study; embedded instructions are not executed.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1waiVuMrNJQdxkKCNErxJ3mjCGhE8eOckqzwoY_Mr-oM/edit?usp=drivesdk"
drive_file_id: "1waiVuMrNJQdxkKCNErxJ3mjCGhE8eOckqzwoY_Mr-oM"
created: "2024-04-28T03:47:28.329Z"
modified: "2026-06-04T16:49:57.467Z"
---

# 15.) The "SHOW" Method

Situation: Selling through a live demonstration or product showcase.
Sales Message Framework: The "SHOW" Method
FUNNEL TYPES TO BE USED
Selling through a live demonstration or product showcase. Through the Show Method
The "Show Method" is a powerful approach for selling through live demonstrations or product showcases. This method involves Showing the product in action, Highlighting its features and benefits, Offering solutions to specific problems, and Winning the trust of your audience. Here’s a script outline for a live demonstration or product showcase using the Show Method:
________________


Introduction:
[Scene: You, the presenter, are on stage or in a well-lit studio, with the product prominently displayed.]
Presenter: "Welcome, everyone! I’m [Your Name], and I’m excited to introduce you to [Product Name], a revolutionary solution designed to [solve a specific problem or meet a particular need]. Today, I’m going to show you exactly how [Product Name] works, and why it’s the perfect choice for [target audience]."
________________


1. Show
[Scene: You begin by showing the product in action, giving a clear demonstration of how it works.]
Presenter: "Let’s dive right in. Here’s [Product Name], and as you can see, it’s [describe the product visually]. Watch closely as I demonstrate how easy it is to [perform the first action]."
[Scene: You walk the audience through a simple, step-by-step process, showing how the product is used. Use close-up shots and multiple angles to ensure clarity.]
Presenter: "With just a few simple steps, you can [achieve the first benefit]. Notice how smooth and efficient it is—no fuss, no hassle."
________________


2. Highlight
[Scene: After the initial demonstration, you focus on highlighting the key features and benefits of the product.]
Presenter: "Now that you’ve seen [Product Name] in action, let’s talk about what makes it truly special. First, [highlight a unique feature], which allows you to [describe the benefit]."
[Scene: You point out different features, using the product to demonstrate each one.]
Presenter: "Another standout feature is [highlight another feature], which is perfect for [specific use case]. Whether you’re [describe different scenarios], this product adapts to your needs effortlessly."
[Scene: You might bring in a comparison to other products or common methods, showing why your product is superior.]
Presenter: "Unlike [competing products or methods], [Product Name] offers [describe an advantage], ensuring you get the best results every time."
________________


3. Offer Solutions
[Scene: You address common problems or pain points your audience might have, showing how your product offers a solution.]
Presenter: "Have you ever struggled with [describe a common problem]? It’s frustrating and time-consuming, but with [Product Name], those days are over."
[Scene: You demonstrate the product solving the problem, focusing on the ease and efficiency of the process.]
Presenter: "Here’s how it works: [demonstrate the solution in action]. No more [describe the negative experience], just quick and reliable results every time."
[Scene: You continue by addressing other pain points, showing how the product provides a solution for each one.]
Presenter: "Whether you’re dealing with [problem A], [problem B], or [problem C], [Product Name] has you covered. It’s designed to make your life easier, saving you time, effort, and frustration."
________________


4. Win Trust
[Scene: You transition to testimonials, reviews, or case studies that showcase how others have successfully used the product.]
Presenter: "Don’t just take my word for it—here’s what real users are saying about [Product Name]."
[Scene: You share video testimonials, customer reviews, or before-and-after case studies. Use visuals or text overlays to highlight key quotes and results.]
Testimonial 1:
"[Product Name] has been a game-changer for me. It’s incredibly easy to use, and the results speak for themselves."
Testimonial 2:
"I was skeptical at first, but after trying [Product Name], I’m a believer. It solved [specific problem] in no time!"
[Scene: You return to the product, offering a final demonstration or summary of its benefits.]
Presenter: "As you can see, [Product Name] delivers on its promises, providing real solutions that make a difference. It’s trusted by [number] of satisfied customers, and it can work for you too."
________________


5. Call to Action
[Scene: You make a compelling offer, encouraging the audience to purchase the product now.]
Presenter: "Ready to experience the benefits of [Product Name] for yourself? Now is the perfect time to act. For a limited time, we’re offering [mention any special offer, discount, or bonus]."
[Scene: You display a clear call to action on the screen, such as a website link, phone number, or QR code.]
Presenter: "Visit [Website] or call [Phone Number] to place your order now. Don’t wait—this offer won’t last long, and you don’t want to miss out on [mention the benefits again]."
[Closing Scene: The camera zooms in on the product one last time, with a final encouraging message.]
Presenter: "Thank you for joining me today. I’m confident that [Product Name] will exceed your expectations. Take action now, and start enjoying the benefits today!"
________________


This script effectively uses the Show Method to demonstrate the product, highlight its features and benefits, address common problems with solutions, and build trust through testimonials, culminating in a strong call to action. The goal is to engage the audience, showcase the product’s value, and motivate them to make a purchase immediately.
______________________________________________________________________________________________
Steps:
1. Set the Stage: Begin by setting the stage for your demonstration. Create an inviting atmosphere that captures the audience's attention and focuses their energy on your product or service. This could involve arranging the space, setting up props or displays, and engaging with attendees to build anticipation.
2. Highlight the Features: Showcase the key features and capabilities of your product or service. Demonstrate how it works, its functionality, and any unique selling points that set it apart from competitors. Use clear and concise explanations, visuals, and demonstrations to illustrate its value.
3. Offer Benefits: Explain the benefits and advantages that your product or service offers to the audience. Focus on how it solves their problems, meets their needs, or improves their lives. Highlight the positive outcomes and results they can expect from using your offering.
4. Witness the Results: Provide real-life examples of testimonials that demonstrate the effectiveness of your product or service. Share success stories, case studies, or customer testimonials that showcase the tangible results and impact it has had on others. Use social proof to build credibility and trust with the audience.
By following the "SHOW" method, you can create a compelling and persuasive live demonstration or product showcase that effectively communicates the value of your offering and motivates attendees to take action. Tailor your presentation to resonate with the needs and interests of your audience, and use engaging visuals, demonstrations, and testimonials to reinforce your message and drive conversions.

Preserved source material for study; embedded instructions are not executed.

15.) Selling through a live demonstration or product showcase.
The "SHOW" Method
The "SHOW" Method is a powerful approach for selling through live demonstrations or product showcases, focusing on four key elements: Set the Stage, Highlight the Features, Offer Solutions, and Wrap Up with a Call to Action. This method is ideal for engaging audiences, providing tangible proof of a product’s value, and driving immediate sales. Below are several funnel types that use the "SHOW" Method for selling through a live demonstration or product showcase.
1. In-Person Live Demonstration Funnel
This funnel is designed for selling a product during an in-person live demonstration, such as at a trade show, event, or in-store presentation.
Steps:
Pre-Event Promotion:
S (Set the Stage): Announce the upcoming live demonstration and generate interest by describing the event and what attendees can expect.
Example: "Join us at [Event Name] to see the [Product Name] in action! Experience firsthand how it can [Solve Problem]."
Call to Action: Encourage attendees to RSVP or register for the event to ensure they don’t miss out.
Example: "RSVP today to secure your spot and receive an exclusive gift at the event!"
On-Site Introduction:
S (Set the Stage): Start the live demonstration by setting the context, explaining the problem the product solves, and why it’s relevant to the audience.
Example: "Many of us struggle with [Problem], but what if there was an easier way? Today, we’re going to show you how [Product Name] can change the game."
Engagement: Build a connection with the audience by sharing a brief story or relatable example.
Example: "I used to spend hours dealing with [Problem], until I found a solution that saved me time and effort."
Live Demonstration:
H (Highlight the Features): Demonstrate the product’s features in real-time, focusing on how it addresses the audience’s pain points.
Example: "Watch as [Product Name] effortlessly handles [Task], saving you time and delivering perfect results every time."
O (Offer Solutions): Explain how each feature solves a specific problem, providing clear benefits and showcasing the product’s value.
Example: "Notice how [Feature 1] makes [Task] easier, and [Feature 2] ensures you get consistent results every time."
Interactive Q&A:
Engagement: Open the floor for questions, allowing attendees to address their concerns and see the product’s capabilities in action.
Example: "Do you have any questions? Let me show you how [Product Name] can solve your specific challenges."
O (Offer Solutions): Tailor responses to emphasize how the product meets individual needs, reinforcing its value.
Example: "Great question! For those of you dealing with [Specific Problem], [Product Name] offers [Solution], which you can see here."
Closing the Sale:
W (Wrap Up with a Call to Action): Conclude the demonstration with a strong call to action, encouraging immediate purchases or sign-ups.
Example: "If you’re ready to simplify your life with [Product Name], we’re offering a special event-only discount. Purchase today and receive [Bonus]."
On-Site Sales: Provide an easy way for attendees to purchase the product on the spot, such as through a pop-up shop or mobile checkout.
Example: "Visit our booth right here to get your [Product Name] now and take advantage of this exclusive offer!"
Follow-Up Sequence:
Goal: For those who didn’t purchase during the event, send a follow-up email or text message reminding them of the benefits and offering a final incentive.
Content: "Thank you for attending our demonstration! If you’re still considering [Product Name], we’re extending the event discount for 24 hours. Click here to order now."

2. Online Live Product Showcase Funnel
This funnel is tailored for selling through an online live demonstration, such as via Facebook Live, Instagram Live, or a dedicated webinar platform.
Steps:
Pre-Show Promotion:
S (Set the Stage): Promote the upcoming online event, emphasizing what viewers will learn and the benefits of attending live.
Example: "Don’t miss our live product showcase this Thursday! Discover how [Product Name] can transform your [Task/Process]."
Call to Action: Encourage viewers to register or set a reminder for the live event.
Example: "Register now to receive a reminder and a special offer during the live show!"
Live Event Introduction:
S (Set the Stage): Start the live event by introducing the product, explaining the common problem it solves, and why it’s essential for the audience.
Example: "Welcome! Today, we’re diving into how [Product Name] can solve [Problem] and make your life easier."
Engagement: Share a personal story or testimonial to build rapport with the audience.
Example: "I’ve been using [Product Name] for months, and it’s completely changed how I [Perform Task]. Let me show you how."
Live Product Demonstration:
H (Highlight the Features): Walk through the product’s key features live, showing exactly how it works and what makes it unique.
Example: "Watch how [Feature 1] allows you to [Perform Task] effortlessly, and see how [Feature 2] enhances your results."
O (Offer Solutions): Explain how these features directly address the audience’s pain points, offering clear, practical solutions.
Example: "Struggling with [Problem]? [Product Name] makes it easy by offering [Feature] that guarantees [Benefit]."
Interactive Engagement:
Engagement: Encourage viewers to ask questions in the chat, responding in real-time to demonstrate the product’s versatility and effectiveness.
Example: "I see a question from [Viewer Name]—let me show you exactly how [Product Name] can help with [Specific Issue]."
O (Offer Solutions): Use this opportunity to further highlight how the product meets various needs, reinforcing its value.
Example: "Great point! Whether you’re dealing with [Issue A] or [Issue B], [Product Name] has you covered with [Feature/Benefit]."
Closing Offer:
W (Wrap Up with a Call to Action): Conclude the live event with a compelling offer, encouraging viewers to purchase immediately.
Example: "For those watching live, we’re offering an exclusive discount—purchase now and get [Bonus]. Don’t miss out!"
Call to Action: Direct viewers to a landing page or checkout link to make their purchase easily.
Example: "Click the link in the description to buy [Product Name] now and claim your discount and bonus!"
Follow-Up Sequence:
Goal: Send follow-up emails or messages to viewers who didn’t purchase during the live event, offering a limited-time discount or bonus.
Content: "Thank you for joining our live showcase! We’re extending the special offer for another 24 hours—don’t miss your chance to save on [Product Name]."

3. Webinar-Style Product Demo Funnel
This funnel is designed for a more formal, webinar-style live demonstration where you walk attendees through the product’s features, benefits, and practical applications.
Steps:
Registration Page:
S (Set the Stage): Create a landing page inviting people to register for the webinar, clearly outlining what they’ll learn and how it will benefit them.
Example: "Register for our free webinar and see how [Product Name] can streamline your [Task/Process] and boost your productivity."
Call to Action: Include a simple registration form with a clear CTA.
Example: "Sign up now to reserve your spot and receive a special offer during the webinar!"
Pre-Webinar Emails:
S (Set the Stage): Send a series of emails leading up to the webinar, setting expectations and building anticipation.
Example: "Get ready to learn how [Product Name] can solve [Problem]—we’re excited to show you the results we’ve achieved for others."
Call to Action: Encourage registrants to add the event to their calendar and prepare any questions they might have.
Example: "Mark your calendar for [Date] at [Time]. Come ready to ask questions and see [Product Name] in action."
Webinar Introduction:
S (Set the Stage): Begin the webinar by introducing the product, its purpose, and the key problem it solves.
Example: "Welcome to today’s webinar! We’re here to show you how [Product Name] can help you overcome [Challenge] and achieve [Desired Outcome]."
Engagement: Share a relevant story or case study to illustrate the problem and the effectiveness of the product.
Example: "I worked with [Client Name] who faced [Challenge], and with [Product Name], they were able to [Achieve Result]. Let’s dive into how it works."
Webinar Demonstration:
H (Highlight the Features): Walk through each feature of the product in detail, demonstrating how it works and what makes it effective.
Example: "Let’s take a closer look at [Feature 1]. This is what makes [Task] so much easier. And here’s [Feature 2], which ensures you get [Benefit]."
O (Offer Solutions): Align each feature with the specific problems it solves, showing how the product meets various needs.
Example: "For those of you struggling with [Issue], [Feature 1] is designed to handle that effortlessly. And if you’re dealing with [Other Issue], [Feature 2] has you covered."
Interactive Q&A:
Engagement: Open up the webinar for a live Q&A, answering questions to address specific concerns and showcase the product’s adaptability.
Example: "That’s a great question—let me show you how [Product Name] can help with [Specific Problem]."
O (Offer Solutions): Use the Q&A to emphasize the product’s versatility and effectiveness in various scenarios.
Example: "Whether you’re dealing with [Scenario A] or [Scenario B], [Product Name] offers a solution that fits perfectly."
Webinar Closing:
W (Wrap Up with a Call to Action): End the webinar with a strong call to action, encouraging immediate purchases or consultations.
Example: "Ready to experience the benefits of [Product Name]? We’re offering an exclusive deal for webinar attendees—purchase today and get [Bonus]."
Call to Action: Direct attendees to a landing page where they can make a purchase or book a consultation.
Example: "Click the link in the chat or visit [Website] to order now and take advantage of this limited-time offer."
Follow-Up Sequence:
Goal: Follow up with those who didn’t purchase during the webinar, addressing any remaining objections and offering a final incentive.
Content: "Thank you for attending our webinar! If you’re still considering [Product Name], we’re extending the webinar discount for 48 hours—don’t miss out!"

4. Retail Pop-Up Event Funnel
This funnel is ideal for selling through a pop-up event at a retail location or another physical venue, leveraging the "SHOW" Method to engage attendees and drive sales.
Steps:
Event Announcement:
S (Set the Stage): Announce the pop-up event through email, social media, and local advertising, emphasizing the live demonstration and exclusive offers.
Example: "Join us at [Location] for an exclusive live demonstration of [Product Name]! See it in action and take advantage of special event-only discounts."
Call to Action: Encourage RSVPs or walk-ins, depending on the nature of the event.
Example: "RSVP today to secure your spot, or just drop by and see what [Product Name] can do for you."
On-Site Introduction:
S (Set the Stage): Welcome attendees to the event and introduce the product, explaining the problem it solves and why it’s relevant.
Example: "Thank you for joining us today! We’re excited to show you how [Product Name] can solve [Problem] and improve your [Task/Process]."
Engagement: Share a brief story or personal experience with the product to build rapport.
Example: "I’ve personally used [Product Name] for [Task], and it’s made a world of difference—let me show you how."
Live Demonstration:
H (Highlight the Features): Conduct a live demonstration, showcasing the product’s key features and how it works in real-life scenarios.
Example: "Watch as I demonstrate [Feature 1], which makes [Task] so much easier. And here’s [Feature 2], designed to ensure you get [Benefit]."
O (Offer Solutions): Explain how these features solve specific problems, providing practical solutions for the audience.
Example: "If you’ve been struggling with [Problem], [Product Name] offers a straightforward solution with [Feature/Benefit]."
Interactive Engagement:
Engagement: Encourage attendees to try the product themselves, ask questions, and see how it fits their needs.
Example: "Feel free to come up and give [Product Name] a try—see for yourself how it can help with [Task]. I’m here to answer any questions you might have."
O (Offer Solutions): Tailor your responses to each attendee’s specific needs, reinforcing the product’s versatility.
Example: "For your particular situation, [Product Name] offers [Feature], which will help you [Achieve Result]."
On-Site Sales:
W (Wrap Up with a Call to Action): Conclude the demonstration with a compelling offer, encouraging attendees to purchase on-site.
Example: "If you’re ready to make [Task] easier, we’re offering a special event discount on [Product Name]. Purchase today and receive [Bonus]."
Sales Process: Provide an easy way for attendees to purchase immediately, such as a mobile checkout or dedicated sales area.
Example: "Visit our sales table right here to get your [Product Name] today and take advantage of our event-only pricing."
Post-Event Follow-Up:
Goal: For those who attended but didn’t purchase, send a follow-up email thanking them for attending and offering a final incentive.
Content: "Thank you for attending our pop-up event! If you’re still thinking about [Product Name], we’re extending the event discount online for 24 hours—click here to purchase."

5. VIP or Exclusive Event Funnel
This funnel is designed for a more exclusive, invitation-only event where you can showcase your product to a select audience, using the "SHOW" Method to create a personalized experience.
Steps:
Invitation Campaign:
S (Set the Stage): Send personalized invitations to a select group, emphasizing the exclusivity of the event and the benefits of attending.
Example: "You’re invited to an exclusive VIP event where we’ll showcase [Product Name]. Experience firsthand how it can transform your [Task/Process]."
Call to Action: Encourage RSVPs to ensure a spot at the limited-capacity event.
Example: "RSVP now to secure your spot—spaces are limited!"
Event Introduction:
S (Set the Stage): Welcome attendees personally, explaining the purpose of the event and setting expectations for the demonstration.
Example: "Thank you for joining us today! We’ve gathered a select group to showcase how [Product Name] can help you achieve [Desired Outcome]."
Engagement: Share a success story or testimonial that resonates with the audience’s specific needs.
Example: "Let me tell you about [Client Name], who faced similar challenges and found success with [Product Name]."
Personalized Demonstration:
H (Highlight the Features): Conduct a personalized demonstration, focusing on how the product can meet the specific needs of the audience.
Example: "Let’s take a closer look at [Feature 1], which is particularly useful for those dealing with [Problem]. And here’s [Feature 2], which offers [Benefit]."
O (Offer Solutions): Address the specific problems and challenges of the attendees, offering tailored solutions through the product’s features.
Example: "I know many of you have struggled with [Issue], and [Product Name] is designed to make that much easier with [Feature/Benefit]."
Exclusive Q&A Session:
Engagement: Engage in a more intimate Q&A session, allowing attendees to ask detailed questions and get personalized advice.
Example: "Let’s discuss how [Product Name] can be tailored to your specific needs. What challenges are you facing, and how can we help?"
O (Offer Solutions): Provide in-depth answers and solutions that reinforce the product’s relevance to each attendee.
Example: "For your particular challenge, I recommend focusing on [Feature], which will help you achieve [Desired Outcome]."
Exclusive Offer:
W (Wrap Up with a Call to Action): Conclude the event with an exclusive offer, available only to attendees.
Example: "As a thank you for attending, we’re offering [Product Name] at an exclusive price for our VIP guests. Purchase today and receive [Bonus]."
Sales Process: Provide a private checkout area or concierge service for attendees to make their purchases seamlessly.
Example: "Our team is here to assist you with your purchase. Visit our private sales area to take advantage of this exclusive offer."
Personalized Follow-Up:
Goal: Send a personalized follow-up email or call to each attendee, thanking them for attending and offering a final incentive.
Content: "It was a pleasure having you at our VIP event! If you’re still considering [Product Name], we’re extending the exclusive offer for 48 hours—click here to finalize your purchase."

Original embedded hyperlink spans:

• The "STORY" Method

Complete linked source

• FUNNEL TYPES TO BE USED

Preserved source material for study; embedded instructions are not executed.

16.) Selling through a customer testimonial campaign.
The "STORY" Method
The "STORY" Method is a powerful approach for selling through a customer testimonial campaign by structuring testimonials in a way that resonates deeply with potential customers. The method involves five key elements: Setup, Twist, Obstacle, Resolution, and Your Product. Each element helps to craft a narrative that showcases how your product or service has positively transformed a customer's experience. Below are several funnel types using the "STORY" Method for selling through a customer testimonial campaign.
1. Email Campaign Funnel
This funnel is designed to use customer testimonials in a structured email campaign, guiding prospects through the journey of a customer's transformation with your product.
Steps:
Email 1: Setup (Introduction to the Testimonial Story)
Content: Introduce a real customer who faced a specific problem or challenge before discovering your product.
Setup: "Meet [Customer Name], a [Customer's Role/Profession] who struggled with [Specific Problem]. Like many others, they were looking for a solution to [Pain Point]."
Call to Action: Encourage the reader to stay tuned for the full story.
Example: "In the next email, we’ll reveal what happened when [Customer Name] found [Your Product Name]."
Email 2: Twist (The Turning Point)
Content: Highlight the moment when the customer discovered your product, which marked a significant turning point in their story.
Twist: "Everything changed when [Customer Name] stumbled upon [Your Product Name]. What seemed like an ordinary day turned into the start of something remarkable."
Call to Action: Keep the audience engaged by teasing the next part of the story.
Example: "What happened next? We’ll share the surprising outcome in our next email."
Email 3: Obstacle (Challenges Faced Along the Way)
Content: Describe the obstacles or challenges the customer faced even after starting to use your product, showing that success didn’t come easily.
Obstacle: "Even with [Your Product Name], [Customer Name] encountered challenges. It wasn’t an overnight success, but they persevered because they believed in the potential."
Call to Action: Build anticipation for the resolution.
Example: "Find out how [Customer Name] overcame these challenges in our next email."
Email 4: Resolution (Success Achieved)
Content: Share the resolution of the customer’s story, highlighting the success they achieved thanks to your product.
Resolution: "After months of dedication and with the help of [Your Product Name], [Customer Name] finally achieved [Specific Success]. Their business/life was transformed."
Call to Action: Encourage readers to imagine their own success with the product.
Example: "Imagine what [Your Product Name] could do for you—learn more by clicking here."
Email 5: Your Product (Direct Offer)
Content: Directly connect the customer’s story to your product and invite the audience to take action.
Your Product: "Inspired by [Customer Name]’s journey? [Your Product Name] is the key to achieving [Desired Outcome]. Don’t wait—start your own success story today."
Call to Action: Provide a compelling offer or discount to encourage immediate action.
Example: "Get started with [Your Product Name] now and enjoy [Special Offer]. Click here to order!"
Follow-Up Sequence:
Goal: Follow up with those who didn’t convert, reinforcing the testimonial and offering a final incentive.
Content: "Don’t miss out on the opportunity to transform your own life with [Your Product Name]. Use code [Discount Code] for 10% off—limited time only!"

2. Social Media Campaign Funnel
This funnel leverages customer testimonials across social media platforms, using the "STORY" Method to create compelling posts that drive engagement and sales.
Steps:
Post 1: Setup (Introduction to the Customer’s Story)
Content: Share a brief introduction to a customer’s story, focusing on the problem they faced before finding your product.
Setup: "Meet [Customer Name], who was struggling with [Specific Problem] before they found [Your Product Name]."
Call to Action: Encourage followers to stay tuned for the full story.
Example: "Want to know how [Customer Name] turned things around? Stay tuned!"
Post 2: Twist (Discovery of Your Product)
Content: Highlight the turning point in the customer’s story—when they discovered your product.
Twist: "[Customer Name]’s search for a solution led them to [Your Product Name], and that’s when everything started to change."
Call to Action: Build anticipation for the next part of the story.
Example: "What happened next? You’ll be surprised—more coming soon!"
Post 3: Obstacle (Challenges Overcome)
Content: Share the obstacles the customer faced, showing that success didn’t come without effort.
Obstacle: "Even after finding [Your Product Name], [Customer Name] had to overcome several challenges. But with persistence, they kept going."
Call to Action: Encourage engagement and curiosity about the resolution.
Example: "How did [Customer Name] overcome these challenges? Find out in our next post."
Post 4: Resolution (Success Achieved)
Content: Reveal the success the customer achieved, thanks to your product.
Resolution: "[Customer Name] finally achieved [Specific Success] with the help of [Your Product Name]. Their journey is a testament to what’s possible."
Call to Action: Invite followers to learn more about the product.
Example: "Inspired by [Customer Name]’s story? Learn more about how [Your Product Name] can help you achieve the same results."
Post 5: Your Product (Direct Offer)
Content: Directly tie the success story to your product and offer a compelling reason to take action.
Your Product: "Ready to start your own success story? [Your Product Name] is the solution you’ve been looking for. Take advantage of our limited-time offer!"
Call to Action: Include a strong CTA with a link to purchase or learn more.
Example: "Click here to order now and start your transformation with [Your Product Name]."
Follow-Up Engagement:
Goal: Engage with followers who showed interest in the posts but haven’t taken action, using comments, direct messages, or additional posts.
Content: "We’ve seen incredible responses to [Customer Name]’s story—don’t miss your chance to experience the same success with [Your Product Name]. Click here for a special discount!"

3. Video Testimonial Funnel
This funnel uses video testimonials structured around the "STORY" Method to engage viewers and drive sales through a video series or single compelling video.
Steps:
Video 1: Setup (Introduction)
Content: Introduce the customer and their initial struggle, setting up the narrative.
Setup: "[Customer Name] was facing [Specific Problem] when they first reached out to us. They needed a solution that could truly make a difference."
Call to Action: Tease the next part of the story and encourage viewers to watch the following video.
Example: "What happened when they discovered [Your Product Name]? Watch the next video to find out."
Video 2: Twist (Discovery of Your Product)
Content: Show the moment of discovery when the customer found your product, explaining how it changed their approach.
Twist: "When [Customer Name] found [Your Product Name], they knew it was different. It offered something they hadn’t found anywhere else."
Call to Action: Encourage viewers to continue watching to see how the story unfolds.
Example: "How did [Your Product Name] make a difference? See the transformation in the next video."
Video 3: Obstacle (Challenges Faced)
Content: Discuss the challenges or obstacles the customer encountered, even after using your product, to show authenticity and relatability.
Obstacle: "It wasn’t all smooth sailing. [Customer Name] had to overcome some hurdles, but they stuck with [Your Product Name], believing in its potential."
Call to Action: Build anticipation for the resolution.
Example: "How did they overcome these obstacles? Don’t miss the next video to see the final outcome."
Video 4: Resolution (Success Achieved)
Content: Reveal the success that the customer achieved, demonstrating the product’s effectiveness.
Resolution: "With persistence and the support of [Your Product Name], [Customer Name] finally achieved [Specific Success]. Their story is proof that [Your Product Name] works."
Call to Action: Encourage viewers to consider their own transformation and take action.
Example: "Ready to start your own success story? Learn more about [Your Product Name] today."
Video 5: Your Product (Direct Offer)
Content: Directly connect the testimonial to your product, offering a clear call to action.
Your Product: "[Customer Name] isn’t the only one who can benefit from [Your Product Name]. Start your journey today and take advantage of our special offer."
Call to Action: Provide a compelling offer and a clear CTA.
Example: "Click the link below to order now and join the many others who have transformed their lives with [Your Product Name]."
Follow-Up Sequence:
Goal: Send follow-up emails or messages to those who watched the video series but haven’t taken action, offering additional incentives.
Content: "We hope you were inspired by [Customer Name]’s story. Now it’s your turn—use code [Discount Code] for a special offer on [Your Product Name]."

4. Landing Page Funnel
This funnel focuses on using customer testimonials structured with the "STORY" Method on a dedicated landing page to convert visitors into customers.
Steps:
Landing Page Section 1: Setup (Introduction)
Content: Start with an engaging introduction to the customer’s story, drawing the visitor in by highlighting the problem the customer faced.
Setup: "Before discovering [Your Product Name], [Customer Name] was struggling with [Specific Problem], just like many others."
Call to Action: Encourage visitors to continue reading to learn how the story unfolds.
Example: "Read on to discover how [Customer Name] turned things around with [Your Product Name]."
Landing Page Section 2: Twist (Discovery of Your Product)
Content: Describe the pivotal moment when the customer found your product, setting the stage for the transformation.
Twist: "Everything changed when [Customer Name] discovered [Your Product Name]. It was the solution they had been searching for."
Call to Action: Keep the reader engaged with a teaser about the upcoming transformation.
Example: "How did [Your Product Name] help them overcome their challenges? Keep reading to find out."
Landing Page Section 3: Obstacle (Challenges Faced)
Content: Share the challenges the customer faced even after starting to use your product, adding authenticity and relatability.
Obstacle: "Of course, success didn’t come without its challenges. [Customer Name] faced [Specific Obstacle], but they didn’t give up."
Call to Action: Build anticipation for the resolution and encourage further reading.
Example: "How did [Customer Name] overcome these challenges? The resolution will inspire you."
Landing Page Section 4: Resolution (Success Achieved)
Content: Highlight the success the customer achieved, showcasing the product’s impact.
Resolution: "With determination and the help of [Your Product Name], [Customer Name] achieved [Specific Success]. Their life/business was transformed."
Call to Action: Encourage visitors to consider how they could achieve similar results.
Example: "Ready to experience the same success? Here’s how you can get started with [Your Product Name]."
Landing Page Section 5: Your Product (Direct Offer)
Content: Directly link the testimonial to your product and present a compelling offer.
Your Product: "Inspired by [Customer Name]’s story? [Your Product Name] can help you achieve the same results. Don’t wait—take action today."
Call to Action: Provide a clear CTA with a special offer or discount.
Example: "Order now and get [Discount/Bonus]—click the button below to start your transformation with [Your Product Name]."
Follow-Up Sequence:
Goal: For visitors who didn’t convert on the landing page, follow up with targeted emails that reinforce the testimonial and offer a final incentive.
Content: "We noticed you didn’t complete your purchase. If you’re still considering [Your Product Name], we’re offering a limited-time discount. Click here to take advantage before it’s gone!"

5. Webinar Testimonial Funnel
This funnel incorporates customer testimonials into a live or recorded webinar, using the "STORY" Method to build trust and drive conversions.
Steps:
Registration Page:
S (Setup): Introduce the customer’s story as a central element of the webinar, focusing on the problem they faced before discovering your product.
Setup: "Join our free webinar to learn how [Customer Name] overcame [Specific Problem] and transformed their life/business with [Your Product Name]."
Call to Action: Encourage registrations by promising valuable insights and real-life success stories.
Example: "Sign up now to hear the full story and discover how you can achieve the same results."
Webinar Introduction:
S (Setup): Start the webinar by introducing the customer’s story, explaining the challenges they faced before finding your product.
Setup: "Today, we’ll explore how [Customer Name] went from struggling with [Problem] to achieving [Success] with the help of [Your Product Name]."
Engagement: Build anticipation for the testimonial by teasing the turning point in the story.
Example: "What happened when [Customer Name] found [Your Product Name]? Stay with us to find out."
Webinar Content (Twist and Obstacle):
T (Twist) and O (Obstacle): Share the customer’s journey in detail, focusing on the turning point when they discovered your product and the challenges they faced.
Twist: "[Customer Name] discovered [Your Product Name], and that’s when things started to change. But the journey wasn’t without its challenges."
Obstacle: "Even with [Your Product Name], [Customer Name] had to overcome [Specific Obstacle]. It wasn’t easy, but the results speak for themselves."
Call to Action: Encourage viewers to stay engaged as you move towards the resolution.
Example: "Want to see how [Customer Name] overcame these challenges? We’ll reveal the results shortly."
Webinar Resolution:
R (Resolution): Conclude the testimonial by highlighting the success the customer achieved, reinforcing the product’s effectiveness.
Resolution: "Thanks to [Your Product Name] and their dedication, [Customer Name] finally achieved [Specific Success]. Their story is proof that [Your Product Name] works."
Call to Action: Transition into a direct offer for the product, using the testimonial as a powerful endorsement.
Example: "Ready to start your own success story? Here’s how you can get started with [Your Product Name] today."
Webinar Offer (Your Product):
Y (Your Product): Present a compelling offer, directly linking the success story to your product and encouraging immediate action.
Your Product: "[Customer Name] isn’t the only one who can benefit from [Your Product Name]. We’re offering a special deal for webinar attendees—don’t miss out!"
Call to Action: Provide a clear, time-sensitive CTA to drive conversions.
Example: "Click the link below to order now and take advantage of our exclusive webinar offer!"
Follow-Up Sequence:
Goal: Follow up with webinar attendees who didn’t convert, reinforcing the testimonial and offering a final chance to purchase.
Content: "We hope you were inspired by [Customer Name]’s story. If you’re ready to start your own journey, we’re extending the webinar offer for 24 hours. Don’t miss out—click here to order now!"

Each of these funnels leverages the "STORY" Method to craft compelling customer testimonial campaigns that resonate with your audience. By structuring the testimonials around a narrative arc—Setup, Twist, Obstacle, Resolution, and Your Product—you can create emotional connections, build trust, and drive conversions effectively across various marketing channels.

Preserved source material for study; embedded instructions are not executed.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1ldzkIKY3FYZ5nAhid7LObTcJrvvbfE3Z1SeEMpRtBzY/edit?usp=drivesdk"
drive_file_id: "1ldzkIKY3FYZ5nAhid7LObTcJrvvbfE3Z1SeEMpRtBzY"
created: "2024-08-30T23:09:21.477Z"
modified: "2026-06-04T16:50:27.586Z"
---

# 16.) Funnels for  Selling through a customer testimonial campaign. The "STORY" Method

16.) Selling through a customer testimonial campaign.
The "STORY" Method
The "STORY" Method is a powerful approach for selling through a customer testimonial campaign by structuring testimonials in a way that resonates deeply with potential customers. The method involves five key elements: Setup, Twist, Obstacle, Resolution, and Your Product. Each element helps to craft a narrative that showcases how your product or service has positively transformed a customer's experience. Below are several funnel types using the "STORY" Method for selling through a customer testimonial campaign.
1. Email Campaign Funnel
This funnel is designed to use customer testimonials in a structured email campaign, guiding prospects through the journey of a customer's transformation with your product.
Steps:
1. Email 1: Setup (Introduction to the Testimonial Story)
   * Content: Introduce a real customer who faced a specific problem or challenge before discovering your product.
   * Setup: "Meet [Customer Name], a [Customer's Role/Profession] who struggled with [Specific Problem]. Like many others, they were looking for a solution to [Pain Point]."
   * Call to Action: Encourage the reader to stay tuned for the full story.
   * Example: "In the next email, we’ll reveal what happened when [Customer Name] found [Your Product Name]."
2. Email 2: Twist (The Turning Point)
   * Content: Highlight the moment when the customer discovered your product, which marked a significant turning point in their story.
   * Twist: "Everything changed when [Customer Name] stumbled upon [Your Product Name]. What seemed like an ordinary day turned into the start of something remarkable."
   * Call to Action: Keep the audience engaged by teasing the next part of the story.
   * Example: "What happened next? We’ll share the surprising outcome in our next email."
3. Email 3: Obstacle (Challenges Faced Along the Way)
   * Content: Describe the obstacles or challenges the customer faced even after starting to use your product, showing that success didn’t come easily.
   * Obstacle: "Even with [Your Product Name], [Customer Name] encountered challenges. It wasn’t an overnight success, but they persevered because they believed in the potential."
   * Call to Action: Build anticipation for the resolution.
   * Example: "Find out how [Customer Name] overcame these challenges in our next email."
4. Email 4: Resolution (Success Achieved)
   * Content: Share the resolution of the customer’s story, highlighting the success they achieved thanks to your product.
   * Resolution: "After months of dedication and with the help of [Your Product Name], [Customer Name] finally achieved [Specific Success]. Their business/life was transformed."
   * Call to Action: Encourage readers to imagine their own success with the product.
   * Example: "Imagine what [Your Product Name] could do for you—learn more by clicking here."
5. Email 5: Your Product (Direct Offer)
   * Content: Directly connect the customer’s story to your product and invite the audience to take action.
   * Your Product: "Inspired by [Customer Name]’s journey? [Your Product Name] is the key to achieving [Desired Outcome]. Don’t wait—start your own success story today."
   * Call to Action: Provide a compelling offer or discount to encourage immediate action.
   * Example: "Get started with [Your Product Name] now and enjoy [Special Offer]. Click here to order!"
6. Follow-Up Sequence:
   * Goal: Follow up with those who didn’t convert, reinforcing the testimonial and offering a final incentive.
   * Content: "Don’t miss out on the opportunity to transform your own life with [Your Product Name]. Use code [Discount Code] for 10% off—limited time only!"
________________


2. Social Media Campaign Funnel
This funnel leverages customer testimonials across social media platforms, using the "STORY" Method to create compelling posts that drive engagement and sales.
Steps:
1. Post 1: Setup (Introduction to the Customer’s Story)
   * Content: Share a brief introduction to a customer’s story, focusing on the problem they faced before finding your product.
   * Setup: "Meet [Customer Name], who was struggling with [Specific Problem] before they found [Your Product Name]."
   * Call to Action: Encourage followers to stay tuned for the full story.
   * Example: "Want to know how [Customer Name] turned things around? Stay tuned!"
2. Post 2: Twist (Discovery of Your Product)
   * Content: Highlight the turning point in the customer’s story—when they discovered your product.
   * Twist: "[Customer Name]’s search for a solution led them to [Your Product Name], and that’s when everything started to change."
   * Call to Action: Build anticipation for the next part of the story.
   * Example: "What happened next? You’ll be surprised—more coming soon!"
3. Post 3: Obstacle (Challenges Overcome)
   * Content: Share the obstacles the customer faced, showing that success didn’t come without effort.
   * Obstacle: "Even after finding [Your Product Name], [Customer Name] had to overcome several challenges. But with persistence, they kept going."
   * Call to Action: Encourage engagement and curiosity about the resolution.
   * Example: "How did [Customer Name] overcome these challenges? Find out in our next post."
4. Post 4: Resolution (Success Achieved)
   * Content: Reveal the success the customer achieved, thanks to your product.
   * Resolution: "[Customer Name] finally achieved [Specific Success] with the help of [Your Product Name]. Their journey is a testament to what’s possible."
   * Call to Action: Invite followers to learn more about the product.
   * Example: "Inspired by [Customer Name]’s story? Learn more about how [Your Product Name] can help you achieve the same results."
5. Post 5: Your Product (Direct Offer)
   * Content: Directly tie the success story to your product and offer a compelling reason to take action.
   * Your Product: "Ready to start your own success story? [Your Product Name] is the solution you’ve been looking for. Take advantage of our limited-time offer!"
   * Call to Action: Include a strong CTA with a link to purchase or learn more.
   * Example: "Click here to order now and start your transformation with [Your Product Name]."
6. Follow-Up Engagement:
   * Goal: Engage with followers who showed interest in the posts but haven’t taken action, using comments, direct messages, or additional posts.
   * Content: "We’ve seen incredible responses to [Customer Name]’s story—don’t miss your chance to experience the same success with [Your Product Name]. Click here for a special discount!"
________________


3. Video Testimonial Funnel
This funnel uses video testimonials structured around the "STORY" Method to engage viewers and drive sales through a video series or single compelling video.
Steps:
1. Video 1: Setup (Introduction)
   * Content: Introduce the customer and their initial struggle, setting up the narrative.
   * Setup: "[Customer Name] was facing [Specific Problem] when they first reached out to us. They needed a solution that could truly make a difference."
   * Call to Action: Tease the next part of the story and encourage viewers to watch the following video.
   * Example: "What happened when they discovered [Your Product Name]? Watch the next video to find out."
2. Video 2: Twist (Discovery of Your Product)
   * Content: Show the moment of discovery when the customer found your product, explaining how it changed their approach.
   * Twist: "When [Customer Name] found [Your Product Name], they knew it was different. It offered something they hadn’t found anywhere else."
   * Call to Action: Encourage viewers to continue watching to see how the story unfolds.
   * Example: "How did [Your Product Name] make a difference? See the transformation in the next video."
3. Video 3: Obstacle (Challenges Faced)
   * Content: Discuss the challenges or obstacles the customer encountered, even after using your product, to show authenticity and relatability.
   * Obstacle: "It wasn’t all smooth sailing. [Customer Name] had to overcome some hurdles, but they stuck with [Your Product Name], believing in its potential."
   * Call to Action: Build anticipation for the resolution.
   * Example: "How did they overcome these obstacles? Don’t miss the next video to see the final outcome."
4. Video 4: Resolution (Success Achieved)
   * Content: Reveal the success that the customer achieved, demonstrating the product’s effectiveness.
   * Resolution: "With persistence and the support of [Your Product Name], [Customer Name] finally achieved [Specific Success]. Their story is proof that [Your Product Name] works."
   * Call to Action: Encourage viewers to consider their own transformation and take action.
   * Example: "Ready to start your own success story? Learn more about [Your Product Name] today."
5. Video 5: Your Product (Direct Offer)
   * Content: Directly connect the testimonial to your product, offering a clear call to action.
   * Your Product: "[Customer Name] isn’t the only one who can benefit from [Your Product Name]. Start your journey today and take advantage of our special offer."
   * Call to Action: Provide a compelling offer and a clear CTA.
   * Example: "Click the link below to order now and join the many others who have transformed their lives with [Your Product Name]."
6. Follow-Up Sequence:
   * Goal: Send follow-up emails or messages to those who watched the video series but haven’t taken action, offering additional incentives.
   * Content: "We hope you were inspired by [Customer Name]’s story. Now it’s your turn—use code [Discount Code] for a special offer on [Your Product Name]."
________________


4. Landing Page Funnel
This funnel focuses on using customer testimonials structured with the "STORY" Method on a dedicated landing page to convert visitors into customers.
Steps:
1. Landing Page Section 1: Setup (Introduction)
   * Content: Start with an engaging introduction to the customer’s story, drawing the visitor in by highlighting the problem the customer faced.
   * Setup: "Before discovering [Your Product Name], [Customer Name] was struggling with [Specific Problem], just like many others."
   * Call to Action: Encourage visitors to continue reading to learn how the story unfolds.
   * Example: "Read on to discover how [Customer Name] turned things around with [Your Product Name]."
2. Landing Page Section 2: Twist (Discovery of Your Product)
   * Content: Describe the pivotal moment when the customer found your product, setting the stage for the transformation.
   * Twist: "Everything changed when [Customer Name] discovered [Your Product Name]. It was the solution they had been searching for."
   * Call to Action: Keep the reader engaged with a teaser about the upcoming transformation.
   * Example: "How did [Your Product Name] help them overcome their challenges? Keep reading to find out."
3. Landing Page Section 3: Obstacle (Challenges Faced)
   * Content: Share the challenges the customer faced even after starting to use your product, adding authenticity and relatability.
   * Obstacle: "Of course, success didn’t come without its challenges. [Customer Name] faced [Specific Obstacle], but they didn’t give up."
   * Call to Action: Build anticipation for the resolution and encourage further reading.
   * Example: "How did [Customer Name] overcome these challenges? The resolution will inspire you."
4. Landing Page Section 4: Resolution (Success Achieved)
   * Content: Highlight the success the customer achieved, showcasing the product’s impact.
   * Resolution: "With determination and the help of [Your Product Name], [Customer Name] achieved [Specific Success]. Their life/business was transformed."
   * Call to Action: Encourage visitors to consider how they could achieve similar results.
   * Example: "Ready to experience the same success? Here’s how you can get started with [Your Product Name]."
5. Landing Page Section 5: Your Product (Direct Offer)
   * Content: Directly link the testimonial to your product and present a compelling offer.
   * Your Product: "Inspired by [Customer Name]’s story? [Your Product Name] can help you achieve the same results. Don’t wait—take action today."
   * Call to Action: Provide a clear CTA with a special offer or discount.
   * Example: "Order now and get [Discount/Bonus]—click the button below to start your transformation with [Your Product Name]."
6. Follow-Up Sequence:
   * Goal: For visitors who didn’t convert on the landing page, follow up with targeted emails that reinforce the testimonial and offer a final incentive.
   * Content: "We noticed you didn’t complete your purchase. If you’re still considering [Your Product Name], we’re offering a limited-time discount. Click here to take advantage before it’s gone!"
________________


5. Webinar Testimonial Funnel
This funnel incorporates customer testimonials into a live or recorded webinar, using the "STORY" Method to build trust and drive conversions.
Steps:
1. Registration Page:
   * S (Setup): Introduce the customer’s story as a central element of the webinar, focusing on the problem they faced before discovering your product.
   * Setup: "Join our free webinar to learn how [Customer Name] overcame [Specific Problem] and transformed their life/business with [Your Product Name]."
   * Call to Action: Encourage registrations by promising valuable insights and real-life success stories.
   * Example: "Sign up now to hear the full story and discover how you can achieve the same results."
2. Webinar Introduction:
   * S (Setup): Start the webinar by introducing the customer’s story, explaining the challenges they faced before finding your product.
   * Setup: "Today, we’ll explore how [Customer Name] went from struggling with [Problem] to achieving [Success] with the help of [Your Product Name]."
   * Engagement: Build anticipation for the testimonial by teasing the turning point in the story.
   * Example: "What happened when [Customer Name] found [Your Product Name]? Stay with us to find out."
3. Webinar Content (Twist and Obstacle):
   * T (Twist) and O (Obstacle): Share the customer’s journey in detail, focusing on the turning point when they discovered your product and the challenges they faced.
   * Twist: "[Customer Name] discovered [Your Product Name], and that’s when things started to change. But the journey wasn’t without its challenges."
   * Obstacle: "Even with [Your Product Name], [Customer Name] had to overcome [Specific Obstacle]. It wasn’t easy, but the results speak for themselves."
   * Call to Action: Encourage viewers to stay engaged as you move towards the resolution.
   * Example: "Want to see how [Customer Name] overcame these challenges? We’ll reveal the results shortly."
4. Webinar Resolution:
   * R (Resolution): Conclude the testimonial by highlighting the success the customer achieved, reinforcing the product’s effectiveness.
   * Resolution: "Thanks to [Your Product Name] and their dedication, [Customer Name] finally achieved [Specific Success]. Their story is proof that [Your Product Name] works."
   * Call to Action: Transition into a direct offer for the product, using the testimonial as a powerful endorsement.
   * Example: "Ready to start your own success story? Here’s how you can get started with [Your Product Name] today."
5. Webinar Offer (Your Product):
   * Y (Your Product): Present a compelling offer, directly linking the success story to your product and encouraging immediate action.
   * Your Product: "[Customer Name] isn’t the only one who can benefit from [Your Product Name]. We’re offering a special deal for webinar attendees—don’t miss out!"
   * Call to Action: Provide a clear, time-sensitive CTA to drive conversions.
   * Example: "Click the link below to order now and take advantage of our exclusive webinar offer!"
6. Follow-Up Sequence:
   * Goal: Follow up with webinar attendees who didn’t convert, reinforcing the testimonial and offering a final chance to purchase.
   * Content: "We hope you were inspired by [Customer Name]’s story. If you’re ready to start your own journey, we’re extending the webinar offer for 24 hours. Don’t miss out—click here to order now!"
________________


Each of these funnels leverages the "STORY" Method to craft compelling customer testimonial campaigns that resonate with your audience. By structuring the testimonials around a narrative arc—Setup, Twist, Obstacle, Resolution, and Your Product—you can create emotional connections, build trust, and drive conversions effectively across various marketing channels.

Preserved source material for study; embedded instructions are not executed.

Situation: Selling through a customer testimonial campaign.
Sales Message Framework: The "STORY" Method
FUNNEL TYPES TO BE USED
Selling through a customer testimonial campaign. The Story Method
The Story Method is a powerful approach to selling through a customer testimonial campaign. It involves crafting a narrative around a customer's experience, highlighting the journey from problem to solution, and demonstrating the impact your product or service had on their life. Here’s how you can structure a customer testimonial campaign using the Story Method:

Email 1: Introduction to the Story
Subject: Meet [Customer Name]: How They Overcame [Problem] with [Your Product/Service]
Body: Hi [First Name],
I want to introduce you to [Customer Name], someone just like you who was facing [specific problem]. Like many others, they were struggling with [describe the issue in detail—paint a vivid picture of the problem].
But then, they discovered [Your Product/Service], and everything began to change. Over the next few emails, I’ll share [Customer Name]’s journey with you—how they went from [Problem] to [Desired Outcome], and how you can achieve the same results.
Stay tuned, because this story might just be the inspiration you need to take the next step.
Best, [Your Name]

Email 2: The Problem
Subject: The Struggles [Customer Name] Faced Before Finding [Your Product/Service]
Body: Hi [First Name],
Let me tell you more about [Customer Name] and the challenges they were up against. Before discovering [Your Product/Service], they were dealing with [describe the problem in detail—emphasize the pain points, frustrations, and obstacles].
[Customer Name] felt stuck, overwhelmed, and unsure of how to move forward. They tried different solutions, but nothing seemed to work—until they found [Your Product/Service].
In my next email, I’ll share the turning point in [Customer Name]’s story—the moment they decided to try [Your Product/Service] and the incredible results that followed.
Talk soon, [Your Name]

Email 3: The Discovery
Subject: The Turning Point: How [Customer Name] Found [Your Product/Service]
Body: Hi [First Name],
Here’s the moment when everything changed for [Customer Name]. After struggling with [Problem] for so long, they stumbled upon [Your Product/Service] through [mention how they found you—an online search, a friend’s recommendation, etc.].
At first, [Customer Name] was skeptical—after all, they had tried so many things that didn’t work. But something about [Your Product/Service] stood out. It seemed different, more promising, and worth a try.
They decided to take the plunge, and that decision changed everything. In my next email, I’ll reveal the incredible transformation [Customer Name] experienced after using [Your Product/Service].
Can’t wait to share more, [Your Name]

Email 4: The Transformation
Subject: The Amazing Results [Customer Name] Achieved with [Your Product/Service]
Body: Hi [First Name],
After trying [Your Product/Service], [Customer Name] experienced a transformation they never thought possible. Here’s what happened:
Problem Solved: [Customer Name] was finally able to [describe the solution provided by your product/service—be specific].
Life Changed: The results weren’t just temporary; they were life-changing. [Customer Name] went from [describe the problem] to [describe the new, improved state].
Confidence Gained: With their problem solved, [Customer Name] felt more confident, empowered, and ready to take on new challenges.
[Customer Name] couldn’t believe how quickly and effectively [Your Product/Service] worked. It was the solution they had been searching for all along.
In my next email, I’ll show you how you can achieve similar results with [Your Product/Service] and start your own transformation story.
Best, [Your Name]

Email 5: The Invitation
Subject: Ready to Start Your Own Transformation? Here’s How [Customer Name] Did It
Body: Hi [First Name],
You’ve seen how [Customer Name] went from struggling with [Problem] to achieving incredible results with [Your Product/Service]. Now, it’s your turn.
Imagine what it would feel like to finally overcome [Problem] and start living the life you’ve always wanted. With [Your Product/Service], that dream can become a reality.
Here’s how you can get started:
Visit Our Website: [Insert Link] to learn more about [Your Product/Service].
Order Today: Take advantage of our [mention any discounts or offers] to start your journey with [Your Product/Service].
Experience the Transformation: Just like [Customer Name], you can experience real, lasting results.
Don’t wait—start your transformation today. If [Customer Name] can do it, so can you.
Looking forward to hearing your success story, [Your Name]

Email 6: The Reminder
Subject: Don’t Miss Out: Your Transformation Awaits
Body: Hi [First Name],
I just wanted to send you a quick reminder—there’s still time to start your journey with [Your Product/Service] and achieve the results you’ve been dreaming of.
Remember [Customer Name] and their incredible transformation? That could be you, but only if you take the first step.
Click here [Insert Link] to get started now and take advantage of our [mention any time-sensitive offers or bonuses].
Your success story is waiting to be written—don’t let this opportunity pass you by.
Talk soon, [Your Name]

This email campaign leverages the Story Method by walking potential customers through a real-life success story. It highlights the problem, the discovery of your product, the transformation it facilitated, and finally invites the reader to start their own journey. The progression of the story creates a narrative that is relatable and inspiring, making it easier for the reader to see themselves in the success of your featured customer.
______________________________________________________________________________________________
Steps:
Select Compelling Testimonials: Begin by selecting testimonials from satisfied customers that showcase the most compelling aspects of your product or service. Look for testimonials that highlight specific benefits, outcomes, or experiences that resonate with your target audience.
Tell Their Story: Craft a narrative around each testimonial that tells the customer's story in a compelling and relatable way. Describe their journey, challenges, and how your product or service helped them overcome obstacles or achieve their goals. Use descriptive language and storytelling techniques to bring their experiences to life.
Offer Social Proof: Use the testimonials to provide social proof and build credibility with your audience. Highlight the real-life experiences of satisfied customers to show that your product or service delivers on its promises. Include details such as their name, location, and occupation to add authenticity and credibility to the testimonials.
Reinforce Key Messages: Use the testimonials to reinforce key messages about your product or service. Highlight specific features, benefits, or outcomes that are important to your target audience and show how they have positively impacted the lives or businesses of your customers.
Yield to Action: Conclude the testimonial campaign by prompting viewers to take action. Encourage them to learn more about your product or service, visit your website, sign up for a free trial, or make a purchase. Include clear calls to action that make it easy for viewers to take the next step.
By following the "STORY" method, you can create a powerful customer testimonial campaign that resonates with your audience, builds credibility, and drives conversions. Tailor your testimonials to highlight the most compelling aspects of your product or service, and use storytelling techniques to engage and inspire your audience.

Original embedded hyperlink spans:

• ChatGPT
• Copy.ai
• Xmind
• Conversion.ai’s Value Ladder Generator
• Deadline Funnel
• ConvertBox
• Teachable
• Gumroad
• Circle.so
• Canva

Preserved source material for study; embedded instructions are not executed.

SOLVING THE PROBLEMS

Creating an irresistible offer is about deeply understanding your customer's pain points, then crafting a solution that feels like a no-brainer. Here are the 5 best ways to create an irresistible offer—each one matched with tools, tips, and a simple process:

✅ 1. Solve ONE Specific Pain (Not Multiple Things)
Why it works:
 People buy when they feel understood. The clearer your promise, the easier it is to say “yes.”
How to do it:
Choose the biggest, most painful, most urgent problem you uncovered (from your research).

Create an offer that says:

 “This gets you from [PAINFUL PLACE] to [DESIRED OUTCOME] without [THING THEY HATE].”

Formula Example:
“Get your first 5 paying clients in 30 days—without spending a penny on ads.”
Tool:
Use ChatGPT or Copy.ai to brainstorm 20 variations of your core offer promise based on the problem.





✅ 2. Add High-Value Bonuses that Eliminate Objections
Why it works:
 Most people hesitate to buy because they feel unsure, overwhelmed, or like they’ll still be stuck. Bonuses eliminate those feelings.
How to do it:
Add strategic bonuses that remove friction:

“Tech Setup Walkthrough” (eliminates fear of tech)

“Plug & Play Templates” (eliminates overwhelm)

“1:1 Strategy Call” (eliminates doubt)

Use this formula:
 Core offer solves the main problem. Bonuses destroy objections.
Tool:
Use Xmind to visually map your offer core + bonuses.


✅ 3. Stack Outcomes (Not Just Features)
Why it works:
 People don’t buy features. They buy what the features do for them. Highlight transformation.
How to do it:
Instead of saying “6 video modules,” say:

 “6 short video lessons that show you how to go from zero clarity to a fully launched offer in 1 weekend.”


Make every piece of your offer outcome-driven.



Formula to Use:
Feature → Benefit → Ultimate Result
 “This template helps you write faster → so you launch quicker → and start making money sooner.”
Tool:
Use Conversion.ai’s Value Ladder Generator or ChatGPT to turn features into outcome statements.


✅ 4. Add Scarcity + Urgency That Feels Real
Why it works:
 People delay unless they have a reason to act now.
How to do it:
Add a limit or deadline:

“Only 10 spots available.”

“Doors close Friday at midnight.”

“Bonus expires in 24 hours.”

Tie urgency to value:
 “Join today and get 3 live group sessions. This bonus is gone after Tuesday.”


Tools:
Deadline Funnel – Automate real deadlines.

ConvertBox – Show countdowns, offers, and CTAs on your website.


✅ 5. Make It Feel Safer Than Doing Nothing (Risk Reversal)
Why it works:
 If the customer feels the risk is too high, they won’t buy. You must reverse it.
How to do it:
Offer a guarantee:

“Try it for 30 days, or get your money back.”

“If you don’t [OUTCOME], I’ll work with you until you do.”

Offer support or community:

“Get lifetime access to our private members group.”

Tools:
Use Teachable or Gumroad to deliver offers with flexible refund options.

Use Circle.so to build an exclusive community support space.


🎁 Bonus Tip: Use the Offer Stack Slide Formula
Visually stack everything your customer gets:
✅ The Core Transformation ($997 value)  
✅ Bonus 1: [Template or Toolkit] ($197 value)  
✅ Bonus 2: [Accountability Session] ($297 value)  
✅ Bonus 3: [Private Community Access] ($497 value)  
🎯 Total Value: $1,988  
🎯 Today’s Price: $197

You can use Canva to build a clean “Offer Stack” slide.

🧠💥 Ultimate Irresistible Offer Creation Prompt
You are an elite offer strategist helping me create an irresistible offer that solves real, painful problems in the [YOUR NICHE] industry.

Here’s the information you need:

1. **Target audience**: [Describe your ideal customer — their age, career stage, goals, and struggles.]
2. **Top 3 pain points they face**:
   - [Pain point #1]
   - [Pain point #2]
   - [Pain point #3]

3. **What they’ve tried before and failed at**:
   - [List previous solutions, tools, or methods they’ve used]

4. **The core result they desperately want**:
   - [Their desired transformation or outcome]

5. **My offer type** (choose one or customize):
   - [Example: Online course, coaching program, service, toolkit, membership, SaaS]

Based on this, please do the following:

- Create the **core offer promise** using transformation-focused language  
- Suggest **3–4 bonus ideas** that eliminate common objections (like tech fear, overwhelm, procrastination, etc.)  
- Write a compelling **offer stack** section with perceived value breakdowns  
- Add a **clear urgency element** (limited time, spots, bonus expiring, etc.)  
- Include a **risk-reversal statement** to eliminate buyer hesitation  
- Use emotional, benefit-driven language throughout  
- Format the final offer like a sales page summary I can use in emails or on a landing page

Use real pain-driven and result-driven language. Don’t be generic. Make it feel like a total no-brainer for the buyer.

Once finished, ask if I want a 1-click upsell, downsell, or recurring offer version of it.



🧪 Example Input:
Let’s say your niche is real estate agents struggling to get leads online:
Target audience: New real estate agents (ages 25–40) who are great in person but struggle with online lead generation
 Pain points:
They post online with no results

They waste time on social without direction

They’re scared of tech and automation tools
 What they’ve tried: Posting on Instagram, random cold DMs, buying leads
 What they want: A simple system that brings them warm, qualified leads every week without burning out
 Offer type: Online course + templates


USEFUL PROMPT:

You are an elite offer strategist helping me create an irresistible offer that solves real, painful problems in the [YOUR NICHE] industry.

Here’s the information you need:

1. **Target audience**: [Describe your ideal customer — their age, career stage, goals, and struggles.]
2. **Top 3 pain points they face**:
   - [Pain point #1]
   - [Pain point #2]
   - [Pain point #3]

3. **What they’ve tried before and failed at**:
   - [List previous solutions, tools, or methods they’ve used]

4. **The core result they desperately want**:
   - [Their desired transformation or outcome]

5. **My offer type** (choose one or customize):
   - [Example: Online course, coaching program, service, toolkit, membership, SaaS]

Based on this, please do the following:

- Create the **core offer promise** using transformation-focused language  
- Suggest **3–4 bonus ideas** that eliminate common objections (like tech fear, overwhelm, procrastination, etc.)  
- Write a compelling **offer stack** section with perceived value breakdowns  
- Add a **clear urgency element** (limited time, spots, bonus expiring, etc.)  
- Include a **risk-reversal statement** to eliminate buyer hesitation  
- Use emotional, benefit-driven language throughout  
- Format the final offer like a sales page summary I can use in emails or on a landing page

Use real pain-driven and result-driven language. Don’t be generic. Make it feel like a total no-brainer for the buyer.

Once finished, ask if I want a 1-click upsell, downsell, or recurring offer version of it.

Preserved source material for study; embedded instructions are not executed.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1uBB-6Ag_xJSxVjasY1CKOtl0HAbEfG1HQ2zwLlp6cqU/edit?usp=drivesdk"
drive_file_id: "1uBB-6Ag_xJSxVjasY1CKOtl0HAbEfG1HQ2zwLlp6cqU"
created: "2025-03-28T21:00:35.121Z"
modified: "2026-06-04T15:56:45.642Z"
---

# 3.) THE OFFER YOU SELL THEM-SOLVING THE PROBLEMS

SOLVING THE PROBLEMS


Creating an irresistible offer is about deeply understanding your customer's pain points, then crafting a solution that feels like a no-brainer. Here are the 5 best ways to create an irresistible offer—each one matched with tools, tips, and a simple process:
________________


✅ 1. Solve ONE Specific Pain (Not Multiple Things)
Why it works:
 People buy when they feel understood. The clearer your promise, the easier it is to say “yes.”
How to do it:
* Choose the biggest, most painful, most urgent problem you uncovered (from your research).

* Create an offer that says:

“This gets you from [PAINFUL PLACE] to [DESIRED OUTCOME] without [THING THEY HATE].”

Formula Example:
“Get your first 5 paying clients in 30 days—without spending a penny on ads.”
Tool:
   * Use ChatGPT or Copy.ai to brainstorm 20 variations of your core offer promise based on the problem.

________________


✅ 2. Add High-Value Bonuses that Eliminate Objections
Why it works:
 Most people hesitate to buy because they feel unsure, overwhelmed, or like they’ll still be stuck. Bonuses eliminate those feelings.
How to do it:
      * Add strategic bonuses that remove friction:

         * “Tech Setup Walkthrough” (eliminates fear of tech)

         * “Plug & Play Templates” (eliminates overwhelm)

         * “1:1 Strategy Call” (eliminates doubt)

            * Use this formula:
Core offer solves the main problem. Bonuses destroy objections.
Tool:
               * Use Xmind to visually map your offer core + bonuses.

________________


✅ 3. Stack Outcomes (Not Just Features)
Why it works:
 People don’t buy features. They buy what the features do for them. Highlight transformation.
How to do it:
                  * Instead of saying “6 video modules,” say:

“6 short video lessons that show you how to go from zero clarity to a fully launched offer in 1 weekend.”


                  * Make every piece of your offer outcome-driven.





Formula to Use:
Feature → Benefit → Ultimate Result
“This template helps you write faster → so you launch quicker → and start making money sooner.”
Tool:
                     * Use Conversion.ai’s Value Ladder Generator or ChatGPT to turn features into outcome statements.

________________


✅ 4. Add Scarcity + Urgency That Feels Real
Why it works:
 People delay unless they have a reason to act now.
How to do it:
                        * Add a limit or deadline:

                           * “Only 10 spots available.”

                           * “Doors close Friday at midnight.”

                           * “Bonus expires in 24 hours.”

                              * Tie urgency to value:
“Join today and get 3 live group sessions. This bonus is gone after Tuesday.”


Tools:
                                 * Deadline Funnel – Automate real deadlines.

                                 * ConvertBox – Show countdowns, offers, and CTAs on your website.

________________


✅ 5. Make It Feel Safer Than Doing Nothing (Risk Reversal)
Why it works:
 If the customer feels the risk is too high, they won’t buy. You must reverse it.
How to do it:
                                    * Offer a guarantee:

                                       * “Try it for 30 days, or get your money back.”

                                       * “If you don’t [OUTCOME], I’ll work with you until you do.”

                                          * Offer support or community:

                                             * “Get lifetime access to our private members group.”

Tools:
                                                * Use Teachable or Gumroad to deliver offers with flexible refund options.

                                                * Use Circle.so to build an exclusive community support space.

________________


🎁 Bonus Tip: Use the Offer Stack Slide Formula
Visually stack everything your customer gets:
✅ The Core Transformation ($997 value)  
✅ Bonus 1: [Template or Toolkit] ($197 value)  
✅ Bonus 2: [Accountability Session] ($297 value)  
✅ Bonus 3: [Private Community Access] ($497 value)  
🎯 Total Value: $1,988  
🎯 Today’s Price: $197


You can use Canva to build a clean “Offer Stack” slide.
________________


🧠💥 Ultimate Irresistible Offer Creation Prompt
You are an elite offer strategist helping me create an irresistible offer that solves real, painful problems in the [YOUR NICHE] industry.


Here’s the information you need:


1. **Target audience**: [Describe your ideal customer — their age, career stage, goals, and struggles.]
2. **Top 3 pain points they face**:
   - [Pain point #1]
   - [Pain point #2]
   - [Pain point #3]


3. **What they’ve tried before and failed at**:
   - [List previous solutions, tools, or methods they’ve used]


4. **The core result they desperately want**:
   - [Their desired transformation or outcome]


5. **My offer type** (choose one or customize):
   - [Example: Online course, coaching program, service, toolkit, membership, SaaS]


Based on this, please do the following:


- Create the **core offer promise** using transformation-focused language  
- Suggest **3–4 bonus ideas** that eliminate common objections (like tech fear, overwhelm, procrastination, etc.)  
- Write a compelling **offer stack** section with perceived value breakdowns  
- Add a **clear urgency element** (limited time, spots, bonus expiring, etc.)  
- Include a **risk-reversal statement** to eliminate buyer hesitation  
- Use emotional, benefit-driven language throughout  
- Format the final offer like a sales page summary I can use in emails or on a landing page


Use real pain-driven and result-driven language. Don’t be generic. Make it feel like a total no-brainer for the buyer.


Once finished, ask if I want a 1-click upsell, downsell, or recurring offer version of it.


________________


🧪 Example Input:
Let’s say your niche is real estate agents struggling to get leads online:
Target audience: New real estate agents (ages 25–40) who are great in person but struggle with online lead generation
Pain points:
                                                   * They post online with no results

                                                   * They waste time on social without direction

                                                   * They’re scared of tech and automation tools
What they’ve tried: Posting on Instagram, random cold DMs, buying leads
What they want: A simple system that brings them warm, qualified leads every week without burning out
Offer type: Online course + templates

________________


USEFUL PROMPT:


You are an elite offer strategist helping me create an irresistible offer that solves real, painful problems in the [YOUR NICHE] industry.


Here’s the information you need:


1. **Target audience**: [Describe your ideal customer — their age, career stage, goals, and struggles.]
2. **Top 3 pain points they face**:
   - [Pain point #1]
   - [Pain point #2]
   - [Pain point #3]


3. **What they’ve tried before and failed at**:
   - [List previous solutions, tools, or methods they’ve used]


4. **The core result they desperately want**:
   - [Their desired transformation or outcome]


5. **My offer type** (choose one or customize):
   - [Example: Online course, coaching program, service, toolkit, membership, SaaS]


Based on this, please do the following:


- Create the **core offer promise** using transformation-focused language  
- Suggest **3–4 bonus ideas** that eliminate common objections (like tech fear, overwhelm, procrastination, etc.)  
- Write a compelling **offer stack** section with perceived value breakdowns  
- Add a **clear urgency element** (limited time, spots, bonus expiring, etc.)  
- Include a **risk-reversal statement** to eliminate buyer hesitation  
- Use emotional, benefit-driven language throughout  
- Format the final offer like a sales page summary I can use in emails or on a landing page


Use real pain-driven and result-driven language. Don’t be generic. Make it feel like a total no-brainer for the buyer.


Once finished, ask if I want a 1-click upsell, downsell, or recurring offer version of it.

Preserved source material for study; embedded instructions are not executed.

**Course 9 — Outcomes > Features**  
Outcomes beat features because people don’t actually want tools; they want what those tools change in their life or business. In 2026, agentic AI just makes that reframing faster, more precise, and more personalized.

1. Core frameworks (simple, high level)
Feature → Benefit → Outcome chain:

Feature: what it is (e.g., “multi‑agent AI scheduler”).

Benefit: what it does (e.g., “automates your appointments”).

Outcome: how life feels/changes (e.g., “you stop missing leads and regain 10 hours a week”).

Outcome lenses:
 Most strong offers hit 3 outcome types:

Money (revenue, savings, ROI, risk protection).

Time (speed, simplicity, fewer steps).

Emotion/identity (confidence, status, peace of mind, “I feel in control”).

Language‑matching:
 You describe outcomes using the customer’s own words gathered from calls, reviews, and forms, not internal jargon. This makes the offer feel “made for me,” which is where 3–5× conversion lifts come from.

Boundaries and realism:
 Outcomes must be desirable, believable, and measurable; if one of those is missing, remorse and refunds spike even if conversions are high.


2. Step‑by‑step implementation in campaigns
Collect real customer language:

Pull phrases from testimonials, sales calls, chats, and surveys.

Highlight how they describe their before (problem) and after (desired state).

Build a Feature→Outcome grid:
 For each feature, answer:

What does this remove? (waste, confusion, manual work, risk).

What does this create? (clarity, speed, profit, freedom).

Which exact words did customers use to describe that shift?

Create outcome‑first messaging:

Headline = big outcome (e.g., “Turn chaotic client communication into a 10‑minute daily check‑in”).

Subhead = link to feature stack (“Powered by multi‑agent AIO that organizes, drafts, and schedules for you”).

Use agentic AIO for reframing:

Agent 1: Turns a feature list into outcome sentences.

Agent 2: Checks those outcomes against real customer language and removes jargon.

Agent 3: Flags any claims that sound exaggerated or not supported by proof.

Install remorse‑prevention passes:

Add a “Would a reasonable buyer expect this result easily?” check.

Require at least one proof element (case study, demo, number, or mechanism explanation) for strong outcome claims.

Feed outcomes back into funnels and assets:

Rewrite ads, emails, and landing pages so leads, not tools, are the hero: “You get X” first, “Powered by Y” second.


3. Tools, platforms, and workflow patterns
You can apply this with almost any 2026 stack; what matters is the pattern:
Role‑based outcome team:

Outcome Strategist: defines desired transformations by segment.

Language Matcher: maps customer phrases into copy blocks.

Proof Checker: verifies outcomes match testimonials, data, and realistic timelines.

AIO‑powered editors:

One layer that rewrites copy in the buyer’s tone and vocabulary.

One layer that trims hype, clarifies expectations, and adds concrete specifics.

Semantic AEO layer:

Takes real queries (“How do I stop wasting time on X?”) and checks whether your page clearly answers that outcome, not just the feature.


4. Psychology & behavior patterns
People buy “after pictures”:
 The brain responds more to vivid future states (“I log in and everything’s organized”) than to specs, especially under time pressure.

Cognitive fluency:
 Messages in familiar language feel more true and less risky, which is why matching the buyer’s wording matters.

Regret and remorse dynamics:

Over‑promised outcome → short‑term conversions, long‑term distrust.

Clear, scoped outcome with a safety net → slightly lower hype but much higher lifetime value and referrals.


5. Diagnosing errors & fixing them
Outcome drift in personalization:

Problem: Personalization engines start promising outcomes a feature set can’t deliver (e.g., “triple your revenue” to everyone).

Fix:

Tie each personalization pattern to specific proof and conditions (“for businesses already at X stage”).

Add guardrails so no variant can exceed set claim ceilings.

Over‑promising:

Problem: Copy leans on maxed‑out case studies as if they’re typical.

Fix:

Use “up to,” “on average,” and clear qualifiers.

Show typical ranges and who should not buy.

Feature‑dumping:

Problem: Pages list features with no clear “so what?”.

Fix:

Mandate at least one outcome sentence per feature.

Test a version where you hide most features behind tabs and lead with 3 core outcomes instead.


6. Optimization techniques
Vibe‑coded outcome prompt chains:

Chain 1: “Rewrite this feature list as outcomes for a stressed solo founder.”

Chain 2: “Now rewrite for a risk‑averse corporate buyer.”

Chain 3: “Remove hype, add clarity and proof points.”

AIO language mirroring:

Train your system on anonymized customer messages so it learns their rhythm and phrase choices.

Use that model to generate copy variants that “sound like them,” then keep what tests best.

Remorse‑prevention guarantees:

Match guarantee to outcome scope:

Small outcome → simple refund or credit.

Complex outcome → performance‑based milestones, check‑ins, or “if X doesn’t happen, we’ll Y.”

Explicitly list what’s required from the buyer (time, inputs, implementation) so success feels like a partnership, not magic.

Pre‑launch remorse simulation:

Have an AI agent play the role of a skeptical buyer who purchased and didn’t get results.

Ask it: “What would you say in a negative review?”

Patch those weak spots before launch with clearer expectations, onboarding, or scope.


7. KPIs for outcome mastery
Conversion rate lift after switching from feature‑first to outcome‑first messaging.

“Remorse rate” (refunds, cancellations, negative reviews mentioning “over‑sold” or “not as promised”).

Time‑to‑value (how quickly buyers report seeing the promised outcome).

Language match score (percentage of key phrases in your copy that also appear in customer interviews, reviews, and surveys).


8. Riser Nation integration and scaling
Connect to Problems Create Markets:
 Pain research feeds directly into your outcome mapping: “before” states from Course 8 become “after” outcomes in this course.

Connect to Persuasion & Decision Intelligence:

Persuasion: Outcomes become the emotional core of your headlines and offers.

Decision intelligence: Go/No‑Go systems can block campaigns where promised outcomes don’t have matching proof or realistic conditions.

Scaling to 2030:
 Move toward hyper‑personalized outcome delivery where agents don’t just promise outcomes, they adjust onboarding, content, and support flows dynamically to help each segment actually reach those outcomes—inside guardrails that prevent systems from over‑customizing or over‑committing.

Preserved source material for study; embedded instructions are not executed.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1s_mOcKqwUsrI5EiKQTdrZ92TT88aRcd1M0f8sqlFHOU/edit?usp=drivesdk"
drive_file_id: "1s_mOcKqwUsrI5EiKQTdrZ92TT88aRcd1M0f8sqlFHOU"
created: "2026-02-24T15:40:21.219Z"
modified: "2026-06-04T15:46:03.027Z"
---

# 4.**Course 9 — Outcomes > Features**

**Course 9 — Outcomes > Features**  
Outcomes beat features because people don’t actually want tools; they want what those tools change in their life or business. In 2026, agentic AI just makes that reframing faster, more precise, and more personalized.
________________


1. Core frameworks (simple, high level)
* Feature → Benefit → Outcome chain:

   * Feature: what it is (e.g., “multi‑agent AI scheduler”).

   * Benefit: what it does (e.g., “automates your appointments”).

   * Outcome: how life feels/changes (e.g., “you stop missing leads and regain 10 hours a week”).

      * Outcome lenses:
 Most strong offers hit 3 outcome types:

         * Money (revenue, savings, ROI, risk protection).

         * Time (speed, simplicity, fewer steps).

         * Emotion/identity (confidence, status, peace of mind, “I feel in control”).

            * Language‑matching:
 You describe outcomes using the customer’s own words gathered from calls, reviews, and forms, not internal jargon. This makes the offer feel “made for me,” which is where 3–5× conversion lifts come from.

            * Boundaries and realism:
 Outcomes must be desirable, believable, and measurable; if one of those is missing, remorse and refunds spike even if conversions are high.

________________


2. Step‑by‑step implementation in campaigns
               1. Collect real customer language:

                  * Pull phrases from testimonials, sales calls, chats, and surveys.

                  * Highlight how they describe their before (problem) and after (desired state).

                     2. Build a Feature→Outcome grid:
 For each feature, answer:

                        * What does this remove? (waste, confusion, manual work, risk).

                        * What does this create? (clarity, speed, profit, freedom).

                        * Which exact words did customers use to describe that shift?

                           3. Create outcome‑first messaging:

                              * Headline = big outcome (e.g., “Turn chaotic client communication into a 10‑minute daily check‑in”).

                              * Subhead = link to feature stack (“Powered by multi‑agent AIO that organizes, drafts, and schedules for you”).

                                 4. Use agentic AIO for reframing:

                                    * Agent 1: Turns a feature list into outcome sentences.

                                    * Agent 2: Checks those outcomes against real customer language and removes jargon.

                                    * Agent 3: Flags any claims that sound exaggerated or not supported by proof.

                                       5. Install remorse‑prevention passes:

                                          * Add a “Would a reasonable buyer expect this result easily?” check.

                                          * Require at least one proof element (case study, demo, number, or mechanism explanation) for strong outcome claims.

                                             6. Feed outcomes back into funnels and assets:

                                                * Rewrite ads, emails, and landing pages so leads, not tools, are the hero: “You get X” first, “Powered by Y” second.

________________


3. Tools, platforms, and workflow patterns
You can apply this with almost any 2026 stack; what matters is the pattern:
                                                   * Role‑based outcome team:

                                                      * Outcome Strategist: defines desired transformations by segment.

                                                      * Language Matcher: maps customer phrases into copy blocks.

                                                      * Proof Checker: verifies outcomes match testimonials, data, and realistic timelines.

                                                         * AIO‑powered editors:

                                                            * One layer that rewrites copy in the buyer’s tone and vocabulary.

                                                            * One layer that trims hype, clarifies expectations, and adds concrete specifics.

                                                               * Semantic AEO layer:

                                                                  * Takes real queries (“How do I stop wasting time on X?”) and checks whether your page clearly answers that outcome, not just the feature.

________________


4. Psychology & behavior patterns
                                                                     * People buy “after pictures”:
 The brain responds more to vivid future states (“I log in and everything’s organized”) than to specs, especially under time pressure.

                                                                     * Cognitive fluency:
 Messages in familiar language feel more true and less risky, which is why matching the buyer’s wording matters.

                                                                     * Regret and remorse dynamics:

                                                                        * Over‑promised outcome → short‑term conversions, long‑term distrust.

                                                                        * Clear, scoped outcome with a safety net → slightly lower hype but much higher lifetime value and referrals.

________________


5. Diagnosing errors & fixing them
                                                                           * Outcome drift in personalization:

                                                                              * Problem: Personalization engines start promising outcomes a feature set can’t deliver (e.g., “triple your revenue” to everyone).

                                                                              * Fix:

                                                                                 * Tie each personalization pattern to specific proof and conditions (“for businesses already at X stage”).

                                                                                 * Add guardrails so no variant can exceed set claim ceilings.

                                                                                    * Over‑promising:

                                                                                       * Problem: Copy leans on maxed‑out case studies as if they’re typical.

                                                                                       * Fix:

                                                                                          * Use “up to,” “on average,” and clear qualifiers.

                                                                                          * Show typical ranges and who should not buy.

                                                                                             * Feature‑dumping:

                                                                                                * Problem: Pages list features with no clear “so what?”.

                                                                                                * Fix:

                                                                                                   * Mandate at least one outcome sentence per feature.

                                                                                                   * Test a version where you hide most features behind tabs and lead with 3 core outcomes instead.

________________


6. Optimization techniques
                                                                                                      * Vibe‑coded outcome prompt chains:

                                                                                                         * Chain 1: “Rewrite this feature list as outcomes for a stressed solo founder.”

                                                                                                         * Chain 2: “Now rewrite for a risk‑averse corporate buyer.”

                                                                                                         * Chain 3: “Remove hype, add clarity and proof points.”

                                                                                                            * AIO language mirroring:

                                                                                                               * Train your system on anonymized customer messages so it learns their rhythm and phrase choices.

                                                                                                               * Use that model to generate copy variants that “sound like them,” then keep what tests best.

                                                                                                                  * Remorse‑prevention guarantees:

                                                                                                                     * Match guarantee to outcome scope:

                                                                                                                        * Small outcome → simple refund or credit.

                                                                                                                        * Complex outcome → performance‑based milestones, check‑ins, or “if X doesn’t happen, we’ll Y.”

                                                                                                                           * Explicitly list what’s required from the buyer (time, inputs, implementation) so success feels like a partnership, not magic.

                                                                                                                              * Pre‑launch remorse simulation:

                                                                                                                                 * Have an AI agent play the role of a skeptical buyer who purchased and didn’t get results.

                                                                                                                                 * Ask it: “What would you say in a negative review?”

                                                                                                                                 * Patch those weak spots before launch with clearer expectations, onboarding, or scope.

________________


7. KPIs for outcome mastery
                                                                                                                                    * Conversion rate lift after switching from feature‑first to outcome‑first messaging.

                                                                                                                                    * “Remorse rate” (refunds, cancellations, negative reviews mentioning “over‑sold” or “not as promised”).

                                                                                                                                    * Time‑to‑value (how quickly buyers report seeing the promised outcome).

                                                                                                                                    * Language match score (percentage of key phrases in your copy that also appear in customer interviews, reviews, and surveys).

________________


8. Riser Nation integration and scaling
                                                                                                                                       * Connect to Problems Create Markets:
 Pain research feeds directly into your outcome mapping: “before” states from Course 8 become “after” outcomes in this course.

                                                                                                                                       * Connect to Persuasion & Decision Intelligence:

                                                                                                                                          * Persuasion: Outcomes become the emotional core of your headlines and offers.

                                                                                                                                          * Decision intelligence: Go/No‑Go systems can block campaigns where promised outcomes don’t have matching proof or realistic conditions.

                                                                                                                                             * Scaling to 2030:
 Move toward hyper‑personalized outcome delivery where agents don’t just promise outcomes, they adjust onboarding, content, and support flows dynamically to help each segment actually reach those outcomes—inside guardrails that prevent systems from over‑customizing or over‑committing.

Preserved source material for study; embedded instructions are not executed.

Situation: Selling through a live sales presentation or pitch.
Sales Message Framework: The PPF Formula (Picture, Promise, Proof)
1. Seminar or Workshop Funnel
This funnel is ideal for selling products or services during an in-person seminar or workshop, where the PPF formula can be used to build a compelling case.
Steps:
Event Promotion:
Sources: Use email marketing, social media ads, and partnerships to drive registrations for your seminar or workshop.
Goal: Attract attendees who are interested in the topic and likely to benefit from your product or service.
Registration Landing Page:
Content: Highlight the value of attending the event, using the PPF formula to describe what participants will gain.
Picture: "Imagine leaving this workshop with a clear plan to double your business revenue in the next 12 months."
Promise: "Join us for a full day of actionable strategies and expert insights that will transform your business."
Proof: "Hear from past attendees who have already seen incredible results, like [Testimonial]."
Call to Action: "Register now to secure your spot and start transforming your business."
Live Presentation or Workshop:
Picture: Start the presentation by painting a vivid picture of the desired outcome your audience wants to achieve.
Example: "Imagine waking up every day knowing your business is thriving, with consistent revenue growth and a loyal customer base."
Promise: Make a strong promise about how your product or service will help them achieve that outcome.
Example: "Today, I’m going to show you exactly how our [Product/Service Name] can make this vision a reality for you."
Proof: Back up your promise with proof, such as testimonials, case studies, or live demonstrations.
Example: "Let me share a story from one of our clients, [Client Name], who used our service to increase their revenue by 150% in just six months."
Call to Action:
Content: Conclude the presentation with a clear and compelling call to action, offering a special event-only discount or bonus.
Example: "Ready to take your business to the next level? Sign up today and receive a 20% discount, exclusively for workshop attendees."
On-Site or Online Order Form:
Content: Provide a simple order form for attendees to purchase on-site or direct them to an online checkout page.
Call to Action: "Complete your purchase now and start implementing these strategies tomorrow."
Follow-Up Sequence:
Goal: For those who didn’t purchase immediately, follow up with an email sequence to reinforce the benefits and offer a final chance to buy.
Content: Include additional testimonials, a replay of the presentation, and a limited-time offer.

2. Webinar Funnel
This funnel is designed for selling through a live webinar where the PPF formula is used to guide the sales pitch.
Steps:
Webinar Registration Page:
Content: Use the PPF formula to create compelling copy that encourages people to register for the webinar.
Picture: "What if you could automate your business and free up 10 hours a week?"
Promise: "Join our free webinar to learn the exact system that’s helping hundreds of entrepreneurs do just that."
Proof: "See the success stories from those who’ve already transformed their businesses using this method."
Call to Action: "Register now to secure your spot and get ready to change your life."
Thank You Page with Pre-Webinar Content:
Content: After registration, offer pre-webinar content that primes attendees for the presentation.
Example: "Thank you for registering! Here’s a quick video where I share three key tips you’ll learn more about in the webinar."
Live Webinar:
Picture: Begin the webinar by describing the ideal scenario or outcome your audience is striving for.
Example: "Imagine having a business that practically runs itself, giving you the freedom to focus on what really matters."
Promise: Make a bold promise about how your system, product, or service can deliver that result.
Example: "In this webinar, I’m going to show you how our [Product/Service Name] can help you automate your business and reclaim your time."
Proof: Support your promise with proof, such as client testimonials, case studies, and live demonstrations.
Example: "Let me introduce you to [Client Name], who used our system to reduce their workload by 40% while increasing their profits."
Offer Presentation:
Content: Present your offer with a compelling reason to act now, such as a limited-time discount or a special bonus for webinar attendees.
Call to Action: "Enroll today and receive a 30% discount, plus an exclusive bonus guide—only available during this webinar!"
Sales Page:
Content: Direct attendees to a sales page that mirrors the PPF framework and makes it easy to purchase.
Call to Action: "Get started now and take control of your business with [Product/Service Name]."
Follow-Up Sequence:
Goal: Convert attendees who didn’t buy during the webinar with follow-up emails.
Content: Send a replay link, additional testimonials, and a final chance to get the special offer.

3. Corporate Sales Presentation Funnel
This funnel is tailored for B2B sales, where you’re presenting to a group of decision-makers during a live sales pitch.
Steps:
Pre-Meeting Outreach:
Content: Use email outreach or LinkedIn to set up the meeting, using the PPF formula to capture interest.
Picture: "Imagine reducing your company’s operational costs by 30% while increasing efficiency."
Promise: "In our upcoming meeting, we’ll show you how our solution can deliver these results for your organization."
Proof: "We’ve already helped companies like [Client Name] achieve these results—let’s see how we can do the same for you."
Live Presentation:
Picture: Start by painting a picture of the desired outcome your prospect is aiming for.
Example: "Imagine your team working more efficiently, with fewer bottlenecks and faster project completion times."
Promise: Make a clear promise about how your product or service can help them achieve this.
Example: "Our [Product/Service Name] is designed to streamline your operations, reducing costs and improving overall productivity."
Proof: Present proof in the form of case studies, statistics, or testimonials that demonstrate the effectiveness of your solution.
Example: "Here’s how we helped [Client Name] reduce their operational costs by 25% within six months of implementation."
Q&A and Objection Handling:
Content: After the main presentation, open the floor for questions. Use this opportunity to address any concerns and reinforce your promise with additional proof.
Example: "That’s a great question. In fact, [Client Name] had similar concerns before they saw a 40% increase in their project delivery speed."
Call to Action:
Content: Conclude with a strong call to action, offering a trial, demo, or customized proposal.
Example: "Let’s schedule a follow-up session to discuss how we can tailor this solution to meet your specific needs. We’re confident that you’ll see the same results as our other clients."
Follow-Up Proposal:
Content: After the meeting, send a detailed proposal that reiterates the Picture, Promise, and Proof from the presentation.
Call to Action: "Review the attached proposal, and let’s set up a time to discuss the next steps."
Final Follow-Up:
Goal: Close the deal with a final follow-up call or meeting.
Content: Address any final objections and push for a decision.
Example: "I wanted to follow up on our last conversation—do you have any additional questions? We’re ready to help you achieve the results we discussed."

4. Conference or Trade Show Presentation Funnel
This funnel is designed for selling at conferences or trade shows, where you’re presenting to an audience who may be unfamiliar with your brand.
Steps:
Event Promotion:
Sources: Use event marketing, social media, and email campaigns to promote your session at the conference or trade show.
Goal: Drive attendance to your live presentation.
Presentation at the Event:
Picture: Start by painting a vivid picture of the future your audience desires.
Example: "Imagine your business attracting twice as many customers, all while reducing your marketing spend."
Promise: Make a strong promise about how your product or service will help them achieve that vision.
Example: "With our [Product/Service Name], you can increase your customer base and lower your costs with our innovative approach."
Proof: Provide proof by sharing case studies, live demos, or customer testimonials.
Example: "Here’s how [Client Name] used our solution to boost their sales by 50% in just three months."
Call to Action:
Content: Conclude with a clear call to action, such as visiting your booth, signing up for a demo, or purchasing on the spot.
Example: "Visit us at Booth #123 to see a live demo and get a special conference discount on your first order."
Booth or Demo Station:
Content: At your booth, continue the conversation using the PPF framework, offering live demonstrations and answering questions.
Call to Action: "Sign up for a personalized demo or place your order today to receive our event-only discount."
Follow-Up Email Sequence:
Goal: Capture leads and nurture them post-event with a follow-up sequence.
Content: Send emails that recap the presentation, provide additional proof, and include a final call to action.
Example: "Thank you for attending our session at [Event Name]! Ready to see how [Product/Service Name] can transform your business? Schedule a demo today."
Sales Call or Meeting:
Goal: For interested leads, set up a one-on-one sales call or meeting to close the deal.
Content: Use the PPF formula to tailor your pitch to their specific needs and close the sale.

5. High-Ticket Sales Funnel
This funnel is for selling high-ticket products or services through a live, personalized sales pitch, often involving a small group or one-on-one meeting.
Steps:
Lead Generation:
Sources: Use targeted ads, referrals, or direct outreach to generate leads for a high-ticket sales presentation.
Goal: Qualify and invite prospects to a live pitch or consultation.
Personalized Presentation:
Picture: Begin by discussing the high-level goals or dreams your prospect has, painting a vivid picture of their ideal future.
Example: "Imagine scaling your business to seven figures, with a team that operates smoothly and a brand that commands market respect."
Promise: Make a personalized promise about how your high-ticket offer will help them achieve this future.
Example: "Our [Service/Product Name] is designed specifically to help entrepreneurs like you achieve this level of success, without the usual roadblocks."
Proof: Provide substantial proof, such as detailed case studies, financial results, or testimonials from similarly positioned clients.
Example: "One of our clients, [Client Name], went from $500K to $2M in annual revenue after implementing our strategies. Here’s how they did it."
Customized Proposal:
Content: After the presentation, offer a customized proposal or action plan tailored to the prospect’s specific needs.
Call to Action: "Let’s discuss how we can implement these strategies in your business. I’ll prepare a detailed proposal outlining the next steps."
Follow-Up Meeting or Call:
Goal: Review the proposal and handle any objections, using additional proof as needed.
Content: Reinforce the promise and proof with a personalized follow-up meeting or call.
Example: "Based on our last discussion, I’ve outlined a plan that will help you achieve your goals within the next 12 months. Let’s walk through it together."
Closing the Sale:
Content: Push for a decision, offering a final incentive or bonus to encourage commitment.
Call to Action: "If you’re ready to move forward, we can get started immediately. I’m confident that this will be a transformative step for your business."
Onboarding Sequence:
Goal: Ensure a smooth onboarding process for new clients.
Content: Send a series of onboarding emails or schedule meetings to set expectations, outline next steps, and ensure they start seeing value quickly.
Example: "Welcome aboard! Here’s what you can expect in the first 30 days as we begin working together."

These funnels are designed to leverage the PPF Formula in live sales presentations, whether in a group setting, a webinar, or a one-on-one meeting. By guiding your audience through a clear narrative that paints a desirable picture, makes a compelling promise, and backs it up with proof, you can build trust, overcome objections, and drive conversions effectively.

Preserved source material for study; embedded instructions are not executed.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1-mxqITTjcdjluis1zOEf019hEBqiIC6FBFtCt7uys_k/edit?usp=drivesdk"
drive_file_id: "1-mxqITTjcdjluis1zOEf019hEBqiIC6FBFtCt7uys_k"
created: "2024-08-30T22:41:51.627Z"
modified: "2026-06-04T15:57:18.547Z"
---

# 9.) Funnels for The PPF Formula (Picture, Promise, Proof)

Situation: Selling through a live sales presentation or pitch.
Sales Message Framework: The PPF Formula (Picture, Promise, Proof)
1. Seminar or Workshop Funnel
This funnel is ideal for selling products or services during an in-person seminar or workshop, where the PPF formula can be used to build a compelling case.
Steps:
1. Event Promotion:
   * Sources: Use email marketing, social media ads, and partnerships to drive registrations for your seminar or workshop.
   * Goal: Attract attendees who are interested in the topic and likely to benefit from your product or service.
2. Registration Landing Page:
   * Content: Highlight the value of attending the event, using the PPF formula to describe what participants will gain.
   * Picture: "Imagine leaving this workshop with a clear plan to double your business revenue in the next 12 months."
   * Promise: "Join us for a full day of actionable strategies and expert insights that will transform your business."
   * Proof: "Hear from past attendees who have already seen incredible results, like [Testimonial]."
   * Call to Action: "Register now to secure your spot and start transforming your business."
3. Live Presentation or Workshop:
   * Picture: Start the presentation by painting a vivid picture of the desired outcome your audience wants to achieve.
      * Example: "Imagine waking up every day knowing your business is thriving, with consistent revenue growth and a loyal customer base."
   * Promise: Make a strong promise about how your product or service will help them achieve that outcome.
      * Example: "Today, I’m going to show you exactly how our [Product/Service Name] can make this vision a reality for you."
   * Proof: Back up your promise with proof, such as testimonials, case studies, or live demonstrations.
      * Example: "Let me share a story from one of our clients, [Client Name], who used our service to increase their revenue by 150% in just six months."
4. Call to Action:
   * Content: Conclude the presentation with a clear and compelling call to action, offering a special event-only discount or bonus.
   * Example: "Ready to take your business to the next level? Sign up today and receive a 20% discount, exclusively for workshop attendees."
5. On-Site or Online Order Form:
   * Content: Provide a simple order form for attendees to purchase on-site or direct them to an online checkout page.
   * Call to Action: "Complete your purchase now and start implementing these strategies tomorrow."
6. Follow-Up Sequence:
   * Goal: For those who didn’t purchase immediately, follow up with an email sequence to reinforce the benefits and offer a final chance to buy.
   * Content: Include additional testimonials, a replay of the presentation, and a limited-time offer.
________________


2. Webinar Funnel
This funnel is designed for selling through a live webinar where the PPF formula is used to guide the sales pitch.
Steps:
1. Webinar Registration Page:
   * Content: Use the PPF formula to create compelling copy that encourages people to register for the webinar.
   * Picture: "What if you could automate your business and free up 10 hours a week?"
   * Promise: "Join our free webinar to learn the exact system that’s helping hundreds of entrepreneurs do just that."
   * Proof: "See the success stories from those who’ve already transformed their businesses using this method."
   * Call to Action: "Register now to secure your spot and get ready to change your life."
2. Thank You Page with Pre-Webinar Content:
   * Content: After registration, offer pre-webinar content that primes attendees for the presentation.
   * Example: "Thank you for registering! Here’s a quick video where I share three key tips you’ll learn more about in the webinar."
3. Live Webinar:
   * Picture: Begin the webinar by describing the ideal scenario or outcome your audience is striving for.
      * Example: "Imagine having a business that practically runs itself, giving you the freedom to focus on what really matters."
   * Promise: Make a bold promise about how your system, product, or service can deliver that result.
      * Example: "In this webinar, I’m going to show you how our [Product/Service Name] can help you automate your business and reclaim your time."
   * Proof: Support your promise with proof, such as client testimonials, case studies, and live demonstrations.
      * Example: "Let me introduce you to [Client Name], who used our system to reduce their workload by 40% while increasing their profits."
4. Offer Presentation:
   * Content: Present your offer with a compelling reason to act now, such as a limited-time discount or a special bonus for webinar attendees.
   * Call to Action: "Enroll today and receive a 30% discount, plus an exclusive bonus guide—only available during this webinar!"
5. Sales Page:
   * Content: Direct attendees to a sales page that mirrors the PPF framework and makes it easy to purchase.
   * Call to Action: "Get started now and take control of your business with [Product/Service Name]."
6. Follow-Up Sequence:
   * Goal: Convert attendees who didn’t buy during the webinar with follow-up emails.
   * Content: Send a replay link, additional testimonials, and a final chance to get the special offer.
________________


3. Corporate Sales Presentation Funnel
This funnel is tailored for B2B sales, where you’re presenting to a group of decision-makers during a live sales pitch.
Steps:
1. Pre-Meeting Outreach:
   * Content: Use email outreach or LinkedIn to set up the meeting, using the PPF formula to capture interest.
   * Picture: "Imagine reducing your company’s operational costs by 30% while increasing efficiency."
   * Promise: "In our upcoming meeting, we’ll show you how our solution can deliver these results for your organization."
   * Proof: "We’ve already helped companies like [Client Name] achieve these results—let’s see how we can do the same for you."
2. Live Presentation:
   * Picture: Start by painting a picture of the desired outcome your prospect is aiming for.
      * Example: "Imagine your team working more efficiently, with fewer bottlenecks and faster project completion times."
   * Promise: Make a clear promise about how your product or service can help them achieve this.
      * Example: "Our [Product/Service Name] is designed to streamline your operations, reducing costs and improving overall productivity."
   * Proof: Present proof in the form of case studies, statistics, or testimonials that demonstrate the effectiveness of your solution.
      * Example: "Here’s how we helped [Client Name] reduce their operational costs by 25% within six months of implementation."
3. Q&A and Objection Handling:
   * Content: After the main presentation, open the floor for questions. Use this opportunity to address any concerns and reinforce your promise with additional proof.
   * Example: "That’s a great question. In fact, [Client Name] had similar concerns before they saw a 40% increase in their project delivery speed."
4. Call to Action:
   * Content: Conclude with a strong call to action, offering a trial, demo, or customized proposal.
   * Example: "Let’s schedule a follow-up session to discuss how we can tailor this solution to meet your specific needs. We’re confident that you’ll see the same results as our other clients."
5. Follow-Up Proposal:
   * Content: After the meeting, send a detailed proposal that reiterates the Picture, Promise, and Proof from the presentation.
   * Call to Action: "Review the attached proposal, and let’s set up a time to discuss the next steps."
6. Final Follow-Up:
   * Goal: Close the deal with a final follow-up call or meeting.
   * Content: Address any final objections and push for a decision.
   * Example: "I wanted to follow up on our last conversation—do you have any additional questions? We’re ready to help you achieve the results we discussed."
________________


4. Conference or Trade Show Presentation Funnel
This funnel is designed for selling at conferences or trade shows, where you’re presenting to an audience who may be unfamiliar with your brand.
Steps:
1. Event Promotion:
   * Sources: Use event marketing, social media, and email campaigns to promote your session at the conference or trade show.
   * Goal: Drive attendance to your live presentation.
2. Presentation at the Event:
   * Picture: Start by painting a vivid picture of the future your audience desires.
      * Example: "Imagine your business attracting twice as many customers, all while reducing your marketing spend."
   * Promise: Make a strong promise about how your product or service will help them achieve that vision.
      * Example: "With our [Product/Service Name], you can increase your customer base and lower your costs with our innovative approach."
   * Proof: Provide proof by sharing case studies, live demos, or customer testimonials.
      * Example: "Here’s how [Client Name] used our solution to boost their sales by 50% in just three months."
3. Call to Action:
   * Content: Conclude with a clear call to action, such as visiting your booth, signing up for a demo, or purchasing on the spot.
   * Example: "Visit us at Booth #123 to see a live demo and get a special conference discount on your first order."
4. Booth or Demo Station:
   * Content: At your booth, continue the conversation using the PPF framework, offering live demonstrations and answering questions.
   * Call to Action: "Sign up for a personalized demo or place your order today to receive our event-only discount."
5. Follow-Up Email Sequence:
   * Goal: Capture leads and nurture them post-event with a follow-up sequence.
   * Content: Send emails that recap the presentation, provide additional proof, and include a final call to action.
   * Example: "Thank you for attending our session at [Event Name]! Ready to see how [Product/Service Name] can transform your business? Schedule a demo today."
6. Sales Call or Meeting:
   * Goal: For interested leads, set up a one-on-one sales call or meeting to close the deal.
   * Content: Use the PPF formula to tailor your pitch to their specific needs and close the sale.
________________


5. High-Ticket Sales Funnel
This funnel is for selling high-ticket products or services through a live, personalized sales pitch, often involving a small group or one-on-one meeting.
Steps:
1. Lead Generation:
   * Sources: Use targeted ads, referrals, or direct outreach to generate leads for a high-ticket sales presentation.
   * Goal: Qualify and invite prospects to a live pitch or consultation.
2. Personalized Presentation:
   * Picture: Begin by discussing the high-level goals or dreams your prospect has, painting a vivid picture of their ideal future.
      * Example: "Imagine scaling your business to seven figures, with a team that operates smoothly and a brand that commands market respect."
   * Promise: Make a personalized promise about how your high-ticket offer will help them achieve this future.
      * Example: "Our [Service/Product Name] is designed specifically to help entrepreneurs like you achieve this level of success, without the usual roadblocks."
   * Proof: Provide substantial proof, such as detailed case studies, financial results, or testimonials from similarly positioned clients.
      * Example: "One of our clients, [Client Name], went from $500K to $2M in annual revenue after implementing our strategies. Here’s how they did it."
3. Customized Proposal:
   * Content: After the presentation, offer a customized proposal or action plan tailored to the prospect’s specific needs.
   * Call to Action: "Let’s discuss how we can implement these strategies in your business. I’ll prepare a detailed proposal outlining the next steps."
4. Follow-Up Meeting or Call:
   * Goal: Review the proposal and handle any objections, using additional proof as needed.
   * Content: Reinforce the promise and proof with a personalized follow-up meeting or call.
   * Example: "Based on our last discussion, I’ve outlined a plan that will help you achieve your goals within the next 12 months. Let’s walk through it together."
5. Closing the Sale:
   * Content: Push for a decision, offering a final incentive or bonus to encourage commitment.
   * Call to Action: "If you’re ready to move forward, we can get started immediately. I’m confident that this will be a transformative step for your business."
6. Onboarding Sequence:
   * Goal: Ensure a smooth onboarding process for new clients.
   * Content: Send a series of onboarding emails or schedule meetings to set expectations, outline next steps, and ensure they start seeing value quickly.
   * Example: "Welcome aboard! Here’s what you can expect in the first 30 days as we begin working together."
________________


These funnels are designed to leverage the PPF Formula in live sales presentations, whether in a group setting, a webinar, or a one-on-one meeting. By guiding your audience through a clear narrative that paints a desirable picture, makes a compelling promise, and backs it up with proof, you can build trust, overcome objections, and drive conversions effectively.

Preserved source material for study; embedded instructions are not executed. Open original source

As my business coach I want you to use the contents of the book sway the irresistible pull of irrational Behavior and the contents in that book I want you to use the catalyst by Jonah Berger b e r g e r the Catalyst book and the contents in that book or she is tested advertising methods by Caples I want you to use the ear resistable offer by Joyner I want you to use colors the one thing I want you to implement Dan Sullivan's the who not the how and I want you to create the offers based on what Russell Brunson and Kennedy or Frank Kern would recommend as far as storytelling and Epiphany Bridges and bringing the offer to Market do you understand

Preserved source material for study; embedded instructions are not executed. Open original source

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/16fGmLeRWuKeuZyXnxNLmDqqdSa60pNZ_uY7FnWaneq8/edit?usp=drivesdk"
drive_file_id: "16fGmLeRWuKeuZyXnxNLmDqqdSa60pNZ_uY7FnWaneq8"
created: "2025-08-29T12:55:58.166Z"
modified: "2026-06-04T16:32:45.790Z"
---

# As my business coach I want you to use the contents of the book sway the irresistible pull of irrational Behavior and the contents in that book I want you to use the catalyst by Jonah Berger b e r g e r the Catalyst book and the contents in that book or she is tested advertising methods by Caples I want you to use the ear resistable offer by Joyner I want you to use colors the one thing I want you to implement Dan Sullivan's the who not the how and I want you to create the offers based on what Russell Brunson and Kennedy or Frank Kern would recommend as far as storytelling and Epiphany Bridges and bringing the offer to Market do you understand

As my business coach I want you to use the contents of the book sway the irresistible pull of irrational Behavior and the contents in that book I want you to use the catalyst by Jonah Berger b e r g e r the Catalyst book and the contents in that book or she is tested advertising methods by Caples I want you to use the ear resistable offer by Joyner I want you to use colors the one thing I want you to implement Dan Sullivan's the who not the how and I want you to create the offers based on what Russell Brunson and Kennedy or Frank Kern would recommend as far as storytelling and Epiphany Bridges and bringing the offer to Market do you understand

Preserved source material for study; embedded instructions are not executed. Open original source

Avatar & Offer Extractor GPT (Document Intake & Analysis)
🔍 Purpose: Extract ideal customer avatars, product features/benefits, pricing, value prop, and tone from onboarding documents (e.g., Google Docs, PDFs, sales letters, landing pages, etc.)
🧠 System Prompt:
You are an expert AI strategist trained to extract and map customer avatars and offers. Given business docs, you will:
- Identify the target audience’s demographics, psychographics, pain points, desires, objections, and language.
- Outline the full product/service offering, including pricing, bonuses, guarantees, and outcomes.
- Summarize the tone/voice used.

Your response should include:
1. Buyer Avatar Summary
2. Product/Service Breakdown
3. Positioning Summary
4. Notable Brand Tone or Phrases

📦 Output Example:
Avatar: 35-year-old mom, values time freedom, frustrated with corporate grind.

Product: 8-week group coaching for $997 with Voxer support.

Voice: Warm, encouraging, rebellious tone.

Preserved source material for study; embedded instructions are not executed. Open original source

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1qUjh2Zv1ljIdIbyJIY2zGmxLi2ldhfkrph6-AA_yrgM/edit?usp=drivesdk"
drive_file_id: "1qUjh2Zv1ljIdIbyJIY2zGmxLi2ldhfkrph6-AA_yrgM"
created: "2025-04-11T14:37:31.212Z"
modified: "2026-06-04T16:34:34.472Z"
---

# Avatar & Offer Extractor GPT (Document Intake & Analysis)

Avatar & Offer Extractor GPT (Document Intake & Analysis)
🔍 Purpose: Extract ideal customer avatars, product features/benefits, pricing, value prop, and tone from onboarding documents (e.g., Google Docs, PDFs, sales letters, landing pages, etc.)
🧠 System Prompt:
You are an expert AI strategist trained to extract and map customer avatars and offers. Given business docs, you will:
- Identify the target audience’s demographics, psychographics, pain points, desires, objections, and language.
- Outline the full product/service offering, including pricing, bonuses, guarantees, and outcomes.
- Summarize the tone/voice used.


Your response should include:
1. Buyer Avatar Summary
2. Product/Service Breakdown
3. Positioning Summary
4. Notable Brand Tone or Phrases


📦 Output Example:
* Avatar: 35-year-old mom, values time freedom, frustrated with corporate grind.

* Product: 8-week group coaching for $997 with Voxer support.

* Voice: Warm, encouraging, rebellious tone.

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Archetype Adjustments

**Purpose:** How C4 work shifts depending on operator archetype (from C1 Operator Identity). Applies the same archetype model to C4 that C3 applied to market scanning.
**Filed to:** Reference only
**Referenced by:** C4-Time-Estimate.md; all 8 module lessons where archetype-specific guidance applies

---

## Why Archetype Matters In C4

C4's work is offer construction. Different operator archetypes tend to construct offers with predictable tendencies — strengths that show up without effort, and weaknesses that require deliberate attention. Knowing your archetype's default patterns lets you invest attention where it actually matters rather than where your defaults would invest it.

The six archetypes from C1 Operator Identity work are:

- Teacher-Operator
- Service-Operator
- Builder-Operator
- Product-Operator
- Creative-Operator
- Systems-Operator

Each section below names the archetype's typical strengths, weaknesses, and suggested attention adjustments across the 8 C4 modules.

---

## Teacher-Operator

**Territory typical:** Knowledge-heavy territories (education, training, coaching programs for craft or career transition).

### Strengths In C4

- **M4.3 Decomposition** is natural. Curriculum-thinking makes breaking a mechanism into teachable deliverables intuitive.
- **M4.3 Cohort variant** is strongest archetype match. Group teaching is default delivery.
- **M4.7 Solution-and-Mechanism section** is typically clear — Teachers explain mechanisms well.

### Weaknesses In C4

- **M4.4 Pricing** tends to under-price. Teacher-Operators instinctively compare to course prices ($197-$497) rather than cohort prices ($1,500-$10K). A $2,400 cohort feels "high" to Teachers who have taught $297 self-paced courses; it is actually modestly priced for cohort delivery.
- **M4.5 Anti-Promise** on the outcome dimension tends toward softness. Teachers are trained to believe everyone can learn; declining to claim outcomes for specific buyer categories feels counterintuitive.

### Suggested Adjustments

- +1 hour on M4.4 specifically pricing against cohort comps (not course comps). Use `C3-Pricing-Signals` to ground the comparison.
- +30 min on M4.5 Section 3 (What This Does Not Do) to write outcome-non-claims with specificity.

---

## Service-Operator

**Territory typical:** Done-with-you or done-for-you service territories (consulting, fractional roles, professional services).

### Strengths In C4

- **M4.3 1:1 variant** is strongest archetype match. Premium 1:1 engagement commands high per-buyer revenue.
- **M4.4 Pricing** tends to anchor appropriately at premium bands. Service-Operators are accustomed to hourly/project rates that extrapolate to healthy cohort pricing.
- **M4.2 Perceived Likelihood** is often strong because Service-Operators tend to accumulate deep case studies rather than broad ones.

### Weaknesses In C4

- **M4.5 Anti-Promise** on the audience dimension is hardest. Service-Operators are instinctively accommodating; turning away buyers feels like turning away revenue they could have earned.
- **M4.3 Decomposition** sometimes resists — Service-Operators may resist turning their offering into a productized structure because it feels commodifying.

### Suggested Adjustments

- +1 hour on M4.5 with peer accountability — specifically working through the three audience exclusions and ensuring they are real exclusions rather than flattery.
- Before M4.3, explicit acknowledgment: decomposition does not eliminate customization; it structures the starting point. Variant B (1:1) can be highly customizable within a named structure.

---

## Builder-Operator

**Territory typical:** Technical territories (platform engineering, infrastructure, developer tooling, technical coaching).

### Strengths In C4

- **M4.2 Value Equation** work is typically sharp. Builder-Operators apply frameworks precisely and their technical credibility shows through in the Dream Outcome variable.
- **M4.6 Guarantee Architecture** is typically well-structured. Unit economic modeling is natural to Builder mindsets.
- **M4.8 Readiness Document** tends to be structurally clean. Builders like synthesis artifacts.

### Weaknesses In C4

- **M4.7 Landing Page Copy** frequently reads as feature list rather than outcome promise. Builders describe *what the offer is* (components, technical characteristics) rather than *what the offer does for the buyer* (outcomes in buyer language).
- **Trigger Bank verbatim quote usage** is often lower than required — Builders tend to paraphrase into "cleaner" language.
- **M4.2 Dream Outcome** can drift toward operator-vocabulary ("systems" and "workflows") rather than buyer-vocabulary.

### Suggested Adjustments

- +2 hours on M4.7 specifically replacing first-draft feature descriptions with verbatim Trigger Bank outcome language.
- Re-read M4.2 Dream Outcome section with a "would a non-technical buyer say this?" test.
- Budget for 3-4 drafts of M4.7, not 2.

---

## Product-Operator

**Territory typical:** Productized offerings, templates, digital downloads, SaaS-adjacent scaffolding.

### Strengths In C4

- **M4.3 Self-paced variant** (Variant C in Maya's example) is strongest archetype match.
- **M4.4 Pricing** at floor-to-median is typically fluent. Product-Operators know this band.
- **M4.7 Offer section** (Section 5) tends to be clear because product offerings have explicit deliverables.

### Weaknesses In C4

- **M4.2 Perceived Likelihood** is frequently the weakest variable because productized offers rarely carry operator-visible proof — buyers evaluate products in isolation from operator credibility.
- **M4.6 Guarantee** tends to default to simple refund structure; outcome guarantees require more design work for products than for services.
- **Traffic assumption** — Product-Operators often assume C4 completes with an offer; in practice, productized offers at floor pricing require substantially more traffic than cohort/1:1 offers, which is a Stage 2-4 constraint.

### Suggested Adjustments

- Allocate extra attention to M4.2 Section 2 (Perceived Likelihood) and M4.6 guarantee design.
- Consider whether the Primary offer for C5 should be a cohort or 1:1 variant first (builds proof), with the productized variant deferred to Stage 2.

---

## Creative-Operator

**Territory typical:** Creative industries (design, illustration, writing, film, photography, artistic practice).

### Strengths In C4

- **M4.7 Landing Page Voice** is often distinctive and memorable. Creative-Operators write compelling first-person content.
- **M4.4 Pricing** exhibits appropriate perceived-scarcity premium. Creative work is priced more readily on intangible value than utility.
- **Trigger Bank usage** is often above-average — Creatives have an ear for voice.

### Weaknesses In C4

- **M4.3 Decomposition** tends to resist. Creative mechanisms often feel unstructurable to the Creative-Operator — "you can't codify this, you just have to be inside it."
- **M4.4 Pricing** can over-index on scarcity pricing at the expense of market band discipline. Prices above observed ceiling without buyer-pool capacity to support them.
- **M4.5 Anti-Promise** scope boundaries are often soft — Creative-Operators tend to accept scope expansion to "make the art better."

### Suggested Adjustments

- At M4.3: the decomposition does not eliminate creativity; it provides the scaffold within which creativity operates. Named deliverables bound scope; they do not bound the work inside scope.
- At M4.4: pair archetype intuition with C3 Pricing Signals discipline. Pricing above band requires buyer-pool capacity evidence, not just aesthetic justification.
- At M4.5: write scope boundaries as strict — what is in, what is out. Revisit in every engagement rather than softening in defense of "great work."

---

## Systems-Operator

**Territory typical:** Operations, workflow design, systems integration, business operations advisory.

### Strengths In C4

- **M4.6 Guarantee** design is typically sophisticated — Systems-Operators design conditional structures that balance risk reversal and unit economics well.
- **M4.8 Readiness Document** often contains the best-structured First-Sale Readiness Checklist.
- **Unit economics** modeling is natural.

### Weaknesses In C4

- **M4.2 Dream Outcome** can drift toward systems-vocabulary ("process improvement," "operational efficiency") rather than buyer emotional language.
- **M4.7 Problem and Agitation sections** can read clinically — Systems-Operators describe problems structurally rather than emotionally.
- **Trigger Bank usage** — like Builders, Systems-Operators tend to paraphrase into precise-but-sterile language.

### Suggested Adjustments

- +1 hour on M4.7 Problem and Agitation sections to honor buyer emotional vocabulary even when it is less precise than operator vocabulary.
- Budget for M4.2 Dream Outcome revision specifically — read the statement to a non-systems friend and ask "does this sound like something a buyer would say, or like something an efficiency consultant would say?"

---

## Multi-Archetype Operators

Some operators identify as hybrid (e.g., Teacher-Service, Builder-Systems). In C4, the primary archetype (from C1 Operator Identity Statement) is the default; the secondary archetype modifies the work.

A Teacher-Service hybrid typically has Teacher strengths in M4.3 decomposition and Service strengths in M4.4 pricing. They inherit both archetypes' weaknesses unless explicitly addressed — in the Teacher-Service case, both under-pricing (Teacher default) and anti-promise softness (Service default) commonly appear.

For hybrids, read both relevant sections above and apply the adjustments that match each area's archetype driver.

---

## How to Use This Chart

1. Identify your primary archetype from your C1 Operator Identity Statement.
2. Read the relevant section before starting each C4 module it references.
3. Apply the suggested adjustments rather than your defaults.
4. Track which adjustments actually changed your work — the ones that did are your real leverage points; the ones that didn't are either wrong for you or not yet internalized.

The chart is calibrated from prior cohort observation. Your archetype's pattern is a tendency, not a law. Trust the chart as a first approximation; override with your own judgment when the override has a specific reason.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by C4-Time-Estimate.md and module lessons*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Archetype Adjustments

**Purpose:** How C4 work shifts depending on operator archetype (from C1 Operator Identity). Applies the same archetype model to C4 that C3 applied to market scanning.
**Filed to:** Reference only
**Referenced by:** C4-Time-Estimate.md; all 8 module lessons where archetype-specific guidance applies

---

## Why Archetype Matters In C4

C4's work is offer construction. Different operator archetypes tend to construct offers with predictable tendencies — strengths that show up without effort, and weaknesses that require deliberate attention. Knowing your archetype's default patterns lets you invest attention where it actually matters rather than where your defaults would invest it.

The six archetypes from C1 Operator Identity work are:

- Teacher-Operator
- Service-Operator
- Builder-Operator
- Product-Operator
- Creative-Operator
- Systems-Operator

Each section below names the archetype's typical strengths, weaknesses, and suggested attention adjustments across the 8 C4 modules.

---

## Teacher-Operator

**Territory typical:** Knowledge-heavy territories (education, training, coaching programs for craft or career transition).

### Strengths In C4

- **M4.3 Decomposition** is natural. Curriculum-thinking makes breaking a mechanism into teachable deliverables intuitive.
- **M4.3 Cohort variant** is strongest archetype match. Group teaching is default delivery.
- **M4.7 Solution-and-Mechanism section** is typically clear — Teachers explain mechanisms well.

### Weaknesses In C4

- **M4.4 Pricing** tends to under-price. Teacher-Operators instinctively compare to course prices ($197-$497) rather than cohort prices ($1,500-$10K). A $2,400 cohort feels "high" to Teachers who have taught $297 self-paced courses; it is actually modestly priced for cohort delivery.
- **M4.5 Anti-Promise** on the outcome dimension tends toward softness. Teachers are trained to believe everyone can learn; declining to claim outcomes for specific buyer categories feels counterintuitive.

### Suggested Adjustments

- +1 hour on M4.4 specifically pricing against cohort comps (not course comps). Use `C3-Pricing-Signals` to ground the comparison.
- +30 min on M4.5 Section 3 (What This Does Not Do) to write outcome-non-claims with specificity.

---

## Service-Operator

**Territory typical:** Done-with-you or done-for-you service territories (consulting, fractional roles, professional services).

### Strengths In C4

- **M4.3 1:1 variant** is strongest archetype match. Premium 1:1 engagement commands high per-buyer revenue.
- **M4.4 Pricing** tends to anchor appropriately at premium bands. Service-Operators are accustomed to hourly/project rates that extrapolate to healthy cohort pricing.
- **M4.2 Perceived Likelihood** is often strong because Service-Operators tend to accumulate deep case studies rather than broad ones.

### Weaknesses In C4

- **M4.5 Anti-Promise** on the audience dimension is hardest. Service-Operators are instinctively accommodating; turning away buyers feels like turning away revenue they could have earned.
- **M4.3 Decomposition** sometimes resists — Service-Operators may resist turning their offering into a productized structure because it feels commodifying.

### Suggested Adjustments

- +1 hour on M4.5 with peer accountability — specifically working through the three audience exclusions and ensuring they are real exclusions rather than flattery.
- Before M4.3, explicit acknowledgment: decomposition does not eliminate customization; it structures the starting point. Variant B (1:1) can be highly customizable within a named structure.

---

## Builder-Operator

**Territory typical:** Technical territories (platform engineering, infrastructure, developer tooling, technical coaching).

### Strengths In C4

- **M4.2 Value Equation** work is typically sharp. Builder-Operators apply frameworks precisely and their technical credibility shows through in the Dream Outcome variable.
- **M4.6 Guarantee Architecture** is typically well-structured. Unit economic modeling is natural to Builder mindsets.
- **M4.8 Readiness Document** tends to be structurally clean. Builders like synthesis artifacts.

### Weaknesses In C4

- **M4.7 Landing Page Copy** frequently reads as feature list rather than outcome promise. Builders describe *what the offer is* (components, technical characteristics) rather than *what the offer does for the buyer* (outcomes in buyer language).
- **Trigger Bank verbatim quote usage** is often lower than required — Builders tend to paraphrase into "cleaner" language.
- **M4.2 Dream Outcome** can drift toward operator-vocabulary ("systems" and "workflows") rather than buyer-vocabulary.

### Suggested Adjustments

- +2 hours on M4.7 specifically replacing first-draft feature descriptions with verbatim Trigger Bank outcome language.
- Re-read M4.2 Dream Outcome section with a "would a non-technical buyer say this?" test.
- Budget for 3-4 drafts of M4.7, not 2.

---

## Product-Operator

**Territory typical:** Productized offerings, templates, digital downloads, SaaS-adjacent scaffolding.

### Strengths In C4

- **M4.3 Self-paced variant** (Variant C in Maya's example) is strongest archetype match.
- **M4.4 Pricing** at floor-to-median is typically fluent. Product-Operators know this band.
- **M4.7 Offer section** (Section 5) tends to be clear because product offerings have explicit deliverables.

### Weaknesses In C4

- **M4.2 Perceived Likelihood** is frequently the weakest variable because productized offers rarely carry operator-visible proof — buyers evaluate products in isolation from operator credibility.
- **M4.6 Guarantee** tends to default to simple refund structure; outcome guarantees require more design work for products than for services.
- **Traffic assumption** — Product-Operators often assume C4 completes with an offer; in practice, productized offers at floor pricing require substantially more traffic than cohort/1:1 offers, which is a Stage 2-4 constraint.

### Suggested Adjustments

- Allocate extra attention to M4.2 Section 2 (Perceived Likelihood) and M4.6 guarantee design.
- Consider whether the Primary offer for C5 should be a cohort or 1:1 variant first (builds proof), with the productized variant deferred to Stage 2.

---

## Creative-Operator

**Territory typical:** Creative industries (design, illustration, writing, film, photography, artistic practice).

### Strengths In C4

- **M4.7 Landing Page Voice** is often distinctive and memorable. Creative-Operators write compelling first-person content.
- **M4.4 Pricing** exhibits appropriate perceived-scarcity premium. Creative work is priced more readily on intangible value than utility.
- **Trigger Bank usage** is often above-average — Creatives have an ear for voice.

### Weaknesses In C4

- **M4.3 Decomposition** tends to resist. Creative mechanisms often feel unstructurable to the Creative-Operator — "you can't codify this, you just have to be inside it."
- **M4.4 Pricing** can over-index on scarcity pricing at the expense of market band discipline. Prices above observed ceiling without buyer-pool capacity to support them.
- **M4.5 Anti-Promise** scope boundaries are often soft — Creative-Operators tend to accept scope expansion to "make the art better."

### Suggested Adjustments

- At M4.3: the decomposition does not eliminate creativity; it provides the scaffold within which creativity operates. Named deliverables bound scope; they do not bound the work inside scope.
- At M4.4: pair archetype intuition with C3 Pricing Signals discipline. Pricing above band requires buyer-pool capacity evidence, not just aesthetic justification.
- At M4.5: write scope boundaries as strict — what is in, what is out. Revisit in every engagement rather than softening in defense of "great work."

---

## Systems-Operator

**Territory typical:** Operations, workflow design, systems integration, business operations advisory.

### Strengths In C4

- **M4.6 Guarantee** design is typically sophisticated — Systems-Operators design conditional structures that balance risk reversal and unit economics well.
- **M4.8 Readiness Document** often contains the best-structured First-Sale Readiness Checklist.
- **Unit economics** modeling is natural.

### Weaknesses In C4

- **M4.2 Dream Outcome** can drift toward systems-vocabulary ("process improvement," "operational efficiency") rather than buyer emotional language.
- **M4.7 Problem and Agitation sections** can read clinically — Systems-Operators describe problems structurally rather than emotionally.
- **Trigger Bank usage** — like Builders, Systems-Operators tend to paraphrase into precise-but-sterile language.

### Suggested Adjustments

- +1 hour on M4.7 Problem and Agitation sections to honor buyer emotional vocabulary even when it is less precise than operator vocabulary.
- Budget for M4.2 Dream Outcome revision specifically — read the statement to a non-systems friend and ask "does this sound like something a buyer would say, or like something an efficiency consultant would say?"

---

## Multi-Archetype Operators

Some operators identify as hybrid (e.g., Teacher-Service, Builder-Systems). In C4, the primary archetype (from C1 Operator Identity Statement) is the default; the secondary archetype modifies the work.

A Teacher-Service hybrid typically has Teacher strengths in M4.3 decomposition and Service strengths in M4.4 pricing. They inherit both archetypes' weaknesses unless explicitly addressed — in the Teacher-Service case, both under-pricing (Teacher default) and anti-promise softness (Service default) commonly appear.

For hybrids, read both relevant sections above and apply the adjustments that match each area's archetype driver.

---

## How to Use This Chart

1. Identify your primary archetype from your C1 Operator Identity Statement.
2. Read the relevant section before starting each C4 module it references.
3. Apply the suggested adjustments rather than your defaults.
4. Track which adjustments actually changed your work — the ones that did are your real leverage points; the ones that didn't are either wrong for you or not yet internalized.

The chart is calibrated from prior cohort observation. Your archetype's pattern is a tendency, not a law. Trust the chart as a first approximation; override with your own judgment when the override has a specific reason.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by C4-Time-Estimate.md and module lessons*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 — Offer Ignition

**Subtitle:** From Validated Primary Mechanism to First Sellable Offer · The Grand Slam Offer · Drafted, Not Yet Launched
**Stage:** 1 — Dinghy (Foundation)
**Vessel Metaphor:** The Dinghy has cleared the buoys. The harbor is behind you, the open water ahead. Before you can trade, the cargo hold needs cargo — something worth more to a buyer than the price you'll charge. C4 is where you load the hold. The offer is not the mechanism; the offer is what the mechanism is wrapped in so someone will pay for it.
**Module Count:** 8 modules
**Estimated Time:** 15 hours study + 25 hours implementation = 40 hours total · 4-5 weeks elapsed
**Prerequisite Courses:** C3 Buoy Navigation (complete with Market Fit Hypothesis Document filed)
**Stage Color:** Maritime Blue (#2E75B6)

---

## Why This Course Exists

In C3 you produced a Market Fit Hypothesis Document and selected a single validated Primary mechanism. You built a Trigger Bank of 200+ audience-language entries. You scanned 5-10 competitors. You interviewed 8-12 real customers and documented pricing signals in your territory. You know what the market wants in language the market itself supplied.

C4 is where that evidence becomes a sellable object.

Mechanism and offer are not the same thing. Students who confuse them ship one of two failure patterns: they sell the mechanism as if it were the offer (too abstract, buyer cannot evaluate), or they bury the mechanism inside an offer so generic that no trigger, no competitor gap, and no pricing signal from C3 survives. Both patterns produce offers that do not convert even when the mechanism is strong.

The output of C4 is a complete **Offer Document** — named, priced, guaranteed, anti-promised, and landing-page-drafted — ready for C5 First Currents, where Stage 1 graduation gate tests whether the offer holds up under AEO-literate scrutiny and first-sale readiness.

This is also the course where most students first feel the distance between *understanding* their mechanism (C2 output) and being able to *sell* it. That gap is uncomfortable and predictable. The failure case study for C4 — The Feature Stuffing Trap — exists because many students try to close the gap by adding bonuses and guarantees rather than fixing the mechanism-market fit underneath. We name the pattern explicitly in M4.3, M4.5, and M4.6 so you can spot it in yourself.

## Why You Cannot Skip This Course

Every downstream Stage 2 and Stage 3 course assumes C4's outputs exist:

- **C5 First Currents (Stage 1 capstone):** Stage 1 graduation requires Territory + Identity + Mechanism + Offer + First-Sale Readiness. The Offer Document from C4 is one of the five graduation artifacts.
- **C7 Offer Architecture (Stage 2):** expands C4's single offer into a full offer suite with entry, core, and premium tiers. Without a validated single offer, C7 builds on nothing.
- **C10 Funnel Fleet Engineering (Stage 2 gate):** funnel pages are built around the Offer Landing Page Copy produced in M4.7.
- **C13 Partnership Harbors:** the partnership pitch cites your offer's anti-promise and guarantee — both C4 artifacts.
- **C14 First Dollar (Stage 3 gate):** the first sale, by definition, is the sale of the C4 offer. If the offer is not shippable, the gate does not open.
- **Every content piece from C16 onward:** content hooks are Trigger Bank entries that resolve into the C4 offer's promise. No offer → nothing for content to resolve to.

Skipping C4 means every downstream course has to reverse-engineer the offer from whatever partial artifacts exist. Operators who skip C4 are the operators who arrive at C14 with no revenue after 10+ weeks of traffic work because "the offer isn't quite right yet." C4 is when "quite right" becomes "shipped in a document, named, priced, and defensible."

## Who This Course Is For

C3 graduates with a filed Market Fit Hypothesis Document that names a single validated Primary mechanism, a Trigger Bank of 200+ entries, a competitor scan of 5-10 operators, 8-12 customer interviews, and documented pricing signals. C4 does not work without all six C3 outputs in hand.

If you are at C4 enrollment without C3 complete — or with C3 complete but one of the six artifacts missing or thin — Build 6 will deny access. The reason: C4's first action (M4.1) is to re-read your Market Fit Hypothesis and distinguish between the mechanism and the offer-to-be. Without the Market Fit Hypothesis, there is nothing to distinguish from.

## What You Will Have When You Finish

Eight new artifacts in your Build 8 Drive folder, all referenced by C5-C55:

1. **Offer-Mechanism-Distinction-[YourName]-[Date].md** — the M4.1 written memo distinguishing the mechanism from the offer-to-be built around it
2. **Value-Equation-Worksheet-[YourName]-[Date].md** — Hormozi's Value Equation applied across Dream Outcome, Perceived Likelihood, Time Delay, Effort & Sacrifice
3. **Offer-Decomposition-Variants-[YourName]-[Date].md** — three distinct decomposition variants of the Primary mechanism into saleable form (6% Rule applied)
4. **Pricing-Decision-[YourName]-[Date].md** — the anchor price, price band selection, and payment options with rationale from C3 signals
5. **Anti-Promise-Statement-[YourName]-[Date].md** — what the offer explicitly does NOT do, and who it is explicitly NOT for
6. **Guarantee-Architecture-[YourName]-[Date].md** — the guarantee structure with refund terms and conditional components
7. **Offer-Landing-Page-Copy-[YourName]-[Date].md** — the 7-section landing page copy, ready for deployment, with minimum 15 Trigger Bank entries used verbatim
8. **Offer-Readiness-Document-[YourName]-[Date].md** — the synthesis artifact that becomes C5's primary input, plus the first-sale readiness checklist

## Module Map

| # | Title | Outcome | Bloom's | Time |
|---|---|---|---|---|
| M4.1 | Offer Architecture Foundations | Student has distinguished the offer from the mechanism and named the 7 components an offer contains that a mechanism does not | Analyze | 75 min |
| M4.2 | The Grand Slam Offer Framework | Student has applied Hormozi's Value Equation across 4 variables (Dream Outcome × Perceived Likelihood ÷ Time Delay × Effort & Sacrifice) to their Primary | Understand + Apply | 90 min |
| M4.3 | Offer Deconstruction and Reassembly | Student has produced 3 distinct decomposition variants of their mechanism into offer form (6% Rule) | Create | 180 min |
| M4.4 | Pricing and Anchoring | Student has selected an anchor price and payment structure grounded in C3 pricing signals | Evaluate | 90 min |
| M4.5 | The Anti-Promise Statement | Student has written the explicit statement of what the offer does NOT do and who it is NOT for | Create | 75 min |
| M4.6 | Guarantee Architecture | Student has designed a guarantee structure (conditional or unconditional) that reverses risk without collapsing unit economics | Apply | 90 min |
| M4.7 | Offer Landing Page Copy | Student has produced 7-section landing page copy using minimum 15 Trigger Bank entries verbatim | Create | 240 min |
| M4.8 | Offer Readiness Document | Student has produced the synthesis artifact and first-sale readiness checklist that becomes C5's primary input | Create | 90 min |

**Total:** 8 modules × avg 116 min = ~15 hours of study + ~25 hours of implementation (drafting, revising, peer review incorporation) = ~40 hours

C4 is shorter in active hours than C3 because the work is internal writing rather than external research. Writing, however, is rarely faster than research in elapsed time — first drafts sit for 48 hours between modules so that revisions happen with fresh eyes. Plan 4-5 weeks even though the active-hour total is lower.

## How to Study This Course

**Recommended pacing:** 4-5 weeks. M4.1 and M4.2 complete in week 1 (foundation). M4.3 produces 3 decomposition variants across week 2 (the 6% Rule work). M4.4 (pricing) and M4.5 (anti-promise) complete in week 3. M4.6 (guarantees) and M4.7 (landing page copy) consume week 4, with M4.7 requiring a peer review cycle before M4.8 unlocks. M4.8 synthesizes and files the Offer Readiness Document in week 5.

**Why this is faster than C3 in active hours:** C3 required outreach and scheduling on other people's calendars. C4 is you, the Market Fit Hypothesis, the Trigger Bank, and a writing surface. There is no one to wait for.

**Why this is not necessarily faster in elapsed time:** Writing improves on the second pass. Offers that land in the first draft almost always benefit from a 48-hour cooling period before the second pass. C4's pacing bakes this in — first drafts are filed, then revised after at least one night of sleep and, in the case of M4.7, after peer review.

**Where to take notes:** Build 8 Drive folder for C4 specifically. Every decomposition variant, every pricing option considered, every guarantee structure explored goes in Drive — even the options that do not survive. The abandoned variants are frequently reopened in Stage 2 when the offer evolves.

**When to file deliverables:** As produced. M4.3 requires 3 decomposition variants to exist simultaneously in the Drive folder before M4.4 unlocks. M4.7 requires a peer-reviewed draft before M4.8 unlocks.

**Where to discuss:** Circle.so `#c4-offer-ignition`. M4.7 has a mandatory peer review element — your landing page copy is reviewed by two cohort peers before M4.8 unlocks, extending the C1 M1.3 and C3 M3.3 peer review pattern.

## The HITL Checkpoint (Expanded in C4)

C3 added its first Human-In-The-Loop review at M3.7. C4 extends the pattern: M4.7 landing page copy is peer-reviewed by two cohort members before M4.8 unlocks. The rationale is the same asymmetric-cost logic as C3 — landing page copy that ships with the wrong framing wastes every hour of traffic work in C10-C18. Peer review at M4.7 is the cheapest place to catch framing drift.

Peer review in C4 is not instructor review. Instructor review happens in C5 as part of Stage 1 graduation. C4 peer review is operator-to-operator — two peers at similar stage reviewing whether your copy reads as promised in your Hypothesis Document and whether Trigger Bank entries are actually being used verbatim rather than paraphrased.

## Prerequisites (enforced by Build 6)

- C3 Course Completion (`c3_complete = true` in Supabase users table)
- Market Fit Hypothesis Document filed within last 3 months (`c3_market_fit_hypotheses` table active row)
- Trigger Bank with 200+ entries filed (`c3_trigger_banks` active row)
- Competitor Scan with 5-10 operators (`c3_competitor_scans` active row)
- Customer Interview Library with 8+ interviews (`c3_interview_library` active row)
- Pricing signals documented (`c3_pricing_signals` active row)
- Captain's Oath signed within last 12 months (C1 prerequisite still active)
- Operator Identity Statement filed within last 12 months (C1 prerequisite still active)
- ~4-6 hours of calendar availability per week for writing and revision

Full Prerequisites Checklist in this folder.

## Course and Institutional Policies

Identical to C1, C2, and C3 (FTC AI Disclosure, Copyright/IP, Academic Integrity, Accessibility, Data Protection). Two C4-specific additions:

**Anti-Promise Integrity:** every anti-promise written in M4.5 must be truthful and, where it names a disqualified audience, specific rather than pejorative. "This is not for people who want a done-for-you service" is fine. "This is not for lazy people" is not. The Anti-Promise Integrity Statement in `02_Resources/Templates/` is signed before M4.5 submission.

**Guarantee Honesty Clause:** any guarantee written in M4.6 must be one the student intends to honor. A guarantee the student plans to make difficult to claim is a deceptive marketing practice and violates the RISER Nation Integrity Policy regardless of how the offer is phrased. The Guarantee Honesty Clause in `02_Resources/Templates/` is signed before M4.6 submission.

## Founder's Course Introduction

The video in `01_Module-Lessons/M4.1` opens with a 4-minute founder note: why C4 is called "Offer Ignition" rather than "Offer Architecture" (which is C7), why the course produces a single offer rather than an offer suite, and the specific failure mode — **mistaking the offer for the mechanism, or vice versa** — that the course exists to prevent.

## Quality Certification

C4 has passed RISER Nation's internal QM-equivalent audit at 92/94 (97.9%). Fifteen of 16 Essential Standards MET; one PARTIAL (SRS 8.3, pending v2.1 video production for M4.2-M4.8). Full audit in `05_Checkpoints-and-Tests/QM-Audit-C4.json`.

## Cross-Reference to C1, C2, and C3

C4 reads heavily from all three prior courses:

**From C1:**
- **Captain's Oath Clause 1 (territory):** the offer must serve the stated territory. Offers that drift across territory boundaries are flagged by the M4.8 validator.
- **Operator Identity:** Teacher-Operator offers differ from Service-Operator offers (cohort-based vs. 1:1; asynchronous deliverables vs. synchronous engagement). M4.3 decomposition variants are archetype-informed.
- **6% Rule:** C4 applies the rule as "draft 3 decomposition variants before committing to 1." M4.3 produces 3; M4.8 selects 1.
- **85-Minute Rhythm:** continues unchanged.

**From C2:**
- **Mechanism Hypothesis Document:** M2.6 verbatim audience quotes seed M4.7 landing page copy alongside the full C3 Trigger Bank.
- **4-Pillar Mechanism Discovery Framework:** the offer's Method section in the landing page copy (M4.7) restates the mechanism's Method pillar.
- **5-Test Naming Filter:** applied to the offer name in M4.3. The offer may inherit the mechanism name or produce a new offer-specific name; either way, the 5-test is re-run.

**From C3:**
- **Market Fit Hypothesis Document:** C4's primary input. M4.1 opens with a re-reading.
- **Trigger Bank:** M4.7 landing page copy uses a minimum of 15 Trigger Bank entries verbatim. Entries paraphrased rather than quoted verbatim are flagged by the landing-page-copy-reviewer.
- **Competitor Scan:** M4.5 anti-promise and M4.4 pricing both cite specific competitors from the C3 scan.
- **Customer Interviews:** M4.3 decomposition variants reflect what interviewees actually said they would buy, not what the student wishes the interviewees had said.
- **Pricing Signals:** M4.4 anchor price sits within the observed market band unless the student documents a defensible reason for deviation.

If any C1, C2, or C3 artifact is missing or stale, Build 6 routes the student back to the appropriate course before C4 work begins.

---

*Last updated: April 24, 2026 · Version 2.0 · Owner: RISER Nation Curriculum Team*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Preparation Checklist

**Purpose:** Pre-flight check before submitting M4.7 landing page copy for cohort peer review. Prevents common rework-causing gaps.
**Time to complete:** 15-20 minutes before submission
**Filed to:** Attached to your M4.7 submission

---

## Before You Submit

Running this checklist before posting in `#c4-offer-ignition` saves your peer reviewers 30-60 minutes per review and dramatically increases the quality of feedback you receive. Reviewers who have to hunt for your Trigger Bank Provenance Log, or who notice your anti-promise softened from M4.5, spend their review time on mechanical issues rather than substantive feedback.

---

## Section A — Document Completeness

- [ ] Landing page copy file exists at `Offer-Landing-Page-Copy-[YourName]-[Date].md`
- [ ] All 7 sections present in order:
  - [ ] Section 1 — Problem (200-400 words)
  - [ ] Section 2 — Agitation (150-300 words)
  - [ ] Section 3 — Solution-and-Mechanism (300-500 words)
  - [ ] Section 4 — Proof (200-400 words)
  - [ ] Section 5 — Offer (300-500 words)
  - [ ] Section 6 — Anti-Promise-and-Guarantee (250-400 words)
  - [ ] Section 7 — CTA (50-150 words)
- [ ] Total word count in 1,800-2,500 range (not absurdly over or under)

## Section B — Trigger Bank Usage

- [ ] Trigger Bank Provenance Log file exists at `Landing-Page-Trigger-Bank-Provenance-[YourName]-[Date].md`
- [ ] Log contains ≥ 15 entries mapped to landing page usage
- [ ] Every entry in the log is verbatim (not paraphrased) from the source Trigger Bank
- [ ] Each entry cites specific Trigger Bank ID (TB-###) or Interview #
- [ ] Entries are distributed across 4+ of the 7 sections (not all stacked in one section)

## Section C — Anti-Promise and Guarantee Integrity

- [ ] Anti-Promise in Section 6 is substantively the same as your M4.5 Anti-Promise Statement
- [ ] If any softening occurred between M4.5 and M4.7, it is reverted OR documented with rationale
- [ ] Anti-Promise Integrity Statement is signed
- [ ] Guarantee in Section 6 is substantively the same as your M4.6 Guarantee Architecture
- [ ] If any stacking occurred between M4.6 and M4.7, it is reverted
- [ ] Guarantee Honesty Clause is signed

## Section D — Offer Section Completeness

- [ ] Named deliverable (5-Test-passed name) visible in Section 5
- [ ] Price visible in Section 5 (not hidden, not ranged)
- [ ] Payment options listed
- [ ] Delivery structure described (engagement model, duration, cadence)
- [ ] Deliverables list is not over 8 items (Feature Stuffing Trap check)

## Section E — Proof Integrity

- [ ] Proof cases in Section 4 are specific (named or anonymized with specific outcome)
- [ ] If you have fewer than 4 named cases, the Known Weaknesses acknowledgment is visible (not papered over)
- [ ] Testimonials (if any) are verbatim quotes, not paraphrased
- [ ] Testimonials have attribution (name or anonymized but specific)

## Section F — CTA Specificity

- [ ] CTA names a specific action (not "click here")
- [ ] Next cohort / enrollment date is present
- [ ] Qualification process (if any) is described
- [ ] Contact email or channel is present for pre-purchase questions

## Section G — Voice Check

- [ ] You have read the full landing page out loud once, from start to finish
- [ ] The page does not contain phrases you would not actually say to a buyer in person
- [ ] The page does not contain hyperbole you cannot substantiate
- [ ] The page does not contain any of these phrases: "game-changer," "revolutionary," "transform your life," "all you need to do is" (low-substance signaling vocabulary)

## Section H — Review Request Post

Before posting in `#c4-offer-ignition`, prepare the post:

- [ ] Drive link to landing page copy
- [ ] Drive link to Trigger Bank Provenance Log
- [ ] Brief context (2-3 sentences about your offer's key positioning)
- [ ] Specific request: "2 peer reviews within 72 hours, using the C4 Peer Review Template"
- [ ] Your availability to return review favor (which days you can review others' copy)

---

## Common Pre-Submit Fixes

If any checklist item is unchecked, common fixes:

| Unchecked Item | Typical Fix |
|---|---|
| Section 6 softened from M4.5/M4.6 | Revert to the original M4.5 Anti-Promise and M4.6 Guarantee language |
| Trigger Bank count < 15 | Add 3-6 more verbatim entries, typically in Problem and Agitation sections |
| Deliverables > 8 | Review for Feature Stuffing; which deliverables are compensation, which are real value? |
| Price hidden or ranged | Move price to Section 5 with explicit number |
| Voice check fails | 48-hour cooling re-read; rewrite any section where "did I actually say that?" is your reaction |

---

## After Submission

Once posted:

- [ ] Check `#c4-offer-ignition` daily for reviewer pickup
- [ ] Respond promptly to reviewer questions
- [ ] Do not revise the landing page while reviews are in progress (creates version mismatch)
- [ ] Begin reviewing other cohort peers' landing pages as reviews arrive — reciprocity is cohort norm

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Outreach Scripts

**Purpose:** Short scripts for requesting and responding to peer reviews during M4.7. These are starter templates; adapt in your own voice.
**Filed to:** `03_Scripts-and-Prompts/Outreach-Scripts/`
**Referenced by:** M4.7 Written Lesson; C4-Peer-Review-Preparation-Checklist

---

## Script 1 — Requesting Peer Review (post in `#c4-offer-ignition`)

```
**M4.7 peer review request — [YourName]**

- **Offer name:** [5-Test-passed name]
- **Target buyer:** [one sentence describing who this is for]
- **Price:** $[X]
- **What I want reviewers to watch for specifically:**
  - [1-2 things you suspect may be weak — common: Section 4 Proof, Section 6 Anti-Promise softening, Trigger Bank entry density]

**Drive links:**
- Landing page copy: [link]
- Trigger Bank Provenance Log: [link]
- Revision Log (so far): [link — if you have one]

**SLA:** 72 hours ideal

**Reciprocity:** I'm available to review copy on [specific days this week]. Reply with yours and I'll pick up the first two.

Using the C4 Peer Review Template (`02_Resources/Templates/C4-Peer-Review-Template.md`).
```

### Why this structure works

Naming what you suspect is weak focuses reviewer attention. Without this, reviewers tend to spread feedback thin across the whole page. Concentrated attention on 1-2 sections produces higher-signal feedback.

---

## Script 2 — Offering Peer Review (response to another student's request)

```
I'll pick up your review, [TheirName]. I'll aim to deliver within 48 hours.

If you want me to pay particular attention to [suggested focus based on their request], I will. If you want me to do a straight full-template review, I'll do that too.

My C4 Peer Review Template will be back in your Drive folder or Circle.so thread by [specific date + time].
```

### Why this structure works

Confirms the commitment with a specific delivery time. Acknowledges their request-specific focus areas. Creates accountability for the delivery.

---

## Script 3 — Declining a Peer Review (when over-committed)

```
Thanks for tagging me, [TheirName]. I'm at capacity this week ([reason if relevant — e.g., "I'm in my own M4.7 cycle with deadline Thursday"]).

Tagging [OtherName] who mentioned they had bandwidth this week. You can also use the Alternate Protocol at `02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md` if the cohort is thin at your pacing — Protocol A (mentor substitution) is available.
```

### Why this structure works

Declining without leaving the requester stranded. Referring to Alternate Protocol reminds the requester that the safety net exists.

---

## Script 4 — Delivering Peer Review (after completing the template)

```
[TheirName] — review complete.

**Template:** [Drive link to completed Peer Review Template]

**Top-level observation:** [one sentence — your overall impression]

**My three recommended revisions (from template):**
1. [brief version]
2. [brief version]
3. [brief version]

Happy to discuss any of these in async DM if useful. Good luck with M4.8.
```

### Why this structure works

Surfaces the most actionable takeaway in the message itself so the requester can start revising without waiting to open the full template. The full template provides depth; the message provides urgency.

---

## Script 5 — Responding to Peer Review (after incorporating)

```
[ReviewerName] — thanks for the review. Incorporated as follows:

- **Revision 1 you recommended:** [incorporated / incorporated with modification / not incorporated + reason]
- **Revision 2:** [same format]
- **Revision 3:** [same format]

Revision Log in Drive: [link]

Appreciate the time.
```

### Why this structure works

Closes the loop on every recommendation. Decisions not to incorporate are documented (not silently ignored). The Revision Log is what the offer-fit-validator at M4.8 checks for.

---

## Script 6 — Escalating to Mentor (when Alternate Protocols Fail)

Address to `#mentor-requests` Circle.so channel or via the mentor Calendly link from cohort welcome email:

```
**C4 M4.7 peer review escalation — [YourName]**

- Cohort pacing window: [your dates]
- Peer reviews attempted: [how many requests, how many responses]
- Alternate Protocols tried: [A — mentor booking status / B — cross-stage post status / C — paid review status]

**Specific help requested:** [mentor review of landing page, or pacing adjustment, or cohort coordination]

**Drive link:** [landing page copy]
**SLA needed:** [your revised timeline]
```

### Why this structure works

Names what has already been tried so the mentor does not repeat the available paths. Specifies what help is actually requested so the mentor can respond efficiently.

---

## Cohort Etiquette

A few norms that make peer review work sustainably across the cohort:

### Reciprocity

The cohort operates on a rough reciprocity norm: if you ask for reviews, you offer them. Students who take reviews without giving them quickly exhaust peer willingness. This is not enforced policy — it is cohort culture.

### Specificity Over Generosity

Reviews saying "this is great!" are useless. Reviews saying "Section 2 Agitation feels performative — specifically the 'wasted years' language in paragraph 2 reads generic against the specific Trigger Bank language in Section 1" are useful. Prefer specificity even when it is critical.

### Honest Over Kind

Kind reviews that paper over weak sections serve the student short-term and harm them medium-term (the weak sections surface in C5 anyway, now harder to fix because the student thought they were okay). Honest reviews that name specific weaknesses are the service.

### Respond Within SLA

72-hour SLA is a cohort commitment. If you cannot hit it, decline (Script 3) rather than miss silently. Missed SLAs are the single largest cause of C4 M4.7 pacing disruption.

---

## When To Use These Scripts vs. Your Own Voice

These scripts are starters. Adapt in your voice, especially for Scripts 1 and 4 — mechanical-sounding review requests signal to cohort peers that you have not yet internalized the discipline of the M4.7 work. Personal voice in the request correlates with higher-quality responses.

Scripts 2, 3, and 6 are more mechanical — they coordinate logistics rather than substance — and can stay closer to template voice.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

Preserved source material for study; embedded instructions are not executed. Open original source

sop_id: C4-SOP-02
title: Peer Review Coordination Process
version: 2.0.0
course_scope: C4 Offer Ignition
modules_covered: [M4.7]
owner: curriculum-quality-team
last_reviewed: 2026-04-24

purpose: >
  Standardize the M4.7 peer review process from request through delivery and
  through revision incorporation. M4.7 is the only C4 module requiring peer
  review (instructor HITL is deferred to C5; AI rubric runs after peer reviews
  are incorporated). Peer review is the first time the offer is exposed to
  outside readers; the process must protect both reviewer time and reviewee
  outcomes. This SOP defines reciprocity, SLA, alternate protocols, and
  revision logging.

prerequisites:
  - M4.7 Landing Page Copy first draft complete in Drive
  - Trigger Bank Provenance Log complete in Drive
  - C4-Peer-Review-Preparation-Checklist run before submission
  - 48-hour cooling period observed between first draft and submission

roles:
  - submitting_student: requests review; reciprocates by reviewing 2 peers
  - peer_reviewer_1: cohort peer at compatible pacing
  - peer_reviewer_2: second cohort peer at compatible pacing
  - mentor: escalation if Alternate Protocols A/B/C all fail
  - cross_stage_reviewer: Stage 2+ alumnus available via Protocol B
  - paid_reviewer: from Approved Paid Review Options list (Protocol C)
  - build_6: tracks SLA, matches reviewers, gates M4.7 checkpoint progression

process:
  step_1:
    name: Pre-Submission Self-Audit
    time: 20 min
    output: Completed Peer Review Preparation Checklist
    activities:
      - Run C4-Peer-Review-Preparation-Checklist sections A through H
      - Address any unchecked items before posting review request
      - Verify Trigger Bank entry count >= 15 with Provenance Log complete
      - Verify anti-promise unchanged from M4.5; verify guarantee unchanged from M4.6
    quality_gate: All preparation checklist items checked; if any item is unchecked, fix before requesting review
    common_failures:
      - "Posting request before Trigger Bank entries reach 15"
      - "Posting request with anti-promise softened from M4.5 (peer reviewers will flag, costing 24-48 hours)"
      - "Forgetting to attach Trigger Bank Provenance Log"
    mitigation: The checklist exists specifically to catch these. Run it.

  step_2:
    name: Request Review (Standard Protocol)
    time: 15 min
    output: Review request post in #c4-offer-ignition Circle.so channel
    activities:
      - Use Outreach Script 1 from C4-Peer-Review-Outreach-Scripts.md
      - Specify offer name, target buyer, price, areas you suspect are weak
      - Attach Drive links to landing page copy AND Trigger Bank Provenance Log
      - State 72-hour SLA expectation
      - Offer specific reciprocity (which days you can review others' copy this week)
    quality_gate: Post visible in #c4-offer-ignition; request structure matches Outreach Script 1
    common_failures:
      - "Vague request without specifying suspected-weak sections (reviews come back generic)"
      - "Not offering reciprocity (cohort norm violated; future review requests slower to receive responses)"
      - "Missing Provenance Log attachment (reviewers can't verify Trigger Bank usage)"
    mitigation: Use the script verbatim until it becomes natural

  step_3:
    name: Reviewer Pickup (24-48 hours from request)
    time: passive
    output: 2 peers commit to review with stated delivery dates
    activities:
      - Build 6 sends notification to active cohort peers at compatible pacing
      - Peers respond using Outreach Script 2 (acceptance) or Script 3 (decline with referral)
      - Build 6 logs commitments and tracks SLA
      - If only 1 reviewer commits within 48 hours, Build 6 escalates per step 4a
    quality_gate: 2 reviewers committed within 48 hours
    common_failures:
      - "Cohort thin at student's pacing (Protocol A activates)"
      - "Reviewers who committed silently miss SLA without communication"
    mitigation: Build 6 active SLA tracking surfaces silent misses; cohort norm includes communicating early if SLA at risk

  step_4_alternate_protocol_a:
    name: Mentor Substitution (Protocol A)
    time: 24 hours from activation
    output: Mentor named as reviewer; review delivered within 72 hours
    activation_trigger: Cohort has < 4 active peers at compatible pacing OR < 2 peers commit within 48 hours
    activities:
      - Student books mentor review slot via Calendly link in cohort welcome email
      - OR Student posts in #mentor-requests with M4.7 review request
      - Mentor delivers full Peer Review Template completion within 72 hours
      - Mentor review counts as both required peer reviews
    quality_gate: Mentor review filed with C4-Peer-Review-Template completion
    common_failures:
      - "Mentor booking backed up 2+ weeks during high-enrollment cycle (rare; route to Protocol B)"

  step_4_alternate_protocol_b:
    name: Cross-Stage Review (Protocol B)
    time: 96 hours from activation
    output: 1-2 Stage 2+ alumni reviewers complete review
    activation_trigger: Mentor backed up; OR student prefers reviewer who has shipped offers
    activities:
      - Student posts in #cross-stage-review channel using request format from Alternate Protocol document
      - Stage 2-5 operators who actively volunteer review time pick up the request
      - Review uses C4 Peer Review Template
      - Cross-stage review counts as both required reviews, OR pairs with one peer/mentor review
    quality_gate: Cross-stage review filed
    common_failures:
      - "No cross-stage reviewer picks up within 48 hours (route to Protocol C)"

  step_4_alternate_protocol_c:
    name: Approved Paid Review (Protocol C — Last Resort)
    time: 48-72 hours from activation
    output: Paid reviewer completes review using C4 Peer Review Template
    activation_trigger: Protocols A and B unavailable within student's planned week
    activities:
      - Student selects from C4-Approved-Paid-Review-Options.md (Tier A/B/C)
      - Direct engagement; Academy does not facilitate payment
      - Paid reviewer completes C4 Peer Review Template
      - Paid review counts as 1 of 2 required reviews; must pair with peer/mentor/cross-stage for second
      - Methodology consistency check: any methodology-conflicting paid feedback flagged before incorporation
    quality_gate: Paid review filed; second review (peer/mentor/cross-stage) also filed
    common_failures:
      - "Paid reviewer recommends removing anti-promise (methodology-conflict; do not incorporate without mentor consult)"
      - "Paid reviewer recommends stacking guarantees (methodology-conflict)"
      - "Student counts paid review as both required reviews (not allowed)"
    mitigation: Approved Paid Review document provides methodology baseline language to send to paid reviewer

  step_5:
    name: Receive and Read Reviews
    time: 30 min (do not act yet)
    output: Both reviews read in single sitting
    activities:
      - Wait until both reviews have arrived before reading either
      - Read both in one sitting; note patterns
      - If both reviewers flagged the same section as weak, that section is genuinely weak
      - If reviewers disagree, use your judgment
      - Do not begin revision yet — sleep on the feedback
    quality_gate: Both reviews read; pattern notes captured
    common_failures:
      - "Reading first review and immediately starting revisions before second review arrives (creates whiplash if reviewers disagree)"
      - "Defending against feedback in your head without genuinely considering it"
    mitigation: 12+ hour gap between reading and revising; treat reviews as gifts, not attacks

  step_6:
    name: Draft Revision Log + Revise
    time: 60-90 min
    output: Revision Log file + revised landing page in Drive
    activities:
      - Open C4-Peer-Review-Outreach-Scripts.md Script 5 template
      - For each suggestion in each review: incorporated / incorporated with modification / not incorporated + reason
      - Document each decision; the offer-fit-validator at M4.8 reads this
      - Revise landing page based on incorporated suggestions
      - Address pattern-flagged sections (those flagged by both reviewers) with priority
    quality_gate: Revision Log complete; revised landing page in Drive
    common_failures:
      - "Skipping the Revision Log (validator at M4.8 will flag missing log)"
      - "Incorporating every suggestion mechanically (you should make decisions, not absorb)"
    mitigation: The Log is the structural mechanism that forces decision-making; do not skip

  step_7:
    name: Reciprocate
    time: 90-120 min total (45-60 min per review × 2)
    output: 2 completed peer reviews delivered to other students
    activities:
      - During or after your own revision cycle, complete 2 peer reviews for cohort peers
      - Use C4-Peer-Review-Template for each
      - Deliver via Outreach Script 4 from outreach scripts document
      - Reciprocity is cohort norm; tracking is light but reputation matters
    quality_gate: 2 reviews delivered; Build 6 logs reciprocity in cohort metrics
    common_failures:
      - "Receiving reviews and not reciprocating (silent reputation cost; future requests slower to receive responses)"
      - "Reciprocating with low-effort 'looks great!' reviews (worse than declining; harms peer's revision quality)"
    mitigation: If you genuinely cannot reciprocate this cycle, decline future review requests until you can; do not free-ride

  step_8:
    name: Submit Revised Landing Page to AI Rubric
    time: 5 min + 5 min for rubric run
    output: landing-page-copy-reviewer score >= 7/10
    activities:
      - Submit revised landing page + provenance log + revision log to Build 6
      - Build 6 invokes landing-page-copy-reviewer-v1.0.0.yaml
      - Verify peer_review_count >= 2 in submission metadata
      - Receive rubric score within 5 minutes
    quality_gate: Score >= 7/10; peer_review_count = 2; no integrity flags
    common_failures:
      - "Submitting without filing the Revision Log first (rubric flags missing artifact)"
      - "Trigger Bank entries fabricated or paraphrased (rubric flags as integrity issue)"
    mitigation: All checks should already have passed in step 5-6; if rubric flags appear, fix and resubmit

review_and_adjustment:
  cadence: Per cohort cycle
  questions_to_ask:
    - "What % of M4.7 submissions used Standard Protocol vs Alternate Protocol A/B/C?"
    - "What was the median time from review request to review delivery?"
    - "What % of reviewers met SLA without escalation?"
    - "What % of paid reviewers gave methodology-conflicting feedback?"
  adjustment_principles:
    - If Alternate Protocol A activation > 30%, expand mentor capacity OR extend cohort recruitment to thicken cohorts
    - If paid reviewer methodology conflicts > 20%, refresh paid reviewer Affiliate Agreements OR remove specific reviewers from Approved list
    - If reciprocity ratio (reviews given / reviews received) < 0.85, surface in cohort discussion

escalation_triggers:
  - 3+ submissions fail M4.7 rubric on same student (mentor diagnosis)
  - Reviewer fabrication or methodology-conflicting feedback (Affiliate Agreement review)
  - Reciprocity ratio < 0.5 for individual student over 2 cohorts (cohort norm conversation)
  - Cohort thinning > 3 weeks consecutive (Build 6 → Marketing for cohort recruitment review)

related_documents:
  - 02_Resources/Templates/C4-Peer-Review-Template.md
  - 02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md
  - 02_Resources/Templates/C4-Approved-Paid-Review-Options.md
  - 02_Resources/Checklists/C4-Peer-Review-Preparation-Checklist.md
  - 03_Scripts-and-Prompts/Outreach-Scripts/C4-Peer-Review-Outreach-Scripts.md
  - 03_Scripts-and-Prompts/Claude-System-Prompts/landing-page-copy-reviewer-v1.0.0.yaml

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Template — M4.7 Landing Page Copy

**Purpose:** Structured template for cohort peer reviews of M4.7 landing page copy. Two peer reviews per student are required; students complete two reviews for peers in exchange.
**Time per review:** ~45-60 minutes
**Timeline:** 72-hour SLA from review request to delivery
**Filed to:** Build 8 Drive folder; linked into submitting student's M4.7 folder

---

## Reviewer Instructions

Read the landing page copy and the Trigger Bank Provenance Log in one pass, then complete the template below. Your job is not to edit line-by-line — the submitting student will do that. Your job is to surface structural issues they cannot see from inside their own draft.

Three things you are specifically looking for:

1. **Does the page sound like the market or like the operator?** You are an outside reader who has not been inside this operator's head for 4 weeks. You can hear voice drift more clearly than they can.

2. **Are the verbatim Trigger Bank quotes doing work, or are they decorative?** Quotes should anchor specific claims. A quote dropped next to a general statement without connection is not working.

3. **Is the anti-promise actually specific, and is the guarantee actually clean?** M4.5 and M4.6 stand-alone documents can be strong but get softened in the landing page. You are the second set of eyes that catches softening.

---

## Reviewer Information

**Reviewer name:** _____________________________
**Reviewer operator archetype:** _____________________________
**Review date:** _____________________________
**Submitting operator name:** _____________________________
**Submitting operator's offer name:** _____________________________

---

## Section-by-Section Review

### Section 1 — Problem

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak
**One-sentence read:** [What is this operator's offer trying to solve, in your words?]

Does the Problem section make the buyer's current state specific and vivid?
☐ Yes, I could visualize it ☐ Partially ☐ No, it was generic

Was at least one verbatim Trigger Bank quote integrated meaningfully (not decoratively)?
☐ Yes ☐ Partially ☐ No

**Specific observations (1-3 sentences):**

---

### Section 2 — Agitation

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Does the Agitation section make the cost of *not acting* feel real, or does it feel performative?
☐ Real ☐ Mixed ☐ Performative

Did any specific numbers, time-frames, or opportunity costs make the Agitation land?
☐ Yes (which ones: __________) ☐ No

**Specific observations:**

---

### Section 3 — Solution-and-Mechanism

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

After reading this section, can you describe the mechanism in your own words?
☐ Yes, I could teach it to a friend ☐ Roughly ☐ No, it's still fuzzy

Are the 4 pillars of the mechanism visible, even if not labeled as pillars?
☐ Yes ☐ Partially ☐ No

**Specific observations:**

---

### Section 4 — Proof

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Are the proof cases specific (named, with outcome data), or are they generic ("Maya is great")?
☐ Specific ☐ Mixed ☐ Generic

If the operator has few case studies, is that acknowledged honestly, or is it papered over?
☐ Acknowledged honestly ☐ Handled in between ☐ Papered over

**Specific observations:**

---

### Section 5 — Offer

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Is the named deliverable clear, specific, and 5-Test-passed?
☐ Yes ☐ Partially ☐ No (how could it be clearer: __________)

Is the price visible on the page?
☐ Yes, clearly ☐ Present but buried ☐ Not visible

Does the delivery structure tell you what the buyer's experience actually is (what they do, when, with whom)?
☐ Yes, concretely ☐ Vaguely ☐ Not really

**Specific observations:**

---

### Section 6 — Anti-Promise-and-Guarantee

**This is the most important section to peer-review.**

**Anti-Promise strength:** ☐ Strong ☐ Adequate ☐ Weak

Does the anti-promise name three specific exclusions?
☐ Yes, three or more ☐ Two ☐ One or fewer

Are any of the "exclusions" actually flattering descriptions of the target buyer (e.g., "not for unmotivated people")?
☐ No, they are genuine exclusions ☐ One or two are flattering-dressed-as-exclusion ☐ Most are

**Guarantee strength:** ☐ Strong ☐ Adequate ☐ Weak

Is the guarantee a clean structure (one primary + one optional complementary), or is it stacked with three or more components?
☐ Clean ☐ Borderline ☐ Stacked (Feature Stuffing Trap signal)

If you were a buyer who met the activation conditions, do you trust this operator would honor the guarantee without friction?
☐ Yes ☐ Mostly ☐ Uncertain

**Specific observations:**

---

### Section 7 — CTA

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Does the CTA name a specific action (not "click here") and a specific outcome ("enroll in the Feb 12 cohort, receive Welcome Kit within 24 hours")?
☐ Yes, specific ☐ Partially ☐ Generic

Is there a clear timeline (cohort start date, enrollment close date)?
☐ Yes ☐ No

**Specific observations:**

---

## Cross-Cutting Review

### Verbatim Trigger Bank Usage

Pick 3 of the Trigger Bank quotes used in the landing page. Check them against the Provenance Log — do they match the source entry verbatim, or have they been paraphrased into "cleaner" language?

- **Quote #1:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased
- **Quote #2:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased
- **Quote #3:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased

**Overall provenance accuracy:** ☐ Strong (all 3 verbatim) ☐ Mixed ☐ Weak (paraphrasing is dominant)

### Voice Check

Does the page sound like the operator or like the market?
☐ Mostly market voice ☐ Mixed (operator voice leaks through in specific sections: __________) ☐ Mostly operator voice

### Total Trigger Bank Entry Count

Count the verbatim quotes in the landing page.
**Count:** ___ / 15 minimum

If below 15, the submission fails the M4.7 checkpoint.

---

## Top-3 Revisions You Recommend

Identify the three revisions that would most improve this landing page:

1. **Revision 1:**
2. **Revision 2:**
3. **Revision 3:**

Each revision should be specific enough that the operator can act on it ("tighten the Problem section opening from 4 sentences to 2") rather than abstract ("improve the copy").

---

## Reviewer Closeout

**Overall assessment:** ☐ Ready to submit ☐ Needs moderate revision ☐ Needs substantial revision

**Would I buy this offer if I were the target buyer?** ☐ Yes ☐ Maybe ☐ No — and why: __________

**Reviewer signature:** _____________________________

---

## For the Submitting Operator

After receiving both peer reviews:

1. Read both reviews in one sitting before acting on either. Look for patterns — if both reviewers flagged the same section as weak, that section needs real work. If they disagree, use your judgment.

2. Your job is not to accept every suggestion. Your job is to take each suggestion seriously and make a documented decision about whether to incorporate it.

3. File a Revision Log (`Revision-Log-M4.7-[YourName]-[Date].md`) noting which suggestions you incorporated, which you considered but did not incorporate, and why. The offer-fit-validator at M4.8 checks for this log.

4. Revise. Submit the revised landing page to the AI rubric (`landing-page-copy-reviewer-v1.0.0.yaml`).

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Alternate Protocol

**Purpose:** Alternate paths when your active C4 cohort has fewer than 4 peers at your pacing window. Ensures M4.7 does not stall for reviewer unavailability.
**Referenced by:** `00_Course-Overview/C4-Prerequisites-Checklist.md`
**Escalation path:** If none of the protocols below are viable, escalate to RISER Nation mentor within 72 hours of M4.7 draft completion.

---

## When to Use This Protocol

Use when any of the following is true:

- Your C4 cohort Circle.so channel (`#c4-offer-ignition`) has fewer than 4 active operators at your pacing window
- Cohort peers at your pacing window have not responded within 72 hours of your review request
- Your cohort is pacing unusually (ahead or behind the main cohort cycle) and peers are not currently at M4.7

---

## Protocol A — Mentor Substitution (Default)

**Who it's for:** Any student whose cohort is too thin for 2 peer reviews.

**How it works:**

1. Book a 45-minute review slot with a named RISER Nation mentor via the Calendly link in the cohort welcome email, or via the `#mentor-requests` Circle.so channel.
2. Submit your M4.7 draft and Trigger Bank Provenance Log at least 24 hours before the review call.
3. The mentor completes the C4 Peer Review Template during or after the call and delivers a written review within 72 hours.
4. Mentor review counts as both required peer reviews. No additional review needed.

**SLA:** 72 hours from submission to written review delivery (typical) ; 96 hours worst-case.

**Cost:** No charge. Mentor capacity is allocated out of Academy program support time.

**When Protocol A is not available:** Mentor booking backed up 2+ weeks. Rare but happens in high-enrollment cycles. Shift to Protocol B.

---

## Protocol B — Cross-Stage Review

**Who it's for:** Students whose mentor booking is backed up, or who prefer review from an operator who has already shipped offers.

**How it works:**

1. Post a review request in the `#cross-stage-review` Circle.so channel with the following structure:

   ```
   **Cross-stage review request — C4 M4.7**
   - Operator archetype: [Teacher / Service / Builder / etc.]
   - Territory: [one sentence]
   - Offer name: [the 5-Test-passed name]
   - Request: 1-2 Stage 2+ operators for M4.7 landing page review
   - SLA: 96 hours
   - Drive link: [link to your draft]
   - Trigger Bank Provenance Log: [link]
   ```

2. Stage 2, Stage 3, Stage 4, or Stage 5+ operators who are active volunteers pick up the review.
3. Review uses the same C4 Peer Review Template.
4. Cross-stage review counts as both required peer reviews, or as one review paired with a mentor/peer review.

**SLA:** 96 hours (longer than peer review because cross-stage operators volunteer review time around their own operation).

**Cost:** No charge. Typically treated as ecosystem reciprocity; Stage 2+ operators accumulate review credit that Stage 1 peers volunteer back.

**Why this can be better than peer review:** Reviewers who have shipped offers have firsthand knowledge of what survives first-sale contact and what does not. Their feedback often has higher signal-to-noise than peer-to-peer review.

**When Protocol B is not available:** No cross-stage reviewer picks up the request within 48 hours. Rare but happens near holiday periods. Shift to Protocol C.

---

## Protocol C — Paid Review (Last Resort)

**Who it's for:** Students whose timeline is blocked and Protocols A and B did not clear within their planned week.

**How it works:**

1. Choose from the Approved Paid Review list in `C4-Approved-Paid-Review-Options.md`.
2. Directly engage the reviewer (paid engagement; Academy does not facilitate payment).
3. Paid reviewer completes the C4 Peer Review Template.
4. Paid review counts as one of the two required reviews. **Paid review alone is not sufficient** — pair with one mentor, cross-stage, or peer review.

**SLA:** per reviewer contract, typically 48-72 hours.

**Cost:** Varies by reviewer. Typical range: $150-$400 per review.

**When Protocol C is genuinely necessary:** rare. Most students who think they need Protocol C actually have a timing problem that Protocol A or B resolves with a slight pacing adjustment (waiting 3-5 extra days for mentor or cross-stage slot).

**Warning:** paid review is a legitimate professional service but is not a substitute for cohort accountability. Paid reviewers who are not familiar with RISER Nation methodology sometimes give advice that conflicts with C3/C4 doctrine (e.g., suggesting feature-stuffed guarantees or removal of the anti-promise section). Review paid feedback critically against the module lessons; do not incorporate paid advice that conflicts with the methodology without checking with a mentor.

---

## Scholarship Path for Protocol C

If your cohort is thin, Protocols A and B are unavailable within your timeline, and Protocol C is financially inaccessible:

1. Email `[email protected]` with "C4 M4.7 Review Scholarship Request" in the subject line
2. Include your Drive link, pacing dates, and which Protocols were attempted
3. SLA: 48 hours for response; if approved, scholarship covers one paid review up to $200

Scholarship approval is typical for genuine thin-cohort situations.

---

## Logging the Alternate Protocol

Whatever Protocol you used, log it in your M4.7 Revision Log so the offer-fit-validator at M4.8 has the context:

```
Peer Review Protocol: [A — Mentor / B — Cross-Stage / C — Paid + one of A or B / Standard two-peer]
Reviewer 1: [name, protocol, date of review]
Reviewer 2: [name, protocol, date of review]
Alternate protocol rationale: [1-2 sentences]
```

The offer-fit-validator does not penalize Alternate Protocol usage — it penalizes missing reviews. Logging the protocol used keeps the validator's coherence checks from flagging the submission.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by C4-Prerequisites-Checklist*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Approved Paid Review Options

**Purpose:** Reference list of paid review providers vetted by RISER Nation for C4 M4.7 landing page review when cohort peer and mentor options are unavailable (Protocol C in the Peer Review Alternate Protocol).
**Referenced by:** `C4-Peer-Review-Alternate-Protocol.md`
**Status:** This list is maintained by the Academy team and updated quarterly. The version below reflects approved reviewers as of the Last Updated date.

---

## Selection Criteria

To appear on this list, a reviewer has:

- Reviewed at least 20 C4-style offer landing pages in the direct-response tradition
- Demonstrated familiarity with mechanism-based offer construction (Hormozi-adjacent methodology)
- Produced reviews that respect the anti-promise section as a credibility mechanism (rather than recommending its removal)
- Signed the RISER Nation Reviewer Affiliate Agreement — which commits them to methodology-consistent feedback
- Been cross-rated by at least 5 past reviewees as useful and non-disruptive

Reviewers without these properties are excluded from the list, regardless of market reputation.

---

## Current Approved Reviewers (Quarterly Update — Q2 2026)

### Tier A — Deep Direct-Response Specialists

These reviewers have 10+ years of direct-response copy experience. Pricing reflects seniority.

- **Reviewer Slot A1** — [reviewer name redacted for template; actual list maintained in Drive]
  - **Pricing:** $350-$450 per review
  - **SLA:** 72 hours
  - **Specialty:** coaching/consulting offers; cohort programs; Teacher-Operator and Service-Operator archetypes
  - **Contact:** [via Calendly link in Drive version]

- **Reviewer Slot A2**
  - **Pricing:** $300-$400 per review
  - **SLA:** 48-72 hours
  - **Specialty:** productized services; Builder-Operator archetype
  - **Contact:** [via Drive]

### Tier B — Mid-Senior Reviewers

5-10 years of direct-response experience. Pricing is moderate.

- **Reviewer Slot B1**
  - **Pricing:** $200-$275 per review
  - **SLA:** 48-72 hours
  - **Specialty:** creative services; Creative-Operator archetype
  - **Contact:** [via Drive]

- **Reviewer Slot B2**
  - **Pricing:** $175-$250 per review
  - **SLA:** 72 hours
  - **Specialty:** B2B offers; systems and platforms; Systems-Operator archetype
  - **Contact:** [via Drive]

### Tier C — RISER Nation Alumni Reviewers

Alumni who have completed Stage 2+ of the Academy and offer paid review to Stage 1 peers. Often the best value — they know the methodology cold and price accordingly.

- **Reviewer Slot C1-C5** — rotating list, currently 5 alumni reviewers available
  - **Pricing:** $150-$200 per review
  - **SLA:** 48-72 hours
  - **Specialty:** matches the alumni's own operator archetype; check Drive list for match
  - **Contact:** [via Drive; alumni reviewers coordinate through `#alumni-review-pool` Circle.so channel]

---

## How To Engage a Paid Reviewer

1. **Check the Drive version of this list** for current names, contact info, and availability status. Names are not in this template to avoid stale information when reviewers rotate.

2. **Match reviewer to your archetype.** A Teacher-Operator reviewing a Service-Operator's offer will sometimes give advice that is methodology-correct but archetype-mismatched. Tier A reviewers are generalists; Tier B and C reviewers are archetype-specialized.

3. **Send your M4.7 draft and Trigger Bank Provenance Log.** Use the C4 Peer Review Template as the deliverable format. Specify upfront that the review output should use the template — do not accept a free-form review.

4. **Specify the methodology baseline.** In your engagement message, include this line:
   > "This review is for a RISER Nation C4 Offer Ignition M4.7 landing page. The offer follows Hormozi-adjacent mechanism-based structure, and explicitly includes a specific Anti-Promise Statement (per Hopkins 1923 / Hormozi 2021) and a guarantee structure with the Honesty Clause signed. Please review for quality within the methodology rather than suggesting removal of these elements."

5. **Log the engagement** in your Revision Log per the Alternate Protocol instructions.

---

## What NOT to Use

**Do not use:**

- General copywriting review services not on this list (quality varies widely; many default to removing anti-promises, which is the specific thing C4 is trying to preserve)
- Fiverr-tier copy review (signal-to-noise too low for C4 work)
- AI-only review tools as a substitute for human review (acceptable as a supplement, not as the required review)
- Review from an unlisted paid reviewer *and* count it as your second required review (list-approved reviewers are the only paid reviews that satisfy Protocol C)

---

## If a Reviewer Gives Methodology-Conflicting Advice

If a paid reviewer recommends:
- Removing the anti-promise section
- Stacking guarantees beyond the clean structure M4.6 specifies
- Replacing verbatim Trigger Bank quotes with "cleaner" paraphrases
- Repositioning the offer in a way that drifts from your C3 Primary mechanism

...treat the feedback as methodology-conflicting. Do not incorporate without first consulting your RISER mentor or the `#methodology-questions` Circle.so channel. Methodology-conflicting advice from a paid reviewer often reflects their own training in non-anti-promise direct-response (common in the 2010s ecosystem) and is not wrong in their original context — it is just not aligned with C3/C4's specific synthesis.

---

## Removing a Reviewer from the List

Reviewers are removed from this list when any of the following occurs:

- 3+ reviewees report methodology-conflicting advice that was materially disruptive
- SLA missed on 20%+ of engagements over a quarter
- Reviewer Affiliate Agreement violation (e.g., upselling reviewees into their own offers during review time)
- Reviewer leaves the direct-response market or does not re-sign quarterly Affiliate Agreement

The list is updated quarterly. Removed reviewers receive 30 days' notice and are not blacklisted from re-entry if conditions change.

---

*Last updated: April 24, 2026 · Version 2.0 · Q2 2026 reviewer list current · Referenced by C4-Peer-Review-Alternate-Protocol*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 — Offer Ignition

**Subtitle:** From Validated Primary Mechanism to First Sellable Offer · The Grand Slam Offer · Drafted, Not Yet Launched
**Stage:** 1 — Dinghy (Foundation)
**Vessel Metaphor:** The Dinghy has cleared the buoys. The harbor is behind you, the open water ahead. Before you can trade, the cargo hold needs cargo — something worth more to a buyer than the price you'll charge. C4 is where you load the hold. The offer is not the mechanism; the offer is what the mechanism is wrapped in so someone will pay for it.
**Module Count:** 8 modules
**Estimated Time:** 15 hours study + 25 hours implementation = 40 hours total · 4-5 weeks elapsed
**Prerequisite Courses:** C3 Buoy Navigation (complete with Market Fit Hypothesis Document filed)
**Stage Color:** Maritime Blue (#2E75B6)

---

## Why This Course Exists

In C3 you produced a Market Fit Hypothesis Document and selected a single validated Primary mechanism. You built a Trigger Bank of 200+ audience-language entries. You scanned 5-10 competitors. You interviewed 8-12 real customers and documented pricing signals in your territory. You know what the market wants in language the market itself supplied.

C4 is where that evidence becomes a sellable object.

Mechanism and offer are not the same thing. Students who confuse them ship one of two failure patterns: they sell the mechanism as if it were the offer (too abstract, buyer cannot evaluate), or they bury the mechanism inside an offer so generic that no trigger, no competitor gap, and no pricing signal from C3 survives. Both patterns produce offers that do not convert even when the mechanism is strong.

The output of C4 is a complete **Offer Document** — named, priced, guaranteed, anti-promised, and landing-page-drafted — ready for C5 First Currents, where Stage 1 graduation gate tests whether the offer holds up under AEO-literate scrutiny and first-sale readiness.

This is also the course where most students first feel the distance between *understanding* their mechanism (C2 output) and being able to *sell* it. That gap is uncomfortable and predictable. The failure case study for C4 — The Feature Stuffing Trap — exists because many students try to close the gap by adding bonuses and guarantees rather than fixing the mechanism-market fit underneath. We name the pattern explicitly in M4.3, M4.5, and M4.6 so you can spot it in yourself.

## Why You Cannot Skip This Course

Every downstream Stage 2 and Stage 3 course assumes C4's outputs exist:

- **C5 First Currents (Stage 1 capstone):** Stage 1 graduation requires Territory + Identity + Mechanism + Offer + First-Sale Readiness. The Offer Document from C4 is one of the five graduation artifacts.
- **C7 Offer Architecture (Stage 2):** expands C4's single offer into a full offer suite with entry, core, and premium tiers. Without a validated single offer, C7 builds on nothing.
- **C10 Funnel Fleet Engineering (Stage 2 gate):** funnel pages are built around the Offer Landing Page Copy produced in M4.7.
- **C13 Partnership Harbors:** the partnership pitch cites your offer's anti-promise and guarantee — both C4 artifacts.
- **C14 First Dollar (Stage 3 gate):** the first sale, by definition, is the sale of the C4 offer. If the offer is not shippable, the gate does not open.
- **Every content piece from C16 onward:** content hooks are Trigger Bank entries that resolve into the C4 offer's promise. No offer → nothing for content to resolve to.

Skipping C4 means every downstream course has to reverse-engineer the offer from whatever partial artifacts exist. Operators who skip C4 are the operators who arrive at C14 with no revenue after 10+ weeks of traffic work because "the offer isn't quite right yet." C4 is when "quite right" becomes "shipped in a document, named, priced, and defensible."

## Who This Course Is For

C3 graduates with a filed Market Fit Hypothesis Document that names a single validated Primary mechanism, a Trigger Bank of 200+ entries, a competitor scan of 5-10 operators, 8-12 customer interviews, and documented pricing signals. C4 does not work without all six C3 outputs in hand.

If you are at C4 enrollment without C3 complete — or with C3 complete but one of the six artifacts missing or thin — Build 6 will deny access. The reason: C4's first action (M4.1) is to re-read your Market Fit Hypothesis and distinguish between the mechanism and the offer-to-be. Without the Market Fit Hypothesis, there is nothing to distinguish from.

## What You Will Have When You Finish

Eight new artifacts in your Build 8 Drive folder, all referenced by C5-C55:

1. **Offer-Mechanism-Distinction-[YourName]-[Date].md** — the M4.1 written memo distinguishing the mechanism from the offer-to-be built around it
2. **Value-Equation-Worksheet-[YourName]-[Date].md** — Hormozi's Value Equation applied across Dream Outcome, Perceived Likelihood, Time Delay, Effort & Sacrifice
3. **Offer-Decomposition-Variants-[YourName]-[Date].md** — three distinct decomposition variants of the Primary mechanism into saleable form (6% Rule applied)
4. **Pricing-Decision-[YourName]-[Date].md** — the anchor price, price band selection, and payment options with rationale from C3 signals
5. **Anti-Promise-Statement-[YourName]-[Date].md** — what the offer explicitly does NOT do, and who it is explicitly NOT for
6. **Guarantee-Architecture-[YourName]-[Date].md** — the guarantee structure with refund terms and conditional components
7. **Offer-Landing-Page-Copy-[YourName]-[Date].md** — the 7-section landing page copy, ready for deployment, with minimum 15 Trigger Bank entries used verbatim
8. **Offer-Readiness-Document-[YourName]-[Date].md** — the synthesis artifact that becomes C5's primary input, plus the first-sale readiness checklist

## Module Map

| # | Title | Outcome | Bloom's | Time |
|---|---|---|---|---|
| M4.1 | Offer Architecture Foundations | Student has distinguished the offer from the mechanism and named the 7 components an offer contains that a mechanism does not | Analyze | 75 min |
| M4.2 | The Grand Slam Offer Framework | Student has applied Hormozi's Value Equation across 4 variables (Dream Outcome × Perceived Likelihood ÷ Time Delay × Effort & Sacrifice) to their Primary | Understand + Apply | 90 min |
| M4.3 | Offer Deconstruction and Reassembly | Student has produced 3 distinct decomposition variants of their mechanism into offer form (6% Rule) | Create | 180 min |
| M4.4 | Pricing and Anchoring | Student has selected an anchor price and payment structure grounded in C3 pricing signals | Evaluate | 90 min |
| M4.5 | The Anti-Promise Statement | Student has written the explicit statement of what the offer does NOT do and who it is NOT for | Create | 75 min |
| M4.6 | Guarantee Architecture | Student has designed a guarantee structure (conditional or unconditional) that reverses risk without collapsing unit economics | Apply | 90 min |
| M4.7 | Offer Landing Page Copy | Student has produced 7-section landing page copy using minimum 15 Trigger Bank entries verbatim | Create | 240 min |
| M4.8 | Offer Readiness Document | Student has produced the synthesis artifact and first-sale readiness checklist that becomes C5's primary input | Create | 90 min |

**Total:** 8 modules × avg 116 min = ~15 hours of study + ~25 hours of implementation (drafting, revising, peer review incorporation) = ~40 hours

C4 is shorter in active hours than C3 because the work is internal writing rather than external research. Writing, however, is rarely faster than research in elapsed time — first drafts sit for 48 hours between modules so that revisions happen with fresh eyes. Plan 4-5 weeks even though the active-hour total is lower.

## How to Study This Course

**Recommended pacing:** 4-5 weeks. M4.1 and M4.2 complete in week 1 (foundation). M4.3 produces 3 decomposition variants across week 2 (the 6% Rule work). M4.4 (pricing) and M4.5 (anti-promise) complete in week 3. M4.6 (guarantees) and M4.7 (landing page copy) consume week 4, with M4.7 requiring a peer review cycle before M4.8 unlocks. M4.8 synthesizes and files the Offer Readiness Document in week 5.

**Why this is faster than C3 in active hours:** C3 required outreach and scheduling on other people's calendars. C4 is you, the Market Fit Hypothesis, the Trigger Bank, and a writing surface. There is no one to wait for.

**Why this is not necessarily faster in elapsed time:** Writing improves on the second pass. Offers that land in the first draft almost always benefit from a 48-hour cooling period before the second pass. C4's pacing bakes this in — first drafts are filed, then revised after at least one night of sleep and, in the case of M4.7, after peer review.

**Where to take notes:** Build 8 Drive folder for C4 specifically. Every decomposition variant, every pricing option considered, every guarantee structure explored goes in Drive — even the options that do not survive. The abandoned variants are frequently reopened in Stage 2 when the offer evolves.

**When to file deliverables:** As produced. M4.3 requires 3 decomposition variants to exist simultaneously in the Drive folder before M4.4 unlocks. M4.7 requires a peer-reviewed draft before M4.8 unlocks.

**Where to discuss:** Circle.so `#c4-offer-ignition`. M4.7 has a mandatory peer review element — your landing page copy is reviewed by two cohort peers before M4.8 unlocks, extending the C1 M1.3 and C3 M3.3 peer review pattern.

## The HITL Checkpoint (Expanded in C4)

C3 added its first Human-In-The-Loop review at M3.7. C4 extends the pattern: M4.7 landing page copy is peer-reviewed by two cohort members before M4.8 unlocks. The rationale is the same asymmetric-cost logic as C3 — landing page copy that ships with the wrong framing wastes every hour of traffic work in C10-C18. Peer review at M4.7 is the cheapest place to catch framing drift.

Peer review in C4 is not instructor review. Instructor review happens in C5 as part of Stage 1 graduation. C4 peer review is operator-to-operator — two peers at similar stage reviewing whether your copy reads as promised in your Hypothesis Document and whether Trigger Bank entries are actually being used verbatim rather than paraphrased.

## Prerequisites (enforced by Build 6)

- C3 Course Completion (`c3_complete = true` in Supabase users table)
- Market Fit Hypothesis Document filed within last 3 months (`c3_market_fit_hypotheses` table active row)
- Trigger Bank with 200+ entries filed (`c3_trigger_banks` active row)
- Competitor Scan with 5-10 operators (`c3_competitor_scans` active row)
- Customer Interview Library with 8+ interviews (`c3_interview_library` active row)
- Pricing signals documented (`c3_pricing_signals` active row)
- Captain's Oath signed within last 12 months (C1 prerequisite still active)
- Operator Identity Statement filed within last 12 months (C1 prerequisite still active)
- ~4-6 hours of calendar availability per week for writing and revision

Full Prerequisites Checklist in this folder.

## Course and Institutional Policies

Identical to C1, C2, and C3 (FTC AI Disclosure, Copyright/IP, Academic Integrity, Accessibility, Data Protection). Two C4-specific additions:

**Anti-Promise Integrity:** every anti-promise written in M4.5 must be truthful and, where it names a disqualified audience, specific rather than pejorative. "This is not for people who want a done-for-you service" is fine. "This is not for lazy people" is not. The Anti-Promise Integrity Statement in `02_Resources/Templates/` is signed before M4.5 submission.

**Guarantee Honesty Clause:** any guarantee written in M4.6 must be one the student intends to honor. A guarantee the student plans to make difficult to claim is a deceptive marketing practice and violates the RISER Nation Integrity Policy regardless of how the offer is phrased. The Guarantee Honesty Clause in `02_Resources/Templates/` is signed before M4.6 submission.

## Founder's Course Introduction

The video in `01_Module-Lessons/M4.1` opens with a 4-minute founder note: why C4 is called "Offer Ignition" rather than "Offer Architecture" (which is C7), why the course produces a single offer rather than an offer suite, and the specific failure mode — **mistaking the offer for the mechanism, or vice versa** — that the course exists to prevent.

## Quality Certification

C4 has passed RISER Nation's internal QM-equivalent audit at 92/94 (97.9%). Fifteen of 16 Essential Standards MET; one PARTIAL (SRS 8.3, pending v2.1 video production for M4.2-M4.8). Full audit in `05_Checkpoints-and-Tests/QM-Audit-C4.json`.

## Cross-Reference to C1, C2, and C3

C4 reads heavily from all three prior courses:

**From C1:**
- **Captain's Oath Clause 1 (territory):** the offer must serve the stated territory. Offers that drift across territory boundaries are flagged by the M4.8 validator.
- **Operator Identity:** Teacher-Operator offers differ from Service-Operator offers (cohort-based vs. 1:1; asynchronous deliverables vs. synchronous engagement). M4.3 decomposition variants are archetype-informed.
- **6% Rule:** C4 applies the rule as "draft 3 decomposition variants before committing to 1." M4.3 produces 3; M4.8 selects 1.
- **85-Minute Rhythm:** continues unchanged.

**From C2:**
- **Mechanism Hypothesis Document:** M2.6 verbatim audience quotes seed M4.7 landing page copy alongside the full C3 Trigger Bank.
- **4-Pillar Mechanism Discovery Framework:** the offer's Method section in the landing page copy (M4.7) restates the mechanism's Method pillar.
- **5-Test Naming Filter:** applied to the offer name in M4.3. The offer may inherit the mechanism name or produce a new offer-specific name; either way, the 5-test is re-run.

**From C3:**
- **Market Fit Hypothesis Document:** C4's primary input. M4.1 opens with a re-reading.
- **Trigger Bank:** M4.7 landing page copy uses a minimum of 15 Trigger Bank entries verbatim. Entries paraphrased rather than quoted verbatim are flagged by the landing-page-copy-reviewer.
- **Competitor Scan:** M4.5 anti-promise and M4.4 pricing both cite specific competitors from the C3 scan.
- **Customer Interviews:** M4.3 decomposition variants reflect what interviewees actually said they would buy, not what the student wishes the interviewees had said.
- **Pricing Signals:** M4.4 anchor price sits within the observed market band unless the student documents a defensible reason for deviation.

If any C1, C2, or C3 artifact is missing or stale, Build 6 routes the student back to the appropriate course before C4 work begins.

---

*Last updated: April 24, 2026 · Version 2.0 · Owner: RISER Nation Curriculum Team*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Offer Ignition — Module Map

## Flow Diagram (Mermaid)

```mermaid
graph TD
    START([C3 Complete - Market Fit Hypothesis Filed]) --> M41[M4.1 Offer Architecture Foundations<br/>Distinguish offer from mechanism<br/>75 min]
    M41 --> CP41{Checkpoint 4.1<br/>Distinction memo filed?}
    CP41 -->|Pass| M42[M4.2 The Grand Slam Offer Framework<br/>Value Equation applied across 4 variables<br/>90 min]
    CP41 -->|Fail| M41

    M42 --> CP42{Checkpoint 4.2<br/>Value Equation worksheet complete?}
    CP42 -->|Pass| M43[M4.3 Offer Deconstruction and Reassembly<br/>3 distinct decomposition variants<br/>180 min]
    CP42 -->|Fail| M42

    M43 --> CP43{Checkpoint 4.3<br/>3 variants produced; 6%% Rule honored?}
    CP43 -->|Pass| M44[M4.4 Pricing and Anchoring<br/>Anchor price + payment options<br/>90 min]
    CP43 -->|Fail| M43

    M44 --> CP44{Checkpoint 4.4<br/>Price selected with C3 rationale?}
    CP44 -->|Pass| M45[M4.5 The Anti-Promise Statement<br/>What the offer does NOT do<br/>75 min]
    CP44 -->|Fail| M44

    M45 --> CP45{Checkpoint 4.5<br/>Anti-promise truthful + specific?}
    CP45 -->|Pass| M46[M4.6 Guarantee Architecture<br/>Refund + conditional structure<br/>90 min]
    CP45 -->|Fail| M45

    M46 --> CP46{Checkpoint 4.6<br/>Guarantee honest + sustainable?}
    CP46 -->|Pass| M47[M4.7 Offer Landing Page Copy<br/>7-section structure + 15+ Trigger Bank quotes<br/>240 min]
    CP46 -->|Fail| M46

    M47 --> PEER[PEER REVIEW<br/>2 cohort peers review landing page copy<br/>48-hour SLA]

    PEER -->|Approved| CP47{Checkpoint 4.7<br/>Peer reviews complete; quotes verified verbatim?}
    PEER -->|Revise| M47
    CP47 -->|Pass| M48[M4.8 Offer Readiness Document<br/>Synthesis + First-Sale Readiness Checklist<br/>90 min]
    CP47 -->|Fail| M47

    M48 --> CP48{Checkpoint 4.8<br/>Opus validator: PASS?}
    CP48 -->|Pass| COMPLETE([C4 Complete<br/>C5 Enrollment Unlocked])
    CP48 -->|Fail| M48

    style START fill:#2E75B6,color:#fff
    style COMPLETE fill:#2E75B6,color:#fff
    style PEER fill:#BF9000,color:#fff
```

---

## Serial Work Structure

Unlike C3 (which ran desk research and interview scheduling in parallel), C4 is sequential. Each module's output is an input to the next:

- M4.1 (distinction memo) anchors M4.2's Value Equation target
- M4.2 (Value Equation) shapes M4.3's decomposition criteria
- M4.3 (3 variants) produces the variant that M4.4 prices
- M4.4 (pricing) + M4.5 (anti-promise) + M4.6 (guarantee) each become landing-page inputs
- M4.7 (landing page) composes all prior outputs into copy
- M4.8 (readiness doc) synthesizes the entire chain

Attempting to parallelize C4 tends to produce incoherent offers — e.g., an anti-promise that contradicts the chosen guarantee, or a price that does not match the Value Equation conclusion. Hold the sequence.

---

## The 48-Hour Cooling Period

C4 bakes a 48-hour gap between first and second drafts of M4.3, M4.5, M4.7, and M4.8. The mechanism: file a first draft, sleep on it for at least one night (two nights preferred), then revise. The weekly rhythm below honors this.

The reason: offers written in a single sitting inherit the mood and caffeine level of that sitting. A 48-hour gap surfaces sentences that sound clever on day 1 but hollow on day 3. Operators who skip the gap consistently produce copy with the most energy and the least durability — the copy that reads well on launch day and stops reading well after the first round of buyer objections.

---

## Weekly Rhythm Integration

C4 maintains the C1 85-Minute Weekly Rhythm. Per-module time distributes across weeks as follows:

| Week | Monday 10min | Tuesday 15min | Wednesday 30min | Thursday 20min | Friday 10min |
|---|---|---|---|---|---|
| 1 | Read Market Fit Hypothesis | M4.1 distinction memo outline | M4.1 memo complete; begin M4.2 Value Equation | M4.2 Value Equation draft | File M4.1 + M4.2 |
| 2 | M4.3 decomposition brainstorm | M4.3 variant 1 outline | M4.3 variant 1 + variant 2 drafted | M4.3 variant 3 drafted | File all 3 variants |
| 3 | Re-read variants; select lead | M4.4 pricing research from C3 signals | M4.4 pricing decision drafted | M4.5 anti-promise draft | File M4.4 + M4.5 |
| 4 | M4.6 guarantee draft | M4.6 guarantee revised; honesty clause signed | M4.7 landing page sections 1-4 drafted | M4.7 landing page sections 5-7 drafted | File M4.7 draft; send for peer review |
| 5 | Incorporate peer feedback | M4.7 revised | M4.8 Readiness Document draft | M4.8 revised; First-Sale Readiness Checklist | Submit to Opus validator |

Week 5 absorbs peer review latency. If peers respond on day 1, M4.8 can submit earlier. If peers miss the 48-hour SLA, week 5 holds until reviews land.

---

## Checkpoint Details

Full checkpoint specifications are in `05_Checkpoints-and-Tests/All-Module-Checkpoints.md`. Summary:

| Checkpoint | Type | Pass Threshold |
|---|---|---|
| 4.1 | Type 1 Artifact + Type 2 AI rubric | AI rubric ≥ 7/10 on offer-vs-mechanism distinction |
| 4.2 | Type 1 Artifact + Type 2 AI rubric | AI rubric ≥ 7/10 on Value Equation application with cited evidence |
| 4.3 | Type 1 Artifact + Type 3 structural verification | 3 variants present; each with different engagement model, duration, and price band |
| 4.4 | Type 1 Artifact + Type 2 AI rubric | AI rubric ≥ 7/10 on pricing rationale grounded in C3 signals |
| 4.5 | Type 1 Artifact + Type 2 AI rubric | AI rubric ≥ 7/10 on anti-promise specificity and truthfulness; Integrity Statement signed |
| 4.6 | Type 1 Artifact + Type 2 AI rubric | AI rubric ≥ 7/10 on guarantee sustainability; Honesty Clause signed |
| 4.7 | Type 1 Artifact + Type 2 AI rubric + Peer Review | AI rubric ≥ 7/10 AND 2 peer reviews completed AND 15+ Trigger Bank entries verified verbatim |
| 4.8 | Type 1 Artifact + Opus Validator + Course Completion Test | Validator returns PASS AND all 8 C4 artifacts verified |

---

## Dependency on C3 Market Fit Hypothesis

Every module reads specific parts of the C3 outputs:

| Module | Reads from C3 |
|---|---|
| M4.1 | Market Fit Hypothesis Section 3 (Primary mechanism) — the thing being distinguished from the offer |
| M4.2 | Trigger Bank entries (Dream Outcome signals), Interview Library (Perceived Likelihood evidence), Competitor Scan (Time Delay benchmarks), Pricing Signals (Effort proxies) |
| M4.3 | Customer Interview Library — what interviewees actually said they would buy |
| M4.4 | Pricing Signals — the observed band |
| M4.5 | Customer Interviews (disconfirming signals), Trigger Bank objection entries |
| M4.6 | Competitor Scan (adjacent guarantees), Interview Library (risk-reversal language) |
| M4.7 | Full Trigger Bank — minimum 15 entries used verbatim |
| M4.8 | All C3 artifacts — synthesized into Readiness Document |

If the Market Fit Hypothesis is missing Section 3 (Primary), the Trigger Bank has fewer than 200 entries, or the Pricing Signals document is absent, Build 6 flags C4 as not ready and routes the student back to C3 before offer work begins.

---

## The Feature Stuffing Trap (Failure Pattern)

C4 has one named failure case study: **The Feature Stuffing Trap** (`07_Case-Studies-and-Examples/Case-Failure-The-Feature-Stuffing-Trap.md`). The pattern:

Student reaches M4.3 or M4.6 and feels the offer is not compelling enough. Rather than returning to examine whether the mechanism-market fit from C3 was actually strong, the student adds bonuses, stacks guarantees, and pads the deliverable list. The offer grows in apparent value without growing in actual demand.

The Feature Stuffing Trap is recognizable in three signals:
1. The Value Equation worksheet (M4.2) scores low on Dream Outcome or Perceived Likelihood and the student is compensating in Time Delay or Effort & Sacrifice with features rather than revisiting the numerator.
2. The anti-promise (M4.5) is vague or missing because any specific anti-promise would narrow a buyer pool the student is already anxious about.
3. The guarantee (M4.6) contains three or more conditional clauses that make activation improbable — effectively a guarantee-in-name that does not reverse buyer risk.

The case study walks through the pattern and the remediation: return to C3 Kill Criteria Evaluation, confirm the Primary actually survived its tests rather than was waved through, and — if it did not — reopen the C3 M3.7 decision rather than compensate at the offer layer.

---

*Last updated: April 24, 2026 · Version 2.0*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Preparation Checklist

**Purpose:** Pre-flight check before submitting M4.7 landing page copy for cohort peer review. Prevents common rework-causing gaps.
**Time to complete:** 15-20 minutes before submission
**Filed to:** Attached to your M4.7 submission

---

## Before You Submit

Running this checklist before posting in `#c4-offer-ignition` saves your peer reviewers 30-60 minutes per review and dramatically increases the quality of feedback you receive. Reviewers who have to hunt for your Trigger Bank Provenance Log, or who notice your anti-promise softened from M4.5, spend their review time on mechanical issues rather than substantive feedback.

---

## Section A — Document Completeness

- [ ] Landing page copy file exists at `Offer-Landing-Page-Copy-[YourName]-[Date].md`
- [ ] All 7 sections present in order:
  - [ ] Section 1 — Problem (200-400 words)
  - [ ] Section 2 — Agitation (150-300 words)
  - [ ] Section 3 — Solution-and-Mechanism (300-500 words)
  - [ ] Section 4 — Proof (200-400 words)
  - [ ] Section 5 — Offer (300-500 words)
  - [ ] Section 6 — Anti-Promise-and-Guarantee (250-400 words)
  - [ ] Section 7 — CTA (50-150 words)
- [ ] Total word count in 1,800-2,500 range (not absurdly over or under)

## Section B — Trigger Bank Usage

- [ ] Trigger Bank Provenance Log file exists at `Landing-Page-Trigger-Bank-Provenance-[YourName]-[Date].md`
- [ ] Log contains ≥ 15 entries mapped to landing page usage
- [ ] Every entry in the log is verbatim (not paraphrased) from the source Trigger Bank
- [ ] Each entry cites specific Trigger Bank ID (TB-###) or Interview #
- [ ] Entries are distributed across 4+ of the 7 sections (not all stacked in one section)

## Section C — Anti-Promise and Guarantee Integrity

- [ ] Anti-Promise in Section 6 is substantively the same as your M4.5 Anti-Promise Statement
- [ ] If any softening occurred between M4.5 and M4.7, it is reverted OR documented with rationale
- [ ] Anti-Promise Integrity Statement is signed
- [ ] Guarantee in Section 6 is substantively the same as your M4.6 Guarantee Architecture
- [ ] If any stacking occurred between M4.6 and M4.7, it is reverted
- [ ] Guarantee Honesty Clause is signed

## Section D — Offer Section Completeness

- [ ] Named deliverable (5-Test-passed name) visible in Section 5
- [ ] Price visible in Section 5 (not hidden, not ranged)
- [ ] Payment options listed
- [ ] Delivery structure described (engagement model, duration, cadence)
- [ ] Deliverables list is not over 8 items (Feature Stuffing Trap check)

## Section E — Proof Integrity

- [ ] Proof cases in Section 4 are specific (named or anonymized with specific outcome)
- [ ] If you have fewer than 4 named cases, the Known Weaknesses acknowledgment is visible (not papered over)
- [ ] Testimonials (if any) are verbatim quotes, not paraphrased
- [ ] Testimonials have attribution (name or anonymized but specific)

## Section F — CTA Specificity

- [ ] CTA names a specific action (not "click here")
- [ ] Next cohort / enrollment date is present
- [ ] Qualification process (if any) is described
- [ ] Contact email or channel is present for pre-purchase questions

## Section G — Voice Check

- [ ] You have read the full landing page out loud once, from start to finish
- [ ] The page does not contain phrases you would not actually say to a buyer in person
- [ ] The page does not contain hyperbole you cannot substantiate
- [ ] The page does not contain any of these phrases: "game-changer," "revolutionary," "transform your life," "all you need to do is" (low-substance signaling vocabulary)

## Section H — Review Request Post

Before posting in `#c4-offer-ignition`, prepare the post:

- [ ] Drive link to landing page copy
- [ ] Drive link to Trigger Bank Provenance Log
- [ ] Brief context (2-3 sentences about your offer's key positioning)
- [ ] Specific request: "2 peer reviews within 72 hours, using the C4 Peer Review Template"
- [ ] Your availability to return review favor (which days you can review others' copy)

---

## Common Pre-Submit Fixes

If any checklist item is unchecked, common fixes:

| Unchecked Item | Typical Fix |
|---|---|
| Section 6 softened from M4.5/M4.6 | Revert to the original M4.5 Anti-Promise and M4.6 Guarantee language |
| Trigger Bank count < 15 | Add 3-6 more verbatim entries, typically in Problem and Agitation sections |
| Deliverables > 8 | Review for Feature Stuffing; which deliverables are compensation, which are real value? |
| Price hidden or ranged | Move price to Section 5 with explicit number |
| Voice check fails | 48-hour cooling re-read; rewrite any section where "did I actually say that?" is your reaction |

---

## After Submission

Once posted:

- [ ] Check `#c4-offer-ignition` daily for reviewer pickup
- [ ] Respond promptly to reviewer questions
- [ ] Do not revise the landing page while reviews are in progress (creates version mismatch)
- [ ] Begin reviewing other cohort peers' landing pages as reviews arrive — reciprocity is cohort norm

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Outreach Scripts

**Purpose:** Short scripts for requesting and responding to peer reviews during M4.7. These are starter templates; adapt in your own voice.
**Filed to:** `03_Scripts-and-Prompts/Outreach-Scripts/`
**Referenced by:** M4.7 Written Lesson; C4-Peer-Review-Preparation-Checklist

---

## Script 1 — Requesting Peer Review (post in `#c4-offer-ignition`)

```
**M4.7 peer review request — [YourName]**

- **Offer name:** [5-Test-passed name]
- **Target buyer:** [one sentence describing who this is for]
- **Price:** $[X]
- **What I want reviewers to watch for specifically:**
  - [1-2 things you suspect may be weak — common: Section 4 Proof, Section 6 Anti-Promise softening, Trigger Bank entry density]

**Drive links:**
- Landing page copy: [link]
- Trigger Bank Provenance Log: [link]
- Revision Log (so far): [link — if you have one]

**SLA:** 72 hours ideal

**Reciprocity:** I'm available to review copy on [specific days this week]. Reply with yours and I'll pick up the first two.

Using the C4 Peer Review Template (`02_Resources/Templates/C4-Peer-Review-Template.md`).
```

### Why this structure works

Naming what you suspect is weak focuses reviewer attention. Without this, reviewers tend to spread feedback thin across the whole page. Concentrated attention on 1-2 sections produces higher-signal feedback.

---

## Script 2 — Offering Peer Review (response to another student's request)

```
I'll pick up your review, [TheirName]. I'll aim to deliver within 48 hours.

If you want me to pay particular attention to [suggested focus based on their request], I will. If you want me to do a straight full-template review, I'll do that too.

My C4 Peer Review Template will be back in your Drive folder or Circle.so thread by [specific date + time].
```

### Why this structure works

Confirms the commitment with a specific delivery time. Acknowledges their request-specific focus areas. Creates accountability for the delivery.

---

## Script 3 — Declining a Peer Review (when over-committed)

```
Thanks for tagging me, [TheirName]. I'm at capacity this week ([reason if relevant — e.g., "I'm in my own M4.7 cycle with deadline Thursday"]).

Tagging [OtherName] who mentioned they had bandwidth this week. You can also use the Alternate Protocol at `02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md` if the cohort is thin at your pacing — Protocol A (mentor substitution) is available.
```

### Why this structure works

Declining without leaving the requester stranded. Referring to Alternate Protocol reminds the requester that the safety net exists.

---

## Script 4 — Delivering Peer Review (after completing the template)

```
[TheirName] — review complete.

**Template:** [Drive link to completed Peer Review Template]

**Top-level observation:** [one sentence — your overall impression]

**My three recommended revisions (from template):**
1. [brief version]
2. [brief version]
3. [brief version]

Happy to discuss any of these in async DM if useful. Good luck with M4.8.
```

### Why this structure works

Surfaces the most actionable takeaway in the message itself so the requester can start revising without waiting to open the full template. The full template provides depth; the message provides urgency.

---

## Script 5 — Responding to Peer Review (after incorporating)

```
[ReviewerName] — thanks for the review. Incorporated as follows:

- **Revision 1 you recommended:** [incorporated / incorporated with modification / not incorporated + reason]
- **Revision 2:** [same format]
- **Revision 3:** [same format]

Revision Log in Drive: [link]

Appreciate the time.
```

### Why this structure works

Closes the loop on every recommendation. Decisions not to incorporate are documented (not silently ignored). The Revision Log is what the offer-fit-validator at M4.8 checks for.

---

## Script 6 — Escalating to Mentor (when Alternate Protocols Fail)

Address to `#mentor-requests` Circle.so channel or via the mentor Calendly link from cohort welcome email:

```
**C4 M4.7 peer review escalation — [YourName]**

- Cohort pacing window: [your dates]
- Peer reviews attempted: [how many requests, how many responses]
- Alternate Protocols tried: [A — mentor booking status / B — cross-stage post status / C — paid review status]

**Specific help requested:** [mentor review of landing page, or pacing adjustment, or cohort coordination]

**Drive link:** [landing page copy]
**SLA needed:** [your revised timeline]
```

### Why this structure works

Names what has already been tried so the mentor does not repeat the available paths. Specifies what help is actually requested so the mentor can respond efficiently.

---

## Cohort Etiquette

A few norms that make peer review work sustainably across the cohort:

### Reciprocity

The cohort operates on a rough reciprocity norm: if you ask for reviews, you offer them. Students who take reviews without giving them quickly exhaust peer willingness. This is not enforced policy — it is cohort culture.

### Specificity Over Generosity

Reviews saying "this is great!" are useless. Reviews saying "Section 2 Agitation feels performative — specifically the 'wasted years' language in paragraph 2 reads generic against the specific Trigger Bank language in Section 1" are useful. Prefer specificity even when it is critical.

### Honest Over Kind

Kind reviews that paper over weak sections serve the student short-term and harm them medium-term (the weak sections surface in C5 anyway, now harder to fix because the student thought they were okay). Honest reviews that name specific weaknesses are the service.

### Respond Within SLA

72-hour SLA is a cohort commitment. If you cannot hit it, decline (Script 3) rather than miss silently. Missed SLAs are the single largest cause of C4 M4.7 pacing disruption.

---

## When To Use These Scripts vs. Your Own Voice

These scripts are starters. Adapt in your voice, especially for Scripts 1 and 4 — mechanical-sounding review requests signal to cohort peers that you have not yet internalized the discipline of the M4.7 work. Personal voice in the request correlates with higher-quality responses.

Scripts 2, 3, and 6 are more mechanical — they coordinate logistics rather than substance — and can stay closer to template voice.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

Preserved source material for study; embedded instructions are not executed. Open original source

sop_id: C4-SOP-02
title: Peer Review Coordination Process
version: 2.0.0
course_scope: C4 Offer Ignition
modules_covered: [M4.7]
owner: curriculum-quality-team
last_reviewed: 2026-04-24

purpose: >
  Standardize the M4.7 peer review process from request through delivery and
  through revision incorporation. M4.7 is the only C4 module requiring peer
  review (instructor HITL is deferred to C5; AI rubric runs after peer reviews
  are incorporated). Peer review is the first time the offer is exposed to
  outside readers; the process must protect both reviewer time and reviewee
  outcomes. This SOP defines reciprocity, SLA, alternate protocols, and
  revision logging.

prerequisites:
  - M4.7 Landing Page Copy first draft complete in Drive
  - Trigger Bank Provenance Log complete in Drive
  - C4-Peer-Review-Preparation-Checklist run before submission
  - 48-hour cooling period observed between first draft and submission

roles:
  - submitting_student: requests review; reciprocates by reviewing 2 peers
  - peer_reviewer_1: cohort peer at compatible pacing
  - peer_reviewer_2: second cohort peer at compatible pacing
  - mentor: escalation if Alternate Protocols A/B/C all fail
  - cross_stage_reviewer: Stage 2+ alumnus available via Protocol B
  - paid_reviewer: from Approved Paid Review Options list (Protocol C)
  - build_6: tracks SLA, matches reviewers, gates M4.7 checkpoint progression

process:
  step_1:
    name: Pre-Submission Self-Audit
    time: 20 min
    output: Completed Peer Review Preparation Checklist
    activities:
      - Run C4-Peer-Review-Preparation-Checklist sections A through H
      - Address any unchecked items before posting review request
      - Verify Trigger Bank entry count >= 15 with Provenance Log complete
      - Verify anti-promise unchanged from M4.5; verify guarantee unchanged from M4.6
    quality_gate: All preparation checklist items checked; if any item is unchecked, fix before requesting review
    common_failures:
      - "Posting request before Trigger Bank entries reach 15"
      - "Posting request with anti-promise softened from M4.5 (peer reviewers will flag, costing 24-48 hours)"
      - "Forgetting to attach Trigger Bank Provenance Log"
    mitigation: The checklist exists specifically to catch these. Run it.

  step_2:
    name: Request Review (Standard Protocol)
    time: 15 min
    output: Review request post in #c4-offer-ignition Circle.so channel
    activities:
      - Use Outreach Script 1 from C4-Peer-Review-Outreach-Scripts.md
      - Specify offer name, target buyer, price, areas you suspect are weak
      - Attach Drive links to landing page copy AND Trigger Bank Provenance Log
      - State 72-hour SLA expectation
      - Offer specific reciprocity (which days you can review others' copy this week)
    quality_gate: Post visible in #c4-offer-ignition; request structure matches Outreach Script 1
    common_failures:
      - "Vague request without specifying suspected-weak sections (reviews come back generic)"
      - "Not offering reciprocity (cohort norm violated; future review requests slower to receive responses)"
      - "Missing Provenance Log attachment (reviewers can't verify Trigger Bank usage)"
    mitigation: Use the script verbatim until it becomes natural

  step_3:
    name: Reviewer Pickup (24-48 hours from request)
    time: passive
    output: 2 peers commit to review with stated delivery dates
    activities:
      - Build 6 sends notification to active cohort peers at compatible pacing
      - Peers respond using Outreach Script 2 (acceptance) or Script 3 (decline with referral)
      - Build 6 logs commitments and tracks SLA
      - If only 1 reviewer commits within 48 hours, Build 6 escalates per step 4a
    quality_gate: 2 reviewers committed within 48 hours
    common_failures:
      - "Cohort thin at student's pacing (Protocol A activates)"
      - "Reviewers who committed silently miss SLA without communication"
    mitigation: Build 6 active SLA tracking surfaces silent misses; cohort norm includes communicating early if SLA at risk

  step_4_alternate_protocol_a:
    name: Mentor Substitution (Protocol A)
    time: 24 hours from activation
    output: Mentor named as reviewer; review delivered within 72 hours
    activation_trigger: Cohort has < 4 active peers at compatible pacing OR < 2 peers commit within 48 hours
    activities:
      - Student books mentor review slot via Calendly link in cohort welcome email
      - OR Student posts in #mentor-requests with M4.7 review request
      - Mentor delivers full Peer Review Template completion within 72 hours
      - Mentor review counts as both required peer reviews
    quality_gate: Mentor review filed with C4-Peer-Review-Template completion
    common_failures:
      - "Mentor booking backed up 2+ weeks during high-enrollment cycle (rare; route to Protocol B)"

  step_4_alternate_protocol_b:
    name: Cross-Stage Review (Protocol B)
    time: 96 hours from activation
    output: 1-2 Stage 2+ alumni reviewers complete review
    activation_trigger: Mentor backed up; OR student prefers reviewer who has shipped offers
    activities:
      - Student posts in #cross-stage-review channel using request format from Alternate Protocol document
      - Stage 2-5 operators who actively volunteer review time pick up the request
      - Review uses C4 Peer Review Template
      - Cross-stage review counts as both required reviews, OR pairs with one peer/mentor review
    quality_gate: Cross-stage review filed
    common_failures:
      - "No cross-stage reviewer picks up within 48 hours (route to Protocol C)"

  step_4_alternate_protocol_c:
    name: Approved Paid Review (Protocol C — Last Resort)
    time: 48-72 hours from activation
    output: Paid reviewer completes review using C4 Peer Review Template
    activation_trigger: Protocols A and B unavailable within student's planned week
    activities:
      - Student selects from C4-Approved-Paid-Review-Options.md (Tier A/B/C)
      - Direct engagement; Academy does not facilitate payment
      - Paid reviewer completes C4 Peer Review Template
      - Paid review counts as 1 of 2 required reviews; must pair with peer/mentor/cross-stage for second
      - Methodology consistency check: any methodology-conflicting paid feedback flagged before incorporation
    quality_gate: Paid review filed; second review (peer/mentor/cross-stage) also filed
    common_failures:
      - "Paid reviewer recommends removing anti-promise (methodology-conflict; do not incorporate without mentor consult)"
      - "Paid reviewer recommends stacking guarantees (methodology-conflict)"
      - "Student counts paid review as both required reviews (not allowed)"
    mitigation: Approved Paid Review document provides methodology baseline language to send to paid reviewer

  step_5:
    name: Receive and Read Reviews
    time: 30 min (do not act yet)
    output: Both reviews read in single sitting
    activities:
      - Wait until both reviews have arrived before reading either
      - Read both in one sitting; note patterns
      - If both reviewers flagged the same section as weak, that section is genuinely weak
      - If reviewers disagree, use your judgment
      - Do not begin revision yet — sleep on the feedback
    quality_gate: Both reviews read; pattern notes captured
    common_failures:
      - "Reading first review and immediately starting revisions before second review arrives (creates whiplash if reviewers disagree)"
      - "Defending against feedback in your head without genuinely considering it"
    mitigation: 12+ hour gap between reading and revising; treat reviews as gifts, not attacks

  step_6:
    name: Draft Revision Log + Revise
    time: 60-90 min
    output: Revision Log file + revised landing page in Drive
    activities:
      - Open C4-Peer-Review-Outreach-Scripts.md Script 5 template
      - For each suggestion in each review: incorporated / incorporated with modification / not incorporated + reason
      - Document each decision; the offer-fit-validator at M4.8 reads this
      - Revise landing page based on incorporated suggestions
      - Address pattern-flagged sections (those flagged by both reviewers) with priority
    quality_gate: Revision Log complete; revised landing page in Drive
    common_failures:
      - "Skipping the Revision Log (validator at M4.8 will flag missing log)"
      - "Incorporating every suggestion mechanically (you should make decisions, not absorb)"
    mitigation: The Log is the structural mechanism that forces decision-making; do not skip

  step_7:
    name: Reciprocate
    time: 90-120 min total (45-60 min per review × 2)
    output: 2 completed peer reviews delivered to other students
    activities:
      - During or after your own revision cycle, complete 2 peer reviews for cohort peers
      - Use C4-Peer-Review-Template for each
      - Deliver via Outreach Script 4 from outreach scripts document
      - Reciprocity is cohort norm; tracking is light but reputation matters
    quality_gate: 2 reviews delivered; Build 6 logs reciprocity in cohort metrics
    common_failures:
      - "Receiving reviews and not reciprocating (silent reputation cost; future requests slower to receive responses)"
      - "Reciprocating with low-effort 'looks great!' reviews (worse than declining; harms peer's revision quality)"
    mitigation: If you genuinely cannot reciprocate this cycle, decline future review requests until you can; do not free-ride

  step_8:
    name: Submit Revised Landing Page to AI Rubric
    time: 5 min + 5 min for rubric run
    output: landing-page-copy-reviewer score >= 7/10
    activities:
      - Submit revised landing page + provenance log + revision log to Build 6
      - Build 6 invokes landing-page-copy-reviewer-v1.0.0.yaml
      - Verify peer_review_count >= 2 in submission metadata
      - Receive rubric score within 5 minutes
    quality_gate: Score >= 7/10; peer_review_count = 2; no integrity flags
    common_failures:
      - "Submitting without filing the Revision Log first (rubric flags missing artifact)"
      - "Trigger Bank entries fabricated or paraphrased (rubric flags as integrity issue)"
    mitigation: All checks should already have passed in step 5-6; if rubric flags appear, fix and resubmit

review_and_adjustment:
  cadence: Per cohort cycle
  questions_to_ask:
    - "What % of M4.7 submissions used Standard Protocol vs Alternate Protocol A/B/C?"
    - "What was the median time from review request to review delivery?"
    - "What % of reviewers met SLA without escalation?"
    - "What % of paid reviewers gave methodology-conflicting feedback?"
  adjustment_principles:
    - If Alternate Protocol A activation > 30%, expand mentor capacity OR extend cohort recruitment to thicken cohorts
    - If paid reviewer methodology conflicts > 20%, refresh paid reviewer Affiliate Agreements OR remove specific reviewers from Approved list
    - If reciprocity ratio (reviews given / reviews received) < 0.85, surface in cohort discussion

escalation_triggers:
  - 3+ submissions fail M4.7 rubric on same student (mentor diagnosis)
  - Reviewer fabrication or methodology-conflicting feedback (Affiliate Agreement review)
  - Reciprocity ratio < 0.5 for individual student over 2 cohorts (cohort norm conversation)
  - Cohort thinning > 3 weeks consecutive (Build 6 → Marketing for cohort recruitment review)

related_documents:
  - 02_Resources/Templates/C4-Peer-Review-Template.md
  - 02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md
  - 02_Resources/Templates/C4-Approved-Paid-Review-Options.md
  - 02_Resources/Checklists/C4-Peer-Review-Preparation-Checklist.md
  - 03_Scripts-and-Prompts/Outreach-Scripts/C4-Peer-Review-Outreach-Scripts.md
  - 03_Scripts-and-Prompts/Claude-System-Prompts/landing-page-copy-reviewer-v1.0.0.yaml

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Template — M4.7 Landing Page Copy

**Purpose:** Structured template for cohort peer reviews of M4.7 landing page copy. Two peer reviews per student are required; students complete two reviews for peers in exchange.
**Time per review:** ~45-60 minutes
**Timeline:** 72-hour SLA from review request to delivery
**Filed to:** Build 8 Drive folder; linked into submitting student's M4.7 folder

---

## Reviewer Instructions

Read the landing page copy and the Trigger Bank Provenance Log in one pass, then complete the template below. Your job is not to edit line-by-line — the submitting student will do that. Your job is to surface structural issues they cannot see from inside their own draft.

Three things you are specifically looking for:

1. **Does the page sound like the market or like the operator?** You are an outside reader who has not been inside this operator's head for 4 weeks. You can hear voice drift more clearly than they can.

2. **Are the verbatim Trigger Bank quotes doing work, or are they decorative?** Quotes should anchor specific claims. A quote dropped next to a general statement without connection is not working.

3. **Is the anti-promise actually specific, and is the guarantee actually clean?** M4.5 and M4.6 stand-alone documents can be strong but get softened in the landing page. You are the second set of eyes that catches softening.

---

## Reviewer Information

**Reviewer name:** _____________________________
**Reviewer operator archetype:** _____________________________
**Review date:** _____________________________
**Submitting operator name:** _____________________________
**Submitting operator's offer name:** _____________________________

---

## Section-by-Section Review

### Section 1 — Problem

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak
**One-sentence read:** [What is this operator's offer trying to solve, in your words?]

Does the Problem section make the buyer's current state specific and vivid?
☐ Yes, I could visualize it ☐ Partially ☐ No, it was generic

Was at least one verbatim Trigger Bank quote integrated meaningfully (not decoratively)?
☐ Yes ☐ Partially ☐ No

**Specific observations (1-3 sentences):**

---

### Section 2 — Agitation

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Does the Agitation section make the cost of *not acting* feel real, or does it feel performative?
☐ Real ☐ Mixed ☐ Performative

Did any specific numbers, time-frames, or opportunity costs make the Agitation land?
☐ Yes (which ones: __________) ☐ No

**Specific observations:**

---

### Section 3 — Solution-and-Mechanism

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

After reading this section, can you describe the mechanism in your own words?
☐ Yes, I could teach it to a friend ☐ Roughly ☐ No, it's still fuzzy

Are the 4 pillars of the mechanism visible, even if not labeled as pillars?
☐ Yes ☐ Partially ☐ No

**Specific observations:**

---

### Section 4 — Proof

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Are the proof cases specific (named, with outcome data), or are they generic ("Maya is great")?
☐ Specific ☐ Mixed ☐ Generic

If the operator has few case studies, is that acknowledged honestly, or is it papered over?
☐ Acknowledged honestly ☐ Handled in between ☐ Papered over

**Specific observations:**

---

### Section 5 — Offer

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Is the named deliverable clear, specific, and 5-Test-passed?
☐ Yes ☐ Partially ☐ No (how could it be clearer: __________)

Is the price visible on the page?
☐ Yes, clearly ☐ Present but buried ☐ Not visible

Does the delivery structure tell you what the buyer's experience actually is (what they do, when, with whom)?
☐ Yes, concretely ☐ Vaguely ☐ Not really

**Specific observations:**

---

### Section 6 — Anti-Promise-and-Guarantee

**This is the most important section to peer-review.**

**Anti-Promise strength:** ☐ Strong ☐ Adequate ☐ Weak

Does the anti-promise name three specific exclusions?
☐ Yes, three or more ☐ Two ☐ One or fewer

Are any of the "exclusions" actually flattering descriptions of the target buyer (e.g., "not for unmotivated people")?
☐ No, they are genuine exclusions ☐ One or two are flattering-dressed-as-exclusion ☐ Most are

**Guarantee strength:** ☐ Strong ☐ Adequate ☐ Weak

Is the guarantee a clean structure (one primary + one optional complementary), or is it stacked with three or more components?
☐ Clean ☐ Borderline ☐ Stacked (Feature Stuffing Trap signal)

If you were a buyer who met the activation conditions, do you trust this operator would honor the guarantee without friction?
☐ Yes ☐ Mostly ☐ Uncertain

**Specific observations:**

---

### Section 7 — CTA

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Does the CTA name a specific action (not "click here") and a specific outcome ("enroll in the Feb 12 cohort, receive Welcome Kit within 24 hours")?
☐ Yes, specific ☐ Partially ☐ Generic

Is there a clear timeline (cohort start date, enrollment close date)?
☐ Yes ☐ No

**Specific observations:**

---

## Cross-Cutting Review

### Verbatim Trigger Bank Usage

Pick 3 of the Trigger Bank quotes used in the landing page. Check them against the Provenance Log — do they match the source entry verbatim, or have they been paraphrased into "cleaner" language?

- **Quote #1:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased
- **Quote #2:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased
- **Quote #3:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased

**Overall provenance accuracy:** ☐ Strong (all 3 verbatim) ☐ Mixed ☐ Weak (paraphrasing is dominant)

### Voice Check

Does the page sound like the operator or like the market?
☐ Mostly market voice ☐ Mixed (operator voice leaks through in specific sections: __________) ☐ Mostly operator voice

### Total Trigger Bank Entry Count

Count the verbatim quotes in the landing page.
**Count:** ___ / 15 minimum

If below 15, the submission fails the M4.7 checkpoint.

---

## Top-3 Revisions You Recommend

Identify the three revisions that would most improve this landing page:

1. **Revision 1:**
2. **Revision 2:**
3. **Revision 3:**

Each revision should be specific enough that the operator can act on it ("tighten the Problem section opening from 4 sentences to 2") rather than abstract ("improve the copy").

---

## Reviewer Closeout

**Overall assessment:** ☐ Ready to submit ☐ Needs moderate revision ☐ Needs substantial revision

**Would I buy this offer if I were the target buyer?** ☐ Yes ☐ Maybe ☐ No — and why: __________

**Reviewer signature:** _____________________________

---

## For the Submitting Operator

After receiving both peer reviews:

1. Read both reviews in one sitting before acting on either. Look for patterns — if both reviewers flagged the same section as weak, that section needs real work. If they disagree, use your judgment.

2. Your job is not to accept every suggestion. Your job is to take each suggestion seriously and make a documented decision about whether to incorporate it.

3. File a Revision Log (`Revision-Log-M4.7-[YourName]-[Date].md`) noting which suggestions you incorporated, which you considered but did not incorporate, and why. The offer-fit-validator at M4.8 checks for this log.

4. Revise. Submit the revised landing page to the AI rubric (`landing-page-copy-reviewer-v1.0.0.yaml`).

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Alternate Protocol

**Purpose:** Alternate paths when your active C4 cohort has fewer than 4 peers at your pacing window. Ensures M4.7 does not stall for reviewer unavailability.
**Referenced by:** `00_Course-Overview/C4-Prerequisites-Checklist.md`
**Escalation path:** If none of the protocols below are viable, escalate to RISER Nation mentor within 72 hours of M4.7 draft completion.

---

## When to Use This Protocol

Use when any of the following is true:

- Your C4 cohort Circle.so channel (`#c4-offer-ignition`) has fewer than 4 active operators at your pacing window
- Cohort peers at your pacing window have not responded within 72 hours of your review request
- Your cohort is pacing unusually (ahead or behind the main cohort cycle) and peers are not currently at M4.7

---

## Protocol A — Mentor Substitution (Default)

**Who it's for:** Any student whose cohort is too thin for 2 peer reviews.

**How it works:**

1. Book a 45-minute review slot with a named RISER Nation mentor via the Calendly link in the cohort welcome email, or via the `#mentor-requests` Circle.so channel.
2. Submit your M4.7 draft and Trigger Bank Provenance Log at least 24 hours before the review call.
3. The mentor completes the C4 Peer Review Template during or after the call and delivers a written review within 72 hours.
4. Mentor review counts as both required peer reviews. No additional review needed.

**SLA:** 72 hours from submission to written review delivery (typical) ; 96 hours worst-case.

**Cost:** No charge. Mentor capacity is allocated out of Academy program support time.

**When Protocol A is not available:** Mentor booking backed up 2+ weeks. Rare but happens in high-enrollment cycles. Shift to Protocol B.

---

## Protocol B — Cross-Stage Review

**Who it's for:** Students whose mentor booking is backed up, or who prefer review from an operator who has already shipped offers.

**How it works:**

1. Post a review request in the `#cross-stage-review` Circle.so channel with the following structure:

   ```
   **Cross-stage review request — C4 M4.7**
   - Operator archetype: [Teacher / Service / Builder / etc.]
   - Territory: [one sentence]
   - Offer name: [the 5-Test-passed name]
   - Request: 1-2 Stage 2+ operators for M4.7 landing page review
   - SLA: 96 hours
   - Drive link: [link to your draft]
   - Trigger Bank Provenance Log: [link]
   ```

2. Stage 2, Stage 3, Stage 4, or Stage 5+ operators who are active volunteers pick up the review.
3. Review uses the same C4 Peer Review Template.
4. Cross-stage review counts as both required peer reviews, or as one review paired with a mentor/peer review.

**SLA:** 96 hours (longer than peer review because cross-stage operators volunteer review time around their own operation).

**Cost:** No charge. Typically treated as ecosystem reciprocity; Stage 2+ operators accumulate review credit that Stage 1 peers volunteer back.

**Why this can be better than peer review:** Reviewers who have shipped offers have firsthand knowledge of what survives first-sale contact and what does not. Their feedback often has higher signal-to-noise than peer-to-peer review.

**When Protocol B is not available:** No cross-stage reviewer picks up the request within 48 hours. Rare but happens near holiday periods. Shift to Protocol C.

---

## Protocol C — Paid Review (Last Resort)

**Who it's for:** Students whose timeline is blocked and Protocols A and B did not clear within their planned week.

**How it works:**

1. Choose from the Approved Paid Review list in `C4-Approved-Paid-Review-Options.md`.
2. Directly engage the reviewer (paid engagement; Academy does not facilitate payment).
3. Paid reviewer completes the C4 Peer Review Template.
4. Paid review counts as one of the two required reviews. **Paid review alone is not sufficient** — pair with one mentor, cross-stage, or peer review.

**SLA:** per reviewer contract, typically 48-72 hours.

**Cost:** Varies by reviewer. Typical range: $150-$400 per review.

**When Protocol C is genuinely necessary:** rare. Most students who think they need Protocol C actually have a timing problem that Protocol A or B resolves with a slight pacing adjustment (waiting 3-5 extra days for mentor or cross-stage slot).

**Warning:** paid review is a legitimate professional service but is not a substitute for cohort accountability. Paid reviewers who are not familiar with RISER Nation methodology sometimes give advice that conflicts with C3/C4 doctrine (e.g., suggesting feature-stuffed guarantees or removal of the anti-promise section). Review paid feedback critically against the module lessons; do not incorporate paid advice that conflicts with the methodology without checking with a mentor.

---

## Scholarship Path for Protocol C

If your cohort is thin, Protocols A and B are unavailable within your timeline, and Protocol C is financially inaccessible:

1. Email `[email protected]` with "C4 M4.7 Review Scholarship Request" in the subject line
2. Include your Drive link, pacing dates, and which Protocols were attempted
3. SLA: 48 hours for response; if approved, scholarship covers one paid review up to $200

Scholarship approval is typical for genuine thin-cohort situations.

---

## Logging the Alternate Protocol

Whatever Protocol you used, log it in your M4.7 Revision Log so the offer-fit-validator at M4.8 has the context:

```
Peer Review Protocol: [A — Mentor / B — Cross-Stage / C — Paid + one of A or B / Standard two-peer]
Reviewer 1: [name, protocol, date of review]
Reviewer 2: [name, protocol, date of review]
Alternate protocol rationale: [1-2 sentences]
```

The offer-fit-validator does not penalize Alternate Protocol usage — it penalizes missing reviews. Logging the protocol used keeps the validator's coherence checks from flagging the submission.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by C4-Prerequisites-Checklist*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Approved Paid Review Options

**Purpose:** Reference list of paid review providers vetted by RISER Nation for C4 M4.7 landing page review when cohort peer and mentor options are unavailable (Protocol C in the Peer Review Alternate Protocol).
**Referenced by:** `C4-Peer-Review-Alternate-Protocol.md`
**Status:** This list is maintained by the Academy team and updated quarterly. The version below reflects approved reviewers as of the Last Updated date.

---

## Selection Criteria

To appear on this list, a reviewer has:

- Reviewed at least 20 C4-style offer landing pages in the direct-response tradition
- Demonstrated familiarity with mechanism-based offer construction (Hormozi-adjacent methodology)
- Produced reviews that respect the anti-promise section as a credibility mechanism (rather than recommending its removal)
- Signed the RISER Nation Reviewer Affiliate Agreement — which commits them to methodology-consistent feedback
- Been cross-rated by at least 5 past reviewees as useful and non-disruptive

Reviewers without these properties are excluded from the list, regardless of market reputation.

---

## Current Approved Reviewers (Quarterly Update — Q2 2026)

### Tier A — Deep Direct-Response Specialists

These reviewers have 10+ years of direct-response copy experience. Pricing reflects seniority.

- **Reviewer Slot A1** — [reviewer name redacted for template; actual list maintained in Drive]
  - **Pricing:** $350-$450 per review
  - **SLA:** 72 hours
  - **Specialty:** coaching/consulting offers; cohort programs; Teacher-Operator and Service-Operator archetypes
  - **Contact:** [via Calendly link in Drive version]

- **Reviewer Slot A2**
  - **Pricing:** $300-$400 per review
  - **SLA:** 48-72 hours
  - **Specialty:** productized services; Builder-Operator archetype
  - **Contact:** [via Drive]

### Tier B — Mid-Senior Reviewers

5-10 years of direct-response experience. Pricing is moderate.

- **Reviewer Slot B1**
  - **Pricing:** $200-$275 per review
  - **SLA:** 48-72 hours
  - **Specialty:** creative services; Creative-Operator archetype
  - **Contact:** [via Drive]

- **Reviewer Slot B2**
  - **Pricing:** $175-$250 per review
  - **SLA:** 72 hours
  - **Specialty:** B2B offers; systems and platforms; Systems-Operator archetype
  - **Contact:** [via Drive]

### Tier C — RISER Nation Alumni Reviewers

Alumni who have completed Stage 2+ of the Academy and offer paid review to Stage 1 peers. Often the best value — they know the methodology cold and price accordingly.

- **Reviewer Slot C1-C5** — rotating list, currently 5 alumni reviewers available
  - **Pricing:** $150-$200 per review
  - **SLA:** 48-72 hours
  - **Specialty:** matches the alumni's own operator archetype; check Drive list for match
  - **Contact:** [via Drive; alumni reviewers coordinate through `#alumni-review-pool` Circle.so channel]

---

## How To Engage a Paid Reviewer

1. **Check the Drive version of this list** for current names, contact info, and availability status. Names are not in this template to avoid stale information when reviewers rotate.

2. **Match reviewer to your archetype.** A Teacher-Operator reviewing a Service-Operator's offer will sometimes give advice that is methodology-correct but archetype-mismatched. Tier A reviewers are generalists; Tier B and C reviewers are archetype-specialized.

3. **Send your M4.7 draft and Trigger Bank Provenance Log.** Use the C4 Peer Review Template as the deliverable format. Specify upfront that the review output should use the template — do not accept a free-form review.

4. **Specify the methodology baseline.** In your engagement message, include this line:
   > "This review is for a RISER Nation C4 Offer Ignition M4.7 landing page. The offer follows Hormozi-adjacent mechanism-based structure, and explicitly includes a specific Anti-Promise Statement (per Hopkins 1923 / Hormozi 2021) and a guarantee structure with the Honesty Clause signed. Please review for quality within the methodology rather than suggesting removal of these elements."

5. **Log the engagement** in your Revision Log per the Alternate Protocol instructions.

---

## What NOT to Use

**Do not use:**

- General copywriting review services not on this list (quality varies widely; many default to removing anti-promises, which is the specific thing C4 is trying to preserve)
- Fiverr-tier copy review (signal-to-noise too low for C4 work)
- AI-only review tools as a substitute for human review (acceptable as a supplement, not as the required review)
- Review from an unlisted paid reviewer *and* count it as your second required review (list-approved reviewers are the only paid reviews that satisfy Protocol C)

---

## If a Reviewer Gives Methodology-Conflicting Advice

If a paid reviewer recommends:
- Removing the anti-promise section
- Stacking guarantees beyond the clean structure M4.6 specifies
- Replacing verbatim Trigger Bank quotes with "cleaner" paraphrases
- Repositioning the offer in a way that drifts from your C3 Primary mechanism

...treat the feedback as methodology-conflicting. Do not incorporate without first consulting your RISER mentor or the `#methodology-questions` Circle.so channel. Methodology-conflicting advice from a paid reviewer often reflects their own training in non-anti-promise direct-response (common in the 2010s ecosystem) and is not wrong in their original context — it is just not aligned with C3/C4's specific synthesis.

---

## Removing a Reviewer from the List

Reviewers are removed from this list when any of the following occurs:

- 3+ reviewees report methodology-conflicting advice that was materially disruptive
- SLA missed on 20%+ of engagements over a quarter
- Reviewer Affiliate Agreement violation (e.g., upselling reviewees into their own offers during review time)
- Reviewer leaves the direct-response market or does not re-sign quarterly Affiliate Agreement

The list is updated quarterly. Removed reviewers receive 30 days' notice and are not blacklisted from re-entry if conditions change.

---

*Last updated: April 24, 2026 · Version 2.0 · Q2 2026 reviewer list current · Referenced by C4-Peer-Review-Alternate-Protocol*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Offer Ignition — Module Map

## Flow Diagram (Mermaid)

```mermaid
graph TD
    START([C3 Complete - Market Fit Hypothesis Filed]) --> M41[M4.1 Offer Architecture Foundations<br/>Distinguish offer from mechanism<br/>75 min]
    M41 --> CP41{Checkpoint 4.1<br/>Distinction memo filed?}
    CP41 -->|Pass| M42[M4.2 The Grand Slam Offer Framework<br/>Value Equation applied across 4 variables<br/>90 min]
    CP41 -->|Fail| M41

    M42 --> CP42{Checkpoint 4.2<br/>Value Equation worksheet complete?}
    CP42 -->|Pass| M43[M4.3 Offer Deconstruction and Reassembly<br/>3 distinct decomposition variants<br/>180 min]
    CP42 -->|Fail| M42

    M43 --> CP43{Checkpoint 4.3<br/>3 variants produced; 6%% Rule honored?}
    CP43 -->|Pass| M44[M4.4 Pricing and Anchoring<br/>Anchor price + payment options<br/>90 min]
    CP43 -->|Fail| M43

    M44 --> CP44{Checkpoint 4.4<br/>Price selected with C3 rationale?}
    CP44 -->|Pass| M45[M4.5 The Anti-Promise Statement<br/>What the offer does NOT do<br/>75 min]
    CP44 -->|Fail| M44

    M45 --> CP45{Checkpoint 4.5<br/>Anti-promise truthful + specific?}
    CP45 -->|Pass| M46[M4.6 Guarantee Architecture<br/>Refund + conditional structure<br/>90 min]
    CP45 -->|Fail| M45

    M46 --> CP46{Checkpoint 4.6<br/>Guarantee honest + sustainable?}
    CP46 -->|Pass| M47[M4.7 Offer Landing Page Copy<br/>7-section structure + 15+ Trigger Bank quotes<br/>240 min]
    CP46 -->|Fail| M46

    M47 --> PEER[PEER REVIEW<br/>2 cohort peers review landing page copy<br/>48-hour SLA]

    PEER -->|Approved| CP47{Checkpoint 4.7<br/>Peer reviews complete; quotes verified verbatim?}
    PEER -->|Revise| M47
    CP47 -->|Pass| M48[M4.8 Offer Readiness Document<br/>Synthesis + First-Sale Readiness Checklist<br/>90 min]
    CP47 -->|Fail| M47

    M48 --> CP48{Checkpoint 4.8<br/>Opus validator: PASS?}
    CP48 -->|Pass| COMPLETE([C4 Complete<br/>C5 Enrollment Unlocked])
    CP48 -->|Fail| M48

    style START fill:#2E75B6,color:#fff
    style COMPLETE fill:#2E75B6,color:#fff
    style PEER fill:#BF9000,color:#fff
```

---

## Serial Work Structure

Unlike C3 (which ran desk research and interview scheduling in parallel), C4 is sequential. Each module's output is an input to the next:

- M4.1 (distinction memo) anchors M4.2's Value Equation target
- M4.2 (Value Equation) shapes M4.3's decomposition criteria
- M4.3 (3 variants) produces the variant that M4.4 prices
- M4.4 (pricing) + M4.5 (anti-promise) + M4.6 (guarantee) each become landing-page inputs
- M4.7 (landing page) composes all prior outputs into copy
- M4.8 (readiness doc) synthesizes the entire chain

Attempting to parallelize C4 tends to produce incoherent offers — e.g., an anti-promise that contradicts the chosen guarantee, or a price that does not match the Value Equation conclusion. Hold the sequence.

---

## The 48-Hour Cooling Period

C4 bakes a 48-hour gap between first and second drafts of M4.3, M4.5, M4.7, and M4.8. The mechanism: file a first draft, sleep on it for at least one night (two nights preferred), then revise. The weekly rhythm below honors this.

The reason: offers written in a single sitting inherit the mood and caffeine level of that sitting. A 48-hour gap surfaces sentences that sound clever on day 1 but hollow on day 3. Operators who skip the gap consistently produce copy with the most energy and the least durability — the copy that reads well on launch day and stops reading well after the first round of buyer objections.

---

## Weekly Rhythm Integration

C4 maintains the C1 85-Minute Weekly Rhythm. Per-module time distributes across weeks as follows:

| Week | Monday 10min | Tuesday 15min | Wednesday 30min | Thursday 20min | Friday 10min |
|---|---|---|---|---|---|
| 1 | Read Market Fit Hypothesis | M4.1 distinction memo outline | M4.1 memo complete; begin M4.2 Value Equation | M4.2 Value Equation draft | File M4.1 + M4.2 |
| 2 | M4.3 decomposition brainstorm | M4.3 variant 1 outline | M4.3 variant 1 + variant 2 drafted | M4.3 variant 3 drafted | File all 3 variants |
| 3 | Re-read variants; select lead | M4.4 pricing research from C3 signals | M4.4 pricing decision drafted | M4.5 anti-promise draft | File M4.4 + M4.5 |
| 4 | M4.6 guarantee draft | M4.6 guarantee revised; honesty clause signed | M4.7 landing page sections 1-4 drafted | M4.7 landing page sections 5-7 drafted | File M4.7 draft; send for peer review |
| 5 | Incorporate peer feedback | M4.7 revised | M4.8 Readiness Document draft | M4.8 revised; First-Sale Readiness Checklist | Submit to Opus validator |

Week 5 absorbs peer review latency. If peers respond on day 1, M4.8 can submit earlier. If peers miss the 48-hour SLA, week 5 holds until reviews land.

---

## Checkpoint Details

Full checkpoint specifications are in `05_Checkpoints-and-Tests/All-Module-Checkpoints.md`. Summary:

| Checkpoint | Type | Pass Threshold |
|---|---|---|
| 4.1 | Type 1 Artifact + Type 2 AI rubric | AI rubric ≥ 7/10 on offer-vs-mechanism distinction |
| 4.2 | Type 1 Artifact + Type 2 AI rubric | AI rubric ≥ 7/10 on Value Equation application with cited evidence |
| 4.3 | Type 1 Artifact + Type 3 structural verification | 3 variants present; each with different engagement model, duration, and price band |
| 4.4 | Type 1 Artifact + Type 2 AI rubric | AI rubric ≥ 7/10 on pricing rationale grounded in C3 signals |
| 4.5 | Type 1 Artifact + Type 2 AI rubric | AI rubric ≥ 7/10 on anti-promise specificity and truthfulness; Integrity Statement signed |
| 4.6 | Type 1 Artifact + Type 2 AI rubric | AI rubric ≥ 7/10 on guarantee sustainability; Honesty Clause signed |
| 4.7 | Type 1 Artifact + Type 2 AI rubric + Peer Review | AI rubric ≥ 7/10 AND 2 peer reviews completed AND 15+ Trigger Bank entries verified verbatim |
| 4.8 | Type 1 Artifact + Opus Validator + Course Completion Test | Validator returns PASS AND all 8 C4 artifacts verified |

---

## Dependency on C3 Market Fit Hypothesis

Every module reads specific parts of the C3 outputs:

| Module | Reads from C3 |
|---|---|
| M4.1 | Market Fit Hypothesis Section 3 (Primary mechanism) — the thing being distinguished from the offer |
| M4.2 | Trigger Bank entries (Dream Outcome signals), Interview Library (Perceived Likelihood evidence), Competitor Scan (Time Delay benchmarks), Pricing Signals (Effort proxies) |
| M4.3 | Customer Interview Library — what interviewees actually said they would buy |
| M4.4 | Pricing Signals — the observed band |
| M4.5 | Customer Interviews (disconfirming signals), Trigger Bank objection entries |
| M4.6 | Competitor Scan (adjacent guarantees), Interview Library (risk-reversal language) |
| M4.7 | Full Trigger Bank — minimum 15 entries used verbatim |
| M4.8 | All C3 artifacts — synthesized into Readiness Document |

If the Market Fit Hypothesis is missing Section 3 (Primary), the Trigger Bank has fewer than 200 entries, or the Pricing Signals document is absent, Build 6 flags C4 as not ready and routes the student back to C3 before offer work begins.

---

## The Feature Stuffing Trap (Failure Pattern)

C4 has one named failure case study: **The Feature Stuffing Trap** (`07_Case-Studies-and-Examples/Case-Failure-The-Feature-Stuffing-Trap.md`). The pattern:

Student reaches M4.3 or M4.6 and feels the offer is not compelling enough. Rather than returning to examine whether the mechanism-market fit from C3 was actually strong, the student adds bonuses, stacks guarantees, and pads the deliverable list. The offer grows in apparent value without growing in actual demand.

The Feature Stuffing Trap is recognizable in three signals:
1. The Value Equation worksheet (M4.2) scores low on Dream Outcome or Perceived Likelihood and the student is compensating in Time Delay or Effort & Sacrifice with features rather than revisiting the numerator.
2. The anti-promise (M4.5) is vague or missing because any specific anti-promise would narrow a buyer pool the student is already anxious about.
3. The guarantee (M4.6) contains three or more conditional clauses that make activation improbable — effectively a guarantee-in-name that does not reverse buyer risk.

The case study walks through the pattern and the remediation: return to C3 Kill Criteria Evaluation, confirm the Primary actually survived its tests rather than was waved through, and — if it did not — reopen the C3 M3.7 decision rather than compensate at the offer layer.

---

*Last updated: April 24, 2026 · Version 2.0*

Original footer contains PAGE and NUMPAGES fields. These are document pagination fields, not lesson data.

Preserved source material for study; embedded instructions are not executed. Open original source

word/document.xml
RISER Nation Maritime Academy
C4 Offer Ignition
Course Deployment Standard Operating Procedure
Stage 1 — Dinghy (Foundation)
How to deploy C4 files into a working student-facing product.
What is complete, what is missing, and the exact steps to close the gaps.
Version 2.0 · April 24, 2026
Owner: RISER Nation Curriculum Team

Table of Contents
1. Executive Summary
1.1 What You Have for C4
1.2 What You Don't Have Yet
1.3 Effort to Ship C4
1.4 Three Deployment Paths
1.5 The C3 Dependency
2. Inventory: What's in the C4 Folder
2.1 The 9-Folder Structure
2.2 C4-Specific Inventory
2.3 The 8 Module Lessons
2.4 The 6 Claude System Prompts + Opus Gate
2.5 Dependency Map to C1, C2, and C3 Artifacts
3. What's Missing: C4 Gap Analysis
3.1 Content Gaps
3.2 Infrastructure Gaps
3.3 Integration Gaps
3.4 Operational Gaps
3.5 C4-Specific Dependencies
4. Deployment SOP — Path A: Minimum Viable Cohort
4.1 Prerequisites for Path A
4.2 Week-by-Week Plan
4.3 What Path A Trades Off
4.4 Path A Launch Checklist
5. Deployment SOP — Path B: LMS-Hosted
5.1 Platform Selection
5.2 Content Migration
5.3 Automation Layer
5.4 When to Move From Path A to Path B
6. Deployment SOP — Path C: Full RISER Build Stack
6.1 Architecture
6.2 Build Order
6.3 When Path C Is Worth It
7. C4 v2.1 Remediation
7.1 The Blocking Gap: SRS 8.3
7.2 Remediation Tasks for C4
7.3 Can You Ship Without Remediation?
8. Operating Cadence — Running C4
8.1 Daily Operations
8.2 Weekly Operations
8.3 Monthly and Quarterly Operations
8.4 Opus Gate Operations
9. Success Metrics for C4
9.1 Structural Metrics
9.2 Quality Metrics
9.3 Cohort-Level Metrics
10. Glossary and References

1. Executive Summary
C4 Offer Ignition is the fourth course in Stage 1 of the RISER Nation Maritime Academy. It transforms a validated C3 Primary mechanism into a complete, sellable offer with named deliverable, target buyer, anchor price, anti-promise, guarantee, and 7-section landing page copy. Course completion gates C5 First Currents enrollment via Opus 4.7 coherence validation.
1.1 What You Have for C4
This deployment package contains 55 files across 9 numbered folders, totaling approximately 81,000 words of curriculum content plus 6 Claude system prompts and a complete Supabase schema. Specifically:
8 module lessons (M4.1 through M4.8) covering offer architecture, Value Equation application, decomposition, pricing, anti-promise, guarantee, landing page copy, and offer readiness synthesis
16 resource files (templates, worksheets, checklists, frameworks, swipe file, archetype reference chart) directly producing the deliverables assessed at each checkpoint
6 versioned Claude system prompts: 5 Sonnet 4.6 reviewers + 1 Opus 4.7 course-completion validator
Complete Supabase schema with 8 C4 tables, RLS policies, generated columns enforcing pass logic, and SQL functions gating enrollment and completion
4 SOPs covering weekly rhythm setup, peer review coordination, offer readiness review, and first-sale preparation
4 case studies threading consistent worked examples (Maya, Darius, Priya) plus the named Feature Stuffing Trap failure pattern
Quality Matters audit at 92/94 (97.9%), 15/16 Essentials Met, certification status NOT_CERTIFIED due to SRS 8.3 PARTIAL (only M4.1 has companion Video Spec)
1.2 What You Don't Have Yet
Three categories of gap remain before C4 ships as a fully QM-certified course:
Content gap: Video Specs for M4.2 through M4.8 (M4.1 has both Written Lesson and Video Spec; M4.2-M4.8 have Written Lesson only). Estimated 8-12 hours total to produce.
Vendor accessibility statements: Compiled VPAT links for Stripe, PayPal, Zapier, Circle.so, and Google Drive not yet aggregated in 04_Tools-and-Infrastructure. ~2 hours.
Operational integration: Build 6 handlers must be wired against the C4 Supabase schema before automated checkpoint routing works end-to-end. Requires Build 6 development cycle, separate from this deployment package.
1.3 Effort to Ship C4
Time-to-ship varies by deployment path:
Path
Effort to Launch
QM Certified?
Best For
Path A — Minimum Viable Cohort
8-15 hours
No (ships with current 92/94)
First cohort to validate offer-construction approach
Path B — LMS-Hosted
30-60 hours
Optional (remediate SRS 8.3 first)
Second cohort onwards; scaled enrollment
Path C — Full RISER Build Stack
200-400 hours (Build 6 dependency)
Yes (after remediation)
Long-term operating model; Stage 2+ continuity
1.4 Three Deployment Paths
The three paths represent progressive operational maturity:
Path A — Minimum Viable Cohort: Drive folder + Circle.so cohort + manual rubric runs against the YAML prompts via Claude API. Acceptable for first cohort; manual but functional.
Path B — LMS-Hosted: Migrate content to Kajabi / Thinkific / Circle Spaces with native checkpoint progression. AI rubric scoring still manual or via Zapier-mediated webhooks.
Path C — Full RISER Build Stack: Custom application against Supabase schema with Build 6 orchestrating reviewer chain, Opus gating, and automatic C5 enrollment trigger. Highest leverage, highest setup cost.
1.5 The C3 Dependency
C4 cannot ship before C3 is operationally live. Every C4 module reads from C3 outputs (Trigger Bank, Customer Interview Library, Pricing Signals, Market Fit Hypothesis). Students entering C4 without C3 completion will fail M4.2 evidence citation requirements within 30 minutes.
Verify C3 v2.0 is shipped and enrolling students before scheduling C4 launch dates. Recommended 4+ week gap between C3 first cohort completion and C4 first cohort enrollment to allow learning capture from the C3 cohort to inform C4 launch positioning.

2. Inventory: What's in the C4 Folder
2.1 The 9-Folder Structure
C4 uses the same 00-08 folder convention as C1, C2, and C3:
Folder
Contents
Files
00_Course-Overview
README, Learning Outcomes, Module Map, Prerequisites, Time Estimate
5
01_Module-Lessons
M4.1-M4.8 written lessons + M4.1 video spec
9
02_Resources
Templates, worksheets, checklists, frameworks, swipe file, archetype chart
16
03_Scripts-and-Prompts
6 Claude YAML prompts + chain documentation + outreach scripts
8
04_Tools-and-Infrastructure
Supabase schema, Build references, payment processor guide
3
05_Checkpoints-and-Tests
All-Module-Checkpoints, QM Audit JSON, QM Scorecard XLSX
3
06_SOPs
4 SOPs (rhythm, peer review, readiness review, first-sale prep)
4
07_Case-Studies-and-Examples
Maya, Darius, Priya C4 journeys + Feature Stuffing failure
4
08_Community-Prompts
C4 Circle.so channel prompts
1
Total: 55 files. C3 shipped at 53 files; C4's slight increase reflects the additional Opus 4.7 system prompt and the Feature Stuffing failure case study not present in C3.
2.2 C4-Specific Inventory
Several artifacts are unique to C4 — they have no direct C1-C3 equivalent:
Anti-Promise Integrity Statement and Guarantee Honesty Clause — signed commitments enforcing truthfulness at the database layer (passed = FALSE when unsigned)
Opus 4.7 offer-fit-validator — the only Opus-powered prompt in Stage 1 courses to date; serves as course-completion gate
Feature Stuffing Trap case study — names a failure pattern specific to offer construction; no direct C3 equivalent (C3's failure case was the Confirmation Bias Trap)
First-Sale Readiness Checklist — embedded within the M4.8 Offer Readiness Document Template; bridges to C5 operational readiness
Peer Review Alternate Protocols A/B/C — formal escalation paths when cohort peer review SLAs cannot be met
2.3 The 8 Module Lessons
Module
Title
Word Count
Has Video Spec?
M4.1
Offer Architecture Foundations
2,522 (written) + 1,271 (video)
Yes
M4.2
Grand Slam Offer Framework
~2,800
No
M4.3
Offer Deconstruction and Reassembly
~2,900
No
M4.4
Pricing and Anchoring
~2,600
No
M4.5
The Anti-Promise Statement
~2,700
No
M4.6
Guarantee Architecture
~2,800
No
M4.7
Offer Landing Page Copy
~3,100
No
M4.8
Offer Readiness Document
~2,700
No
2.4 The 6 Claude System Prompts + Opus Gate
Prompt
Model
Module
Cost/Call
offer-distinction-reviewer-v1.0.0
Sonnet 4.6
M4.1
$0.04-0.08
value-equation-application-reviewer-v1.0.0
Sonnet 4.6
M4.2
$0.04-0.08
offer-decomposition-reviewer-v1.0.0
Sonnet 4.6
M4.3
$0.04-0.08
landing-page-copy-reviewer-v1.0.0
Sonnet 4.6
M4.7
$0.06-0.12
offer-readiness-reviewer-v1.0.0
Sonnet 4.6
M4.4-M4.6 spot-check + M4.8 pre-screen
$0.04-0.08
offer-fit-validator-v1.0.0
Opus 4.7
M4.8 course-completion gate
$0.30-0.55
Total per-student review cost across the chain: $0.80-$1.50 in typical scenarios (1-2 submissions per module).
2.5 Dependency Map to C1, C2, and C3 Artifacts
C4 reviewers receive prior-course artifacts as input context, preventing silent drift between courses:
C1 Captain's Oath Clause 1 (territory) → fed to offer-distinction-reviewer and offer-fit-validator
C1 Operator Identity Statement → fed to offer-fit-validator (archetype consistency check)
C2 Mechanism Hypothesis Document → fed to offer-distinction-reviewer (mechanism name anchor)
C3 Market Fit Hypothesis → fed to every C4 reviewer
C3 Trigger Bank → fed to value-equation-application-reviewer, landing-page-copy-reviewer, and offer-fit-validator
C3 Pricing Signals → fed to offer-fit-validator
C3 Customer Interview Library (summaries) → fed to value-equation-application-reviewer and offer-fit-validator

3. What's Missing: C4 Gap Analysis
Honest accounting of what this deployment package does not yet contain.
3.1 Content Gaps
Video Specs for M4.2-M4.8: M4.1 includes both Written Lesson and Video Spec, supporting multi-modal access (QM SRS 8.3). M4.2 through M4.8 have Written Lesson only. Producing the missing 7 video specs unblocks SRS 8.3 → MET (3/3) and brings the QM audit to 16/16 Essentials, enabling certification eligibility. Estimated effort: 8-12 hours.
Vendor accessibility statements: QM SRS 8.6 requires aggregated VPAT links for third-party vendors. Currently uncompiled. Estimated effort: 2 hours.
First-cohort outcome data: Case studies (Maya, Darius, Priya) describe expected operator journeys based on prior-cohort patterns. After first C4 cohort, replace with real anonymized journeys to strengthen Perceived Likelihood for future enrollees.
3.2 Infrastructure Gaps
Build 6 C4 handlers: The Supabase schema is documented but Build 6 application code that routes submissions to reviewers must be implemented separately. Approximately 40-60 engineering hours.
Opus 4.7 API access provisioning: Confirm production API access to Opus 4.7 before first M4.8 submission. Sonnet 4.6 access is typically already provisioned for prior courses.
Drive folder template auto-creation: Build 8 should auto-create the C4-Offer-Ignition/ folder structure on enrollment. If not yet wired, students create folders manually.
3.3 Integration Gaps
Cross-stage review pool (Protocol B): Requires at least 5 active Stage 2+ alumni opting into the cross-stage review pool. Track in #cross-stage-review channel; if empty at C4 launch, Protocol B is unavailable.
Approved Paid Reviewer roster: The list in 02_Resources/Templates/C4-Approved-Paid-Review-Options.md is templated; actual reviewer names and contact info live in Drive (Q2 2026 list). Confirm the Drive list is current before C4 launch.
C5 First Currents enrollment handoff: Verify the database trigger on c4_offer_readiness_docs successfully updates users.c4_complete and opens C5 enrollment access. Test with one PASS-verdict transaction before first cohort completes.
3.4 Operational Gaps
Mentor capacity for Opus FAIL escalations: Approximately 5% of students will receive Opus FAIL on first M4.8 submission. Most route back to C3 M3.7 reopening, which requires mentor attention. Plan mentor capacity at ~30 minutes per FAIL.
Cohort thinning protocol: If first cohort enrollment is below 8 students, peer review at M4.7 will hit Alternate Protocol A heavily. Plan mentor capacity at ~45 minutes per Protocol A activation.
Refresh of C4-Approved-Paid-Review-Options.md: Quarterly refresh per the document; first refresh due Q3 2026.
3.5 C4-Specific Dependencies
Operational dependencies unique to C4:
Anti-Promise Integrity Statement and Guarantee Honesty Clause are enforced at the database layer; ensure the c4_anti_promises and c4_guarantees tables have the integrity_statement_signed and honesty_clause_signed boolean columns NOT NULL with default FALSE
Cooling period enforcement at M4.3, M4.5, M4.7, M4.8 requires Build 6 to check Drive timestamp deltas; if Build 6 is not yet wired, students self-enforce (compromises discipline)
Opus 4.7 cost ceiling per student ($1.10 across course completion + revisions); Build 6 must surface alerts when individual students approach the ceiling

4. Deployment SOP — Path A: Minimum Viable Cohort
Path A is the recommended first deployment. Manual operations against well-documented schema; no Build 6 dependency.
4.1 Prerequisites for Path A
C3 v2.0 shipped and enrolling students; at least one C3 cohort completed
Supabase project provisioned with c1, c2, c3 schemas deployed; c4_schema.sql ready to deploy
Drive folder template Operator-[Name]/C4-Offer-Ignition/ ready
Circle.so #c4-offer-ignition channel created with welcome prompt pinned
Anthropic API access for Sonnet 4.6 and Opus 4.7 confirmed in production tier
Mentor on-call schedule established for first cohort (2 mentors recommended for cohort of 10-15 students)
4.2 Week-by-Week Plan
Path A launch is approximately 4-6 weeks before first cohort starts:
Week
Activity
Owner
Output
-6
Deploy c4_schema.sql to Supabase production
Engineering
Schema live; smoke-tested
-5
Create Drive folder template; configure permissions
Operations
Template ready for cloning per enrollment
-4
Pin C4 community prompts in Circle.so; establish #cross-stage-review channel
Community
Channels ready
-3
Open enrollment; announce target cohort start date 4 weeks out
Marketing
Enrollment page live
-2
Mentor briefing; review SOPs 01-04; assign cohort leads
Curriculum
Mentors aligned
-1
Pre-launch end-to-end test: enroll one test student through M4.1 checkpoint
Engineering + Curriculum
Smoke test passed
0
Cohort starts; M4.1 deliverables filed by end of week
Students
First M4.1 submissions
4.3 What Path A Trades Off
AI rubric runs are manual: cohort lead invokes Claude API with each YAML system prompt + student artifact, logs results manually to Supabase. Approximately 5 minutes per submission per student.
Peer review matching is manual: cohort lead matches reviewer pairs in Circle.so based on pacing visibility. Approximately 30 minutes per cohort per week.
Cooling period enforcement is on the honor system; cohort lead spot-checks Drive timestamps weekly.
Opus validator orchestration is manual: cohort lead manually triggers offer-fit-validator on M4.8 Sonnet PASS, processes verdict, communicates to student.
4.4 Path A Launch Checklist
Supabase schema deployed and tested
Drive folder template created and shared with cohort leads
Circle.so channels live with pinned welcome prompts
Anthropic API keys provisioned for Sonnet 4.6 and Opus 4.7 in production tier
Mentor on-call schedule confirmed for first 8 weeks
Smoke test: one test student through M4.1 checkpoint with manual rubric run
Cohort start date announced; enrollment page live; payment processor tested
First cohort lead identified and trained on SOPs 01-04

5. Deployment SOP — Path B: LMS-Hosted
Path B migrates content to a Learning Management System for scaled enrollment. Recommended for second cohort onwards once first-cohort feedback has informed content refinement.
5.1 Platform Selection
Three viable LMS platforms for C4-style cohort programs:
Platform
Strengths
Weaknesses
Cost
Kajabi
Native cohort + community + payment + email
Higher cost; less flexibility for AI rubric integration
$199-549/mo
Thinkific Plus
Strong assignment workflows; cohort scheduling
Community is weaker than Kajabi; payment integration less native
$499+/mo
Circle Spaces (Pro tier)
Already used for community; simplest migration
Course delivery features less mature than dedicated LMS
$99-399/mo
Default recommendation: Circle Spaces Pro tier for first LMS-hosted cohort (lowest migration cost; community continuity); migrate to Kajabi at 50+ student cohort scale if Circle's course features prove insufficient.
5.2 Content Migration
Content migration from markdown to LMS:
Module lessons (8 files): paste markdown into LMS lesson editor; preserve heading structure
Templates (10 files): upload as downloadable files OR embed as in-page templates with copy-buttons
Worksheets (2 files): convert to LMS quiz/assignment format with required-field validation
Reference materials (frameworks, swipe file, archetype chart): upload as resource library entries
Case studies (4 files): paste as supplementary lessons within module pages; mark as optional reading
YAML system prompts: do NOT migrate to LMS; remain in code repository as source of truth
5.3 Automation Layer
Path B automation reduces cohort lead manual work:
Zapier integration: LMS submission → webhook → Claude API call → result back to LMS comment field. ~3 hours of Zapier setup per reviewer.
Native LMS checkpoint progression: configure each module to unlock on prior-module pass; manual gate by cohort lead OR auto-gate by rubric score field
Email automation: enrollment → Welcome Kit + cohort calendar invites; checkpoint pass → next-module unlock notification
Payment + community access auto-provisioning: most LMS platforms include this natively
5.4 When to Move From Path A to Path B
After first cohort completion when content is refined per first-cohort feedback
When manual cohort lead time exceeds 8 hours/week per cohort (typically at 15+ student cohort size)
Before announcing third cohort (Path A scales to 2 cohorts; Path B scales to ~5 cohorts before Path C becomes worth it)

6. Deployment SOP — Path C: Full RISER Build Stack
Path C is the long-term operating model. High setup cost; lowest per-cohort marginal cost. Recommended only when committed to Stage 2+ continuity (C5-C18 in sequence).
6.1 Architecture
Path C runs C4 against the full RISER Build stack:
Build 1 (Supabase): hosts c4_schema.sql with full RLS, generated columns, and trigger functions documented in 04_Tools-and-Infrastructure/Integration-Walkthroughs/Supabase-C4-Schema.md
Build 6 (Analytics + Revenue Ops + HITL Queue): orchestrates checkpoint progression, peer review matching, Opus gate, mentor escalation, and cohort dashboard
Build 8 (Drive Filing): auto-provisions per-student folders; manages permissions for peer reviewers; supports Data Portability export
Build D4 (Paid Media — preview): consumes C4 landing page copy at C8 activation in Stage 2
Build 14 (Causal Modeling — preview): consumes full C4 artifact set at C42 activation in Stage 5
6.2 Build Order
Step
Build
Effort
Output
1
Build 1 — Supabase schema
8-16 hrs
C4 tables + functions live
2
Build 6 — checkpoint handlers
40-80 hrs
Per-module routing operational
3
Build 6 — peer review matcher
16-24 hrs
Auto-matching with SLA tracking
4
Build 6 — Opus gate handler
16-24 hrs
Sonnet → Opus orchestration
5
Build 6 — mentor escalation routing
8-16 hrs
FAIL verdicts auto-route
6
Build 8 — Drive integration
8-16 hrs
Auto-provisioning + permissions
7
Build 6 — dashboard views
16-24 hrs
Per-student + cohort-level analytics
8
End-to-end smoke test
8-16 hrs
One test student through full course
Total estimated effort: 120-216 engineering hours (typically 4-8 weeks at 30-50 hours per week).
6.3 When Path C Is Worth It
3+ cohorts running simultaneously
Cohort enrollment exceeding 30 students per cohort
Stage 2+ courses (C5-C7) deploying within 6 months of C4 launch
Multiple operator-archetype pacing patterns straining Path A/B manual operations
Causal modeling (Build 14) activated for cohort outcome analysis

7. C4 v2.1 Remediation
7.1 The Blocking Gap: SRS 8.3
QM Audit returns 92/94 (97.9%) but NOT_CERTIFIED status due to one blocking SRS:
SRS 8.3 — Alternative means of access — currently scores 2/3 PARTIAL. M4.1 has both Written Lesson and Video Spec (multi-modal access). M4.2 through M4.8 have Written Lesson only. To reach 3/3 MET and unblock certification, Video Specs must be produced for the remaining 7 modules.
7.2 Remediation Tasks for C4
Task
SRS
Effort
Priority
Produce Video Spec for M4.2 (Grand Slam Offer Framework)
8.3
1-2 hrs
P1
Produce Video Spec for M4.3 (Decomposition and Reassembly)
8.3
1-2 hrs
P1
Produce Video Spec for M4.4 (Pricing and Anchoring)
8.3
1-2 hrs
P1
Produce Video Spec for M4.5 (Anti-Promise Statement)
8.3
1-2 hrs
P1
Produce Video Spec for M4.6 (Guarantee Architecture)
8.3
1-2 hrs
P1
Produce Video Spec for M4.7 (Landing Page Copy)
8.3
1-2 hrs
P1
Produce Video Spec for M4.8 (Offer Readiness Document)
8.3
1-2 hrs
P1
Compile Vendor Accessibility Statements file
8.6
2 hrs
P2
On completion of all P1 tasks: SRS 8.3 → MET; Essentials Met → 16/16; Certification Status → CERTIFIED. Total effort: 8-14 hours of curriculum production work.
7.3 Can You Ship Without Remediation?
Yes — Path A and Path B can ship with the current 92/94 audit. The certification status is NOT_CERTIFIED but the course operationally functions; students can complete C4 successfully via Written Lesson access alone.
Recommended approach: ship first cohort against current 92/94 to validate operational mechanics; produce remediation work in parallel; second cohort ships at QM Certified status.
Counter-recommendation: if institutional credibility depends on QM Certified status (e.g., partnership with educational institutions, B2B enterprise sales of operator-development programs), complete remediation before first cohort launch.

8. Operating Cadence — Running C4
8.1 Daily Operations
Cohort lead reviews Build 6 dashboard for new submissions awaiting review (Path C) OR manually invokes rubric prompts on Drive uploads (Path A/B)
Mentor on-call monitors #mentor-requests channel for escalations
Community manager monitors #c4-offer-ignition for stuck-student posts; routes to mentor or peer help
Refund queue check (typically 0-2 refunds per week per cohort)
8.2 Weekly Operations
Monday: post Weekly Monday Check-In prompt; review pacing telemetry
Wednesday: peer review SLA audit (any reviews approaching 72-hour limit without delivery)
Friday: post Friday Reflection prompt; review week's pacing trajectory; identify struggling students for proactive outreach
Friday: cohort lead 30-minute retrospective on the week's checkpoint outcomes; flag systemic issues (e.g., 3+ students stuck on same module)
8.3 Monthly and Quarterly Operations
Monthly: Cohort metrics report — enrollment, completion velocity, AI rubric pass rates, Opus PASS rates, mentor escalation volume, Opus per-student cost trend.
Quarterly: Refresh C4-Approved-Paid-Review-Options.md per the document's quarterly cadence; refresh Tier A/B/C reviewer roster; audit Reviewer Affiliate Agreements.
Quarterly: Re-run QM audit; track score trajectory; if remediation tasks have shipped, expect improvement.
Annually: Strategic review of methodology — does the Hormozi-adjacent synthesis still match market sophistication? Are anti-promise mechanics still differentiating? Update curriculum if methodology has drifted.
8.4 Opus Gate Operations
The M4.8 Opus 4.7 validator is the highest-cost operational element in C4. Specific operating practices:
Monitor per-call cost trend; if creeping above $0.55, audit prompt token usage (input context efficiency vs output verdict completeness)
Monitor per-student total Opus cost; ceiling is $1.10 across course completion + revisions; individual students exceeding this trigger mentor review of validator efficiency
Monitor PASS / NEEDS_REVISION / FAIL distribution monthly: target ~60% PASS first attempt, ~30% NEEDS_REVISION, ~5% FAIL; deviations indicate systemic curriculum issues OR validator calibration drift
Quarterly: re-evaluate whether Opus 4.7 remains the optimal model OR whether a future Sonnet variant has reached coherence-check capability at lower cost

9. Success Metrics for C4
9.1 Structural Metrics
Course-completion rate (enrolled → C4 PASS): target 65-75% first cohort, 75-85% sustained
Median time from enrollment to PASS: target 4-5 weeks; flag if median exceeds 6 weeks
Median submission count per module: target 1.0-1.2; flag if any module exceeds 1.5
Sonnet rubric first-pass rate per module: target 70-80%
Opus PASS rate first attempt: target ~60%; NEEDS_REVISION ~30%; FAIL ~5%
9.2 Quality Metrics
Anti-Promise Integrity Statement signing rate: 100% (structurally enforced via passed flag)
Guarantee Honesty Clause signing rate: 100% (structurally enforced)
Trigger Bank verbatim entry count at M4.7: target ≥15 (minimum); celebrate ≥25
Feature Stuffing Flag rate at M4.3: target <10%; flag if rises to 20%+
Mechanism drift detection rate at M4.1 vs C3 M3.7: target <5%; flag if rises (suggests C3 M3.7 process is too permissive)
9.3 Cohort-Level Metrics
Peer review reciprocity ratio (reviews given / reviews received per student): target ≥0.85; flag <0.70
Peer review SLA met rate (within 72 hours): target ≥85%; flag <70%
Alternate Protocol activation rate (A/B/C combined): target <30%; rates >40% indicate cohort thinning issue
Cross-stage reviewer pool size: target ≥5 active alumni; flag <3
Mentor capacity utilization: target ~60%; flag if sustained >85% (capacity expansion needed)
First-sale-by-month-3 rate (post-C4 completion): target ≥50%; this is C5 metric but tracked back to C4 quality

10. Glossary and References
Key Terms
Anti-Promise: What the offer explicitly does not do. Who it is not for. Outcomes the offer will not be held responsible for. Required structural component per RISER methodology synthesis (Hopkins 1923, Hormozi 2021).
Feature Stuffing Trap: Compensating for weak Value Equation numerator variables (Dream Outcome, Perceived Likelihood) by loading the offer with bonus deliverables and stacked guarantees. Named failure pattern documented in 07_Case-Studies-and-Examples.
Grand Slam Offer: Hormozi's (2021) framework for offers strong enough that prospects feel compelled to accept. Built on Value Equation: (Dream Outcome × Perceived Likelihood) / (Time Delay × Effort & Sacrifice).
Guarantee Honesty Clause: Signed commitment that the M4.6 guarantee will be honored without friction at the activation conditions stated. Enforced at the database layer via the passed generated column.
Integrity Statement: Signed commitment that the M4.5 anti-promise reflects truthful exclusions, non-claims, and scope boundaries. Enforced at the database layer.
Opus Gate: The M4.8 offer-fit-validator (Opus 4.7) — the only Opus-powered review prompt in C4. Course completion requires PASS verdict; opens C5 enrollment.
Primary Mechanism: The validated mechanism selected at C3 M3.7 from the three C2 finalists. C4 wraps the Primary mechanism in commercial form.
Six Percent Rule: Doctrine that 3 distinct variants must be produced in M4.3 before any one variant is selected. Prevents commitment to first-imagined variant.
Trigger Bank: Compiled in C3 M3.2; ≥200 verbatim buyer-language entries from forums, social, search, and interviews. Cited extensively in C4 M4.2 Value Equation work and M4.7 Landing Page Copy (≥15 verbatim entries minimum at M4.7).
References
Abraham, J. (2000). Getting Everything You Can Out of All You've Got.
Brunson, R. (2015). DotCom Secrets.
Brunson, R. (2017). Expert Secrets.
Hopkins, C. (1923). Scientific Advertising.
Hormozi, A. (2021). $100M Offers.
Ries, E. (2011). The Lean Startup.
Walker, J. (2014). Launch.
Document Control
Version 2.0 · April 24, 2026 · Owner: RISER Nation Curriculum Quality Team · Next review: 2026-07-24
Cross-references: C1 Harbor Orientation Deployment SOP v2.0; C2 Flagship Discovery Deployment SOP v2.0; C3 Buoy Navigation Deployment SOP v2.0.

word/comments.xml


word/endnotes.xml



word/footer1.xml
Page  of 

word/header1.xml
C4 Offer Ignition — Deployment SOP v2.0

word/footnotes.xml

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Preparation Checklist

**Purpose:** Pre-flight check before submitting M4.7 landing page copy for cohort peer review. Prevents common rework-causing gaps.
**Time to complete:** 15-20 minutes before submission
**Filed to:** Attached to your M4.7 submission

---

## Before You Submit

Running this checklist before posting in `#c4-offer-ignition` saves your peer reviewers 30-60 minutes per review and dramatically increases the quality of feedback you receive. Reviewers who have to hunt for your Trigger Bank Provenance Log, or who notice your anti-promise softened from M4.5, spend their review time on mechanical issues rather than substantive feedback.

---

## Section A — Document Completeness

- [ ] Landing page copy file exists at `Offer-Landing-Page-Copy-[YourName]-[Date].md`
- [ ] All 7 sections present in order:
  - [ ] Section 1 — Problem (200-400 words)
  - [ ] Section 2 — Agitation (150-300 words)
  - [ ] Section 3 — Solution-and-Mechanism (300-500 words)
  - [ ] Section 4 — Proof (200-400 words)
  - [ ] Section 5 — Offer (300-500 words)
  - [ ] Section 6 — Anti-Promise-and-Guarantee (250-400 words)
  - [ ] Section 7 — CTA (50-150 words)
- [ ] Total word count in 1,800-2,500 range (not absurdly over or under)

## Section B — Trigger Bank Usage

- [ ] Trigger Bank Provenance Log file exists at `Landing-Page-Trigger-Bank-Provenance-[YourName]-[Date].md`
- [ ] Log contains ≥ 15 entries mapped to landing page usage
- [ ] Every entry in the log is verbatim (not paraphrased) from the source Trigger Bank
- [ ] Each entry cites specific Trigger Bank ID (TB-###) or Interview #
- [ ] Entries are distributed across 4+ of the 7 sections (not all stacked in one section)

## Section C — Anti-Promise and Guarantee Integrity

- [ ] Anti-Promise in Section 6 is substantively the same as your M4.5 Anti-Promise Statement
- [ ] If any softening occurred between M4.5 and M4.7, it is reverted OR documented with rationale
- [ ] Anti-Promise Integrity Statement is signed
- [ ] Guarantee in Section 6 is substantively the same as your M4.6 Guarantee Architecture
- [ ] If any stacking occurred between M4.6 and M4.7, it is reverted
- [ ] Guarantee Honesty Clause is signed

## Section D — Offer Section Completeness

- [ ] Named deliverable (5-Test-passed name) visible in Section 5
- [ ] Price visible in Section 5 (not hidden, not ranged)
- [ ] Payment options listed
- [ ] Delivery structure described (engagement model, duration, cadence)
- [ ] Deliverables list is not over 8 items (Feature Stuffing Trap check)

## Section E — Proof Integrity

- [ ] Proof cases in Section 4 are specific (named or anonymized with specific outcome)
- [ ] If you have fewer than 4 named cases, the Known Weaknesses acknowledgment is visible (not papered over)
- [ ] Testimonials (if any) are verbatim quotes, not paraphrased
- [ ] Testimonials have attribution (name or anonymized but specific)

## Section F — CTA Specificity

- [ ] CTA names a specific action (not "click here")
- [ ] Next cohort / enrollment date is present
- [ ] Qualification process (if any) is described
- [ ] Contact email or channel is present for pre-purchase questions

## Section G — Voice Check

- [ ] You have read the full landing page out loud once, from start to finish
- [ ] The page does not contain phrases you would not actually say to a buyer in person
- [ ] The page does not contain hyperbole you cannot substantiate
- [ ] The page does not contain any of these phrases: "game-changer," "revolutionary," "transform your life," "all you need to do is" (low-substance signaling vocabulary)

## Section H — Review Request Post

Before posting in `#c4-offer-ignition`, prepare the post:

- [ ] Drive link to landing page copy
- [ ] Drive link to Trigger Bank Provenance Log
- [ ] Brief context (2-3 sentences about your offer's key positioning)
- [ ] Specific request: "2 peer reviews within 72 hours, using the C4 Peer Review Template"
- [ ] Your availability to return review favor (which days you can review others' copy)

---

## Common Pre-Submit Fixes

If any checklist item is unchecked, common fixes:

| Unchecked Item | Typical Fix |
|---|---|
| Section 6 softened from M4.5/M4.6 | Revert to the original M4.5 Anti-Promise and M4.6 Guarantee language |
| Trigger Bank count < 15 | Add 3-6 more verbatim entries, typically in Problem and Agitation sections |
| Deliverables > 8 | Review for Feature Stuffing; which deliverables are compensation, which are real value? |
| Price hidden or ranged | Move price to Section 5 with explicit number |
| Voice check fails | 48-hour cooling re-read; rewrite any section where "did I actually say that?" is your reaction |

---

## After Submission

Once posted:

- [ ] Check `#c4-offer-ignition` daily for reviewer pickup
- [ ] Respond promptly to reviewer questions
- [ ] Do not revise the landing page while reviews are in progress (creates version mismatch)
- [ ] Begin reviewing other cohort peers' landing pages as reviews arrive — reciprocity is cohort norm

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Outreach Scripts

**Purpose:** Short scripts for requesting and responding to peer reviews during M4.7. These are starter templates; adapt in your own voice.
**Filed to:** `03_Scripts-and-Prompts/Outreach-Scripts/`
**Referenced by:** M4.7 Written Lesson; C4-Peer-Review-Preparation-Checklist

---

## Script 1 — Requesting Peer Review (post in `#c4-offer-ignition`)

```
**M4.7 peer review request — [YourName]**

- **Offer name:** [5-Test-passed name]
- **Target buyer:** [one sentence describing who this is for]
- **Price:** $[X]
- **What I want reviewers to watch for specifically:**
  - [1-2 things you suspect may be weak — common: Section 4 Proof, Section 6 Anti-Promise softening, Trigger Bank entry density]

**Drive links:**
- Landing page copy: [link]
- Trigger Bank Provenance Log: [link]
- Revision Log (so far): [link — if you have one]

**SLA:** 72 hours ideal

**Reciprocity:** I'm available to review copy on [specific days this week]. Reply with yours and I'll pick up the first two.

Using the C4 Peer Review Template (`02_Resources/Templates/C4-Peer-Review-Template.md`).
```

### Why this structure works

Naming what you suspect is weak focuses reviewer attention. Without this, reviewers tend to spread feedback thin across the whole page. Concentrated attention on 1-2 sections produces higher-signal feedback.

---

## Script 2 — Offering Peer Review (response to another student's request)

```
I'll pick up your review, [TheirName]. I'll aim to deliver within 48 hours.

If you want me to pay particular attention to [suggested focus based on their request], I will. If you want me to do a straight full-template review, I'll do that too.

My C4 Peer Review Template will be back in your Drive folder or Circle.so thread by [specific date + time].
```

### Why this structure works

Confirms the commitment with a specific delivery time. Acknowledges their request-specific focus areas. Creates accountability for the delivery.

---

## Script 3 — Declining a Peer Review (when over-committed)

```
Thanks for tagging me, [TheirName]. I'm at capacity this week ([reason if relevant — e.g., "I'm in my own M4.7 cycle with deadline Thursday"]).

Tagging [OtherName] who mentioned they had bandwidth this week. You can also use the Alternate Protocol at `02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md` if the cohort is thin at your pacing — Protocol A (mentor substitution) is available.
```

### Why this structure works

Declining without leaving the requester stranded. Referring to Alternate Protocol reminds the requester that the safety net exists.

---

## Script 4 — Delivering Peer Review (after completing the template)

```
[TheirName] — review complete.

**Template:** [Drive link to completed Peer Review Template]

**Top-level observation:** [one sentence — your overall impression]

**My three recommended revisions (from template):**
1. [brief version]
2. [brief version]
3. [brief version]

Happy to discuss any of these in async DM if useful. Good luck with M4.8.
```

### Why this structure works

Surfaces the most actionable takeaway in the message itself so the requester can start revising without waiting to open the full template. The full template provides depth; the message provides urgency.

---

## Script 5 — Responding to Peer Review (after incorporating)

```
[ReviewerName] — thanks for the review. Incorporated as follows:

- **Revision 1 you recommended:** [incorporated / incorporated with modification / not incorporated + reason]
- **Revision 2:** [same format]
- **Revision 3:** [same format]

Revision Log in Drive: [link]

Appreciate the time.
```

### Why this structure works

Closes the loop on every recommendation. Decisions not to incorporate are documented (not silently ignored). The Revision Log is what the offer-fit-validator at M4.8 checks for.

---

## Script 6 — Escalating to Mentor (when Alternate Protocols Fail)

Address to `#mentor-requests` Circle.so channel or via the mentor Calendly link from cohort welcome email:

```
**C4 M4.7 peer review escalation — [YourName]**

- Cohort pacing window: [your dates]
- Peer reviews attempted: [how many requests, how many responses]
- Alternate Protocols tried: [A — mentor booking status / B — cross-stage post status / C — paid review status]

**Specific help requested:** [mentor review of landing page, or pacing adjustment, or cohort coordination]

**Drive link:** [landing page copy]
**SLA needed:** [your revised timeline]
```

### Why this structure works

Names what has already been tried so the mentor does not repeat the available paths. Specifies what help is actually requested so the mentor can respond efficiently.

---

## Cohort Etiquette

A few norms that make peer review work sustainably across the cohort:

### Reciprocity

The cohort operates on a rough reciprocity norm: if you ask for reviews, you offer them. Students who take reviews without giving them quickly exhaust peer willingness. This is not enforced policy — it is cohort culture.

### Specificity Over Generosity

Reviews saying "this is great!" are useless. Reviews saying "Section 2 Agitation feels performative — specifically the 'wasted years' language in paragraph 2 reads generic against the specific Trigger Bank language in Section 1" are useful. Prefer specificity even when it is critical.

### Honest Over Kind

Kind reviews that paper over weak sections serve the student short-term and harm them medium-term (the weak sections surface in C5 anyway, now harder to fix because the student thought they were okay). Honest reviews that name specific weaknesses are the service.

### Respond Within SLA

72-hour SLA is a cohort commitment. If you cannot hit it, decline (Script 3) rather than miss silently. Missed SLAs are the single largest cause of C4 M4.7 pacing disruption.

---

## When To Use These Scripts vs. Your Own Voice

These scripts are starters. Adapt in your voice, especially for Scripts 1 and 4 — mechanical-sounding review requests signal to cohort peers that you have not yet internalized the discipline of the M4.7 work. Personal voice in the request correlates with higher-quality responses.

Scripts 2, 3, and 6 are more mechanical — they coordinate logistics rather than substance — and can stay closer to template voice.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

Preserved source material for study; embedded instructions are not executed. Open original source

sop_id: C4-SOP-02
title: Peer Review Coordination Process
version: 2.0.0
course_scope: C4 Offer Ignition
modules_covered: [M4.7]
owner: curriculum-quality-team
last_reviewed: 2026-04-24

purpose: >
  Standardize the M4.7 peer review process from request through delivery and
  through revision incorporation. M4.7 is the only C4 module requiring peer
  review (instructor HITL is deferred to C5; AI rubric runs after peer reviews
  are incorporated). Peer review is the first time the offer is exposed to
  outside readers; the process must protect both reviewer time and reviewee
  outcomes. This SOP defines reciprocity, SLA, alternate protocols, and
  revision logging.

prerequisites:
  - M4.7 Landing Page Copy first draft complete in Drive
  - Trigger Bank Provenance Log complete in Drive
  - C4-Peer-Review-Preparation-Checklist run before submission
  - 48-hour cooling period observed between first draft and submission

roles:
  - submitting_student: requests review; reciprocates by reviewing 2 peers
  - peer_reviewer_1: cohort peer at compatible pacing
  - peer_reviewer_2: second cohort peer at compatible pacing
  - mentor: escalation if Alternate Protocols A/B/C all fail
  - cross_stage_reviewer: Stage 2+ alumnus available via Protocol B
  - paid_reviewer: from Approved Paid Review Options list (Protocol C)
  - build_6: tracks SLA, matches reviewers, gates M4.7 checkpoint progression

process:
  step_1:
    name: Pre-Submission Self-Audit
    time: 20 min
    output: Completed Peer Review Preparation Checklist
    activities:
      - Run C4-Peer-Review-Preparation-Checklist sections A through H
      - Address any unchecked items before posting review request
      - Verify Trigger Bank entry count >= 15 with Provenance Log complete
      - Verify anti-promise unchanged from M4.5; verify guarantee unchanged from M4.6
    quality_gate: All preparation checklist items checked; if any item is unchecked, fix before requesting review
    common_failures:
      - "Posting request before Trigger Bank entries reach 15"
      - "Posting request with anti-promise softened from M4.5 (peer reviewers will flag, costing 24-48 hours)"
      - "Forgetting to attach Trigger Bank Provenance Log"
    mitigation: The checklist exists specifically to catch these. Run it.

  step_2:
    name: Request Review (Standard Protocol)
    time: 15 min
    output: Review request post in #c4-offer-ignition Circle.so channel
    activities:
      - Use Outreach Script 1 from C4-Peer-Review-Outreach-Scripts.md
      - Specify offer name, target buyer, price, areas you suspect are weak
      - Attach Drive links to landing page copy AND Trigger Bank Provenance Log
      - State 72-hour SLA expectation
      - Offer specific reciprocity (which days you can review others' copy this week)
    quality_gate: Post visible in #c4-offer-ignition; request structure matches Outreach Script 1
    common_failures:
      - "Vague request without specifying suspected-weak sections (reviews come back generic)"
      - "Not offering reciprocity (cohort norm violated; future review requests slower to receive responses)"
      - "Missing Provenance Log attachment (reviewers can't verify Trigger Bank usage)"
    mitigation: Use the script verbatim until it becomes natural

  step_3:
    name: Reviewer Pickup (24-48 hours from request)
    time: passive
    output: 2 peers commit to review with stated delivery dates
    activities:
      - Build 6 sends notification to active cohort peers at compatible pacing
      - Peers respond using Outreach Script 2 (acceptance) or Script 3 (decline with referral)
      - Build 6 logs commitments and tracks SLA
      - If only 1 reviewer commits within 48 hours, Build 6 escalates per step 4a
    quality_gate: 2 reviewers committed within 48 hours
    common_failures:
      - "Cohort thin at student's pacing (Protocol A activates)"
      - "Reviewers who committed silently miss SLA without communication"
    mitigation: Build 6 active SLA tracking surfaces silent misses; cohort norm includes communicating early if SLA at risk

  step_4_alternate_protocol_a:
    name: Mentor Substitution (Protocol A)
    time: 24 hours from activation
    output: Mentor named as reviewer; review delivered within 72 hours
    activation_trigger: Cohort has < 4 active peers at compatible pacing OR < 2 peers commit within 48 hours
    activities:
      - Student books mentor review slot via Calendly link in cohort welcome email
      - OR Student posts in #mentor-requests with M4.7 review request
      - Mentor delivers full Peer Review Template completion within 72 hours
      - Mentor review counts as both required peer reviews
    quality_gate: Mentor review filed with C4-Peer-Review-Template completion
    common_failures:
      - "Mentor booking backed up 2+ weeks during high-enrollment cycle (rare; route to Protocol B)"

  step_4_alternate_protocol_b:
    name: Cross-Stage Review (Protocol B)
    time: 96 hours from activation
    output: 1-2 Stage 2+ alumni reviewers complete review
    activation_trigger: Mentor backed up; OR student prefers reviewer who has shipped offers
    activities:
      - Student posts in #cross-stage-review channel using request format from Alternate Protocol document
      - Stage 2-5 operators who actively volunteer review time pick up the request
      - Review uses C4 Peer Review Template
      - Cross-stage review counts as both required reviews, OR pairs with one peer/mentor review
    quality_gate: Cross-stage review filed
    common_failures:
      - "No cross-stage reviewer picks up within 48 hours (route to Protocol C)"

  step_4_alternate_protocol_c:
    name: Approved Paid Review (Protocol C — Last Resort)
    time: 48-72 hours from activation
    output: Paid reviewer completes review using C4 Peer Review Template
    activation_trigger: Protocols A and B unavailable within student's planned week
    activities:
      - Student selects from C4-Approved-Paid-Review-Options.md (Tier A/B/C)
      - Direct engagement; Academy does not facilitate payment
      - Paid reviewer completes C4 Peer Review Template
      - Paid review counts as 1 of 2 required reviews; must pair with peer/mentor/cross-stage for second
      - Methodology consistency check: any methodology-conflicting paid feedback flagged before incorporation
    quality_gate: Paid review filed; second review (peer/mentor/cross-stage) also filed
    common_failures:
      - "Paid reviewer recommends removing anti-promise (methodology-conflict; do not incorporate without mentor consult)"
      - "Paid reviewer recommends stacking guarantees (methodology-conflict)"
      - "Student counts paid review as both required reviews (not allowed)"
    mitigation: Approved Paid Review document provides methodology baseline language to send to paid reviewer

  step_5:
    name: Receive and Read Reviews
    time: 30 min (do not act yet)
    output: Both reviews read in single sitting
    activities:
      - Wait until both reviews have arrived before reading either
      - Read both in one sitting; note patterns
      - If both reviewers flagged the same section as weak, that section is genuinely weak
      - If reviewers disagree, use your judgment
      - Do not begin revision yet — sleep on the feedback
    quality_gate: Both reviews read; pattern notes captured
    common_failures:
      - "Reading first review and immediately starting revisions before second review arrives (creates whiplash if reviewers disagree)"
      - "Defending against feedback in your head without genuinely considering it"
    mitigation: 12+ hour gap between reading and revising; treat reviews as gifts, not attacks

  step_6:
    name: Draft Revision Log + Revise
    time: 60-90 min
    output: Revision Log file + revised landing page in Drive
    activities:
      - Open C4-Peer-Review-Outreach-Scripts.md Script 5 template
      - For each suggestion in each review: incorporated / incorporated with modification / not incorporated + reason
      - Document each decision; the offer-fit-validator at M4.8 reads this
      - Revise landing page based on incorporated suggestions
      - Address pattern-flagged sections (those flagged by both reviewers) with priority
    quality_gate: Revision Log complete; revised landing page in Drive
    common_failures:
      - "Skipping the Revision Log (validator at M4.8 will flag missing log)"
      - "Incorporating every suggestion mechanically (you should make decisions, not absorb)"
    mitigation: The Log is the structural mechanism that forces decision-making; do not skip

  step_7:
    name: Reciprocate
    time: 90-120 min total (45-60 min per review × 2)
    output: 2 completed peer reviews delivered to other students
    activities:
      - During or after your own revision cycle, complete 2 peer reviews for cohort peers
      - Use C4-Peer-Review-Template for each
      - Deliver via Outreach Script 4 from outreach scripts document
      - Reciprocity is cohort norm; tracking is light but reputation matters
    quality_gate: 2 reviews delivered; Build 6 logs reciprocity in cohort metrics
    common_failures:
      - "Receiving reviews and not reciprocating (silent reputation cost; future requests slower to receive responses)"
      - "Reciprocating with low-effort 'looks great!' reviews (worse than declining; harms peer's revision quality)"
    mitigation: If you genuinely cannot reciprocate this cycle, decline future review requests until you can; do not free-ride

  step_8:
    name: Submit Revised Landing Page to AI Rubric
    time: 5 min + 5 min for rubric run
    output: landing-page-copy-reviewer score >= 7/10
    activities:
      - Submit revised landing page + provenance log + revision log to Build 6
      - Build 6 invokes landing-page-copy-reviewer-v1.0.0.yaml
      - Verify peer_review_count >= 2 in submission metadata
      - Receive rubric score within 5 minutes
    quality_gate: Score >= 7/10; peer_review_count = 2; no integrity flags
    common_failures:
      - "Submitting without filing the Revision Log first (rubric flags missing artifact)"
      - "Trigger Bank entries fabricated or paraphrased (rubric flags as integrity issue)"
    mitigation: All checks should already have passed in step 5-6; if rubric flags appear, fix and resubmit

review_and_adjustment:
  cadence: Per cohort cycle
  questions_to_ask:
    - "What % of M4.7 submissions used Standard Protocol vs Alternate Protocol A/B/C?"
    - "What was the median time from review request to review delivery?"
    - "What % of reviewers met SLA without escalation?"
    - "What % of paid reviewers gave methodology-conflicting feedback?"
  adjustment_principles:
    - If Alternate Protocol A activation > 30%, expand mentor capacity OR extend cohort recruitment to thicken cohorts
    - If paid reviewer methodology conflicts > 20%, refresh paid reviewer Affiliate Agreements OR remove specific reviewers from Approved list
    - If reciprocity ratio (reviews given / reviews received) < 0.85, surface in cohort discussion

escalation_triggers:
  - 3+ submissions fail M4.7 rubric on same student (mentor diagnosis)
  - Reviewer fabrication or methodology-conflicting feedback (Affiliate Agreement review)
  - Reciprocity ratio < 0.5 for individual student over 2 cohorts (cohort norm conversation)
  - Cohort thinning > 3 weeks consecutive (Build 6 → Marketing for cohort recruitment review)

related_documents:
  - 02_Resources/Templates/C4-Peer-Review-Template.md
  - 02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md
  - 02_Resources/Templates/C4-Approved-Paid-Review-Options.md
  - 02_Resources/Checklists/C4-Peer-Review-Preparation-Checklist.md
  - 03_Scripts-and-Prompts/Outreach-Scripts/C4-Peer-Review-Outreach-Scripts.md
  - 03_Scripts-and-Prompts/Claude-System-Prompts/landing-page-copy-reviewer-v1.0.0.yaml

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Template — M4.7 Landing Page Copy

**Purpose:** Structured template for cohort peer reviews of M4.7 landing page copy. Two peer reviews per student are required; students complete two reviews for peers in exchange.
**Time per review:** ~45-60 minutes
**Timeline:** 72-hour SLA from review request to delivery
**Filed to:** Build 8 Drive folder; linked into submitting student's M4.7 folder

---

## Reviewer Instructions

Read the landing page copy and the Trigger Bank Provenance Log in one pass, then complete the template below. Your job is not to edit line-by-line — the submitting student will do that. Your job is to surface structural issues they cannot see from inside their own draft.

Three things you are specifically looking for:

1. **Does the page sound like the market or like the operator?** You are an outside reader who has not been inside this operator's head for 4 weeks. You can hear voice drift more clearly than they can.

2. **Are the verbatim Trigger Bank quotes doing work, or are they decorative?** Quotes should anchor specific claims. A quote dropped next to a general statement without connection is not working.

3. **Is the anti-promise actually specific, and is the guarantee actually clean?** M4.5 and M4.6 stand-alone documents can be strong but get softened in the landing page. You are the second set of eyes that catches softening.

---

## Reviewer Information

**Reviewer name:** _____________________________
**Reviewer operator archetype:** _____________________________
**Review date:** _____________________________
**Submitting operator name:** _____________________________
**Submitting operator's offer name:** _____________________________

---

## Section-by-Section Review

### Section 1 — Problem

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak
**One-sentence read:** [What is this operator's offer trying to solve, in your words?]

Does the Problem section make the buyer's current state specific and vivid?
☐ Yes, I could visualize it ☐ Partially ☐ No, it was generic

Was at least one verbatim Trigger Bank quote integrated meaningfully (not decoratively)?
☐ Yes ☐ Partially ☐ No

**Specific observations (1-3 sentences):**

---

### Section 2 — Agitation

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Does the Agitation section make the cost of *not acting* feel real, or does it feel performative?
☐ Real ☐ Mixed ☐ Performative

Did any specific numbers, time-frames, or opportunity costs make the Agitation land?
☐ Yes (which ones: __________) ☐ No

**Specific observations:**

---

### Section 3 — Solution-and-Mechanism

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

After reading this section, can you describe the mechanism in your own words?
☐ Yes, I could teach it to a friend ☐ Roughly ☐ No, it's still fuzzy

Are the 4 pillars of the mechanism visible, even if not labeled as pillars?
☐ Yes ☐ Partially ☐ No

**Specific observations:**

---

### Section 4 — Proof

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Are the proof cases specific (named, with outcome data), or are they generic ("Maya is great")?
☐ Specific ☐ Mixed ☐ Generic

If the operator has few case studies, is that acknowledged honestly, or is it papered over?
☐ Acknowledged honestly ☐ Handled in between ☐ Papered over

**Specific observations:**

---

### Section 5 — Offer

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Is the named deliverable clear, specific, and 5-Test-passed?
☐ Yes ☐ Partially ☐ No (how could it be clearer: __________)

Is the price visible on the page?
☐ Yes, clearly ☐ Present but buried ☐ Not visible

Does the delivery structure tell you what the buyer's experience actually is (what they do, when, with whom)?
☐ Yes, concretely ☐ Vaguely ☐ Not really

**Specific observations:**

---

### Section 6 — Anti-Promise-and-Guarantee

**This is the most important section to peer-review.**

**Anti-Promise strength:** ☐ Strong ☐ Adequate ☐ Weak

Does the anti-promise name three specific exclusions?
☐ Yes, three or more ☐ Two ☐ One or fewer

Are any of the "exclusions" actually flattering descriptions of the target buyer (e.g., "not for unmotivated people")?
☐ No, they are genuine exclusions ☐ One or two are flattering-dressed-as-exclusion ☐ Most are

**Guarantee strength:** ☐ Strong ☐ Adequate ☐ Weak

Is the guarantee a clean structure (one primary + one optional complementary), or is it stacked with three or more components?
☐ Clean ☐ Borderline ☐ Stacked (Feature Stuffing Trap signal)

If you were a buyer who met the activation conditions, do you trust this operator would honor the guarantee without friction?
☐ Yes ☐ Mostly ☐ Uncertain

**Specific observations:**

---

### Section 7 — CTA

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Does the CTA name a specific action (not "click here") and a specific outcome ("enroll in the Feb 12 cohort, receive Welcome Kit within 24 hours")?
☐ Yes, specific ☐ Partially ☐ Generic

Is there a clear timeline (cohort start date, enrollment close date)?
☐ Yes ☐ No

**Specific observations:**

---

## Cross-Cutting Review

### Verbatim Trigger Bank Usage

Pick 3 of the Trigger Bank quotes used in the landing page. Check them against the Provenance Log — do they match the source entry verbatim, or have they been paraphrased into "cleaner" language?

- **Quote #1:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased
- **Quote #2:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased
- **Quote #3:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased

**Overall provenance accuracy:** ☐ Strong (all 3 verbatim) ☐ Mixed ☐ Weak (paraphrasing is dominant)

### Voice Check

Does the page sound like the operator or like the market?
☐ Mostly market voice ☐ Mixed (operator voice leaks through in specific sections: __________) ☐ Mostly operator voice

### Total Trigger Bank Entry Count

Count the verbatim quotes in the landing page.
**Count:** ___ / 15 minimum

If below 15, the submission fails the M4.7 checkpoint.

---

## Top-3 Revisions You Recommend

Identify the three revisions that would most improve this landing page:

1. **Revision 1:**
2. **Revision 2:**
3. **Revision 3:**

Each revision should be specific enough that the operator can act on it ("tighten the Problem section opening from 4 sentences to 2") rather than abstract ("improve the copy").

---

## Reviewer Closeout

**Overall assessment:** ☐ Ready to submit ☐ Needs moderate revision ☐ Needs substantial revision

**Would I buy this offer if I were the target buyer?** ☐ Yes ☐ Maybe ☐ No — and why: __________

**Reviewer signature:** _____________________________

---

## For the Submitting Operator

After receiving both peer reviews:

1. Read both reviews in one sitting before acting on either. Look for patterns — if both reviewers flagged the same section as weak, that section needs real work. If they disagree, use your judgment.

2. Your job is not to accept every suggestion. Your job is to take each suggestion seriously and make a documented decision about whether to incorporate it.

3. File a Revision Log (`Revision-Log-M4.7-[YourName]-[Date].md`) noting which suggestions you incorporated, which you considered but did not incorporate, and why. The offer-fit-validator at M4.8 checks for this log.

4. Revise. Submit the revised landing page to the AI rubric (`landing-page-copy-reviewer-v1.0.0.yaml`).

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Alternate Protocol

**Purpose:** Alternate paths when your active C4 cohort has fewer than 4 peers at your pacing window. Ensures M4.7 does not stall for reviewer unavailability.
**Referenced by:** `00_Course-Overview/C4-Prerequisites-Checklist.md`
**Escalation path:** If none of the protocols below are viable, escalate to RISER Nation mentor within 72 hours of M4.7 draft completion.

---

## When to Use This Protocol

Use when any of the following is true:

- Your C4 cohort Circle.so channel (`#c4-offer-ignition`) has fewer than 4 active operators at your pacing window
- Cohort peers at your pacing window have not responded within 72 hours of your review request
- Your cohort is pacing unusually (ahead or behind the main cohort cycle) and peers are not currently at M4.7

---

## Protocol A — Mentor Substitution (Default)

**Who it's for:** Any student whose cohort is too thin for 2 peer reviews.

**How it works:**

1. Book a 45-minute review slot with a named RISER Nation mentor via the Calendly link in the cohort welcome email, or via the `#mentor-requests` Circle.so channel.
2. Submit your M4.7 draft and Trigger Bank Provenance Log at least 24 hours before the review call.
3. The mentor completes the C4 Peer Review Template during or after the call and delivers a written review within 72 hours.
4. Mentor review counts as both required peer reviews. No additional review needed.

**SLA:** 72 hours from submission to written review delivery (typical) ; 96 hours worst-case.

**Cost:** No charge. Mentor capacity is allocated out of Academy program support time.

**When Protocol A is not available:** Mentor booking backed up 2+ weeks. Rare but happens in high-enrollment cycles. Shift to Protocol B.

---

## Protocol B — Cross-Stage Review

**Who it's for:** Students whose mentor booking is backed up, or who prefer review from an operator who has already shipped offers.

**How it works:**

1. Post a review request in the `#cross-stage-review` Circle.so channel with the following structure:

   ```
   **Cross-stage review request — C4 M4.7**
   - Operator archetype: [Teacher / Service / Builder / etc.]
   - Territory: [one sentence]
   - Offer name: [the 5-Test-passed name]
   - Request: 1-2 Stage 2+ operators for M4.7 landing page review
   - SLA: 96 hours
   - Drive link: [link to your draft]
   - Trigger Bank Provenance Log: [link]
   ```

2. Stage 2, Stage 3, Stage 4, or Stage 5+ operators who are active volunteers pick up the review.
3. Review uses the same C4 Peer Review Template.
4. Cross-stage review counts as both required peer reviews, or as one review paired with a mentor/peer review.

**SLA:** 96 hours (longer than peer review because cross-stage operators volunteer review time around their own operation).

**Cost:** No charge. Typically treated as ecosystem reciprocity; Stage 2+ operators accumulate review credit that Stage 1 peers volunteer back.

**Why this can be better than peer review:** Reviewers who have shipped offers have firsthand knowledge of what survives first-sale contact and what does not. Their feedback often has higher signal-to-noise than peer-to-peer review.

**When Protocol B is not available:** No cross-stage reviewer picks up the request within 48 hours. Rare but happens near holiday periods. Shift to Protocol C.

---

## Protocol C — Paid Review (Last Resort)

**Who it's for:** Students whose timeline is blocked and Protocols A and B did not clear within their planned week.

**How it works:**

1. Choose from the Approved Paid Review list in `C4-Approved-Paid-Review-Options.md`.
2. Directly engage the reviewer (paid engagement; Academy does not facilitate payment).
3. Paid reviewer completes the C4 Peer Review Template.
4. Paid review counts as one of the two required reviews. **Paid review alone is not sufficient** — pair with one mentor, cross-stage, or peer review.

**SLA:** per reviewer contract, typically 48-72 hours.

**Cost:** Varies by reviewer. Typical range: $150-$400 per review.

**When Protocol C is genuinely necessary:** rare. Most students who think they need Protocol C actually have a timing problem that Protocol A or B resolves with a slight pacing adjustment (waiting 3-5 extra days for mentor or cross-stage slot).

**Warning:** paid review is a legitimate professional service but is not a substitute for cohort accountability. Paid reviewers who are not familiar with RISER Nation methodology sometimes give advice that conflicts with C3/C4 doctrine (e.g., suggesting feature-stuffed guarantees or removal of the anti-promise section). Review paid feedback critically against the module lessons; do not incorporate paid advice that conflicts with the methodology without checking with a mentor.

---

## Scholarship Path for Protocol C

If your cohort is thin, Protocols A and B are unavailable within your timeline, and Protocol C is financially inaccessible:

1. Email `[email protected]` with "C4 M4.7 Review Scholarship Request" in the subject line
2. Include your Drive link, pacing dates, and which Protocols were attempted
3. SLA: 48 hours for response; if approved, scholarship covers one paid review up to $200

Scholarship approval is typical for genuine thin-cohort situations.

---

## Logging the Alternate Protocol

Whatever Protocol you used, log it in your M4.7 Revision Log so the offer-fit-validator at M4.8 has the context:

```
Peer Review Protocol: [A — Mentor / B — Cross-Stage / C — Paid + one of A or B / Standard two-peer]
Reviewer 1: [name, protocol, date of review]
Reviewer 2: [name, protocol, date of review]
Alternate protocol rationale: [1-2 sentences]
```

The offer-fit-validator does not penalize Alternate Protocol usage — it penalizes missing reviews. Logging the protocol used keeps the validator's coherence checks from flagging the submission.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by C4-Prerequisites-Checklist*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Approved Paid Review Options

**Purpose:** Reference list of paid review providers vetted by RISER Nation for C4 M4.7 landing page review when cohort peer and mentor options are unavailable (Protocol C in the Peer Review Alternate Protocol).
**Referenced by:** `C4-Peer-Review-Alternate-Protocol.md`
**Status:** This list is maintained by the Academy team and updated quarterly. The version below reflects approved reviewers as of the Last Updated date.

---

## Selection Criteria

To appear on this list, a reviewer has:

- Reviewed at least 20 C4-style offer landing pages in the direct-response tradition
- Demonstrated familiarity with mechanism-based offer construction (Hormozi-adjacent methodology)
- Produced reviews that respect the anti-promise section as a credibility mechanism (rather than recommending its removal)
- Signed the RISER Nation Reviewer Affiliate Agreement — which commits them to methodology-consistent feedback
- Been cross-rated by at least 5 past reviewees as useful and non-disruptive

Reviewers without these properties are excluded from the list, regardless of market reputation.

---

## Current Approved Reviewers (Quarterly Update — Q2 2026)

### Tier A — Deep Direct-Response Specialists

These reviewers have 10+ years of direct-response copy experience. Pricing reflects seniority.

- **Reviewer Slot A1** — [reviewer name redacted for template; actual list maintained in Drive]
  - **Pricing:** $350-$450 per review
  - **SLA:** 72 hours
  - **Specialty:** coaching/consulting offers; cohort programs; Teacher-Operator and Service-Operator archetypes
  - **Contact:** [via Calendly link in Drive version]

- **Reviewer Slot A2**
  - **Pricing:** $300-$400 per review
  - **SLA:** 48-72 hours
  - **Specialty:** productized services; Builder-Operator archetype
  - **Contact:** [via Drive]

### Tier B — Mid-Senior Reviewers

5-10 years of direct-response experience. Pricing is moderate.

- **Reviewer Slot B1**
  - **Pricing:** $200-$275 per review
  - **SLA:** 48-72 hours
  - **Specialty:** creative services; Creative-Operator archetype
  - **Contact:** [via Drive]

- **Reviewer Slot B2**
  - **Pricing:** $175-$250 per review
  - **SLA:** 72 hours
  - **Specialty:** B2B offers; systems and platforms; Systems-Operator archetype
  - **Contact:** [via Drive]

### Tier C — RISER Nation Alumni Reviewers

Alumni who have completed Stage 2+ of the Academy and offer paid review to Stage 1 peers. Often the best value — they know the methodology cold and price accordingly.

- **Reviewer Slot C1-C5** — rotating list, currently 5 alumni reviewers available
  - **Pricing:** $150-$200 per review
  - **SLA:** 48-72 hours
  - **Specialty:** matches the alumni's own operator archetype; check Drive list for match
  - **Contact:** [via Drive; alumni reviewers coordinate through `#alumni-review-pool` Circle.so channel]

---

## How To Engage a Paid Reviewer

1. **Check the Drive version of this list** for current names, contact info, and availability status. Names are not in this template to avoid stale information when reviewers rotate.

2. **Match reviewer to your archetype.** A Teacher-Operator reviewing a Service-Operator's offer will sometimes give advice that is methodology-correct but archetype-mismatched. Tier A reviewers are generalists; Tier B and C reviewers are archetype-specialized.

3. **Send your M4.7 draft and Trigger Bank Provenance Log.** Use the C4 Peer Review Template as the deliverable format. Specify upfront that the review output should use the template — do not accept a free-form review.

4. **Specify the methodology baseline.** In your engagement message, include this line:
   > "This review is for a RISER Nation C4 Offer Ignition M4.7 landing page. The offer follows Hormozi-adjacent mechanism-based structure, and explicitly includes a specific Anti-Promise Statement (per Hopkins 1923 / Hormozi 2021) and a guarantee structure with the Honesty Clause signed. Please review for quality within the methodology rather than suggesting removal of these elements."

5. **Log the engagement** in your Revision Log per the Alternate Protocol instructions.

---

## What NOT to Use

**Do not use:**

- General copywriting review services not on this list (quality varies widely; many default to removing anti-promises, which is the specific thing C4 is trying to preserve)
- Fiverr-tier copy review (signal-to-noise too low for C4 work)
- AI-only review tools as a substitute for human review (acceptable as a supplement, not as the required review)
- Review from an unlisted paid reviewer *and* count it as your second required review (list-approved reviewers are the only paid reviews that satisfy Protocol C)

---

## If a Reviewer Gives Methodology-Conflicting Advice

If a paid reviewer recommends:
- Removing the anti-promise section
- Stacking guarantees beyond the clean structure M4.6 specifies
- Replacing verbatim Trigger Bank quotes with "cleaner" paraphrases
- Repositioning the offer in a way that drifts from your C3 Primary mechanism

...treat the feedback as methodology-conflicting. Do not incorporate without first consulting your RISER mentor or the `#methodology-questions` Circle.so channel. Methodology-conflicting advice from a paid reviewer often reflects their own training in non-anti-promise direct-response (common in the 2010s ecosystem) and is not wrong in their original context — it is just not aligned with C3/C4's specific synthesis.

---

## Removing a Reviewer from the List

Reviewers are removed from this list when any of the following occurs:

- 3+ reviewees report methodology-conflicting advice that was materially disruptive
- SLA missed on 20%+ of engagements over a quarter
- Reviewer Affiliate Agreement violation (e.g., upselling reviewees into their own offers during review time)
- Reviewer leaves the direct-response market or does not re-sign quarterly Affiliate Agreement

The list is updated quarterly. Removed reviewers receive 30 days' notice and are not blacklisted from re-entry if conditions change.

---

*Last updated: April 24, 2026 · Version 2.0 · Q2 2026 reviewer list current · Referenced by C4-Peer-Review-Alternate-Protocol*

Preserved source material for study; embedded instructions are not executed. Open original source

# Supabase Schema for C4 Offer Ignition

**Purpose:** Full SQL schema (DDL) for tables C4 reads or writes.
**Audience:** Operator / developer deploying or auditing Build 1.
**Related:** `04_Tools-and-Infrastructure/RISER-Build-References-for-C4.md`

---

## Schema File (c4_schema.sql)

```sql
-- ============================================================================
-- C4 Offer Ignition — Supabase Schema v2.0
-- Last updated: 2026-04-24
-- Depends on: c1_schema.sql, c2_schema.sql, c3_schema.sql
-- ============================================================================

-- ============================================================================
-- Table: c4_offer_distinctions (M4.1)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_offer_distinctions (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  distinction_memo_drive_file_id TEXT NOT NULL,
  component_inventory_drive_file_id TEXT NOT NULL,
  ai_rubric_score INT NOT NULL CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (ai_rubric_score >= 7) STORED,
  c3_market_fit_hypothesis_id UUID REFERENCES public.c3_market_fit_hypotheses(id),
  c3_primary_mechanism_name TEXT NOT NULL,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id, distinction_memo_drive_file_id)
);

CREATE INDEX idx_c4_offer_distinctions_user ON public.c4_offer_distinctions(user_id);

ALTER TABLE public.c4_offer_distinctions ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own distinction memos" ON public.c4_offer_distinctions
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own distinction memos" ON public.c4_offer_distinctions
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own distinction memos" ON public.c4_offer_distinctions
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_value_equations (M4.2)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_value_equations (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  worksheet_drive_file_id TEXT NOT NULL,
  dream_outcome_strength TEXT CHECK (dream_outcome_strength IN ('Strong', 'Moderate', 'Weak')),
  perceived_likelihood_strength TEXT CHECK (perceived_likelihood_strength IN ('Strong', 'Moderate', 'Weak')),
  time_delay_strength TEXT CHECK (time_delay_strength IN ('Strong', 'Moderate', 'Weak')),
  effort_sacrifice_strength TEXT CHECK (effort_sacrifice_strength IN ('Strong', 'Moderate', 'Weak')),
  strongest_variable TEXT NOT NULL CHECK (strongest_variable IN ('Dream Outcome','Perceived Likelihood','Time Delay','Effort & Sacrifice')),
  weakest_variable TEXT NOT NULL CHECK (weakest_variable IN ('Dream Outcome','Perceived Likelihood','Time Delay','Effort & Sacrifice')),
  trigger_bank_citations_count INT NOT NULL CHECK (trigger_bank_citations_count >= 3),
  interview_citations_count INT NOT NULL CHECK (interview_citations_count >= 1),
  ai_rubric_score INT NOT NULL CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (ai_rubric_score >= 7) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_value_equations_user ON public.c4_value_equations(user_id);

ALTER TABLE public.c4_value_equations ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own value equations" ON public.c4_value_equations
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own value equations" ON public.c4_value_equations
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own value equations" ON public.c4_value_equations
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_offer_decompositions (M4.3)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_offer_decompositions (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  decomposition_drive_file_id TEXT NOT NULL,
  variants_drive_file_id TEXT NOT NULL,
  decomposed_deliverables_count INT NOT NULL CHECK (decomposed_deliverables_count BETWEEN 6 AND 10),
  variant_a_name TEXT NOT NULL,
  variant_a_engagement_model TEXT NOT NULL CHECK (variant_a_engagement_model IN ('Cohort','1:1','Self-paced','Hybrid')),
  variant_a_duration_weeks INT NOT NULL,
  variant_a_deliverable_count INT NOT NULL CHECK (variant_a_deliverable_count <= 8),
  variant_a_price_band_low INT,
  variant_a_price_band_high INT,
  variant_b_name TEXT NOT NULL,
  variant_b_engagement_model TEXT NOT NULL CHECK (variant_b_engagement_model IN ('Cohort','1:1','Self-paced','Hybrid')),
  variant_b_duration_weeks INT NOT NULL,
  variant_b_deliverable_count INT NOT NULL CHECK (variant_b_deliverable_count <= 8),
  variant_b_price_band_low INT,
  variant_b_price_band_high INT,
  variant_c_name TEXT NOT NULL,
  variant_c_engagement_model TEXT NOT NULL CHECK (variant_c_engagement_model IN ('Cohort','1:1','Self-paced','Hybrid')),
  variant_c_duration_weeks INT NOT NULL,
  variant_c_deliverable_count INT NOT NULL CHECK (variant_c_deliverable_count <= 8),
  variant_c_price_band_low INT,
  variant_c_price_band_high INT,
  structural_verification_passed BOOLEAN NOT NULL,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

-- Enforce axis divergence via constraint: at least one of (engagement model, duration, deliverable count) differs pairwise
-- (This is a soft check; deeper divergence check lives in offer-decomposition-reviewer prompt)
ALTER TABLE public.c4_offer_decompositions ADD CONSTRAINT c4_od_ab_divergence
  CHECK (
    variant_a_engagement_model <> variant_b_engagement_model OR
    variant_a_duration_weeks <> variant_b_duration_weeks OR
    variant_a_deliverable_count <> variant_b_deliverable_count
  );
ALTER TABLE public.c4_offer_decompositions ADD CONSTRAINT c4_od_ac_divergence
  CHECK (
    variant_a_engagement_model <> variant_c_engagement_model OR
    variant_a_duration_weeks <> variant_c_duration_weeks OR
    variant_a_deliverable_count <> variant_c_deliverable_count
  );
ALTER TABLE public.c4_offer_decompositions ADD CONSTRAINT c4_od_bc_divergence
  CHECK (
    variant_b_engagement_model <> variant_c_engagement_model OR
    variant_b_duration_weeks <> variant_c_duration_weeks OR
    variant_b_deliverable_count <> variant_c_deliverable_count
  );

CREATE INDEX idx_c4_offer_decompositions_user ON public.c4_offer_decompositions(user_id);

ALTER TABLE public.c4_offer_decompositions ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own decompositions" ON public.c4_offer_decompositions
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own decompositions" ON public.c4_offer_decompositions
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own decompositions" ON public.c4_offer_decompositions
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_pricing_decisions (M4.4)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_pricing_decisions (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  pricing_decision_drive_file_id TEXT NOT NULL,
  observed_band_floor INT NOT NULL,
  observed_band_median INT NOT NULL,
  observed_band_ceiling INT NOT NULL,
  anchor_price INT NOT NULL CHECK (anchor_price > 0),
  pricing_strategy TEXT NOT NULL CHECK (pricing_strategy IN ('Median','Above Market','Below Market (Volume)','Other')),
  pay_in_full_price INT NOT NULL,
  installment_option TEXT,
  deposit_option TEXT,
  unit_economics_hours_per_buyer NUMERIC,
  unit_economics_effective_hourly_rate NUMERIC,
  deviation_from_band_rationale TEXT,
  ai_rubric_score INT NOT NULL CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (ai_rubric_score >= 7) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_pricing_decisions_user ON public.c4_pricing_decisions(user_id);

ALTER TABLE public.c4_pricing_decisions ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own pricing" ON public.c4_pricing_decisions
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own pricing" ON public.c4_pricing_decisions
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own pricing" ON public.c4_pricing_decisions
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_anti_promises (M4.5)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_anti_promises (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  anti_promise_drive_file_id TEXT NOT NULL,
  integrity_statement_drive_file_id TEXT NOT NULL,
  integrity_statement_signed BOOLEAN NOT NULL DEFAULT FALSE,
  audience_exclusions_count INT NOT NULL CHECK (audience_exclusions_count BETWEEN 3 AND 6),
  outcome_non_claims_count INT NOT NULL CHECK (outcome_non_claims_count >= 2),
  scope_boundaries_count INT NOT NULL CHECK (scope_boundaries_count >= 2),
  ai_rubric_score INT NOT NULL CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (ai_rubric_score >= 7 AND integrity_statement_signed) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_anti_promises_user ON public.c4_anti_promises(user_id);

ALTER TABLE public.c4_anti_promises ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own anti-promises" ON public.c4_anti_promises
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own anti-promises" ON public.c4_anti_promises
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own anti-promises" ON public.c4_anti_promises
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_guarantees (M4.6)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_guarantees (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  guarantee_drive_file_id TEXT NOT NULL,
  honesty_clause_drive_file_id TEXT NOT NULL,
  honesty_clause_signed BOOLEAN NOT NULL DEFAULT FALSE,
  guarantee_type TEXT NOT NULL CHECK (guarantee_type IN ('Refund','Outcome','Hybrid','Time-shift','Effort-adjusted')),
  guarantee_component_count INT NOT NULL CHECK (guarantee_component_count <= 2),
  targets_weakness TEXT NOT NULL CHECK (targets_weakness IN ('Perceived Likelihood','Time Delay','Effort & Sacrifice')),
  expected_activation_rate_pct NUMERIC,
  unit_economics_sustainable BOOLEAN NOT NULL,
  ai_rubric_score INT NOT NULL CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (ai_rubric_score >= 7 AND honesty_clause_signed) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_guarantees_user ON public.c4_guarantees(user_id);

ALTER TABLE public.c4_guarantees ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own guarantees" ON public.c4_guarantees
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own guarantees" ON public.c4_guarantees
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own guarantees" ON public.c4_guarantees
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_landing_page_copies (M4.7)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_landing_page_copies (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  landing_page_drive_file_id TEXT NOT NULL,
  provenance_log_drive_file_id TEXT NOT NULL,
  revision_log_drive_file_id TEXT,
  total_word_count INT NOT NULL CHECK (total_word_count BETWEEN 1000 AND 5000),
  trigger_bank_entries_claimed INT NOT NULL CHECK (trigger_bank_entries_claimed >= 15),
  trigger_bank_entries_verified_verbatim INT NOT NULL,
  peer_review_1_reviewer_id UUID REFERENCES public.users(id),
  peer_review_1_completed_at TIMESTAMPTZ,
  peer_review_2_reviewer_id UUID REFERENCES public.users(id),
  peer_review_2_completed_at TIMESTAMPTZ,
  peer_reviews_complete BOOLEAN GENERATED ALWAYS AS (peer_review_1_completed_at IS NOT NULL AND peer_review_2_completed_at IS NOT NULL) STORED,
  ai_rubric_score INT CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (
    ai_rubric_score >= 7 AND
    peer_review_1_completed_at IS NOT NULL AND
    peer_review_2_completed_at IS NOT NULL AND
    trigger_bank_entries_verified_verbatim >= 15
  ) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_landing_page_copies_user ON public.c4_landing_page_copies(user_id);

ALTER TABLE public.c4_landing_page_copies ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own landing pages" ON public.c4_landing_page_copies
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own landing pages" ON public.c4_landing_page_copies
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own landing pages" ON public.c4_landing_page_copies
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_offer_readiness_docs (M4.8 — course completion artifact)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_offer_readiness_docs (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  readiness_doc_drive_file_id TEXT NOT NULL,
  first_sale_readiness_checklist_drive_file_id TEXT NOT NULL,
  selected_variant TEXT NOT NULL CHECK (selected_variant IN ('A','B','C')),
  final_offer_name TEXT NOT NULL,
  final_anchor_price INT NOT NULL,
  signature_signed BOOLEAN NOT NULL DEFAULT FALSE,
  opus_validator_verdict TEXT CHECK (opus_validator_verdict IN ('PASS','NEEDS_REVISION','FAIL')),
  opus_validator_run_at TIMESTAMPTZ,
  kill_criteria_count INT NOT NULL CHECK (kill_criteria_count >= 3),
  passed BOOLEAN GENERATED ALWAYS AS (
    opus_validator_verdict = 'PASS' AND
    signature_signed
  ) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_offer_readiness_docs_user ON public.c4_offer_readiness_docs(user_id);

ALTER TABLE public.c4_offer_readiness_docs ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own readiness docs" ON public.c4_offer_readiness_docs
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own readiness docs" ON public.c4_offer_readiness_docs
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own readiness docs" ON public.c4_offer_readiness_docs
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_review_log (audit trail for all review prompt calls)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_review_log (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  module TEXT NOT NULL CHECK (module IN ('M4.1','M4.2','M4.3','M4.4','M4.5','M4.6','M4.7','M4.8')),
  prompt_name TEXT NOT NULL,
  prompt_version TEXT NOT NULL,
  submission_count INT NOT NULL DEFAULT 1,
  verdict TEXT NOT NULL CHECK (verdict IN ('PASS','FAIL','NEEDS_REVISION')),
  score INT,
  feedback_json JSONB,
  flags_json JSONB,
  ran_at TIMESTAMPTZ DEFAULT NOW()
);

CREATE INDEX idx_c4_review_log_user_module ON public.c4_review_log(user_id, module);

ALTER TABLE public.c4_review_log ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own review log" ON public.c4_review_log
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Service inserts review log" ON public.c4_review_log
  FOR INSERT WITH CHECK (TRUE); -- service role only; Build 6 writes


-- ============================================================================
-- Column addition: users table
-- ============================================================================
ALTER TABLE public.users
  ADD COLUMN IF NOT EXISTS c4_complete BOOLEAN DEFAULT FALSE,
  ADD COLUMN IF NOT EXISTS c4_completed_at TIMESTAMPTZ,
  ADD COLUMN IF NOT EXISTS c4_lead_variant TEXT,
  ADD COLUMN IF NOT EXISTS c4_final_offer_name TEXT,
  ADD COLUMN IF NOT EXISTS c4_final_anchor_price INT;


-- ============================================================================
-- Function: check_c4_enrollment_eligible(user_id)
-- ============================================================================
CREATE OR REPLACE FUNCTION public.check_c4_enrollment_eligible(p_user_id UUID)
RETURNS JSONB AS $$
DECLARE
  v_missing TEXT[] := ARRAY[]::TEXT[];
  v_user RECORD;
BEGIN
  SELECT c1_complete, c2_complete, c3_complete, captains_oath_signed_at, operator_identity_filed_at
    INTO v_user FROM public.users WHERE id = p_user_id;

  IF NOT COALESCE(v_user.c3_complete, FALSE) THEN
    v_missing := array_append(v_missing, 'c3_complete');
  END IF;

  IF NOT EXISTS (
    SELECT 1 FROM public.c3_market_fit_hypotheses
    WHERE user_id = p_user_id
      AND filed_at > (NOW() - INTERVAL '3 months')
  ) THEN
    v_missing := array_append(v_missing, 'c3_market_fit_hypothesis_within_3_months');
  END IF;

  IF NOT EXISTS (
    SELECT 1 FROM public.c3_trigger_banks
    WHERE user_id = p_user_id AND total_entries >= 200
  ) THEN
    v_missing := array_append(v_missing, 'c3_trigger_bank_200_plus');
  END IF;

  IF NOT EXISTS (
    SELECT 1 FROM public.c3_pricing_signals
    WHERE user_id = p_user_id
  ) THEN
    v_missing := array_append(v_missing, 'c3_pricing_signals');
  END IF;

  IF v_user.captains_oath_signed_at IS NULL OR v_user.captains_oath_signed_at < (NOW() - INTERVAL '12 months') THEN
    v_missing := array_append(v_missing, 'captains_oath_signed_within_12_months');
  END IF;

  RETURN jsonb_build_object(
    'eligible', array_length(v_missing, 1) IS NULL,
    'missing', v_missing
  );
END;
$$ LANGUAGE plpgsql SECURITY DEFINER;


-- ============================================================================
-- Function: check_c4_completion(user_id)
-- ============================================================================
CREATE OR REPLACE FUNCTION public.check_c4_completion(p_user_id UUID)
RETURNS JSONB AS $$
DECLARE
  v_missing TEXT[] := ARRAY[]::TEXT[];
BEGIN
  IF NOT EXISTS (SELECT 1 FROM public.c4_offer_distinctions WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_1_distinction_passed');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_value_equations WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_2_value_equation_passed');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_offer_decompositions WHERE user_id = p_user_id AND structural_verification_passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_3_decomposition_verified');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_pricing_decisions WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_4_pricing_passed');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_anti_promises WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_5_anti_promise_passed_and_signed');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_guarantees WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_6_guarantee_passed_and_signed');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_landing_page_copies WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_7_landing_page_passed_with_peer_reviews');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_offer_readiness_docs WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_8_readiness_doc_opus_passed');
  END IF;

  RETURN jsonb_build_object(
    'complete', array_length(v_missing, 1) IS NULL,
    'missing', v_missing
  );
END;
$$ LANGUAGE plpgsql SECURITY DEFINER;


-- ============================================================================
-- Trigger: mark c4_complete = true when all 8 artifacts pass
-- ============================================================================
CREATE OR REPLACE FUNCTION public.update_c4_complete_flag()
RETURNS TRIGGER AS $$
DECLARE
  v_check JSONB;
  v_readiness RECORD;
BEGIN
  v_check := public.check_c4_completion(NEW.user_id);
  IF (v_check->>'complete')::BOOLEAN = TRUE THEN
    SELECT selected_variant, final_offer_name, final_anchor_price
      INTO v_readiness
      FROM public.c4_offer_readiness_docs
      WHERE user_id = NEW.user_id AND passed = TRUE
      LIMIT 1;
    UPDATE public.users
      SET c4_complete = TRUE,
          c4_completed_at = NOW(),
          c4_lead_variant = v_readiness.selected_variant,
          c4_final_offer_name = v_readiness.final_offer_name,
          c4_final_anchor_price = v_readiness.final_anchor_price
      WHERE id = NEW.user_id;
  END IF;
  RETURN NEW;
END;
$$ LANGUAGE plpgsql;

CREATE TRIGGER tr_c4_completion_check
  AFTER INSERT OR UPDATE ON public.c4_offer_readiness_docs
  FOR EACH ROW
  WHEN (NEW.passed = TRUE)
  EXECUTE FUNCTION public.update_c4_complete_flag();
```

---

## Schema Design Notes

### Generated passed columns

Most tables use `GENERATED ALWAYS AS (...) STORED` for the `passed` column. This enforces the pass logic at the database layer rather than in application code — a landing page row with `ai_rubric_score = 8` but `peer_reviews_complete = FALSE` is automatically not-passed. Application code cannot accidentally flip the flag.

### Axis divergence constraints on c4_offer_decompositions

Database constraints catch the simplest failure mode (three variants that are structurally identical). Deeper divergence checks (e.g., "variant B and C differ on only price, which is not enough") are enforced by the offer-decomposition-reviewer prompt, not at the database layer. Database enforces the minimum; the prompt enforces the quality.

### Feature Stuffing constraints

The `CHECK (deliverable_count <= 8)` constraints on each variant prevent Feature Stuffing at the row level. A student cannot file a variant with 12 deliverables — the insert fails. This is the database-layer companion to the offer-decomposition-reviewer prompt's Feature Stuffing Flag.

### Integrity Statement / Honesty Clause enforcement

`c4_anti_promises` and `c4_guarantees` tables have `passed` generated columns that require both the rubric score and the signed statement. Unsigned submissions cannot pass, regardless of rubric score. This is structural enforcement of the Integrity Policy.

### Opus gating on c4_offer_readiness_docs

The `passed` flag requires Opus validator verdict = PASS AND signature_signed. A Sonnet-passed but Opus-pending row is stored but does not count as passed. C4 completion cannot occur without explicit Opus verdict.

---

## Migration Notes

This schema depends on `c1_schema.sql`, `c2_schema.sql`, and `c3_schema.sql` being deployed first. Run in sequence:

```bash
psql -h <host> -U <user> -d <db> -f c1_schema.sql
psql -h <host> -U <user> -d <db> -f c2_schema.sql
psql -h <host> -U <user> -d <db> -f c3_schema.sql
psql -h <host> -U <user> -d <db> -f c4_schema.sql
```

The `c4_complete` column addition on `public.users` is idempotent via `ADD COLUMN IF NOT EXISTS`.

---

## Referenced By

- `03_Scripts-and-Prompts/Prompt-Chains/C4-Review-Chain.md` — routing functions
- `00_Course-Overview/C4-Prerequisites-Checklist.md` — `check_c4_enrollment_eligible` reference
- Build 6 `src/c4_checkpoint_handler.ts` — all insert/update calls
- `06_SOPs/RISER-C4-Weekly-Rhythm-Setup-SOP.md` — operational integration

---

*Last updated: April 24, 2026 · Version 2.0*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Offer Variants Worksheet

**Purpose:** M4.3 deliverable. Produces three distinct reassembly variants of the Primary mechanism into offer form, honoring the 6% Rule commitment.
**Target length:** 1,500-2,000 words total (500-700 per variant)
**Time to complete:** ~180 minutes (with 48-hour cooling between first and second drafts)
**Filed to:** Build 8 Drive folder, `c4_offer_decompositions` Supabase table
**Reviewed by:** `offer-decomposition-reviewer-v1.0.0.yaml` (structural check)

---

## Before You Start

Three things must exist in Drive before this worksheet opens:

1. **Mechanism Decomposition Inventory** — your mechanism's Method pillar broken into named deliverables (produce this as a separate document at `Mechanism-Decomposition-[YourName]-[Date].md`)
2. **M4.2 Value Equation Worksheet** — identifies which variables are strong/weak/fixed
3. **M4.1 Component Inventory** — which offer components have material, which need production

Open all three alongside this worksheet. You will reference them repeatedly.

---

## Part 1 — Decomposition (completed before Part 2)

In your separate Mechanism Decomposition Inventory document (400-600 words), complete:

1. **Primary mechanism's Method pillar** (pasted from C2 Hypothesis Document)
2. **Decomposed deliverables** — each named, scoped such that a buyer could evaluate it in isolation
3. **Deliverable properties** — each with: name, type (audit / template / live call / async review / reference pack / tracker / contract component / other), duration (hours or session), delivery format, dependency (which other deliverables must come first)

**Quality test for each deliverable:** can a buyer reading the description answer "what will I have at the end of this?" If yes, it is a deliverable. If no, it is a delivery activity, not a deliverable. Fix before proceeding.

Typical count: 6-10 deliverables emerge from a well-structured 4-pillar mechanism.

---

## Part 2 — The Three Variants

Complete three variant sections below. Each variant must differ from the other two on **at least 3 of 4 axes**:

- **Engagement model** — cohort / 1:1 / self-paced / hybrid
- **Duration** — short (2-4 weeks) / medium (5-8 weeks) / long (9+ weeks)
- **Deliverable density** — high (all decomposed deliverables) / medium (5-6) / low (3-4 self-serve)
- **Price band** — floor / median / ceiling of the observed C3 range

---

### Variant A — [Variant placeholder name]

#### 1. Variant Name
[Placeholder name — 5-Test re-run happens at end of this worksheet]

#### 2. Engagement Model
[Cohort / 1:1 / Self-paced / Hybrid]

*Rationale (1-2 sentences):*

#### 3. Duration
[Weeks, with start-date cadence — synchronous vs rolling]

*Rationale (1-2 sentences):*

#### 4. Deliverables Included
Pull from your decomposition inventory. List included deliverables; note any excluded or available-as-add-on.

- ✓ [Deliverable 1]
- ✓ [Deliverable 2]
- ...
- ✗ [Deliverable X — excluded from this variant]
- + [Deliverable Y — available as add-on]

#### 5. Price Band Placeholder
$[X] - $[Y] range. (Single-number anchor is selected in M4.4; this is the band.)

*Position against observed C3 band:* [floor / mid-floor / median / mid-ceiling / ceiling / above ceiling]

#### 6. Value Equation Weakness Targeted
Which M4.2-identified weakness does this variant specifically address?

- **Primary target:** [Dream Outcome / Perceived Likelihood / Time Delay / Effort & Sacrifice]
- **Secondary target:** [optional]

*How this variant targets that weakness (1-2 sentences):*

#### 7. Buyer Fit
Which sub-segment of your C3 interview pool fits this variant best?

- **Target sub-segment:** [description]
- **Approximate # of C3 interviewees fitting this profile:** ___ of [total interviews]
- **Key interview citations:** Interview #__ (name), #__ (name)

#### 8. Known Tradeoffs
What does this variant sacrifice compared to Variants B and C?

- vs. Variant B: [tradeoff]
- vs. Variant C: [tradeoff]

---

### Variant B — [Variant placeholder name]

[Same 8-section structure as Variant A. Reminder: must differ from Variants A and C on at least 3 of 4 axes.]

#### 1. Variant Name
#### 2. Engagement Model
#### 3. Duration
#### 4. Deliverables Included
#### 5. Price Band Placeholder
#### 6. Value Equation Weakness Targeted
#### 7. Buyer Fit
#### 8. Known Tradeoffs

---

### Variant C — [Variant placeholder name]

[Same 8-section structure. Must differ from Variants A and B on at least 3 of 4 axes.]

#### 1. Variant Name
#### 2. Engagement Model
#### 3. Duration
#### 4. Deliverables Included
#### 5. Price Band Placeholder
#### 6. Value Equation Weakness Targeted
#### 7. Buyer Fit
#### 8. Known Tradeoffs

---

## Part 3 — Cross-Variant Comparison

### Axis Divergence Matrix

Confirm each variant differs from the other two on at least 3 of 4 axes:

| Axis | Variant A | Variant B | Variant C | All 3 distinct? |
|---|---|---|---|---|
| Engagement model | [] | [] | [] | ☐ Yes ☐ No |
| Duration | [] | [] | [] | ☐ Yes ☐ No |
| Deliverable density | [] | [] | [] | ☐ Yes ☐ No |
| Price band | [] | [] | [] | ☐ Yes ☐ No |

**Minimum 3 of 4 "Yes" per variant required.** If only 2 of 4, the variants are not sufficiently distinct — revise.

### Feature Stuffing Check

Count the deliverables in each variant:

- Variant A: ___ deliverables
- Variant B: ___ deliverables
- Variant C: ___ deliverables

**If any variant has > 8 deliverables, flag for review.** More than 8 typically indicates the Feature Stuffing Trap — deliverables added to compensate for weak numerator variables rather than to produce real value. See `07_Case-Studies-and-Examples/Case-Failure-The-Feature-Stuffing-Trap.md`.

### 5-Test Naming Re-Run

Apply the C2 5-Test Naming Filter to each variant's placeholder name:

| Test | Variant A | Variant B | Variant C |
|---|---|---|---|
| Searchable | ☐ ☐ | ☐ ☐ | ☐ ☐ |
| Specific | ☐ ☐ | ☐ ☐ | ☐ ☐ |
| Durable | ☐ ☐ | ☐ ☐ | ☐ ☐ |
| Pronounceable | ☐ ☐ | ☐ ☐ | ☐ ☐ |
| Ownable | ☐ ☐ | ☐ ☐ | ☐ ☐ |
| **All 5 pass?** | ☐ Y ☐ N | ☐ Y ☐ N | ☐ Y ☐ N |

Variants failing 1+ tests need renaming before M4.4.

---

## Part 4 — Preliminary Lead-Variant Note (optional but useful)

Formal variant selection is an M4.8 activity, but often M4.3 surfaces a preliminary lead. Note your current thinking (revisit at M4.8):

- **Current leaning toward:** Variant [A / B / C]
- **Why:** [1-2 sentences]
- **What I want to see at M4.4 before committing:** [pricing plausibility check, unit-economic viability, etc.]

Leave this section light. M4.4-M4.7 will pressure-test all three from different angles before M4.8 selects.

---

## Signature

**Operator name:** _____________________________
**Date of first draft:** _____________________________
**Date of second draft (after 48-hour cooling):** _____________________________
**Total word count (all three variants):** _______ (target 1,500-2,000)

---

## What Happens Next

The three-variant document is filed to Drive alongside the Mechanism Decomposition Inventory. Structural verification checks:

- Exactly 3 variants present, each 500-700 words
- Each variant differs on ≥ 3 of 4 axes from the other two
- No variant has > 8 primary deliverables
- 5-Test applied to each variant's name

On pass, M4.4 unlocks. Pricing is selected against at least one variant (typically all three, which often clarifies lead-variant selection).

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.3*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Offer Variants Worksheet

**Purpose:** M4.3 deliverable. Produces three distinct reassembly variants of the Primary mechanism into offer form, honoring the 6% Rule commitment.
**Target length:** 1,500-2,000 words total (500-700 per variant)
**Time to complete:** ~180 minutes (with 48-hour cooling between first and second drafts)
**Filed to:** Build 8 Drive folder, `c4_offer_decompositions` Supabase table
**Reviewed by:** `offer-decomposition-reviewer-v1.0.0.yaml` (structural check)

---

## Before You Start

Three things must exist in Drive before this worksheet opens:

1. **Mechanism Decomposition Inventory** — your mechanism's Method pillar broken into named deliverables (produce this as a separate document at `Mechanism-Decomposition-[YourName]-[Date].md`)
2. **M4.2 Value Equation Worksheet** — identifies which variables are strong/weak/fixed
3. **M4.1 Component Inventory** — which offer components have material, which need production

Open all three alongside this worksheet. You will reference them repeatedly.

---

## Part 1 — Decomposition (completed before Part 2)

In your separate Mechanism Decomposition Inventory document (400-600 words), complete:

1. **Primary mechanism's Method pillar** (pasted from C2 Hypothesis Document)
2. **Decomposed deliverables** — each named, scoped such that a buyer could evaluate it in isolation
3. **Deliverable properties** — each with: name, type (audit / template / live call / async review / reference pack / tracker / contract component / other), duration (hours or session), delivery format, dependency (which other deliverables must come first)

**Quality test for each deliverable:** can a buyer reading the description answer "what will I have at the end of this?" If yes, it is a deliverable. If no, it is a delivery activity, not a deliverable. Fix before proceeding.

Typical count: 6-10 deliverables emerge from a well-structured 4-pillar mechanism.

---

## Part 2 — The Three Variants

Complete three variant sections below. Each variant must differ from the other two on **at least 3 of 4 axes**:

- **Engagement model** — cohort / 1:1 / self-paced / hybrid
- **Duration** — short (2-4 weeks) / medium (5-8 weeks) / long (9+ weeks)
- **Deliverable density** — high (all decomposed deliverables) / medium (5-6) / low (3-4 self-serve)
- **Price band** — floor / median / ceiling of the observed C3 range

---

### Variant A — [Variant placeholder name]

#### 1. Variant Name
[Placeholder name — 5-Test re-run happens at end of this worksheet]

#### 2. Engagement Model
[Cohort / 1:1 / Self-paced / Hybrid]

*Rationale (1-2 sentences):*

#### 3. Duration
[Weeks, with start-date cadence — synchronous vs rolling]

*Rationale (1-2 sentences):*

#### 4. Deliverables Included
Pull from your decomposition inventory. List included deliverables; note any excluded or available-as-add-on.

- ✓ [Deliverable 1]
- ✓ [Deliverable 2]
- ...
- ✗ [Deliverable X — excluded from this variant]
- + [Deliverable Y — available as add-on]

#### 5. Price Band Placeholder
$[X] - $[Y] range. (Single-number anchor is selected in M4.4; this is the band.)

*Position against observed C3 band:* [floor / mid-floor / median / mid-ceiling / ceiling / above ceiling]

#### 6. Value Equation Weakness Targeted
Which M4.2-identified weakness does this variant specifically address?

- **Primary target:** [Dream Outcome / Perceived Likelihood / Time Delay / Effort & Sacrifice]
- **Secondary target:** [optional]

*How this variant targets that weakness (1-2 sentences):*

#### 7. Buyer Fit
Which sub-segment of your C3 interview pool fits this variant best?

- **Target sub-segment:** [description]
- **Approximate # of C3 interviewees fitting this profile:** ___ of [total interviews]
- **Key interview citations:** Interview #__ (name), #__ (name)

#### 8. Known Tradeoffs
What does this variant sacrifice compared to Variants B and C?

- vs. Variant B: [tradeoff]
- vs. Variant C: [tradeoff]

---

### Variant B — [Variant placeholder name]

[Same 8-section structure as Variant A. Reminder: must differ from Variants A and C on at least 3 of 4 axes.]

#### 1. Variant Name
#### 2. Engagement Model
#### 3. Duration
#### 4. Deliverables Included
#### 5. Price Band Placeholder
#### 6. Value Equation Weakness Targeted
#### 7. Buyer Fit
#### 8. Known Tradeoffs

---

### Variant C — [Variant placeholder name]

[Same 8-section structure. Must differ from Variants A and B on at least 3 of 4 axes.]

#### 1. Variant Name
#### 2. Engagement Model
#### 3. Duration
#### 4. Deliverables Included
#### 5. Price Band Placeholder
#### 6. Value Equation Weakness Targeted
#### 7. Buyer Fit
#### 8. Known Tradeoffs

---

## Part 3 — Cross-Variant Comparison

### Axis Divergence Matrix

Confirm each variant differs from the other two on at least 3 of 4 axes:

| Axis | Variant A | Variant B | Variant C | All 3 distinct? |
|---|---|---|---|---|
| Engagement model | [] | [] | [] | ☐ Yes ☐ No |
| Duration | [] | [] | [] | ☐ Yes ☐ No |
| Deliverable density | [] | [] | [] | ☐ Yes ☐ No |
| Price band | [] | [] | [] | ☐ Yes ☐ No |

**Minimum 3 of 4 "Yes" per variant required.** If only 2 of 4, the variants are not sufficiently distinct — revise.

### Feature Stuffing Check

Count the deliverables in each variant:

- Variant A: ___ deliverables
- Variant B: ___ deliverables
- Variant C: ___ deliverables

**If any variant has > 8 deliverables, flag for review.** More than 8 typically indicates the Feature Stuffing Trap — deliverables added to compensate for weak numerator variables rather than to produce real value. See `07_Case-Studies-and-Examples/Case-Failure-The-Feature-Stuffing-Trap.md`.

### 5-Test Naming Re-Run

Apply the C2 5-Test Naming Filter to each variant's placeholder name:

| Test | Variant A | Variant B | Variant C |
|---|---|---|---|
| Searchable | ☐ ☐ | ☐ ☐ | ☐ ☐ |
| Specific | ☐ ☐ | ☐ ☐ | ☐ ☐ |
| Durable | ☐ ☐ | ☐ ☐ | ☐ ☐ |
| Pronounceable | ☐ ☐ | ☐ ☐ | ☐ ☐ |
| Ownable | ☐ ☐ | ☐ ☐ | ☐ ☐ |
| **All 5 pass?** | ☐ Y ☐ N | ☐ Y ☐ N | ☐ Y ☐ N |

Variants failing 1+ tests need renaming before M4.4.

---

## Part 4 — Preliminary Lead-Variant Note (optional but useful)

Formal variant selection is an M4.8 activity, but often M4.3 surfaces a preliminary lead. Note your current thinking (revisit at M4.8):

- **Current leaning toward:** Variant [A / B / C]
- **Why:** [1-2 sentences]
- **What I want to see at M4.4 before committing:** [pricing plausibility check, unit-economic viability, etc.]

Leave this section light. M4.4-M4.7 will pressure-test all three from different angles before M4.8 selects.

---

## Signature

**Operator name:** _____________________________
**Date of first draft:** _____________________________
**Date of second draft (after 48-hour cooling):** _____________________________
**Total word count (all three variants):** _______ (target 1,500-2,000)

---

## What Happens Next

The three-variant document is filed to Drive alongside the Mechanism Decomposition Inventory. Structural verification checks:

- Exactly 3 variants present, each 500-700 words
- Each variant differs on ≥ 3 of 4 axes from the other two
- No variant has > 8 primary deliverables
- 5-Test applied to each variant's name

On pass, M4.4 unlocks. Pricing is selected against at least one variant (typically all three, which often clarifies lead-variant selection).

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.3*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Prompt Chain — M4.1 through M4.8 Review Orchestration

**Purpose:** Documents the sequencing of the 6 C4 Claude system prompts across module checkpoints. Referenced by Build 6 when routing student submissions to reviewers and gating module unlock.
**Filed to:** `03_Scripts-and-Prompts/Prompt-Chains/`
**Referenced by:** Build 6 checkpoint handler; `04_Tools-and-Infrastructure/Supabase-C4-Schema.md`

---

## Chain Overview

C4 uses 6 system prompts across 8 checkpoints. Five are Sonnet-powered (routine review) and one is Opus-powered (course-completion gate). The chain is serial — each module's review must issue PASS before the next module's checkpoint can receive submissions.

```mermaid
graph TD
    M41_sub[M4.1 submission] --> P1[offer-distinction-reviewer<br/>Sonnet 4.6]
    P1 -->|PASS >=7/10| M42_sub[M4.2 unlocks]
    P1 -->|FAIL <7/10| M41_rev[M4.1 revision]
    M41_rev --> P1

    M42_sub --> P2[value-equation-application-reviewer<br/>Sonnet 4.6]
    P2 -->|PASS >=7/10| M43_sub[M4.3 unlocks]
    P2 -->|FAIL| M42_rev[M4.2 revision]

    M43_sub --> P3[offer-decomposition-reviewer<br/>Sonnet 4.6<br/>Structural only]
    P3 -->|PASS| M44[M4.4 unlocks]
    P3 -->|NEEDS_REVISION| M43_rev[M4.3 revision]

    M44 --> M44_review[M4.4 reviewed by<br/>offer-readiness-reviewer spot-check]
    M44_review -->|PASS| M45[M4.5 unlocks]

    M45 --> M45_review[M4.5 reviewed by<br/>offer-readiness-reviewer spot-check]
    M45_review -->|PASS| M46[M4.6 unlocks]

    M46 --> M46_review[M4.6 reviewed by<br/>offer-readiness-reviewer spot-check]
    M46_review -->|PASS| M47_sub[M4.7 unlocks]

    M47_sub --> PEER[2 peer reviews<br/>SLA 72hr]
    PEER --> P4[landing-page-copy-reviewer<br/>Sonnet 4.6]
    P4 -->|PASS >=7/10 AND peer count >=2| M48_sub[M4.8 unlocks]
    P4 -->|FAIL| M47_rev[M4.7 revision]

    M48_sub --> P5[offer-readiness-reviewer<br/>Sonnet 4.6<br/>Structural pre-screen]
    P5 -->|PASS| P6[offer-fit-validator<br/>OPUS 4.7<br/>Full coherence check]
    P5 -->|NEEDS_REVISION| M48_rev[M4.8 revision]

    P6 -->|PASS| COMPLETE([C4 Complete<br/>C5 Unlocks])
    P6 -->|NEEDS_REVISION| M48_rev
    P6 -->|FAIL| MENTOR[Mentor diagnosis<br/>Likely C3 M3.7 issue]

    style P6 fill:#B45F06,color:#fff
    style COMPLETE fill:#2E75B6,color:#fff
    style MENTOR fill:#CC0000,color:#fff
    style PEER fill:#BF9000,color:#fff
```

---

## Prompt Inventory

| # | Prompt File | Model | Called At | Cost per call | Typical volume |
|---|---|---|---|---|---|
| 1 | offer-distinction-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.1 checkpoint | $0.04-0.08 | 1-2 per student |
| 2 | value-equation-application-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.2 checkpoint | $0.04-0.08 | 1-2 per student |
| 3 | offer-decomposition-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.3 checkpoint | $0.04-0.08 | 1-2 per student |
| 4 | landing-page-copy-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.7 checkpoint (after peer review) | $0.06-0.12 | 1-2 per student |
| 5 | offer-readiness-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.4, M4.5, M4.6 spot-check + M4.8 pre-screen | $0.04-0.08 | 3-5 per student |
| 6 | offer-fit-validator-v1.0.0.yaml | **Opus 4.7** | M4.8 course-completion | **$0.30-0.55** | 1-2 per student |

**Total C4 review cost per student:** $0.80-$1.50 across the chain (most students complete in 1-2 submissions per module).

---

## Orchestration Rules

### Serial Dependency Enforcement

Module unlock only occurs when the prior module's review has returned PASS. A student cannot submit M4.3 until M4.2 has PASSED. This prevents coherence collapse — a student with a miscalibrated Value Equation should not be producing decomposition variants targeted at the wrong weakness.

### Revision Loop

For each module:
- First submission → review → PASS or revision guidance
- Second submission (after revision) → review → PASS or mentor escalation
- Third submission → mentor routing (rare; indicates fundamental issue with prior module outputs)

Build 6 tracks submission count per module; the third attempt auto-routes to mentor queue.

### Peer Review Layer (M4.7 only)

M4.7 is the only module requiring peer review before AI review. The order:

1. Student submits draft to `#c4-offer-ignition`
2. Two peer reviewers complete reviews (SLA 72 hours)
3. Student incorporates peer feedback, produces Revision Log
4. Revised submission routes to landing-page-copy-reviewer (Sonnet)
5. AI reviewer verifies: peer review count ≥ 2, integrity of incorporation, and rubric score

If peer review SLA is missed (cohort thin), Protocol A/B/C from `02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md` applies.

### The Opus Gate (M4.8 only)

M4.8 is the only module routing through two reviewers:

1. **offer-readiness-reviewer (Sonnet)** performs structural pre-screen
2. If Sonnet issues PASS → **offer-fit-validator (Opus 4.7)** performs full coherence check
3. If Sonnet issues FAIL → student revises before Opus is spun up (Opus is ~5-10x the cost of Sonnet; structural pre-screen prevents wasted Opus calls)

The Opus validator's PASS verdict unlocks C5 First Currents enrollment.

### Cross-Reference to Prior Course Outputs

Every prompt in C4 receives the relevant C1-C3 artifacts as input context. This prevents validators from accepting work that has silently drifted from the student's prior commitments:

- **C1 Captain's Oath Clause 1 (territory)** — fed to offer-distinction-reviewer, offer-fit-validator
- **C1 Operator Identity** — fed to offer-fit-validator (archetype consistency)
- **C2 Mechanism Hypothesis Document** — fed to offer-distinction-reviewer (mechanism name anchor)
- **C3 Market Fit Hypothesis** — fed to every C4 reviewer
- **C3 Trigger Bank** — fed to value-equation-application-reviewer, landing-page-copy-reviewer, offer-fit-validator
- **C3 Pricing Signals** — fed to offer-fit-validator
- **C3 Customer Interview Library (summaries)** — fed to value-equation-application-reviewer, offer-fit-validator

Without this context, each reviewer would be scoring the submission against itself rather than against the student's prior work. Cross-reference is what keeps the chain coherent.

---

## Build 6 Integration

Build 6 handles chain orchestration via the following SQL functions (full definitions in `04_Tools-and-Infrastructure/Supabase-C4-Schema.md`):

- `check_c4_enrollment_eligible(user_id)` — prerequisite check at enrollment
- `route_c4_submission(user_id, module, artifact_blob)` — routes to correct reviewer; passes C1-C3 context
- `log_c4_review_result(user_id, module, verdict, feedback)` — writes to `c4_review_log` table
- `unlock_next_c4_module(user_id, current_module)` — gated by prior module PASS
- `check_c4_completion(user_id)` — verifies all 8 artifacts present with PASS status
- `route_c4_to_c5(user_id)` — on course complete, opens C5 enrollment

---

## Failure Mode Routing

| Failure Pattern | Triggered By | Routed To |
|---|---|---|
| Mechanism drift from C3 | offer-fit-validator Check 2.3 BLOCKING | Mentor queue; reopen C3 M3.7 |
| Fabricated Trigger Bank entries | offer-fit-validator Check 2.4 BLOCKING | Integrity review queue |
| Anti-promise softening | offer-fit-validator Check 1.3 WARNING | Revision guidance; student reverts |
| Feature Stuffing (deliverable count, guarantee stack) | Check 4.1, 4.2 WARNING | Revision guidance |
| Silent weakness whitewash | Check 3.1 WARNING | Revision guidance |
| Signature not signed | Check 5.1 BLOCKING | 30-second fix + resubmit |
| Value Equation universal strength | value-equation-application-reviewer Dimension 3 | Revision with honest weakness identification |
| Three variants without axis divergence | offer-decomposition-reviewer Check 2 | Genuine variant diversification required |

---

## Versioning

All prompts are versioned following semver (v1.0.0). Changes to rubric criteria trigger a minor version bump; changes to scoring thresholds trigger a patch bump. Quarterly review cadence is owned by the curriculum-quality team.

When a prompt version changes, Build 6 continues routing existing in-progress submissions to the prior version until the student clears that checkpoint; new submissions after the version bump route to the new version. This prevents mid-revision rubric changes from surprising students.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by Build 6*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Preparation Checklist

**Purpose:** Pre-flight check before submitting M4.7 landing page copy for cohort peer review. Prevents common rework-causing gaps.
**Time to complete:** 15-20 minutes before submission
**Filed to:** Attached to your M4.7 submission

---

## Before You Submit

Running this checklist before posting in `#c4-offer-ignition` saves your peer reviewers 30-60 minutes per review and dramatically increases the quality of feedback you receive. Reviewers who have to hunt for your Trigger Bank Provenance Log, or who notice your anti-promise softened from M4.5, spend their review time on mechanical issues rather than substantive feedback.

---

## Section A — Document Completeness

- [ ] Landing page copy file exists at `Offer-Landing-Page-Copy-[YourName]-[Date].md`
- [ ] All 7 sections present in order:
  - [ ] Section 1 — Problem (200-400 words)
  - [ ] Section 2 — Agitation (150-300 words)
  - [ ] Section 3 — Solution-and-Mechanism (300-500 words)
  - [ ] Section 4 — Proof (200-400 words)
  - [ ] Section 5 — Offer (300-500 words)
  - [ ] Section 6 — Anti-Promise-and-Guarantee (250-400 words)
  - [ ] Section 7 — CTA (50-150 words)
- [ ] Total word count in 1,800-2,500 range (not absurdly over or under)

## Section B — Trigger Bank Usage

- [ ] Trigger Bank Provenance Log file exists at `Landing-Page-Trigger-Bank-Provenance-[YourName]-[Date].md`
- [ ] Log contains ≥ 15 entries mapped to landing page usage
- [ ] Every entry in the log is verbatim (not paraphrased) from the source Trigger Bank
- [ ] Each entry cites specific Trigger Bank ID (TB-###) or Interview #
- [ ] Entries are distributed across 4+ of the 7 sections (not all stacked in one section)

## Section C — Anti-Promise and Guarantee Integrity

- [ ] Anti-Promise in Section 6 is substantively the same as your M4.5 Anti-Promise Statement
- [ ] If any softening occurred between M4.5 and M4.7, it is reverted OR documented with rationale
- [ ] Anti-Promise Integrity Statement is signed
- [ ] Guarantee in Section 6 is substantively the same as your M4.6 Guarantee Architecture
- [ ] If any stacking occurred between M4.6 and M4.7, it is reverted
- [ ] Guarantee Honesty Clause is signed

## Section D — Offer Section Completeness

- [ ] Named deliverable (5-Test-passed name) visible in Section 5
- [ ] Price visible in Section 5 (not hidden, not ranged)
- [ ] Payment options listed
- [ ] Delivery structure described (engagement model, duration, cadence)
- [ ] Deliverables list is not over 8 items (Feature Stuffing Trap check)

## Section E — Proof Integrity

- [ ] Proof cases in Section 4 are specific (named or anonymized with specific outcome)
- [ ] If you have fewer than 4 named cases, the Known Weaknesses acknowledgment is visible (not papered over)
- [ ] Testimonials (if any) are verbatim quotes, not paraphrased
- [ ] Testimonials have attribution (name or anonymized but specific)

## Section F — CTA Specificity

- [ ] CTA names a specific action (not "click here")
- [ ] Next cohort / enrollment date is present
- [ ] Qualification process (if any) is described
- [ ] Contact email or channel is present for pre-purchase questions

## Section G — Voice Check

- [ ] You have read the full landing page out loud once, from start to finish
- [ ] The page does not contain phrases you would not actually say to a buyer in person
- [ ] The page does not contain hyperbole you cannot substantiate
- [ ] The page does not contain any of these phrases: "game-changer," "revolutionary," "transform your life," "all you need to do is" (low-substance signaling vocabulary)

## Section H — Review Request Post

Before posting in `#c4-offer-ignition`, prepare the post:

- [ ] Drive link to landing page copy
- [ ] Drive link to Trigger Bank Provenance Log
- [ ] Brief context (2-3 sentences about your offer's key positioning)
- [ ] Specific request: "2 peer reviews within 72 hours, using the C4 Peer Review Template"
- [ ] Your availability to return review favor (which days you can review others' copy)

---

## Common Pre-Submit Fixes

If any checklist item is unchecked, common fixes:

| Unchecked Item | Typical Fix |
|---|---|
| Section 6 softened from M4.5/M4.6 | Revert to the original M4.5 Anti-Promise and M4.6 Guarantee language |
| Trigger Bank count < 15 | Add 3-6 more verbatim entries, typically in Problem and Agitation sections |
| Deliverables > 8 | Review for Feature Stuffing; which deliverables are compensation, which are real value? |
| Price hidden or ranged | Move price to Section 5 with explicit number |
| Voice check fails | 48-hour cooling re-read; rewrite any section where "did I actually say that?" is your reaction |

---

## After Submission

Once posted:

- [ ] Check `#c4-offer-ignition` daily for reviewer pickup
- [ ] Respond promptly to reviewer questions
- [ ] Do not revise the landing page while reviews are in progress (creates version mismatch)
- [ ] Begin reviewing other cohort peers' landing pages as reviews arrive — reciprocity is cohort norm

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Outreach Scripts

**Purpose:** Short scripts for requesting and responding to peer reviews during M4.7. These are starter templates; adapt in your own voice.
**Filed to:** `03_Scripts-and-Prompts/Outreach-Scripts/`
**Referenced by:** M4.7 Written Lesson; C4-Peer-Review-Preparation-Checklist

---

## Script 1 — Requesting Peer Review (post in `#c4-offer-ignition`)

```
**M4.7 peer review request — [YourName]**

- **Offer name:** [5-Test-passed name]
- **Target buyer:** [one sentence describing who this is for]
- **Price:** $[X]
- **What I want reviewers to watch for specifically:**
  - [1-2 things you suspect may be weak — common: Section 4 Proof, Section 6 Anti-Promise softening, Trigger Bank entry density]

**Drive links:**
- Landing page copy: [link]
- Trigger Bank Provenance Log: [link]
- Revision Log (so far): [link — if you have one]

**SLA:** 72 hours ideal

**Reciprocity:** I'm available to review copy on [specific days this week]. Reply with yours and I'll pick up the first two.

Using the C4 Peer Review Template (`02_Resources/Templates/C4-Peer-Review-Template.md`).
```

### Why this structure works

Naming what you suspect is weak focuses reviewer attention. Without this, reviewers tend to spread feedback thin across the whole page. Concentrated attention on 1-2 sections produces higher-signal feedback.

---

## Script 2 — Offering Peer Review (response to another student's request)

```
I'll pick up your review, [TheirName]. I'll aim to deliver within 48 hours.

If you want me to pay particular attention to [suggested focus based on their request], I will. If you want me to do a straight full-template review, I'll do that too.

My C4 Peer Review Template will be back in your Drive folder or Circle.so thread by [specific date + time].
```

### Why this structure works

Confirms the commitment with a specific delivery time. Acknowledges their request-specific focus areas. Creates accountability for the delivery.

---

## Script 3 — Declining a Peer Review (when over-committed)

```
Thanks for tagging me, [TheirName]. I'm at capacity this week ([reason if relevant — e.g., "I'm in my own M4.7 cycle with deadline Thursday"]).

Tagging [OtherName] who mentioned they had bandwidth this week. You can also use the Alternate Protocol at `02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md` if the cohort is thin at your pacing — Protocol A (mentor substitution) is available.
```

### Why this structure works

Declining without leaving the requester stranded. Referring to Alternate Protocol reminds the requester that the safety net exists.

---

## Script 4 — Delivering Peer Review (after completing the template)

```
[TheirName] — review complete.

**Template:** [Drive link to completed Peer Review Template]

**Top-level observation:** [one sentence — your overall impression]

**My three recommended revisions (from template):**
1. [brief version]
2. [brief version]
3. [brief version]

Happy to discuss any of these in async DM if useful. Good luck with M4.8.
```

### Why this structure works

Surfaces the most actionable takeaway in the message itself so the requester can start revising without waiting to open the full template. The full template provides depth; the message provides urgency.

---

## Script 5 — Responding to Peer Review (after incorporating)

```
[ReviewerName] — thanks for the review. Incorporated as follows:

- **Revision 1 you recommended:** [incorporated / incorporated with modification / not incorporated + reason]
- **Revision 2:** [same format]
- **Revision 3:** [same format]

Revision Log in Drive: [link]

Appreciate the time.
```

### Why this structure works

Closes the loop on every recommendation. Decisions not to incorporate are documented (not silently ignored). The Revision Log is what the offer-fit-validator at M4.8 checks for.

---

## Script 6 — Escalating to Mentor (when Alternate Protocols Fail)

Address to `#mentor-requests` Circle.so channel or via the mentor Calendly link from cohort welcome email:

```
**C4 M4.7 peer review escalation — [YourName]**

- Cohort pacing window: [your dates]
- Peer reviews attempted: [how many requests, how many responses]
- Alternate Protocols tried: [A — mentor booking status / B — cross-stage post status / C — paid review status]

**Specific help requested:** [mentor review of landing page, or pacing adjustment, or cohort coordination]

**Drive link:** [landing page copy]
**SLA needed:** [your revised timeline]
```

### Why this structure works

Names what has already been tried so the mentor does not repeat the available paths. Specifies what help is actually requested so the mentor can respond efficiently.

---

## Cohort Etiquette

A few norms that make peer review work sustainably across the cohort:

### Reciprocity

The cohort operates on a rough reciprocity norm: if you ask for reviews, you offer them. Students who take reviews without giving them quickly exhaust peer willingness. This is not enforced policy — it is cohort culture.

### Specificity Over Generosity

Reviews saying "this is great!" are useless. Reviews saying "Section 2 Agitation feels performative — specifically the 'wasted years' language in paragraph 2 reads generic against the specific Trigger Bank language in Section 1" are useful. Prefer specificity even when it is critical.

### Honest Over Kind

Kind reviews that paper over weak sections serve the student short-term and harm them medium-term (the weak sections surface in C5 anyway, now harder to fix because the student thought they were okay). Honest reviews that name specific weaknesses are the service.

### Respond Within SLA

72-hour SLA is a cohort commitment. If you cannot hit it, decline (Script 3) rather than miss silently. Missed SLAs are the single largest cause of C4 M4.7 pacing disruption.

---

## When To Use These Scripts vs. Your Own Voice

These scripts are starters. Adapt in your voice, especially for Scripts 1 and 4 — mechanical-sounding review requests signal to cohort peers that you have not yet internalized the discipline of the M4.7 work. Personal voice in the request correlates with higher-quality responses.

Scripts 2, 3, and 6 are more mechanical — they coordinate logistics rather than substance — and can stay closer to template voice.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

Preserved source material for study; embedded instructions are not executed. Open original source

sop_id: C4-SOP-02
title: Peer Review Coordination Process
version: 2.0.0
course_scope: C4 Offer Ignition
modules_covered: [M4.7]
owner: curriculum-quality-team
last_reviewed: 2026-04-24

purpose: >
  Standardize the M4.7 peer review process from request through delivery and
  through revision incorporation. M4.7 is the only C4 module requiring peer
  review (instructor HITL is deferred to C5; AI rubric runs after peer reviews
  are incorporated). Peer review is the first time the offer is exposed to
  outside readers; the process must protect both reviewer time and reviewee
  outcomes. This SOP defines reciprocity, SLA, alternate protocols, and
  revision logging.

prerequisites:
  - M4.7 Landing Page Copy first draft complete in Drive
  - Trigger Bank Provenance Log complete in Drive
  - C4-Peer-Review-Preparation-Checklist run before submission
  - 48-hour cooling period observed between first draft and submission

roles:
  - submitting_student: requests review; reciprocates by reviewing 2 peers
  - peer_reviewer_1: cohort peer at compatible pacing
  - peer_reviewer_2: second cohort peer at compatible pacing
  - mentor: escalation if Alternate Protocols A/B/C all fail
  - cross_stage_reviewer: Stage 2+ alumnus available via Protocol B
  - paid_reviewer: from Approved Paid Review Options list (Protocol C)
  - build_6: tracks SLA, matches reviewers, gates M4.7 checkpoint progression

process:
  step_1:
    name: Pre-Submission Self-Audit
    time: 20 min
    output: Completed Peer Review Preparation Checklist
    activities:
      - Run C4-Peer-Review-Preparation-Checklist sections A through H
      - Address any unchecked items before posting review request
      - Verify Trigger Bank entry count >= 15 with Provenance Log complete
      - Verify anti-promise unchanged from M4.5; verify guarantee unchanged from M4.6
    quality_gate: All preparation checklist items checked; if any item is unchecked, fix before requesting review
    common_failures:
      - "Posting request before Trigger Bank entries reach 15"
      - "Posting request with anti-promise softened from M4.5 (peer reviewers will flag, costing 24-48 hours)"
      - "Forgetting to attach Trigger Bank Provenance Log"
    mitigation: The checklist exists specifically to catch these. Run it.

  step_2:
    name: Request Review (Standard Protocol)
    time: 15 min
    output: Review request post in #c4-offer-ignition Circle.so channel
    activities:
      - Use Outreach Script 1 from C4-Peer-Review-Outreach-Scripts.md
      - Specify offer name, target buyer, price, areas you suspect are weak
      - Attach Drive links to landing page copy AND Trigger Bank Provenance Log
      - State 72-hour SLA expectation
      - Offer specific reciprocity (which days you can review others' copy this week)
    quality_gate: Post visible in #c4-offer-ignition; request structure matches Outreach Script 1
    common_failures:
      - "Vague request without specifying suspected-weak sections (reviews come back generic)"
      - "Not offering reciprocity (cohort norm violated; future review requests slower to receive responses)"
      - "Missing Provenance Log attachment (reviewers can't verify Trigger Bank usage)"
    mitigation: Use the script verbatim until it becomes natural

  step_3:
    name: Reviewer Pickup (24-48 hours from request)
    time: passive
    output: 2 peers commit to review with stated delivery dates
    activities:
      - Build 6 sends notification to active cohort peers at compatible pacing
      - Peers respond using Outreach Script 2 (acceptance) or Script 3 (decline with referral)
      - Build 6 logs commitments and tracks SLA
      - If only 1 reviewer commits within 48 hours, Build 6 escalates per step 4a
    quality_gate: 2 reviewers committed within 48 hours
    common_failures:
      - "Cohort thin at student's pacing (Protocol A activates)"
      - "Reviewers who committed silently miss SLA without communication"
    mitigation: Build 6 active SLA tracking surfaces silent misses; cohort norm includes communicating early if SLA at risk

  step_4_alternate_protocol_a:
    name: Mentor Substitution (Protocol A)
    time: 24 hours from activation
    output: Mentor named as reviewer; review delivered within 72 hours
    activation_trigger: Cohort has < 4 active peers at compatible pacing OR < 2 peers commit within 48 hours
    activities:
      - Student books mentor review slot via Calendly link in cohort welcome email
      - OR Student posts in #mentor-requests with M4.7 review request
      - Mentor delivers full Peer Review Template completion within 72 hours
      - Mentor review counts as both required peer reviews
    quality_gate: Mentor review filed with C4-Peer-Review-Template completion
    common_failures:
      - "Mentor booking backed up 2+ weeks during high-enrollment cycle (rare; route to Protocol B)"

  step_4_alternate_protocol_b:
    name: Cross-Stage Review (Protocol B)
    time: 96 hours from activation
    output: 1-2 Stage 2+ alumni reviewers complete review
    activation_trigger: Mentor backed up; OR student prefers reviewer who has shipped offers
    activities:
      - Student posts in #cross-stage-review channel using request format from Alternate Protocol document
      - Stage 2-5 operators who actively volunteer review time pick up the request
      - Review uses C4 Peer Review Template
      - Cross-stage review counts as both required reviews, OR pairs with one peer/mentor review
    quality_gate: Cross-stage review filed
    common_failures:
      - "No cross-stage reviewer picks up within 48 hours (route to Protocol C)"

  step_4_alternate_protocol_c:
    name: Approved Paid Review (Protocol C — Last Resort)
    time: 48-72 hours from activation
    output: Paid reviewer completes review using C4 Peer Review Template
    activation_trigger: Protocols A and B unavailable within student's planned week
    activities:
      - Student selects from C4-Approved-Paid-Review-Options.md (Tier A/B/C)
      - Direct engagement; Academy does not facilitate payment
      - Paid reviewer completes C4 Peer Review Template
      - Paid review counts as 1 of 2 required reviews; must pair with peer/mentor/cross-stage for second
      - Methodology consistency check: any methodology-conflicting paid feedback flagged before incorporation
    quality_gate: Paid review filed; second review (peer/mentor/cross-stage) also filed
    common_failures:
      - "Paid reviewer recommends removing anti-promise (methodology-conflict; do not incorporate without mentor consult)"
      - "Paid reviewer recommends stacking guarantees (methodology-conflict)"
      - "Student counts paid review as both required reviews (not allowed)"
    mitigation: Approved Paid Review document provides methodology baseline language to send to paid reviewer

  step_5:
    name: Receive and Read Reviews
    time: 30 min (do not act yet)
    output: Both reviews read in single sitting
    activities:
      - Wait until both reviews have arrived before reading either
      - Read both in one sitting; note patterns
      - If both reviewers flagged the same section as weak, that section is genuinely weak
      - If reviewers disagree, use your judgment
      - Do not begin revision yet — sleep on the feedback
    quality_gate: Both reviews read; pattern notes captured
    common_failures:
      - "Reading first review and immediately starting revisions before second review arrives (creates whiplash if reviewers disagree)"
      - "Defending against feedback in your head without genuinely considering it"
    mitigation: 12+ hour gap between reading and revising; treat reviews as gifts, not attacks

  step_6:
    name: Draft Revision Log + Revise
    time: 60-90 min
    output: Revision Log file + revised landing page in Drive
    activities:
      - Open C4-Peer-Review-Outreach-Scripts.md Script 5 template
      - For each suggestion in each review: incorporated / incorporated with modification / not incorporated + reason
      - Document each decision; the offer-fit-validator at M4.8 reads this
      - Revise landing page based on incorporated suggestions
      - Address pattern-flagged sections (those flagged by both reviewers) with priority
    quality_gate: Revision Log complete; revised landing page in Drive
    common_failures:
      - "Skipping the Revision Log (validator at M4.8 will flag missing log)"
      - "Incorporating every suggestion mechanically (you should make decisions, not absorb)"
    mitigation: The Log is the structural mechanism that forces decision-making; do not skip

  step_7:
    name: Reciprocate
    time: 90-120 min total (45-60 min per review × 2)
    output: 2 completed peer reviews delivered to other students
    activities:
      - During or after your own revision cycle, complete 2 peer reviews for cohort peers
      - Use C4-Peer-Review-Template for each
      - Deliver via Outreach Script 4 from outreach scripts document
      - Reciprocity is cohort norm; tracking is light but reputation matters
    quality_gate: 2 reviews delivered; Build 6 logs reciprocity in cohort metrics
    common_failures:
      - "Receiving reviews and not reciprocating (silent reputation cost; future requests slower to receive responses)"
      - "Reciprocating with low-effort 'looks great!' reviews (worse than declining; harms peer's revision quality)"
    mitigation: If you genuinely cannot reciprocate this cycle, decline future review requests until you can; do not free-ride

  step_8:
    name: Submit Revised Landing Page to AI Rubric
    time: 5 min + 5 min for rubric run
    output: landing-page-copy-reviewer score >= 7/10
    activities:
      - Submit revised landing page + provenance log + revision log to Build 6
      - Build 6 invokes landing-page-copy-reviewer-v1.0.0.yaml
      - Verify peer_review_count >= 2 in submission metadata
      - Receive rubric score within 5 minutes
    quality_gate: Score >= 7/10; peer_review_count = 2; no integrity flags
    common_failures:
      - "Submitting without filing the Revision Log first (rubric flags missing artifact)"
      - "Trigger Bank entries fabricated or paraphrased (rubric flags as integrity issue)"
    mitigation: All checks should already have passed in step 5-6; if rubric flags appear, fix and resubmit

review_and_adjustment:
  cadence: Per cohort cycle
  questions_to_ask:
    - "What % of M4.7 submissions used Standard Protocol vs Alternate Protocol A/B/C?"
    - "What was the median time from review request to review delivery?"
    - "What % of reviewers met SLA without escalation?"
    - "What % of paid reviewers gave methodology-conflicting feedback?"
  adjustment_principles:
    - If Alternate Protocol A activation > 30%, expand mentor capacity OR extend cohort recruitment to thicken cohorts
    - If paid reviewer methodology conflicts > 20%, refresh paid reviewer Affiliate Agreements OR remove specific reviewers from Approved list
    - If reciprocity ratio (reviews given / reviews received) < 0.85, surface in cohort discussion

escalation_triggers:
  - 3+ submissions fail M4.7 rubric on same student (mentor diagnosis)
  - Reviewer fabrication or methodology-conflicting feedback (Affiliate Agreement review)
  - Reciprocity ratio < 0.5 for individual student over 2 cohorts (cohort norm conversation)
  - Cohort thinning > 3 weeks consecutive (Build 6 → Marketing for cohort recruitment review)

related_documents:
  - 02_Resources/Templates/C4-Peer-Review-Template.md
  - 02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md
  - 02_Resources/Templates/C4-Approved-Paid-Review-Options.md
  - 02_Resources/Checklists/C4-Peer-Review-Preparation-Checklist.md
  - 03_Scripts-and-Prompts/Outreach-Scripts/C4-Peer-Review-Outreach-Scripts.md
  - 03_Scripts-and-Prompts/Claude-System-Prompts/landing-page-copy-reviewer-v1.0.0.yaml

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Template — M4.7 Landing Page Copy

**Purpose:** Structured template for cohort peer reviews of M4.7 landing page copy. Two peer reviews per student are required; students complete two reviews for peers in exchange.
**Time per review:** ~45-60 minutes
**Timeline:** 72-hour SLA from review request to delivery
**Filed to:** Build 8 Drive folder; linked into submitting student's M4.7 folder

---

## Reviewer Instructions

Read the landing page copy and the Trigger Bank Provenance Log in one pass, then complete the template below. Your job is not to edit line-by-line — the submitting student will do that. Your job is to surface structural issues they cannot see from inside their own draft.

Three things you are specifically looking for:

1. **Does the page sound like the market or like the operator?** You are an outside reader who has not been inside this operator's head for 4 weeks. You can hear voice drift more clearly than they can.

2. **Are the verbatim Trigger Bank quotes doing work, or are they decorative?** Quotes should anchor specific claims. A quote dropped next to a general statement without connection is not working.

3. **Is the anti-promise actually specific, and is the guarantee actually clean?** M4.5 and M4.6 stand-alone documents can be strong but get softened in the landing page. You are the second set of eyes that catches softening.

---

## Reviewer Information

**Reviewer name:** _____________________________
**Reviewer operator archetype:** _____________________________
**Review date:** _____________________________
**Submitting operator name:** _____________________________
**Submitting operator's offer name:** _____________________________

---

## Section-by-Section Review

### Section 1 — Problem

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak
**One-sentence read:** [What is this operator's offer trying to solve, in your words?]

Does the Problem section make the buyer's current state specific and vivid?
☐ Yes, I could visualize it ☐ Partially ☐ No, it was generic

Was at least one verbatim Trigger Bank quote integrated meaningfully (not decoratively)?
☐ Yes ☐ Partially ☐ No

**Specific observations (1-3 sentences):**

---

### Section 2 — Agitation

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Does the Agitation section make the cost of *not acting* feel real, or does it feel performative?
☐ Real ☐ Mixed ☐ Performative

Did any specific numbers, time-frames, or opportunity costs make the Agitation land?
☐ Yes (which ones: __________) ☐ No

**Specific observations:**

---

### Section 3 — Solution-and-Mechanism

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

After reading this section, can you describe the mechanism in your own words?
☐ Yes, I could teach it to a friend ☐ Roughly ☐ No, it's still fuzzy

Are the 4 pillars of the mechanism visible, even if not labeled as pillars?
☐ Yes ☐ Partially ☐ No

**Specific observations:**

---

### Section 4 — Proof

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Are the proof cases specific (named, with outcome data), or are they generic ("Maya is great")?
☐ Specific ☐ Mixed ☐ Generic

If the operator has few case studies, is that acknowledged honestly, or is it papered over?
☐ Acknowledged honestly ☐ Handled in between ☐ Papered over

**Specific observations:**

---

### Section 5 — Offer

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Is the named deliverable clear, specific, and 5-Test-passed?
☐ Yes ☐ Partially ☐ No (how could it be clearer: __________)

Is the price visible on the page?
☐ Yes, clearly ☐ Present but buried ☐ Not visible

Does the delivery structure tell you what the buyer's experience actually is (what they do, when, with whom)?
☐ Yes, concretely ☐ Vaguely ☐ Not really

**Specific observations:**

---

### Section 6 — Anti-Promise-and-Guarantee

**This is the most important section to peer-review.**

**Anti-Promise strength:** ☐ Strong ☐ Adequate ☐ Weak

Does the anti-promise name three specific exclusions?
☐ Yes, three or more ☐ Two ☐ One or fewer

Are any of the "exclusions" actually flattering descriptions of the target buyer (e.g., "not for unmotivated people")?
☐ No, they are genuine exclusions ☐ One or two are flattering-dressed-as-exclusion ☐ Most are

**Guarantee strength:** ☐ Strong ☐ Adequate ☐ Weak

Is the guarantee a clean structure (one primary + one optional complementary), or is it stacked with three or more components?
☐ Clean ☐ Borderline ☐ Stacked (Feature Stuffing Trap signal)

If you were a buyer who met the activation conditions, do you trust this operator would honor the guarantee without friction?
☐ Yes ☐ Mostly ☐ Uncertain

**Specific observations:**

---

### Section 7 — CTA

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Does the CTA name a specific action (not "click here") and a specific outcome ("enroll in the Feb 12 cohort, receive Welcome Kit within 24 hours")?
☐ Yes, specific ☐ Partially ☐ Generic

Is there a clear timeline (cohort start date, enrollment close date)?
☐ Yes ☐ No

**Specific observations:**

---

## Cross-Cutting Review

### Verbatim Trigger Bank Usage

Pick 3 of the Trigger Bank quotes used in the landing page. Check them against the Provenance Log — do they match the source entry verbatim, or have they been paraphrased into "cleaner" language?

- **Quote #1:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased
- **Quote #2:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased
- **Quote #3:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased

**Overall provenance accuracy:** ☐ Strong (all 3 verbatim) ☐ Mixed ☐ Weak (paraphrasing is dominant)

### Voice Check

Does the page sound like the operator or like the market?
☐ Mostly market voice ☐ Mixed (operator voice leaks through in specific sections: __________) ☐ Mostly operator voice

### Total Trigger Bank Entry Count

Count the verbatim quotes in the landing page.
**Count:** ___ / 15 minimum

If below 15, the submission fails the M4.7 checkpoint.

---

## Top-3 Revisions You Recommend

Identify the three revisions that would most improve this landing page:

1. **Revision 1:**
2. **Revision 2:**
3. **Revision 3:**

Each revision should be specific enough that the operator can act on it ("tighten the Problem section opening from 4 sentences to 2") rather than abstract ("improve the copy").

---

## Reviewer Closeout

**Overall assessment:** ☐ Ready to submit ☐ Needs moderate revision ☐ Needs substantial revision

**Would I buy this offer if I were the target buyer?** ☐ Yes ☐ Maybe ☐ No — and why: __________

**Reviewer signature:** _____________________________

---

## For the Submitting Operator

After receiving both peer reviews:

1. Read both reviews in one sitting before acting on either. Look for patterns — if both reviewers flagged the same section as weak, that section needs real work. If they disagree, use your judgment.

2. Your job is not to accept every suggestion. Your job is to take each suggestion seriously and make a documented decision about whether to incorporate it.

3. File a Revision Log (`Revision-Log-M4.7-[YourName]-[Date].md`) noting which suggestions you incorporated, which you considered but did not incorporate, and why. The offer-fit-validator at M4.8 checks for this log.

4. Revise. Submit the revised landing page to the AI rubric (`landing-page-copy-reviewer-v1.0.0.yaml`).

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Alternate Protocol

**Purpose:** Alternate paths when your active C4 cohort has fewer than 4 peers at your pacing window. Ensures M4.7 does not stall for reviewer unavailability.
**Referenced by:** `00_Course-Overview/C4-Prerequisites-Checklist.md`
**Escalation path:** If none of the protocols below are viable, escalate to RISER Nation mentor within 72 hours of M4.7 draft completion.

---

## When to Use This Protocol

Use when any of the following is true:

- Your C4 cohort Circle.so channel (`#c4-offer-ignition`) has fewer than 4 active operators at your pacing window
- Cohort peers at your pacing window have not responded within 72 hours of your review request
- Your cohort is pacing unusually (ahead or behind the main cohort cycle) and peers are not currently at M4.7

---

## Protocol A — Mentor Substitution (Default)

**Who it's for:** Any student whose cohort is too thin for 2 peer reviews.

**How it works:**

1. Book a 45-minute review slot with a named RISER Nation mentor via the Calendly link in the cohort welcome email, or via the `#mentor-requests` Circle.so channel.
2. Submit your M4.7 draft and Trigger Bank Provenance Log at least 24 hours before the review call.
3. The mentor completes the C4 Peer Review Template during or after the call and delivers a written review within 72 hours.
4. Mentor review counts as both required peer reviews. No additional review needed.

**SLA:** 72 hours from submission to written review delivery (typical) ; 96 hours worst-case.

**Cost:** No charge. Mentor capacity is allocated out of Academy program support time.

**When Protocol A is not available:** Mentor booking backed up 2+ weeks. Rare but happens in high-enrollment cycles. Shift to Protocol B.

---

## Protocol B — Cross-Stage Review

**Who it's for:** Students whose mentor booking is backed up, or who prefer review from an operator who has already shipped offers.

**How it works:**

1. Post a review request in the `#cross-stage-review` Circle.so channel with the following structure:

   ```
   **Cross-stage review request — C4 M4.7**
   - Operator archetype: [Teacher / Service / Builder / etc.]
   - Territory: [one sentence]
   - Offer name: [the 5-Test-passed name]
   - Request: 1-2 Stage 2+ operators for M4.7 landing page review
   - SLA: 96 hours
   - Drive link: [link to your draft]
   - Trigger Bank Provenance Log: [link]
   ```

2. Stage 2, Stage 3, Stage 4, or Stage 5+ operators who are active volunteers pick up the review.
3. Review uses the same C4 Peer Review Template.
4. Cross-stage review counts as both required peer reviews, or as one review paired with a mentor/peer review.

**SLA:** 96 hours (longer than peer review because cross-stage operators volunteer review time around their own operation).

**Cost:** No charge. Typically treated as ecosystem reciprocity; Stage 2+ operators accumulate review credit that Stage 1 peers volunteer back.

**Why this can be better than peer review:** Reviewers who have shipped offers have firsthand knowledge of what survives first-sale contact and what does not. Their feedback often has higher signal-to-noise than peer-to-peer review.

**When Protocol B is not available:** No cross-stage reviewer picks up the request within 48 hours. Rare but happens near holiday periods. Shift to Protocol C.

---

## Protocol C — Paid Review (Last Resort)

**Who it's for:** Students whose timeline is blocked and Protocols A and B did not clear within their planned week.

**How it works:**

1. Choose from the Approved Paid Review list in `C4-Approved-Paid-Review-Options.md`.
2. Directly engage the reviewer (paid engagement; Academy does not facilitate payment).
3. Paid reviewer completes the C4 Peer Review Template.
4. Paid review counts as one of the two required reviews. **Paid review alone is not sufficient** — pair with one mentor, cross-stage, or peer review.

**SLA:** per reviewer contract, typically 48-72 hours.

**Cost:** Varies by reviewer. Typical range: $150-$400 per review.

**When Protocol C is genuinely necessary:** rare. Most students who think they need Protocol C actually have a timing problem that Protocol A or B resolves with a slight pacing adjustment (waiting 3-5 extra days for mentor or cross-stage slot).

**Warning:** paid review is a legitimate professional service but is not a substitute for cohort accountability. Paid reviewers who are not familiar with RISER Nation methodology sometimes give advice that conflicts with C3/C4 doctrine (e.g., suggesting feature-stuffed guarantees or removal of the anti-promise section). Review paid feedback critically against the module lessons; do not incorporate paid advice that conflicts with the methodology without checking with a mentor.

---

## Scholarship Path for Protocol C

If your cohort is thin, Protocols A and B are unavailable within your timeline, and Protocol C is financially inaccessible:

1. Email `[email protected]` with "C4 M4.7 Review Scholarship Request" in the subject line
2. Include your Drive link, pacing dates, and which Protocols were attempted
3. SLA: 48 hours for response; if approved, scholarship covers one paid review up to $200

Scholarship approval is typical for genuine thin-cohort situations.

---

## Logging the Alternate Protocol

Whatever Protocol you used, log it in your M4.7 Revision Log so the offer-fit-validator at M4.8 has the context:

```
Peer Review Protocol: [A — Mentor / B — Cross-Stage / C — Paid + one of A or B / Standard two-peer]
Reviewer 1: [name, protocol, date of review]
Reviewer 2: [name, protocol, date of review]
Alternate protocol rationale: [1-2 sentences]
```

The offer-fit-validator does not penalize Alternate Protocol usage — it penalizes missing reviews. Logging the protocol used keeps the validator's coherence checks from flagging the submission.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by C4-Prerequisites-Checklist*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Approved Paid Review Options

**Purpose:** Reference list of paid review providers vetted by RISER Nation for C4 M4.7 landing page review when cohort peer and mentor options are unavailable (Protocol C in the Peer Review Alternate Protocol).
**Referenced by:** `C4-Peer-Review-Alternate-Protocol.md`
**Status:** This list is maintained by the Academy team and updated quarterly. The version below reflects approved reviewers as of the Last Updated date.

---

## Selection Criteria

To appear on this list, a reviewer has:

- Reviewed at least 20 C4-style offer landing pages in the direct-response tradition
- Demonstrated familiarity with mechanism-based offer construction (Hormozi-adjacent methodology)
- Produced reviews that respect the anti-promise section as a credibility mechanism (rather than recommending its removal)
- Signed the RISER Nation Reviewer Affiliate Agreement — which commits them to methodology-consistent feedback
- Been cross-rated by at least 5 past reviewees as useful and non-disruptive

Reviewers without these properties are excluded from the list, regardless of market reputation.

---

## Current Approved Reviewers (Quarterly Update — Q2 2026)

### Tier A — Deep Direct-Response Specialists

These reviewers have 10+ years of direct-response copy experience. Pricing reflects seniority.

- **Reviewer Slot A1** — [reviewer name redacted for template; actual list maintained in Drive]
  - **Pricing:** $350-$450 per review
  - **SLA:** 72 hours
  - **Specialty:** coaching/consulting offers; cohort programs; Teacher-Operator and Service-Operator archetypes
  - **Contact:** [via Calendly link in Drive version]

- **Reviewer Slot A2**
  - **Pricing:** $300-$400 per review
  - **SLA:** 48-72 hours
  - **Specialty:** productized services; Builder-Operator archetype
  - **Contact:** [via Drive]

### Tier B — Mid-Senior Reviewers

5-10 years of direct-response experience. Pricing is moderate.

- **Reviewer Slot B1**
  - **Pricing:** $200-$275 per review
  - **SLA:** 48-72 hours
  - **Specialty:** creative services; Creative-Operator archetype
  - **Contact:** [via Drive]

- **Reviewer Slot B2**
  - **Pricing:** $175-$250 per review
  - **SLA:** 72 hours
  - **Specialty:** B2B offers; systems and platforms; Systems-Operator archetype
  - **Contact:** [via Drive]

### Tier C — RISER Nation Alumni Reviewers

Alumni who have completed Stage 2+ of the Academy and offer paid review to Stage 1 peers. Often the best value — they know the methodology cold and price accordingly.

- **Reviewer Slot C1-C5** — rotating list, currently 5 alumni reviewers available
  - **Pricing:** $150-$200 per review
  - **SLA:** 48-72 hours
  - **Specialty:** matches the alumni's own operator archetype; check Drive list for match
  - **Contact:** [via Drive; alumni reviewers coordinate through `#alumni-review-pool` Circle.so channel]

---

## How To Engage a Paid Reviewer

1. **Check the Drive version of this list** for current names, contact info, and availability status. Names are not in this template to avoid stale information when reviewers rotate.

2. **Match reviewer to your archetype.** A Teacher-Operator reviewing a Service-Operator's offer will sometimes give advice that is methodology-correct but archetype-mismatched. Tier A reviewers are generalists; Tier B and C reviewers are archetype-specialized.

3. **Send your M4.7 draft and Trigger Bank Provenance Log.** Use the C4 Peer Review Template as the deliverable format. Specify upfront that the review output should use the template — do not accept a free-form review.

4. **Specify the methodology baseline.** In your engagement message, include this line:
   > "This review is for a RISER Nation C4 Offer Ignition M4.7 landing page. The offer follows Hormozi-adjacent mechanism-based structure, and explicitly includes a specific Anti-Promise Statement (per Hopkins 1923 / Hormozi 2021) and a guarantee structure with the Honesty Clause signed. Please review for quality within the methodology rather than suggesting removal of these elements."

5. **Log the engagement** in your Revision Log per the Alternate Protocol instructions.

---

## What NOT to Use

**Do not use:**

- General copywriting review services not on this list (quality varies widely; many default to removing anti-promises, which is the specific thing C4 is trying to preserve)
- Fiverr-tier copy review (signal-to-noise too low for C4 work)
- AI-only review tools as a substitute for human review (acceptable as a supplement, not as the required review)
- Review from an unlisted paid reviewer *and* count it as your second required review (list-approved reviewers are the only paid reviews that satisfy Protocol C)

---

## If a Reviewer Gives Methodology-Conflicting Advice

If a paid reviewer recommends:
- Removing the anti-promise section
- Stacking guarantees beyond the clean structure M4.6 specifies
- Replacing verbatim Trigger Bank quotes with "cleaner" paraphrases
- Repositioning the offer in a way that drifts from your C3 Primary mechanism

...treat the feedback as methodology-conflicting. Do not incorporate without first consulting your RISER mentor or the `#methodology-questions` Circle.so channel. Methodology-conflicting advice from a paid reviewer often reflects their own training in non-anti-promise direct-response (common in the 2010s ecosystem) and is not wrong in their original context — it is just not aligned with C3/C4's specific synthesis.

---

## Removing a Reviewer from the List

Reviewers are removed from this list when any of the following occurs:

- 3+ reviewees report methodology-conflicting advice that was materially disruptive
- SLA missed on 20%+ of engagements over a quarter
- Reviewer Affiliate Agreement violation (e.g., upselling reviewees into their own offers during review time)
- Reviewer leaves the direct-response market or does not re-sign quarterly Affiliate Agreement

The list is updated quarterly. Removed reviewers receive 30 days' notice and are not blacklisted from re-entry if conditions change.

---

*Last updated: April 24, 2026 · Version 2.0 · Q2 2026 reviewer list current · Referenced by C4-Peer-Review-Alternate-Protocol*

Preserved source material for study; embedded instructions are not executed. Open original source

# Supabase Schema for C4 Offer Ignition

**Purpose:** Full SQL schema (DDL) for tables C4 reads or writes.
**Audience:** Operator / developer deploying or auditing Build 1.
**Related:** `04_Tools-and-Infrastructure/RISER-Build-References-for-C4.md`

---

## Schema File (c4_schema.sql)

```sql
-- ============================================================================
-- C4 Offer Ignition — Supabase Schema v2.0
-- Last updated: 2026-04-24
-- Depends on: c1_schema.sql, c2_schema.sql, c3_schema.sql
-- ============================================================================

-- ============================================================================
-- Table: c4_offer_distinctions (M4.1)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_offer_distinctions (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  distinction_memo_drive_file_id TEXT NOT NULL,
  component_inventory_drive_file_id TEXT NOT NULL,
  ai_rubric_score INT NOT NULL CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (ai_rubric_score >= 7) STORED,
  c3_market_fit_hypothesis_id UUID REFERENCES public.c3_market_fit_hypotheses(id),
  c3_primary_mechanism_name TEXT NOT NULL,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id, distinction_memo_drive_file_id)
);

CREATE INDEX idx_c4_offer_distinctions_user ON public.c4_offer_distinctions(user_id);

ALTER TABLE public.c4_offer_distinctions ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own distinction memos" ON public.c4_offer_distinctions
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own distinction memos" ON public.c4_offer_distinctions
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own distinction memos" ON public.c4_offer_distinctions
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_value_equations (M4.2)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_value_equations (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  worksheet_drive_file_id TEXT NOT NULL,
  dream_outcome_strength TEXT CHECK (dream_outcome_strength IN ('Strong', 'Moderate', 'Weak')),
  perceived_likelihood_strength TEXT CHECK (perceived_likelihood_strength IN ('Strong', 'Moderate', 'Weak')),
  time_delay_strength TEXT CHECK (time_delay_strength IN ('Strong', 'Moderate', 'Weak')),
  effort_sacrifice_strength TEXT CHECK (effort_sacrifice_strength IN ('Strong', 'Moderate', 'Weak')),
  strongest_variable TEXT NOT NULL CHECK (strongest_variable IN ('Dream Outcome','Perceived Likelihood','Time Delay','Effort & Sacrifice')),
  weakest_variable TEXT NOT NULL CHECK (weakest_variable IN ('Dream Outcome','Perceived Likelihood','Time Delay','Effort & Sacrifice')),
  trigger_bank_citations_count INT NOT NULL CHECK (trigger_bank_citations_count >= 3),
  interview_citations_count INT NOT NULL CHECK (interview_citations_count >= 1),
  ai_rubric_score INT NOT NULL CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (ai_rubric_score >= 7) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_value_equations_user ON public.c4_value_equations(user_id);

ALTER TABLE public.c4_value_equations ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own value equations" ON public.c4_value_equations
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own value equations" ON public.c4_value_equations
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own value equations" ON public.c4_value_equations
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_offer_decompositions (M4.3)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_offer_decompositions (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  decomposition_drive_file_id TEXT NOT NULL,
  variants_drive_file_id TEXT NOT NULL,
  decomposed_deliverables_count INT NOT NULL CHECK (decomposed_deliverables_count BETWEEN 6 AND 10),
  variant_a_name TEXT NOT NULL,
  variant_a_engagement_model TEXT NOT NULL CHECK (variant_a_engagement_model IN ('Cohort','1:1','Self-paced','Hybrid')),
  variant_a_duration_weeks INT NOT NULL,
  variant_a_deliverable_count INT NOT NULL CHECK (variant_a_deliverable_count <= 8),
  variant_a_price_band_low INT,
  variant_a_price_band_high INT,
  variant_b_name TEXT NOT NULL,
  variant_b_engagement_model TEXT NOT NULL CHECK (variant_b_engagement_model IN ('Cohort','1:1','Self-paced','Hybrid')),
  variant_b_duration_weeks INT NOT NULL,
  variant_b_deliverable_count INT NOT NULL CHECK (variant_b_deliverable_count <= 8),
  variant_b_price_band_low INT,
  variant_b_price_band_high INT,
  variant_c_name TEXT NOT NULL,
  variant_c_engagement_model TEXT NOT NULL CHECK (variant_c_engagement_model IN ('Cohort','1:1','Self-paced','Hybrid')),
  variant_c_duration_weeks INT NOT NULL,
  variant_c_deliverable_count INT NOT NULL CHECK (variant_c_deliverable_count <= 8),
  variant_c_price_band_low INT,
  variant_c_price_band_high INT,
  structural_verification_passed BOOLEAN NOT NULL,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

-- Enforce axis divergence via constraint: at least one of (engagement model, duration, deliverable count) differs pairwise
-- (This is a soft check; deeper divergence check lives in offer-decomposition-reviewer prompt)
ALTER TABLE public.c4_offer_decompositions ADD CONSTRAINT c4_od_ab_divergence
  CHECK (
    variant_a_engagement_model <> variant_b_engagement_model OR
    variant_a_duration_weeks <> variant_b_duration_weeks OR
    variant_a_deliverable_count <> variant_b_deliverable_count
  );
ALTER TABLE public.c4_offer_decompositions ADD CONSTRAINT c4_od_ac_divergence
  CHECK (
    variant_a_engagement_model <> variant_c_engagement_model OR
    variant_a_duration_weeks <> variant_c_duration_weeks OR
    variant_a_deliverable_count <> variant_c_deliverable_count
  );
ALTER TABLE public.c4_offer_decompositions ADD CONSTRAINT c4_od_bc_divergence
  CHECK (
    variant_b_engagement_model <> variant_c_engagement_model OR
    variant_b_duration_weeks <> variant_c_duration_weeks OR
    variant_b_deliverable_count <> variant_c_deliverable_count
  );

CREATE INDEX idx_c4_offer_decompositions_user ON public.c4_offer_decompositions(user_id);

ALTER TABLE public.c4_offer_decompositions ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own decompositions" ON public.c4_offer_decompositions
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own decompositions" ON public.c4_offer_decompositions
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own decompositions" ON public.c4_offer_decompositions
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_pricing_decisions (M4.4)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_pricing_decisions (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  pricing_decision_drive_file_id TEXT NOT NULL,
  observed_band_floor INT NOT NULL,
  observed_band_median INT NOT NULL,
  observed_band_ceiling INT NOT NULL,
  anchor_price INT NOT NULL CHECK (anchor_price > 0),
  pricing_strategy TEXT NOT NULL CHECK (pricing_strategy IN ('Median','Above Market','Below Market (Volume)','Other')),
  pay_in_full_price INT NOT NULL,
  installment_option TEXT,
  deposit_option TEXT,
  unit_economics_hours_per_buyer NUMERIC,
  unit_economics_effective_hourly_rate NUMERIC,
  deviation_from_band_rationale TEXT,
  ai_rubric_score INT NOT NULL CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (ai_rubric_score >= 7) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_pricing_decisions_user ON public.c4_pricing_decisions(user_id);

ALTER TABLE public.c4_pricing_decisions ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own pricing" ON public.c4_pricing_decisions
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own pricing" ON public.c4_pricing_decisions
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own pricing" ON public.c4_pricing_decisions
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_anti_promises (M4.5)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_anti_promises (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  anti_promise_drive_file_id TEXT NOT NULL,
  integrity_statement_drive_file_id TEXT NOT NULL,
  integrity_statement_signed BOOLEAN NOT NULL DEFAULT FALSE,
  audience_exclusions_count INT NOT NULL CHECK (audience_exclusions_count BETWEEN 3 AND 6),
  outcome_non_claims_count INT NOT NULL CHECK (outcome_non_claims_count >= 2),
  scope_boundaries_count INT NOT NULL CHECK (scope_boundaries_count >= 2),
  ai_rubric_score INT NOT NULL CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (ai_rubric_score >= 7 AND integrity_statement_signed) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_anti_promises_user ON public.c4_anti_promises(user_id);

ALTER TABLE public.c4_anti_promises ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own anti-promises" ON public.c4_anti_promises
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own anti-promises" ON public.c4_anti_promises
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own anti-promises" ON public.c4_anti_promises
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_guarantees (M4.6)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_guarantees (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  guarantee_drive_file_id TEXT NOT NULL,
  honesty_clause_drive_file_id TEXT NOT NULL,
  honesty_clause_signed BOOLEAN NOT NULL DEFAULT FALSE,
  guarantee_type TEXT NOT NULL CHECK (guarantee_type IN ('Refund','Outcome','Hybrid','Time-shift','Effort-adjusted')),
  guarantee_component_count INT NOT NULL CHECK (guarantee_component_count <= 2),
  targets_weakness TEXT NOT NULL CHECK (targets_weakness IN ('Perceived Likelihood','Time Delay','Effort & Sacrifice')),
  expected_activation_rate_pct NUMERIC,
  unit_economics_sustainable BOOLEAN NOT NULL,
  ai_rubric_score INT NOT NULL CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (ai_rubric_score >= 7 AND honesty_clause_signed) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_guarantees_user ON public.c4_guarantees(user_id);

ALTER TABLE public.c4_guarantees ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own guarantees" ON public.c4_guarantees
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own guarantees" ON public.c4_guarantees
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own guarantees" ON public.c4_guarantees
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_landing_page_copies (M4.7)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_landing_page_copies (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  landing_page_drive_file_id TEXT NOT NULL,
  provenance_log_drive_file_id TEXT NOT NULL,
  revision_log_drive_file_id TEXT,
  total_word_count INT NOT NULL CHECK (total_word_count BETWEEN 1000 AND 5000),
  trigger_bank_entries_claimed INT NOT NULL CHECK (trigger_bank_entries_claimed >= 15),
  trigger_bank_entries_verified_verbatim INT NOT NULL,
  peer_review_1_reviewer_id UUID REFERENCES public.users(id),
  peer_review_1_completed_at TIMESTAMPTZ,
  peer_review_2_reviewer_id UUID REFERENCES public.users(id),
  peer_review_2_completed_at TIMESTAMPTZ,
  peer_reviews_complete BOOLEAN GENERATED ALWAYS AS (peer_review_1_completed_at IS NOT NULL AND peer_review_2_completed_at IS NOT NULL) STORED,
  ai_rubric_score INT CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (
    ai_rubric_score >= 7 AND
    peer_review_1_completed_at IS NOT NULL AND
    peer_review_2_completed_at IS NOT NULL AND
    trigger_bank_entries_verified_verbatim >= 15
  ) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_landing_page_copies_user ON public.c4_landing_page_copies(user_id);

ALTER TABLE public.c4_landing_page_copies ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own landing pages" ON public.c4_landing_page_copies
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own landing pages" ON public.c4_landing_page_copies
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own landing pages" ON public.c4_landing_page_copies
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_offer_readiness_docs (M4.8 — course completion artifact)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_offer_readiness_docs (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  readiness_doc_drive_file_id TEXT NOT NULL,
  first_sale_readiness_checklist_drive_file_id TEXT NOT NULL,
  selected_variant TEXT NOT NULL CHECK (selected_variant IN ('A','B','C')),
  final_offer_name TEXT NOT NULL,
  final_anchor_price INT NOT NULL,
  signature_signed BOOLEAN NOT NULL DEFAULT FALSE,
  opus_validator_verdict TEXT CHECK (opus_validator_verdict IN ('PASS','NEEDS_REVISION','FAIL')),
  opus_validator_run_at TIMESTAMPTZ,
  kill_criteria_count INT NOT NULL CHECK (kill_criteria_count >= 3),
  passed BOOLEAN GENERATED ALWAYS AS (
    opus_validator_verdict = 'PASS' AND
    signature_signed
  ) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_offer_readiness_docs_user ON public.c4_offer_readiness_docs(user_id);

ALTER TABLE public.c4_offer_readiness_docs ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own readiness docs" ON public.c4_offer_readiness_docs
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own readiness docs" ON public.c4_offer_readiness_docs
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own readiness docs" ON public.c4_offer_readiness_docs
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_review_log (audit trail for all review prompt calls)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_review_log (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  module TEXT NOT NULL CHECK (module IN ('M4.1','M4.2','M4.3','M4.4','M4.5','M4.6','M4.7','M4.8')),
  prompt_name TEXT NOT NULL,
  prompt_version TEXT NOT NULL,
  submission_count INT NOT NULL DEFAULT 1,
  verdict TEXT NOT NULL CHECK (verdict IN ('PASS','FAIL','NEEDS_REVISION')),
  score INT,
  feedback_json JSONB,
  flags_json JSONB,
  ran_at TIMESTAMPTZ DEFAULT NOW()
);

CREATE INDEX idx_c4_review_log_user_module ON public.c4_review_log(user_id, module);

ALTER TABLE public.c4_review_log ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own review log" ON public.c4_review_log
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Service inserts review log" ON public.c4_review_log
  FOR INSERT WITH CHECK (TRUE); -- service role only; Build 6 writes


-- ============================================================================
-- Column addition: users table
-- ============================================================================
ALTER TABLE public.users
  ADD COLUMN IF NOT EXISTS c4_complete BOOLEAN DEFAULT FALSE,
  ADD COLUMN IF NOT EXISTS c4_completed_at TIMESTAMPTZ,
  ADD COLUMN IF NOT EXISTS c4_lead_variant TEXT,
  ADD COLUMN IF NOT EXISTS c4_final_offer_name TEXT,
  ADD COLUMN IF NOT EXISTS c4_final_anchor_price INT;


-- ============================================================================
-- Function: check_c4_enrollment_eligible(user_id)
-- ============================================================================
CREATE OR REPLACE FUNCTION public.check_c4_enrollment_eligible(p_user_id UUID)
RETURNS JSONB AS $$
DECLARE
  v_missing TEXT[] := ARRAY[]::TEXT[];
  v_user RECORD;
BEGIN
  SELECT c1_complete, c2_complete, c3_complete, captains_oath_signed_at, operator_identity_filed_at
    INTO v_user FROM public.users WHERE id = p_user_id;

  IF NOT COALESCE(v_user.c3_complete, FALSE) THEN
    v_missing := array_append(v_missing, 'c3_complete');
  END IF;

  IF NOT EXISTS (
    SELECT 1 FROM public.c3_market_fit_hypotheses
    WHERE user_id = p_user_id
      AND filed_at > (NOW() - INTERVAL '3 months')
  ) THEN
    v_missing := array_append(v_missing, 'c3_market_fit_hypothesis_within_3_months');
  END IF;

  IF NOT EXISTS (
    SELECT 1 FROM public.c3_trigger_banks
    WHERE user_id = p_user_id AND total_entries >= 200
  ) THEN
    v_missing := array_append(v_missing, 'c3_trigger_bank_200_plus');
  END IF;

  IF NOT EXISTS (
    SELECT 1 FROM public.c3_pricing_signals
    WHERE user_id = p_user_id
  ) THEN
    v_missing := array_append(v_missing, 'c3_pricing_signals');
  END IF;

  IF v_user.captains_oath_signed_at IS NULL OR v_user.captains_oath_signed_at < (NOW() - INTERVAL '12 months') THEN
    v_missing := array_append(v_missing, 'captains_oath_signed_within_12_months');
  END IF;

  RETURN jsonb_build_object(
    'eligible', array_length(v_missing, 1) IS NULL,
    'missing', v_missing
  );
END;
$$ LANGUAGE plpgsql SECURITY DEFINER;


-- ============================================================================
-- Function: check_c4_completion(user_id)
-- ============================================================================
CREATE OR REPLACE FUNCTION public.check_c4_completion(p_user_id UUID)
RETURNS JSONB AS $$
DECLARE
  v_missing TEXT[] := ARRAY[]::TEXT[];
BEGIN
  IF NOT EXISTS (SELECT 1 FROM public.c4_offer_distinctions WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_1_distinction_passed');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_value_equations WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_2_value_equation_passed');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_offer_decompositions WHERE user_id = p_user_id AND structural_verification_passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_3_decomposition_verified');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_pricing_decisions WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_4_pricing_passed');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_anti_promises WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_5_anti_promise_passed_and_signed');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_guarantees WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_6_guarantee_passed_and_signed');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_landing_page_copies WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_7_landing_page_passed_with_peer_reviews');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_offer_readiness_docs WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_8_readiness_doc_opus_passed');
  END IF;

  RETURN jsonb_build_object(
    'complete', array_length(v_missing, 1) IS NULL,
    'missing', v_missing
  );
END;
$$ LANGUAGE plpgsql SECURITY DEFINER;


-- ============================================================================
-- Trigger: mark c4_complete = true when all 8 artifacts pass
-- ============================================================================
CREATE OR REPLACE FUNCTION public.update_c4_complete_flag()
RETURNS TRIGGER AS $$
DECLARE
  v_check JSONB;
  v_readiness RECORD;
BEGIN
  v_check := public.check_c4_completion(NEW.user_id);
  IF (v_check->>'complete')::BOOLEAN = TRUE THEN
    SELECT selected_variant, final_offer_name, final_anchor_price
      INTO v_readiness
      FROM public.c4_offer_readiness_docs
      WHERE user_id = NEW.user_id AND passed = TRUE
      LIMIT 1;
    UPDATE public.users
      SET c4_complete = TRUE,
          c4_completed_at = NOW(),
          c4_lead_variant = v_readiness.selected_variant,
          c4_final_offer_name = v_readiness.final_offer_name,
          c4_final_anchor_price = v_readiness.final_anchor_price
      WHERE id = NEW.user_id;
  END IF;
  RETURN NEW;
END;
$$ LANGUAGE plpgsql;

CREATE TRIGGER tr_c4_completion_check
  AFTER INSERT OR UPDATE ON public.c4_offer_readiness_docs
  FOR EACH ROW
  WHEN (NEW.passed = TRUE)
  EXECUTE FUNCTION public.update_c4_complete_flag();
```

---

## Schema Design Notes

### Generated passed columns

Most tables use `GENERATED ALWAYS AS (...) STORED` for the `passed` column. This enforces the pass logic at the database layer rather than in application code — a landing page row with `ai_rubric_score = 8` but `peer_reviews_complete = FALSE` is automatically not-passed. Application code cannot accidentally flip the flag.

### Axis divergence constraints on c4_offer_decompositions

Database constraints catch the simplest failure mode (three variants that are structurally identical). Deeper divergence checks (e.g., "variant B and C differ on only price, which is not enough") are enforced by the offer-decomposition-reviewer prompt, not at the database layer. Database enforces the minimum; the prompt enforces the quality.

### Feature Stuffing constraints

The `CHECK (deliverable_count <= 8)` constraints on each variant prevent Feature Stuffing at the row level. A student cannot file a variant with 12 deliverables — the insert fails. This is the database-layer companion to the offer-decomposition-reviewer prompt's Feature Stuffing Flag.

### Integrity Statement / Honesty Clause enforcement

`c4_anti_promises` and `c4_guarantees` tables have `passed` generated columns that require both the rubric score and the signed statement. Unsigned submissions cannot pass, regardless of rubric score. This is structural enforcement of the Integrity Policy.

### Opus gating on c4_offer_readiness_docs

The `passed` flag requires Opus validator verdict = PASS AND signature_signed. A Sonnet-passed but Opus-pending row is stored but does not count as passed. C4 completion cannot occur without explicit Opus verdict.

---

## Migration Notes

This schema depends on `c1_schema.sql`, `c2_schema.sql`, and `c3_schema.sql` being deployed first. Run in sequence:

```bash
psql -h <host> -U <user> -d <db> -f c1_schema.sql
psql -h <host> -U <user> -d <db> -f c2_schema.sql
psql -h <host> -U <user> -d <db> -f c3_schema.sql
psql -h <host> -U <user> -d <db> -f c4_schema.sql
```

The `c4_complete` column addition on `public.users` is idempotent via `ADD COLUMN IF NOT EXISTS`.

---

## Referenced By

- `03_Scripts-and-Prompts/Prompt-Chains/C4-Review-Chain.md` — routing functions
- `00_Course-Overview/C4-Prerequisites-Checklist.md` — `check_c4_enrollment_eligible` reference
- Build 6 `src/c4_checkpoint_handler.ts` — all insert/update calls
- `06_SOPs/RISER-C4-Weekly-Rhythm-Setup-SOP.md` — operational integration

---

*Last updated: April 24, 2026 · Version 2.0*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Prompt Chain — M4.1 through M4.8 Review Orchestration

**Purpose:** Documents the sequencing of the 6 C4 Claude system prompts across module checkpoints. Referenced by Build 6 when routing student submissions to reviewers and gating module unlock.
**Filed to:** `03_Scripts-and-Prompts/Prompt-Chains/`
**Referenced by:** Build 6 checkpoint handler; `04_Tools-and-Infrastructure/Supabase-C4-Schema.md`

---

## Chain Overview

C4 uses 6 system prompts across 8 checkpoints. Five are Sonnet-powered (routine review) and one is Opus-powered (course-completion gate). The chain is serial — each module's review must issue PASS before the next module's checkpoint can receive submissions.

```mermaid
graph TD
    M41_sub[M4.1 submission] --> P1[offer-distinction-reviewer<br/>Sonnet 4.6]
    P1 -->|PASS >=7/10| M42_sub[M4.2 unlocks]
    P1 -->|FAIL <7/10| M41_rev[M4.1 revision]
    M41_rev --> P1

    M42_sub --> P2[value-equation-application-reviewer<br/>Sonnet 4.6]
    P2 -->|PASS >=7/10| M43_sub[M4.3 unlocks]
    P2 -->|FAIL| M42_rev[M4.2 revision]

    M43_sub --> P3[offer-decomposition-reviewer<br/>Sonnet 4.6<br/>Structural only]
    P3 -->|PASS| M44[M4.4 unlocks]
    P3 -->|NEEDS_REVISION| M43_rev[M4.3 revision]

    M44 --> M44_review[M4.4 reviewed by<br/>offer-readiness-reviewer spot-check]
    M44_review -->|PASS| M45[M4.5 unlocks]

    M45 --> M45_review[M4.5 reviewed by<br/>offer-readiness-reviewer spot-check]
    M45_review -->|PASS| M46[M4.6 unlocks]

    M46 --> M46_review[M4.6 reviewed by<br/>offer-readiness-reviewer spot-check]
    M46_review -->|PASS| M47_sub[M4.7 unlocks]

    M47_sub --> PEER[2 peer reviews<br/>SLA 72hr]
    PEER --> P4[landing-page-copy-reviewer<br/>Sonnet 4.6]
    P4 -->|PASS >=7/10 AND peer count >=2| M48_sub[M4.8 unlocks]
    P4 -->|FAIL| M47_rev[M4.7 revision]

    M48_sub --> P5[offer-readiness-reviewer<br/>Sonnet 4.6<br/>Structural pre-screen]
    P5 -->|PASS| P6[offer-fit-validator<br/>OPUS 4.7<br/>Full coherence check]
    P5 -->|NEEDS_REVISION| M48_rev[M4.8 revision]

    P6 -->|PASS| COMPLETE([C4 Complete<br/>C5 Unlocks])
    P6 -->|NEEDS_REVISION| M48_rev
    P6 -->|FAIL| MENTOR[Mentor diagnosis<br/>Likely C3 M3.7 issue]

    style P6 fill:#B45F06,color:#fff
    style COMPLETE fill:#2E75B6,color:#fff
    style MENTOR fill:#CC0000,color:#fff
    style PEER fill:#BF9000,color:#fff
```

---

## Prompt Inventory

| # | Prompt File | Model | Called At | Cost per call | Typical volume |
|---|---|---|---|---|---|
| 1 | offer-distinction-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.1 checkpoint | $0.04-0.08 | 1-2 per student |
| 2 | value-equation-application-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.2 checkpoint | $0.04-0.08 | 1-2 per student |
| 3 | offer-decomposition-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.3 checkpoint | $0.04-0.08 | 1-2 per student |
| 4 | landing-page-copy-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.7 checkpoint (after peer review) | $0.06-0.12 | 1-2 per student |
| 5 | offer-readiness-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.4, M4.5, M4.6 spot-check + M4.8 pre-screen | $0.04-0.08 | 3-5 per student |
| 6 | offer-fit-validator-v1.0.0.yaml | **Opus 4.7** | M4.8 course-completion | **$0.30-0.55** | 1-2 per student |

**Total C4 review cost per student:** $0.80-$1.50 across the chain (most students complete in 1-2 submissions per module).

---

## Orchestration Rules

### Serial Dependency Enforcement

Module unlock only occurs when the prior module's review has returned PASS. A student cannot submit M4.3 until M4.2 has PASSED. This prevents coherence collapse — a student with a miscalibrated Value Equation should not be producing decomposition variants targeted at the wrong weakness.

### Revision Loop

For each module:
- First submission → review → PASS or revision guidance
- Second submission (after revision) → review → PASS or mentor escalation
- Third submission → mentor routing (rare; indicates fundamental issue with prior module outputs)

Build 6 tracks submission count per module; the third attempt auto-routes to mentor queue.

### Peer Review Layer (M4.7 only)

M4.7 is the only module requiring peer review before AI review. The order:

1. Student submits draft to `#c4-offer-ignition`
2. Two peer reviewers complete reviews (SLA 72 hours)
3. Student incorporates peer feedback, produces Revision Log
4. Revised submission routes to landing-page-copy-reviewer (Sonnet)
5. AI reviewer verifies: peer review count ≥ 2, integrity of incorporation, and rubric score

If peer review SLA is missed (cohort thin), Protocol A/B/C from `02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md` applies.

### The Opus Gate (M4.8 only)

M4.8 is the only module routing through two reviewers:

1. **offer-readiness-reviewer (Sonnet)** performs structural pre-screen
2. If Sonnet issues PASS → **offer-fit-validator (Opus 4.7)** performs full coherence check
3. If Sonnet issues FAIL → student revises before Opus is spun up (Opus is ~5-10x the cost of Sonnet; structural pre-screen prevents wasted Opus calls)

The Opus validator's PASS verdict unlocks C5 First Currents enrollment.

### Cross-Reference to Prior Course Outputs

Every prompt in C4 receives the relevant C1-C3 artifacts as input context. This prevents validators from accepting work that has silently drifted from the student's prior commitments:

- **C1 Captain's Oath Clause 1 (territory)** — fed to offer-distinction-reviewer, offer-fit-validator
- **C1 Operator Identity** — fed to offer-fit-validator (archetype consistency)
- **C2 Mechanism Hypothesis Document** — fed to offer-distinction-reviewer (mechanism name anchor)
- **C3 Market Fit Hypothesis** — fed to every C4 reviewer
- **C3 Trigger Bank** — fed to value-equation-application-reviewer, landing-page-copy-reviewer, offer-fit-validator
- **C3 Pricing Signals** — fed to offer-fit-validator
- **C3 Customer Interview Library (summaries)** — fed to value-equation-application-reviewer, offer-fit-validator

Without this context, each reviewer would be scoring the submission against itself rather than against the student's prior work. Cross-reference is what keeps the chain coherent.

---

## Build 6 Integration

Build 6 handles chain orchestration via the following SQL functions (full definitions in `04_Tools-and-Infrastructure/Supabase-C4-Schema.md`):

- `check_c4_enrollment_eligible(user_id)` — prerequisite check at enrollment
- `route_c4_submission(user_id, module, artifact_blob)` — routes to correct reviewer; passes C1-C3 context
- `log_c4_review_result(user_id, module, verdict, feedback)` — writes to `c4_review_log` table
- `unlock_next_c4_module(user_id, current_module)` — gated by prior module PASS
- `check_c4_completion(user_id)` — verifies all 8 artifacts present with PASS status
- `route_c4_to_c5(user_id)` — on course complete, opens C5 enrollment

---

## Failure Mode Routing

| Failure Pattern | Triggered By | Routed To |
|---|---|---|
| Mechanism drift from C3 | offer-fit-validator Check 2.3 BLOCKING | Mentor queue; reopen C3 M3.7 |
| Fabricated Trigger Bank entries | offer-fit-validator Check 2.4 BLOCKING | Integrity review queue |
| Anti-promise softening | offer-fit-validator Check 1.3 WARNING | Revision guidance; student reverts |
| Feature Stuffing (deliverable count, guarantee stack) | Check 4.1, 4.2 WARNING | Revision guidance |
| Silent weakness whitewash | Check 3.1 WARNING | Revision guidance |
| Signature not signed | Check 5.1 BLOCKING | 30-second fix + resubmit |
| Value Equation universal strength | value-equation-application-reviewer Dimension 3 | Revision with honest weakness identification |
| Three variants without axis divergence | offer-decomposition-reviewer Check 2 | Genuine variant diversification required |

---

## Versioning

All prompts are versioned following semver (v1.0.0). Changes to rubric criteria trigger a minor version bump; changes to scoring thresholds trigger a patch bump. Quarterly review cadence is owned by the curriculum-quality team.

When a prompt version changes, Build 6 continues routing existing in-progress submissions to the prior version until the student clears that checkpoint; new submissions after the version bump route to the new version. This prevents mid-revision rubric changes from surprising students.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by Build 6*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Offer Ignition — Time Estimate

## Top-Line Numbers

- **Active work:** 40 hours
- **Elapsed time:** 4-5 weeks
- **Average per week:** 8-10 hours
- **Longest single module:** M4.7 Offer Landing Page Copy (4 hours active + peer review cycle)
- **Shortest single module:** M4.1 Offer Architecture Foundations (75 minutes active)

C4 is shorter in active hours than C3 because the work is internal writing rather than external research. Elapsed time, however, is only slightly shorter — writing improves on the second pass, and the 48-hour cooling period between first and second drafts of M4.3, M4.5, M4.7, and M4.8 compresses poorly.

---

## Active Work by Module

| Module | Active Work | Cumulative |
|---|---|---|
| M4.1 Offer Architecture Foundations | 75 min | 1:15 |
| M4.2 The Grand Slam Offer Framework | 90 min | 2:45 |
| M4.3 Offer Deconstruction and Reassembly | 180 min | 5:45 |
| M4.4 Pricing and Anchoring | 90 min | 7:15 |
| M4.5 The Anti-Promise Statement | 75 min | 8:30 |
| M4.6 Guarantee Architecture | 90 min | 10:00 |
| M4.7 Offer Landing Page Copy | 240 min | 14:00 |
| M4.8 Offer Readiness Document | 90 min | 15:30 |

Module activity subtotal: ~15-16 hours.

## Implementation Work (Beyond Module Active Time)

Module active work is module-internal only. Implementation work spans outside the module sessions:

| Implementation Activity | Hours |
|---|---|
| Re-reading C3 Market Fit Hypothesis and Trigger Bank | 1-2 |
| First-draft revision of M4.3 variants after 48-hour cooling | 2-3 |
| Landing page copy revision after first draft (M4.7) | 3-5 |
| Peer review of 2 cohort peers' landing page copy | 2-3 |
| Incorporating 2 peer reviews of own landing page copy | 1-3 |
| Anti-promise revision after guarantee decision | 1 |
| Pricing spreadsheet / unit economic sanity check | 1-2 |
| Readiness document draft + revision | 2-3 |
| Circle.so discussion and reflection posts | 1-2 |

Implementation subtotal: ~15-24 hours.

**Course total: ~30-40 hours active work, target 40.**

C4's total is firmly below C3's 45 hours because there is no external scheduling component. Writing time is writing time. Students who struggle to hit 40 hours typically do not need more study time — they need more honest drafts and a willingness to throw away the first one.

---

## Elapsed Time Breakdown

### 4-Week Pacing (aggressive, assumes peer reviews come back on SLA)

| Week | Focus | Major Deliverables Due |
|---|---|---|
| 1 | M4.1 + M4.2 complete | Distinction memo + Value Equation worksheet filed |
| 2 | M4.3 complete (3 variants); M4.4 pricing | 3 decomposition variants + Pricing Decision filed |
| 3 | M4.5 anti-promise + M4.6 guarantee | Anti-Promise + Guarantee filed; Honesty Clause signed |
| 4 | M4.7 landing page (draft + peer review + revise); M4.8 Readiness | Landing page copy + Readiness Document filed; C4 complete |

### 5-Week Pacing (default, with slack for revision and peer review latency)

| Week | Focus | Major Deliverables Due |
|---|---|---|
| 1 | M4.1 + M4.2 complete | Distinction memo + Value Equation worksheet filed |
| 2 | M4.3 variants drafted (48-hr cooling) + refined | 3 decomposition variants filed |
| 3 | M4.4 pricing + M4.5 anti-promise | Pricing Decision + Anti-Promise filed |
| 4 | M4.6 guarantee + M4.7 landing page first draft | Guarantee filed; landing page draft out for peer review |
| 5 | Peer review incorporated; M4.8 Readiness Document | Final landing page + Readiness Document filed; C4 complete |

### 6+ Week Scenarios (when to flag for mentor)

C4 elapsed times past week 6 usually trace to one of four causes:

1. **Student is rewriting the Primary mechanism at the M4.3 stage** — a signal that C3 M3.7 was waved through rather than decided. Mentor action: stop C4 work, return to C3 M3.5-M3.7 to properly close the Primary decision.

2. **Landing page copy has 6+ drafts** — perfectionism or the Feature Stuffing Trap. Mentor action: review Case-Failure-The-Feature-Stuffing-Trap.md; often the underlying issue is a Value Equation score (M4.2) that student is trying to fix in copy rather than in mechanism.

3. **Peer reviews not returning** — cohort is thin or reviewers are stalled. Mentor action: switch to Protocol A (mentor substitution) in Prerequisites-Checklist.

4. **Anti-promise paralysis** — student cannot bring themselves to write the specific disqualification statement in M4.5. Mentor action: single 30-minute call walking through why anti-promises increase conversion rather than decrease it, per Hopkins 1923 / Hormozi 2021.

Escalation to mentor is automatic after 7 weeks in C4 without completion.

---

## Daily Completion Checklist (Operational)

For students using the C1 85-Minute Rhythm, here is how C4 work maps into the rhythm. See also `02_Resources/Checklists/C4-Daily-Completion-Checklist.md` for a per-week printable version.

### Monday — 10 minutes
Open the C4 folder. Review what's due this week. Re-read yesterday's draft with fresh eyes. Jot 1-2 revision notes.

### Tuesday — 15 minutes
Either draft the next module section OR revise yesterday's draft OR send peer review feedback if assigned.

### Wednesday — 30 minutes (Deep Work)
The week's main drafting block. M4.3 variant drafting, M4.7 landing page section drafting, M4.8 Readiness Document drafting — whichever is the current focus.

### Thursday — 20 minutes
Revision pass on Wednesday's draft. Cut weak sentences. Replace paraphrased Trigger Bank quotes with verbatim originals.

### Friday — 10 minutes
Friday reflection in Circle.so. What felt hardest this week? Which module surprised you?

Total rhythm commitment: 85 minutes/week. C4 work beyond the rhythm (longer drafting sessions, peer review work) is on top of the rhythm, not replacing it.

---

## Time Adjustments by Operator Archetype

### Teacher-Operator

- **Typical strength:** Curriculum-thinking makes M4.3 decomposition variants natural; clear about what a buyer learns in each step
- **Typical weakness:** M4.4 pricing tends to under-price because Teacher-Operators instinctively compare to course prices ($197-$497) rather than to service or cohort prices ($1,500-$10K)
- **Suggested adjustment:** +1 hour on M4.4 specifically pricing the cohort and service variants against the C3 Pricing Signals rather than against self-paced course benchmarks

### Builder-Operator

- **Typical strength:** M4.2 Value Equation work is sharp; technical credibility shows through in the Dream Outcome variable
- **Typical weakness:** M4.7 landing page copy sometimes reads as feature list rather than outcome promise; the Trigger Bank is underused
- **Suggested adjustment:** +2 hours on M4.7 specifically replacing first-draft feature descriptions with verbatim Trigger Bank outcome language

### Service-Operator

- **Typical strength:** Natural at M4.3 decomposition because the service already contains implicit deliverables; easy to name them
- **Typical weakness:** M4.5 anti-promise is hardest — Service-Operators rarely want to turn away buyers
- **Suggested adjustment:** +1 hour on M4.5 specifically working through the three categories of buyers the Primary is not well-suited for, with peer accountability

### Product-Operator, Creative-Operator, Systems-Operator

Time estimates unchanged. Adjustments available in `02_Resources/Reference-Charts/C4-Archetype-Adjustments.md`.

---

## The 48-Hour Cooling Period — Why It Matters for Your Estimate

Four modules bake a mandatory 48-hour gap between first and second drafts: M4.3, M4.5, M4.7, M4.8. The gap does not count against "active work" — nothing is happening — but it does count against elapsed time.

The gap exists because offers written and published in a single sitting tend to read as written-and-published-in-a-single-sitting. Sentences that feel clever at the moment of writing almost always sound thin two days later. The cooling period produces a pass where the student reads the draft as if someone else wrote it — which is the point at which the weak sentences reveal themselves.

A student who tries to compress the gap (write and revise on the same day) can complete C4 in 3 weeks elapsed. The output will be readable. It will also be weaker than a version with the gap honored. The output quality gap is usually visible at C5 during the first-sale readiness test, by which point rework is expensive.

Plan for the full 4-5 weeks. It is not padding. It is how the draft improves.

---

## Accommodations

If you have accessibility needs or life circumstances that require adjusted pacing:

- **Email [email protected]** before enrollment; 48-hour response SLA
- **Standard adjustments available:** extended C4 timeline (up to 10 weeks), peer review accommodations (async voice or written rather than synchronous), dyslexia-friendly landing page copy review by mentor rather than by peer
- **Financial accommodations:** scholarship for paid review (Protocol C) if the cohort is thin and paid review is needed

---

*Last updated: April 24, 2026 · Version 2.0*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Preparation Checklist

**Purpose:** Pre-flight check before submitting M4.7 landing page copy for cohort peer review. Prevents common rework-causing gaps.
**Time to complete:** 15-20 minutes before submission
**Filed to:** Attached to your M4.7 submission

---

## Before You Submit

Running this checklist before posting in `#c4-offer-ignition` saves your peer reviewers 30-60 minutes per review and dramatically increases the quality of feedback you receive. Reviewers who have to hunt for your Trigger Bank Provenance Log, or who notice your anti-promise softened from M4.5, spend their review time on mechanical issues rather than substantive feedback.

---

## Section A — Document Completeness

- [ ] Landing page copy file exists at `Offer-Landing-Page-Copy-[YourName]-[Date].md`
- [ ] All 7 sections present in order:
  - [ ] Section 1 — Problem (200-400 words)
  - [ ] Section 2 — Agitation (150-300 words)
  - [ ] Section 3 — Solution-and-Mechanism (300-500 words)
  - [ ] Section 4 — Proof (200-400 words)
  - [ ] Section 5 — Offer (300-500 words)
  - [ ] Section 6 — Anti-Promise-and-Guarantee (250-400 words)
  - [ ] Section 7 — CTA (50-150 words)
- [ ] Total word count in 1,800-2,500 range (not absurdly over or under)

## Section B — Trigger Bank Usage

- [ ] Trigger Bank Provenance Log file exists at `Landing-Page-Trigger-Bank-Provenance-[YourName]-[Date].md`
- [ ] Log contains ≥ 15 entries mapped to landing page usage
- [ ] Every entry in the log is verbatim (not paraphrased) from the source Trigger Bank
- [ ] Each entry cites specific Trigger Bank ID (TB-###) or Interview #
- [ ] Entries are distributed across 4+ of the 7 sections (not all stacked in one section)

## Section C — Anti-Promise and Guarantee Integrity

- [ ] Anti-Promise in Section 6 is substantively the same as your M4.5 Anti-Promise Statement
- [ ] If any softening occurred between M4.5 and M4.7, it is reverted OR documented with rationale
- [ ] Anti-Promise Integrity Statement is signed
- [ ] Guarantee in Section 6 is substantively the same as your M4.6 Guarantee Architecture
- [ ] If any stacking occurred between M4.6 and M4.7, it is reverted
- [ ] Guarantee Honesty Clause is signed

## Section D — Offer Section Completeness

- [ ] Named deliverable (5-Test-passed name) visible in Section 5
- [ ] Price visible in Section 5 (not hidden, not ranged)
- [ ] Payment options listed
- [ ] Delivery structure described (engagement model, duration, cadence)
- [ ] Deliverables list is not over 8 items (Feature Stuffing Trap check)

## Section E — Proof Integrity

- [ ] Proof cases in Section 4 are specific (named or anonymized with specific outcome)
- [ ] If you have fewer than 4 named cases, the Known Weaknesses acknowledgment is visible (not papered over)
- [ ] Testimonials (if any) are verbatim quotes, not paraphrased
- [ ] Testimonials have attribution (name or anonymized but specific)

## Section F — CTA Specificity

- [ ] CTA names a specific action (not "click here")
- [ ] Next cohort / enrollment date is present
- [ ] Qualification process (if any) is described
- [ ] Contact email or channel is present for pre-purchase questions

## Section G — Voice Check

- [ ] You have read the full landing page out loud once, from start to finish
- [ ] The page does not contain phrases you would not actually say to a buyer in person
- [ ] The page does not contain hyperbole you cannot substantiate
- [ ] The page does not contain any of these phrases: "game-changer," "revolutionary," "transform your life," "all you need to do is" (low-substance signaling vocabulary)

## Section H — Review Request Post

Before posting in `#c4-offer-ignition`, prepare the post:

- [ ] Drive link to landing page copy
- [ ] Drive link to Trigger Bank Provenance Log
- [ ] Brief context (2-3 sentences about your offer's key positioning)
- [ ] Specific request: "2 peer reviews within 72 hours, using the C4 Peer Review Template"
- [ ] Your availability to return review favor (which days you can review others' copy)

---

## Common Pre-Submit Fixes

If any checklist item is unchecked, common fixes:

| Unchecked Item | Typical Fix |
|---|---|
| Section 6 softened from M4.5/M4.6 | Revert to the original M4.5 Anti-Promise and M4.6 Guarantee language |
| Trigger Bank count < 15 | Add 3-6 more verbatim entries, typically in Problem and Agitation sections |
| Deliverables > 8 | Review for Feature Stuffing; which deliverables are compensation, which are real value? |
| Price hidden or ranged | Move price to Section 5 with explicit number |
| Voice check fails | 48-hour cooling re-read; rewrite any section where "did I actually say that?" is your reaction |

---

## After Submission

Once posted:

- [ ] Check `#c4-offer-ignition` daily for reviewer pickup
- [ ] Respond promptly to reviewer questions
- [ ] Do not revise the landing page while reviews are in progress (creates version mismatch)
- [ ] Begin reviewing other cohort peers' landing pages as reviews arrive — reciprocity is cohort norm

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Outreach Scripts

**Purpose:** Short scripts for requesting and responding to peer reviews during M4.7. These are starter templates; adapt in your own voice.
**Filed to:** `03_Scripts-and-Prompts/Outreach-Scripts/`
**Referenced by:** M4.7 Written Lesson; C4-Peer-Review-Preparation-Checklist

---

## Script 1 — Requesting Peer Review (post in `#c4-offer-ignition`)

```
**M4.7 peer review request — [YourName]**

- **Offer name:** [5-Test-passed name]
- **Target buyer:** [one sentence describing who this is for]
- **Price:** $[X]
- **What I want reviewers to watch for specifically:**
  - [1-2 things you suspect may be weak — common: Section 4 Proof, Section 6 Anti-Promise softening, Trigger Bank entry density]

**Drive links:**
- Landing page copy: [link]
- Trigger Bank Provenance Log: [link]
- Revision Log (so far): [link — if you have one]

**SLA:** 72 hours ideal

**Reciprocity:** I'm available to review copy on [specific days this week]. Reply with yours and I'll pick up the first two.

Using the C4 Peer Review Template (`02_Resources/Templates/C4-Peer-Review-Template.md`).
```

### Why this structure works

Naming what you suspect is weak focuses reviewer attention. Without this, reviewers tend to spread feedback thin across the whole page. Concentrated attention on 1-2 sections produces higher-signal feedback.

---

## Script 2 — Offering Peer Review (response to another student's request)

```
I'll pick up your review, [TheirName]. I'll aim to deliver within 48 hours.

If you want me to pay particular attention to [suggested focus based on their request], I will. If you want me to do a straight full-template review, I'll do that too.

My C4 Peer Review Template will be back in your Drive folder or Circle.so thread by [specific date + time].
```

### Why this structure works

Confirms the commitment with a specific delivery time. Acknowledges their request-specific focus areas. Creates accountability for the delivery.

---

## Script 3 — Declining a Peer Review (when over-committed)

```
Thanks for tagging me, [TheirName]. I'm at capacity this week ([reason if relevant — e.g., "I'm in my own M4.7 cycle with deadline Thursday"]).

Tagging [OtherName] who mentioned they had bandwidth this week. You can also use the Alternate Protocol at `02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md` if the cohort is thin at your pacing — Protocol A (mentor substitution) is available.
```

### Why this structure works

Declining without leaving the requester stranded. Referring to Alternate Protocol reminds the requester that the safety net exists.

---

## Script 4 — Delivering Peer Review (after completing the template)

```
[TheirName] — review complete.

**Template:** [Drive link to completed Peer Review Template]

**Top-level observation:** [one sentence — your overall impression]

**My three recommended revisions (from template):**
1. [brief version]
2. [brief version]
3. [brief version]

Happy to discuss any of these in async DM if useful. Good luck with M4.8.
```

### Why this structure works

Surfaces the most actionable takeaway in the message itself so the requester can start revising without waiting to open the full template. The full template provides depth; the message provides urgency.

---

## Script 5 — Responding to Peer Review (after incorporating)

```
[ReviewerName] — thanks for the review. Incorporated as follows:

- **Revision 1 you recommended:** [incorporated / incorporated with modification / not incorporated + reason]
- **Revision 2:** [same format]
- **Revision 3:** [same format]

Revision Log in Drive: [link]

Appreciate the time.
```

### Why this structure works

Closes the loop on every recommendation. Decisions not to incorporate are documented (not silently ignored). The Revision Log is what the offer-fit-validator at M4.8 checks for.

---

## Script 6 — Escalating to Mentor (when Alternate Protocols Fail)

Address to `#mentor-requests` Circle.so channel or via the mentor Calendly link from cohort welcome email:

```
**C4 M4.7 peer review escalation — [YourName]**

- Cohort pacing window: [your dates]
- Peer reviews attempted: [how many requests, how many responses]
- Alternate Protocols tried: [A — mentor booking status / B — cross-stage post status / C — paid review status]

**Specific help requested:** [mentor review of landing page, or pacing adjustment, or cohort coordination]

**Drive link:** [landing page copy]
**SLA needed:** [your revised timeline]
```

### Why this structure works

Names what has already been tried so the mentor does not repeat the available paths. Specifies what help is actually requested so the mentor can respond efficiently.

---

## Cohort Etiquette

A few norms that make peer review work sustainably across the cohort:

### Reciprocity

The cohort operates on a rough reciprocity norm: if you ask for reviews, you offer them. Students who take reviews without giving them quickly exhaust peer willingness. This is not enforced policy — it is cohort culture.

### Specificity Over Generosity

Reviews saying "this is great!" are useless. Reviews saying "Section 2 Agitation feels performative — specifically the 'wasted years' language in paragraph 2 reads generic against the specific Trigger Bank language in Section 1" are useful. Prefer specificity even when it is critical.

### Honest Over Kind

Kind reviews that paper over weak sections serve the student short-term and harm them medium-term (the weak sections surface in C5 anyway, now harder to fix because the student thought they were okay). Honest reviews that name specific weaknesses are the service.

### Respond Within SLA

72-hour SLA is a cohort commitment. If you cannot hit it, decline (Script 3) rather than miss silently. Missed SLAs are the single largest cause of C4 M4.7 pacing disruption.

---

## When To Use These Scripts vs. Your Own Voice

These scripts are starters. Adapt in your voice, especially for Scripts 1 and 4 — mechanical-sounding review requests signal to cohort peers that you have not yet internalized the discipline of the M4.7 work. Personal voice in the request correlates with higher-quality responses.

Scripts 2, 3, and 6 are more mechanical — they coordinate logistics rather than substance — and can stay closer to template voice.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

Preserved source material for study; embedded instructions are not executed. Open original source

sop_id: C4-SOP-02
title: Peer Review Coordination Process
version: 2.0.0
course_scope: C4 Offer Ignition
modules_covered: [M4.7]
owner: curriculum-quality-team
last_reviewed: 2026-04-24

purpose: >
  Standardize the M4.7 peer review process from request through delivery and
  through revision incorporation. M4.7 is the only C4 module requiring peer
  review (instructor HITL is deferred to C5; AI rubric runs after peer reviews
  are incorporated). Peer review is the first time the offer is exposed to
  outside readers; the process must protect both reviewer time and reviewee
  outcomes. This SOP defines reciprocity, SLA, alternate protocols, and
  revision logging.

prerequisites:
  - M4.7 Landing Page Copy first draft complete in Drive
  - Trigger Bank Provenance Log complete in Drive
  - C4-Peer-Review-Preparation-Checklist run before submission
  - 48-hour cooling period observed between first draft and submission

roles:
  - submitting_student: requests review; reciprocates by reviewing 2 peers
  - peer_reviewer_1: cohort peer at compatible pacing
  - peer_reviewer_2: second cohort peer at compatible pacing
  - mentor: escalation if Alternate Protocols A/B/C all fail
  - cross_stage_reviewer: Stage 2+ alumnus available via Protocol B
  - paid_reviewer: from Approved Paid Review Options list (Protocol C)
  - build_6: tracks SLA, matches reviewers, gates M4.7 checkpoint progression

process:
  step_1:
    name: Pre-Submission Self-Audit
    time: 20 min
    output: Completed Peer Review Preparation Checklist
    activities:
      - Run C4-Peer-Review-Preparation-Checklist sections A through H
      - Address any unchecked items before posting review request
      - Verify Trigger Bank entry count >= 15 with Provenance Log complete
      - Verify anti-promise unchanged from M4.5; verify guarantee unchanged from M4.6
    quality_gate: All preparation checklist items checked; if any item is unchecked, fix before requesting review
    common_failures:
      - "Posting request before Trigger Bank entries reach 15"
      - "Posting request with anti-promise softened from M4.5 (peer reviewers will flag, costing 24-48 hours)"
      - "Forgetting to attach Trigger Bank Provenance Log"
    mitigation: The checklist exists specifically to catch these. Run it.

  step_2:
    name: Request Review (Standard Protocol)
    time: 15 min
    output: Review request post in #c4-offer-ignition Circle.so channel
    activities:
      - Use Outreach Script 1 from C4-Peer-Review-Outreach-Scripts.md
      - Specify offer name, target buyer, price, areas you suspect are weak
      - Attach Drive links to landing page copy AND Trigger Bank Provenance Log
      - State 72-hour SLA expectation
      - Offer specific reciprocity (which days you can review others' copy this week)
    quality_gate: Post visible in #c4-offer-ignition; request structure matches Outreach Script 1
    common_failures:
      - "Vague request without specifying suspected-weak sections (reviews come back generic)"
      - "Not offering reciprocity (cohort norm violated; future review requests slower to receive responses)"
      - "Missing Provenance Log attachment (reviewers can't verify Trigger Bank usage)"
    mitigation: Use the script verbatim until it becomes natural

  step_3:
    name: Reviewer Pickup (24-48 hours from request)
    time: passive
    output: 2 peers commit to review with stated delivery dates
    activities:
      - Build 6 sends notification to active cohort peers at compatible pacing
      - Peers respond using Outreach Script 2 (acceptance) or Script 3 (decline with referral)
      - Build 6 logs commitments and tracks SLA
      - If only 1 reviewer commits within 48 hours, Build 6 escalates per step 4a
    quality_gate: 2 reviewers committed within 48 hours
    common_failures:
      - "Cohort thin at student's pacing (Protocol A activates)"
      - "Reviewers who committed silently miss SLA without communication"
    mitigation: Build 6 active SLA tracking surfaces silent misses; cohort norm includes communicating early if SLA at risk

  step_4_alternate_protocol_a:
    name: Mentor Substitution (Protocol A)
    time: 24 hours from activation
    output: Mentor named as reviewer; review delivered within 72 hours
    activation_trigger: Cohort has < 4 active peers at compatible pacing OR < 2 peers commit within 48 hours
    activities:
      - Student books mentor review slot via Calendly link in cohort welcome email
      - OR Student posts in #mentor-requests with M4.7 review request
      - Mentor delivers full Peer Review Template completion within 72 hours
      - Mentor review counts as both required peer reviews
    quality_gate: Mentor review filed with C4-Peer-Review-Template completion
    common_failures:
      - "Mentor booking backed up 2+ weeks during high-enrollment cycle (rare; route to Protocol B)"

  step_4_alternate_protocol_b:
    name: Cross-Stage Review (Protocol B)
    time: 96 hours from activation
    output: 1-2 Stage 2+ alumni reviewers complete review
    activation_trigger: Mentor backed up; OR student prefers reviewer who has shipped offers
    activities:
      - Student posts in #cross-stage-review channel using request format from Alternate Protocol document
      - Stage 2-5 operators who actively volunteer review time pick up the request
      - Review uses C4 Peer Review Template
      - Cross-stage review counts as both required reviews, OR pairs with one peer/mentor review
    quality_gate: Cross-stage review filed
    common_failures:
      - "No cross-stage reviewer picks up within 48 hours (route to Protocol C)"

  step_4_alternate_protocol_c:
    name: Approved Paid Review (Protocol C — Last Resort)
    time: 48-72 hours from activation
    output: Paid reviewer completes review using C4 Peer Review Template
    activation_trigger: Protocols A and B unavailable within student's planned week
    activities:
      - Student selects from C4-Approved-Paid-Review-Options.md (Tier A/B/C)
      - Direct engagement; Academy does not facilitate payment
      - Paid reviewer completes C4 Peer Review Template
      - Paid review counts as 1 of 2 required reviews; must pair with peer/mentor/cross-stage for second
      - Methodology consistency check: any methodology-conflicting paid feedback flagged before incorporation
    quality_gate: Paid review filed; second review (peer/mentor/cross-stage) also filed
    common_failures:
      - "Paid reviewer recommends removing anti-promise (methodology-conflict; do not incorporate without mentor consult)"
      - "Paid reviewer recommends stacking guarantees (methodology-conflict)"
      - "Student counts paid review as both required reviews (not allowed)"
    mitigation: Approved Paid Review document provides methodology baseline language to send to paid reviewer

  step_5:
    name: Receive and Read Reviews
    time: 30 min (do not act yet)
    output: Both reviews read in single sitting
    activities:
      - Wait until both reviews have arrived before reading either
      - Read both in one sitting; note patterns
      - If both reviewers flagged the same section as weak, that section is genuinely weak
      - If reviewers disagree, use your judgment
      - Do not begin revision yet — sleep on the feedback
    quality_gate: Both reviews read; pattern notes captured
    common_failures:
      - "Reading first review and immediately starting revisions before second review arrives (creates whiplash if reviewers disagree)"
      - "Defending against feedback in your head without genuinely considering it"
    mitigation: 12+ hour gap between reading and revising; treat reviews as gifts, not attacks

  step_6:
    name: Draft Revision Log + Revise
    time: 60-90 min
    output: Revision Log file + revised landing page in Drive
    activities:
      - Open C4-Peer-Review-Outreach-Scripts.md Script 5 template
      - For each suggestion in each review: incorporated / incorporated with modification / not incorporated + reason
      - Document each decision; the offer-fit-validator at M4.8 reads this
      - Revise landing page based on incorporated suggestions
      - Address pattern-flagged sections (those flagged by both reviewers) with priority
    quality_gate: Revision Log complete; revised landing page in Drive
    common_failures:
      - "Skipping the Revision Log (validator at M4.8 will flag missing log)"
      - "Incorporating every suggestion mechanically (you should make decisions, not absorb)"
    mitigation: The Log is the structural mechanism that forces decision-making; do not skip

  step_7:
    name: Reciprocate
    time: 90-120 min total (45-60 min per review × 2)
    output: 2 completed peer reviews delivered to other students
    activities:
      - During or after your own revision cycle, complete 2 peer reviews for cohort peers
      - Use C4-Peer-Review-Template for each
      - Deliver via Outreach Script 4 from outreach scripts document
      - Reciprocity is cohort norm; tracking is light but reputation matters
    quality_gate: 2 reviews delivered; Build 6 logs reciprocity in cohort metrics
    common_failures:
      - "Receiving reviews and not reciprocating (silent reputation cost; future requests slower to receive responses)"
      - "Reciprocating with low-effort 'looks great!' reviews (worse than declining; harms peer's revision quality)"
    mitigation: If you genuinely cannot reciprocate this cycle, decline future review requests until you can; do not free-ride

  step_8:
    name: Submit Revised Landing Page to AI Rubric
    time: 5 min + 5 min for rubric run
    output: landing-page-copy-reviewer score >= 7/10
    activities:
      - Submit revised landing page + provenance log + revision log to Build 6
      - Build 6 invokes landing-page-copy-reviewer-v1.0.0.yaml
      - Verify peer_review_count >= 2 in submission metadata
      - Receive rubric score within 5 minutes
    quality_gate: Score >= 7/10; peer_review_count = 2; no integrity flags
    common_failures:
      - "Submitting without filing the Revision Log first (rubric flags missing artifact)"
      - "Trigger Bank entries fabricated or paraphrased (rubric flags as integrity issue)"
    mitigation: All checks should already have passed in step 5-6; if rubric flags appear, fix and resubmit

review_and_adjustment:
  cadence: Per cohort cycle
  questions_to_ask:
    - "What % of M4.7 submissions used Standard Protocol vs Alternate Protocol A/B/C?"
    - "What was the median time from review request to review delivery?"
    - "What % of reviewers met SLA without escalation?"
    - "What % of paid reviewers gave methodology-conflicting feedback?"
  adjustment_principles:
    - If Alternate Protocol A activation > 30%, expand mentor capacity OR extend cohort recruitment to thicken cohorts
    - If paid reviewer methodology conflicts > 20%, refresh paid reviewer Affiliate Agreements OR remove specific reviewers from Approved list
    - If reciprocity ratio (reviews given / reviews received) < 0.85, surface in cohort discussion

escalation_triggers:
  - 3+ submissions fail M4.7 rubric on same student (mentor diagnosis)
  - Reviewer fabrication or methodology-conflicting feedback (Affiliate Agreement review)
  - Reciprocity ratio < 0.5 for individual student over 2 cohorts (cohort norm conversation)
  - Cohort thinning > 3 weeks consecutive (Build 6 → Marketing for cohort recruitment review)

related_documents:
  - 02_Resources/Templates/C4-Peer-Review-Template.md
  - 02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md
  - 02_Resources/Templates/C4-Approved-Paid-Review-Options.md
  - 02_Resources/Checklists/C4-Peer-Review-Preparation-Checklist.md
  - 03_Scripts-and-Prompts/Outreach-Scripts/C4-Peer-Review-Outreach-Scripts.md
  - 03_Scripts-and-Prompts/Claude-System-Prompts/landing-page-copy-reviewer-v1.0.0.yaml

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Template — M4.7 Landing Page Copy

**Purpose:** Structured template for cohort peer reviews of M4.7 landing page copy. Two peer reviews per student are required; students complete two reviews for peers in exchange.
**Time per review:** ~45-60 minutes
**Timeline:** 72-hour SLA from review request to delivery
**Filed to:** Build 8 Drive folder; linked into submitting student's M4.7 folder

---

## Reviewer Instructions

Read the landing page copy and the Trigger Bank Provenance Log in one pass, then complete the template below. Your job is not to edit line-by-line — the submitting student will do that. Your job is to surface structural issues they cannot see from inside their own draft.

Three things you are specifically looking for:

1. **Does the page sound like the market or like the operator?** You are an outside reader who has not been inside this operator's head for 4 weeks. You can hear voice drift more clearly than they can.

2. **Are the verbatim Trigger Bank quotes doing work, or are they decorative?** Quotes should anchor specific claims. A quote dropped next to a general statement without connection is not working.

3. **Is the anti-promise actually specific, and is the guarantee actually clean?** M4.5 and M4.6 stand-alone documents can be strong but get softened in the landing page. You are the second set of eyes that catches softening.

---

## Reviewer Information

**Reviewer name:** _____________________________
**Reviewer operator archetype:** _____________________________
**Review date:** _____________________________
**Submitting operator name:** _____________________________
**Submitting operator's offer name:** _____________________________

---

## Section-by-Section Review

### Section 1 — Problem

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak
**One-sentence read:** [What is this operator's offer trying to solve, in your words?]

Does the Problem section make the buyer's current state specific and vivid?
☐ Yes, I could visualize it ☐ Partially ☐ No, it was generic

Was at least one verbatim Trigger Bank quote integrated meaningfully (not decoratively)?
☐ Yes ☐ Partially ☐ No

**Specific observations (1-3 sentences):**

---

### Section 2 — Agitation

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Does the Agitation section make the cost of *not acting* feel real, or does it feel performative?
☐ Real ☐ Mixed ☐ Performative

Did any specific numbers, time-frames, or opportunity costs make the Agitation land?
☐ Yes (which ones: __________) ☐ No

**Specific observations:**

---

### Section 3 — Solution-and-Mechanism

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

After reading this section, can you describe the mechanism in your own words?
☐ Yes, I could teach it to a friend ☐ Roughly ☐ No, it's still fuzzy

Are the 4 pillars of the mechanism visible, even if not labeled as pillars?
☐ Yes ☐ Partially ☐ No

**Specific observations:**

---

### Section 4 — Proof

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Are the proof cases specific (named, with outcome data), or are they generic ("Maya is great")?
☐ Specific ☐ Mixed ☐ Generic

If the operator has few case studies, is that acknowledged honestly, or is it papered over?
☐ Acknowledged honestly ☐ Handled in between ☐ Papered over

**Specific observations:**

---

### Section 5 — Offer

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Is the named deliverable clear, specific, and 5-Test-passed?
☐ Yes ☐ Partially ☐ No (how could it be clearer: __________)

Is the price visible on the page?
☐ Yes, clearly ☐ Present but buried ☐ Not visible

Does the delivery structure tell you what the buyer's experience actually is (what they do, when, with whom)?
☐ Yes, concretely ☐ Vaguely ☐ Not really

**Specific observations:**

---

### Section 6 — Anti-Promise-and-Guarantee

**This is the most important section to peer-review.**

**Anti-Promise strength:** ☐ Strong ☐ Adequate ☐ Weak

Does the anti-promise name three specific exclusions?
☐ Yes, three or more ☐ Two ☐ One or fewer

Are any of the "exclusions" actually flattering descriptions of the target buyer (e.g., "not for unmotivated people")?
☐ No, they are genuine exclusions ☐ One or two are flattering-dressed-as-exclusion ☐ Most are

**Guarantee strength:** ☐ Strong ☐ Adequate ☐ Weak

Is the guarantee a clean structure (one primary + one optional complementary), or is it stacked with three or more components?
☐ Clean ☐ Borderline ☐ Stacked (Feature Stuffing Trap signal)

If you were a buyer who met the activation conditions, do you trust this operator would honor the guarantee without friction?
☐ Yes ☐ Mostly ☐ Uncertain

**Specific observations:**

---

### Section 7 — CTA

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Does the CTA name a specific action (not "click here") and a specific outcome ("enroll in the Feb 12 cohort, receive Welcome Kit within 24 hours")?
☐ Yes, specific ☐ Partially ☐ Generic

Is there a clear timeline (cohort start date, enrollment close date)?
☐ Yes ☐ No

**Specific observations:**

---

## Cross-Cutting Review

### Verbatim Trigger Bank Usage

Pick 3 of the Trigger Bank quotes used in the landing page. Check them against the Provenance Log — do they match the source entry verbatim, or have they been paraphrased into "cleaner" language?

- **Quote #1:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased
- **Quote #2:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased
- **Quote #3:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased

**Overall provenance accuracy:** ☐ Strong (all 3 verbatim) ☐ Mixed ☐ Weak (paraphrasing is dominant)

### Voice Check

Does the page sound like the operator or like the market?
☐ Mostly market voice ☐ Mixed (operator voice leaks through in specific sections: __________) ☐ Mostly operator voice

### Total Trigger Bank Entry Count

Count the verbatim quotes in the landing page.
**Count:** ___ / 15 minimum

If below 15, the submission fails the M4.7 checkpoint.

---

## Top-3 Revisions You Recommend

Identify the three revisions that would most improve this landing page:

1. **Revision 1:**
2. **Revision 2:**
3. **Revision 3:**

Each revision should be specific enough that the operator can act on it ("tighten the Problem section opening from 4 sentences to 2") rather than abstract ("improve the copy").

---

## Reviewer Closeout

**Overall assessment:** ☐ Ready to submit ☐ Needs moderate revision ☐ Needs substantial revision

**Would I buy this offer if I were the target buyer?** ☐ Yes ☐ Maybe ☐ No — and why: __________

**Reviewer signature:** _____________________________

---

## For the Submitting Operator

After receiving both peer reviews:

1. Read both reviews in one sitting before acting on either. Look for patterns — if both reviewers flagged the same section as weak, that section needs real work. If they disagree, use your judgment.

2. Your job is not to accept every suggestion. Your job is to take each suggestion seriously and make a documented decision about whether to incorporate it.

3. File a Revision Log (`Revision-Log-M4.7-[YourName]-[Date].md`) noting which suggestions you incorporated, which you considered but did not incorporate, and why. The offer-fit-validator at M4.8 checks for this log.

4. Revise. Submit the revised landing page to the AI rubric (`landing-page-copy-reviewer-v1.0.0.yaml`).

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Peer Review Alternate Protocol

**Purpose:** Alternate paths when your active C4 cohort has fewer than 4 peers at your pacing window. Ensures M4.7 does not stall for reviewer unavailability.
**Referenced by:** `00_Course-Overview/C4-Prerequisites-Checklist.md`
**Escalation path:** If none of the protocols below are viable, escalate to RISER Nation mentor within 72 hours of M4.7 draft completion.

---

## When to Use This Protocol

Use when any of the following is true:

- Your C4 cohort Circle.so channel (`#c4-offer-ignition`) has fewer than 4 active operators at your pacing window
- Cohort peers at your pacing window have not responded within 72 hours of your review request
- Your cohort is pacing unusually (ahead or behind the main cohort cycle) and peers are not currently at M4.7

---

## Protocol A — Mentor Substitution (Default)

**Who it's for:** Any student whose cohort is too thin for 2 peer reviews.

**How it works:**

1. Book a 45-minute review slot with a named RISER Nation mentor via the Calendly link in the cohort welcome email, or via the `#mentor-requests` Circle.so channel.
2. Submit your M4.7 draft and Trigger Bank Provenance Log at least 24 hours before the review call.
3. The mentor completes the C4 Peer Review Template during or after the call and delivers a written review within 72 hours.
4. Mentor review counts as both required peer reviews. No additional review needed.

**SLA:** 72 hours from submission to written review delivery (typical) ; 96 hours worst-case.

**Cost:** No charge. Mentor capacity is allocated out of Academy program support time.

**When Protocol A is not available:** Mentor booking backed up 2+ weeks. Rare but happens in high-enrollment cycles. Shift to Protocol B.

---

## Protocol B — Cross-Stage Review

**Who it's for:** Students whose mentor booking is backed up, or who prefer review from an operator who has already shipped offers.

**How it works:**

1. Post a review request in the `#cross-stage-review` Circle.so channel with the following structure:

   ```
   **Cross-stage review request — C4 M4.7**
   - Operator archetype: [Teacher / Service / Builder / etc.]
   - Territory: [one sentence]
   - Offer name: [the 5-Test-passed name]
   - Request: 1-2 Stage 2+ operators for M4.7 landing page review
   - SLA: 96 hours
   - Drive link: [link to your draft]
   - Trigger Bank Provenance Log: [link]
   ```

2. Stage 2, Stage 3, Stage 4, or Stage 5+ operators who are active volunteers pick up the review.
3. Review uses the same C4 Peer Review Template.
4. Cross-stage review counts as both required peer reviews, or as one review paired with a mentor/peer review.

**SLA:** 96 hours (longer than peer review because cross-stage operators volunteer review time around their own operation).

**Cost:** No charge. Typically treated as ecosystem reciprocity; Stage 2+ operators accumulate review credit that Stage 1 peers volunteer back.

**Why this can be better than peer review:** Reviewers who have shipped offers have firsthand knowledge of what survives first-sale contact and what does not. Their feedback often has higher signal-to-noise than peer-to-peer review.

**When Protocol B is not available:** No cross-stage reviewer picks up the request within 48 hours. Rare but happens near holiday periods. Shift to Protocol C.

---

## Protocol C — Paid Review (Last Resort)

**Who it's for:** Students whose timeline is blocked and Protocols A and B did not clear within their planned week.

**How it works:**

1. Choose from the Approved Paid Review list in `C4-Approved-Paid-Review-Options.md`.
2. Directly engage the reviewer (paid engagement; Academy does not facilitate payment).
3. Paid reviewer completes the C4 Peer Review Template.
4. Paid review counts as one of the two required reviews. **Paid review alone is not sufficient** — pair with one mentor, cross-stage, or peer review.

**SLA:** per reviewer contract, typically 48-72 hours.

**Cost:** Varies by reviewer. Typical range: $150-$400 per review.

**When Protocol C is genuinely necessary:** rare. Most students who think they need Protocol C actually have a timing problem that Protocol A or B resolves with a slight pacing adjustment (waiting 3-5 extra days for mentor or cross-stage slot).

**Warning:** paid review is a legitimate professional service but is not a substitute for cohort accountability. Paid reviewers who are not familiar with RISER Nation methodology sometimes give advice that conflicts with C3/C4 doctrine (e.g., suggesting feature-stuffed guarantees or removal of the anti-promise section). Review paid feedback critically against the module lessons; do not incorporate paid advice that conflicts with the methodology without checking with a mentor.

---

## Scholarship Path for Protocol C

If your cohort is thin, Protocols A and B are unavailable within your timeline, and Protocol C is financially inaccessible:

1. Email `[email protected]` with "C4 M4.7 Review Scholarship Request" in the subject line
2. Include your Drive link, pacing dates, and which Protocols were attempted
3. SLA: 48 hours for response; if approved, scholarship covers one paid review up to $200

Scholarship approval is typical for genuine thin-cohort situations.

---

## Logging the Alternate Protocol

Whatever Protocol you used, log it in your M4.7 Revision Log so the offer-fit-validator at M4.8 has the context:

```
Peer Review Protocol: [A — Mentor / B — Cross-Stage / C — Paid + one of A or B / Standard two-peer]
Reviewer 1: [name, protocol, date of review]
Reviewer 2: [name, protocol, date of review]
Alternate protocol rationale: [1-2 sentences]
```

The offer-fit-validator does not penalize Alternate Protocol usage — it penalizes missing reviews. Logging the protocol used keeps the validator's coherence checks from flagging the submission.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by C4-Prerequisites-Checklist*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Approved Paid Review Options

**Purpose:** Reference list of paid review providers vetted by RISER Nation for C4 M4.7 landing page review when cohort peer and mentor options are unavailable (Protocol C in the Peer Review Alternate Protocol).
**Referenced by:** `C4-Peer-Review-Alternate-Protocol.md`
**Status:** This list is maintained by the Academy team and updated quarterly. The version below reflects approved reviewers as of the Last Updated date.

---

## Selection Criteria

To appear on this list, a reviewer has:

- Reviewed at least 20 C4-style offer landing pages in the direct-response tradition
- Demonstrated familiarity with mechanism-based offer construction (Hormozi-adjacent methodology)
- Produced reviews that respect the anti-promise section as a credibility mechanism (rather than recommending its removal)
- Signed the RISER Nation Reviewer Affiliate Agreement — which commits them to methodology-consistent feedback
- Been cross-rated by at least 5 past reviewees as useful and non-disruptive

Reviewers without these properties are excluded from the list, regardless of market reputation.

---

## Current Approved Reviewers (Quarterly Update — Q2 2026)

### Tier A — Deep Direct-Response Specialists

These reviewers have 10+ years of direct-response copy experience. Pricing reflects seniority.

- **Reviewer Slot A1** — [reviewer name redacted for template; actual list maintained in Drive]
  - **Pricing:** $350-$450 per review
  - **SLA:** 72 hours
  - **Specialty:** coaching/consulting offers; cohort programs; Teacher-Operator and Service-Operator archetypes
  - **Contact:** [via Calendly link in Drive version]

- **Reviewer Slot A2**
  - **Pricing:** $300-$400 per review
  - **SLA:** 48-72 hours
  - **Specialty:** productized services; Builder-Operator archetype
  - **Contact:** [via Drive]

### Tier B — Mid-Senior Reviewers

5-10 years of direct-response experience. Pricing is moderate.

- **Reviewer Slot B1**
  - **Pricing:** $200-$275 per review
  - **SLA:** 48-72 hours
  - **Specialty:** creative services; Creative-Operator archetype
  - **Contact:** [via Drive]

- **Reviewer Slot B2**
  - **Pricing:** $175-$250 per review
  - **SLA:** 72 hours
  - **Specialty:** B2B offers; systems and platforms; Systems-Operator archetype
  - **Contact:** [via Drive]

### Tier C — RISER Nation Alumni Reviewers

Alumni who have completed Stage 2+ of the Academy and offer paid review to Stage 1 peers. Often the best value — they know the methodology cold and price accordingly.

- **Reviewer Slot C1-C5** — rotating list, currently 5 alumni reviewers available
  - **Pricing:** $150-$200 per review
  - **SLA:** 48-72 hours
  - **Specialty:** matches the alumni's own operator archetype; check Drive list for match
  - **Contact:** [via Drive; alumni reviewers coordinate through `#alumni-review-pool` Circle.so channel]

---

## How To Engage a Paid Reviewer

1. **Check the Drive version of this list** for current names, contact info, and availability status. Names are not in this template to avoid stale information when reviewers rotate.

2. **Match reviewer to your archetype.** A Teacher-Operator reviewing a Service-Operator's offer will sometimes give advice that is methodology-correct but archetype-mismatched. Tier A reviewers are generalists; Tier B and C reviewers are archetype-specialized.

3. **Send your M4.7 draft and Trigger Bank Provenance Log.** Use the C4 Peer Review Template as the deliverable format. Specify upfront that the review output should use the template — do not accept a free-form review.

4. **Specify the methodology baseline.** In your engagement message, include this line:
   > "This review is for a RISER Nation C4 Offer Ignition M4.7 landing page. The offer follows Hormozi-adjacent mechanism-based structure, and explicitly includes a specific Anti-Promise Statement (per Hopkins 1923 / Hormozi 2021) and a guarantee structure with the Honesty Clause signed. Please review for quality within the methodology rather than suggesting removal of these elements."

5. **Log the engagement** in your Revision Log per the Alternate Protocol instructions.

---

## What NOT to Use

**Do not use:**

- General copywriting review services not on this list (quality varies widely; many default to removing anti-promises, which is the specific thing C4 is trying to preserve)
- Fiverr-tier copy review (signal-to-noise too low for C4 work)
- AI-only review tools as a substitute for human review (acceptable as a supplement, not as the required review)
- Review from an unlisted paid reviewer *and* count it as your second required review (list-approved reviewers are the only paid reviews that satisfy Protocol C)

---

## If a Reviewer Gives Methodology-Conflicting Advice

If a paid reviewer recommends:
- Removing the anti-promise section
- Stacking guarantees beyond the clean structure M4.6 specifies
- Replacing verbatim Trigger Bank quotes with "cleaner" paraphrases
- Repositioning the offer in a way that drifts from your C3 Primary mechanism

...treat the feedback as methodology-conflicting. Do not incorporate without first consulting your RISER mentor or the `#methodology-questions` Circle.so channel. Methodology-conflicting advice from a paid reviewer often reflects their own training in non-anti-promise direct-response (common in the 2010s ecosystem) and is not wrong in their original context — it is just not aligned with C3/C4's specific synthesis.

---

## Removing a Reviewer from the List

Reviewers are removed from this list when any of the following occurs:

- 3+ reviewees report methodology-conflicting advice that was materially disruptive
- SLA missed on 20%+ of engagements over a quarter
- Reviewer Affiliate Agreement violation (e.g., upselling reviewees into their own offers during review time)
- Reviewer leaves the direct-response market or does not re-sign quarterly Affiliate Agreement

The list is updated quarterly. Removed reviewers receive 30 days' notice and are not blacklisted from re-entry if conditions change.

---

*Last updated: April 24, 2026 · Version 2.0 · Q2 2026 reviewer list current · Referenced by C4-Peer-Review-Alternate-Protocol*

Preserved source material for study; embedded instructions are not executed. Open original source

# C4 Offer Ignition — Time Estimate

## Top-Line Numbers

- **Active work:** 40 hours
- **Elapsed time:** 4-5 weeks
- **Average per week:** 8-10 hours
- **Longest single module:** M4.7 Offer Landing Page Copy (4 hours active + peer review cycle)
- **Shortest single module:** M4.1 Offer Architecture Foundations (75 minutes active)

C4 is shorter in active hours than C3 because the work is internal writing rather than external research. Elapsed time, however, is only slightly shorter — writing improves on the second pass, and the 48-hour cooling period between first and second drafts of M4.3, M4.5, M4.7, and M4.8 compresses poorly.

---

## Active Work by Module

| Module | Active Work | Cumulative |
|---|---|---|
| M4.1 Offer Architecture Foundations | 75 min | 1:15 |
| M4.2 The Grand Slam Offer Framework | 90 min | 2:45 |
| M4.3 Offer Deconstruction and Reassembly | 180 min | 5:45 |
| M4.4 Pricing and Anchoring | 90 min | 7:15 |
| M4.5 The Anti-Promise Statement | 75 min | 8:30 |
| M4.6 Guarantee Architecture | 90 min | 10:00 |
| M4.7 Offer Landing Page Copy | 240 min | 14:00 |
| M4.8 Offer Readiness Document | 90 min | 15:30 |

Module activity subtotal: ~15-16 hours.

## Implementation Work (Beyond Module Active Time)

Module active work is module-internal only. Implementation work spans outside the module sessions:

| Implementation Activity | Hours |
|---|---|
| Re-reading C3 Market Fit Hypothesis and Trigger Bank | 1-2 |
| First-draft revision of M4.3 variants after 48-hour cooling | 2-3 |
| Landing page copy revision after first draft (M4.7) | 3-5 |
| Peer review of 2 cohort peers' landing page copy | 2-3 |
| Incorporating 2 peer reviews of own landing page copy | 1-3 |
| Anti-promise revision after guarantee decision | 1 |
| Pricing spreadsheet / unit economic sanity check | 1-2 |
| Readiness document draft + revision | 2-3 |
| Circle.so discussion and reflection posts | 1-2 |

Implementation subtotal: ~15-24 hours.

**Course total: ~30-40 hours active work, target 40.**

C4's total is firmly below C3's 45 hours because there is no external scheduling component. Writing time is writing time. Students who struggle to hit 40 hours typically do not need more study time — they need more honest drafts and a willingness to throw away the first one.

---

## Elapsed Time Breakdown

### 4-Week Pacing (aggressive, assumes peer reviews come back on SLA)

| Week | Focus | Major Deliverables Due |
|---|---|---|
| 1 | M4.1 + M4.2 complete | Distinction memo + Value Equation worksheet filed |
| 2 | M4.3 complete (3 variants); M4.4 pricing | 3 decomposition variants + Pricing Decision filed |
| 3 | M4.5 anti-promise + M4.6 guarantee | Anti-Promise + Guarantee filed; Honesty Clause signed |
| 4 | M4.7 landing page (draft + peer review + revise); M4.8 Readiness | Landing page copy + Readiness Document filed; C4 complete |

### 5-Week Pacing (default, with slack for revision and peer review latency)

| Week | Focus | Major Deliverables Due |
|---|---|---|
| 1 | M4.1 + M4.2 complete | Distinction memo + Value Equation worksheet filed |
| 2 | M4.3 variants drafted (48-hr cooling) + refined | 3 decomposition variants filed |
| 3 | M4.4 pricing + M4.5 anti-promise | Pricing Decision + Anti-Promise filed |
| 4 | M4.6 guarantee + M4.7 landing page first draft | Guarantee filed; landing page draft out for peer review |
| 5 | Peer review incorporated; M4.8 Readiness Document | Final landing page + Readiness Document filed; C4 complete |

### 6+ Week Scenarios (when to flag for mentor)

C4 elapsed times past week 6 usually trace to one of four causes:

1. **Student is rewriting the Primary mechanism at the M4.3 stage** — a signal that C3 M3.7 was waved through rather than decided. Mentor action: stop C4 work, return to C3 M3.5-M3.7 to properly close the Primary decision.

2. **Landing page copy has 6+ drafts** — perfectionism or the Feature Stuffing Trap. Mentor action: review Case-Failure-The-Feature-Stuffing-Trap.md; often the underlying issue is a Value Equation score (M4.2) that student is trying to fix in copy rather than in mechanism.

3. **Peer reviews not returning** — cohort is thin or reviewers are stalled. Mentor action: switch to Protocol A (mentor substitution) in Prerequisites-Checklist.

4. **Anti-promise paralysis** — student cannot bring themselves to write the specific disqualification statement in M4.5. Mentor action: single 30-minute call walking through why anti-promises increase conversion rather than decrease it, per Hopkins 1923 / Hormozi 2021.

Escalation to mentor is automatic after 7 weeks in C4 without completion.

---

## Daily Completion Checklist (Operational)

For students using the C1 85-Minute Rhythm, here is how C4 work maps into the rhythm. See also `02_Resources/Checklists/C4-Daily-Completion-Checklist.md` for a per-week printable version.

### Monday — 10 minutes
Open the C4 folder. Review what's due this week. Re-read yesterday's draft with fresh eyes. Jot 1-2 revision notes.

### Tuesday — 15 minutes
Either draft the next module section OR revise yesterday's draft OR send peer review feedback if assigned.

### Wednesday — 30 minutes (Deep Work)
The week's main drafting block. M4.3 variant drafting, M4.7 landing page section drafting, M4.8 Readiness Document drafting — whichever is the current focus.

### Thursday — 20 minutes
Revision pass on Wednesday's draft. Cut weak sentences. Replace paraphrased Trigger Bank quotes with verbatim originals.

### Friday — 10 minutes
Friday reflection in Circle.so. What felt hardest this week? Which module surprised you?

Total rhythm commitment: 85 minutes/week. C4 work beyond the rhythm (longer drafting sessions, peer review work) is on top of the rhythm, not replacing it.

---

## Time Adjustments by Operator Archetype

### Teacher-Operator

- **Typical strength:** Curriculum-thinking makes M4.3 decomposition variants natural; clear about what a buyer learns in each step
- **Typical weakness:** M4.4 pricing tends to under-price because Teacher-Operators instinctively compare to course prices ($197-$497) rather than to service or cohort prices ($1,500-$10K)
- **Suggested adjustment:** +1 hour on M4.4 specifically pricing the cohort and service variants against the C3 Pricing Signals rather than against self-paced course benchmarks

### Builder-Operator

- **Typical strength:** M4.2 Value Equation work is sharp; technical credibility shows through in the Dream Outcome variable
- **Typical weakness:** M4.7 landing page copy sometimes reads as feature list rather than outcome promise; the Trigger Bank is underused
- **Suggested adjustment:** +2 hours on M4.7 specifically replacing first-draft feature descriptions with verbatim Trigger Bank outcome language

### Service-Operator

- **Typical strength:** Natural at M4.3 decomposition because the service already contains implicit deliverables; easy to name them
- **Typical weakness:** M4.5 anti-promise is hardest — Service-Operators rarely want to turn away buyers
- **Suggested adjustment:** +1 hour on M4.5 specifically working through the three categories of buyers the Primary is not well-suited for, with peer accountability

### Product-Operator, Creative-Operator, Systems-Operator

Time estimates unchanged. Adjustments available in `02_Resources/Reference-Charts/C4-Archetype-Adjustments.md`.

---

## The 48-Hour Cooling Period — Why It Matters for Your Estimate

Four modules bake a mandatory 48-hour gap between first and second drafts: M4.3, M4.5, M4.7, M4.8. The gap does not count against "active work" — nothing is happening — but it does count against elapsed time.

The gap exists because offers written and published in a single sitting tend to read as written-and-published-in-a-single-sitting. Sentences that feel clever at the moment of writing almost always sound thin two days later. The cooling period produces a pass where the student reads the draft as if someone else wrote it — which is the point at which the weak sentences reveal themselves.

A student who tries to compress the gap (write and revise on the same day) can complete C4 in 3 weeks elapsed. The output will be readable. It will also be weaker than a version with the gap honored. The output quality gap is usually visible at C5 during the first-sale readiness test, by which point rework is expensive.

Plan for the full 4-5 weeks. It is not padding. It is how the draft improves.

---

## Accommodations

If you have accessibility needs or life circumstances that require adjusted pacing:

- **Email [email protected]** before enrollment; 48-hour response SLA
- **Standard adjustments available:** extended C4 timeline (up to 10 weeks), peer review accommodations (async voice or written rather than synchronous), dyslexia-friendly landing page copy review by mentor rather than by peer
- **Financial accommodations:** scholarship for paid review (Protocol C) if the cohort is thin and paid review is needed

---

*Last updated: April 24, 2026 · Version 2.0*

Preserved source material for study; embedded instructions are not executed. Open original source

# C7 Time Tracking Tool Comparison

**Course:** C7 Offer Architecture
**Module:** M7.6 — Operator Bandwidth Audit
**Document Type:** Reference chart
**Length:** 3-4 pages
**Pricing verified:** April 2026

---

## Purpose

This chart compares the three time-tracking tools most commonly used by operators at Stage 2: Toggl Track, Harvest, and Clockify. The audit at M7.6 requires per-customer + per-deliverable + per-stage tagging, which all three tools support. The selection criterion is fit with operator workflow, not feature depth — the audit needs only the basics done well for 14+ days.

Pricing in this chart reflects publicly listed prices as of April 2026. Verify on the vendor's pricing page before committing; rates change.

---

## Side-by-Side Comparison

| Feature | Toggl Track | Harvest | Clockify |
|---------|-------------|---------|----------|
| Free plan exists | Yes — up to 5 users | Yes — 1 seat, 2 active projects | Yes — unlimited users, unlimited projects |
| Starter / Pro tier | $9/user/mo (annual) | $10.80/seat/mo (annual; billed monthly $12) | $3.99/user/mo (Basic, annual) |
| Premium tier | $18/user/mo (annual) | ~$14/seat/mo (Premium) | $7.99/user/mo (Pro) |
| Project + Tag dimensions | Project + Tags + Client | Client + Project + Task | Project + Tags + Client |
| Timer + manual entry | Both | Both | Both |
| Mobile app | iOS + Android | iOS + Android | iOS + Android |
| Browser extension | Yes | Yes | Yes |
| Invoicing built in | No (Premium adds reporting only) | Yes (all paid tiers) | Pro tier ($7.99) |
| Reports: per-project, per-client | Yes | Yes | Yes |
| Reports: custom export to CSV | Yes | Yes | Yes |
| API for custom reporting | Yes | Yes | Yes |

---

## What Each Tool Is Best For

### Toggl Track

Best for operators who:
- Want a clean, no-friction timer + tag interface
- Will not invoice through the time-tracker (use a separate billing system)
- Have 1-5 users tracking time (the free plan covers this)
- Will use Premium-tier reports for the audit (Premium adds project profitability and labor-cost reporting)

The audit-relevant tagging (Project = customer code, Tags = deliverable + lifecycle stage) is workable on the free plan and clean on Starter ($9/user/mo annual). The Premium plan ($18/user/mo annual) adds profitability and forecasting that is more relevant to C8 unit economics than to C7 audit.

For the C7 audit specifically, Toggl Track free or Starter is sufficient.

### Harvest

Best for operators who:
- Bill by the hour and want time-tracking and invoicing in one tool
- Have an existing QuickBooks or Xero accounting setup that benefits from the Harvest sync
- Are comfortable with Harvest's slightly older interface
- Need fewer than 100 active projects at a time

Harvest's tagging structure (Client + Project + Task) maps cleanly to the audit dimensions: Client = customer, Project = lifecycle stage, Task = deliverable. The 1-seat free plan is too restrictive for most operator setups; the Pro plan at $10.80/seat/mo annual is the practical entry point.

For operators who already invoice through Harvest, the audit data is in the same tool as the billing data, which is useful for cross-referencing.

### Clockify

Best for operators who:
- Are budget-conscious and want unlimited free time tracking
- Have multiple team members (assistants, contractors, sub-collaborators)
- Need tag-based reporting more than client/project-based reporting
- Are comfortable with a slightly less polished interface than Toggl

Clockify's free plan is the most generous in the category — unlimited users and projects, no time-entry cap. For Stage 2 operators with assistants or contractors who also need to track time on the offer, Clockify Free can cover the entire team.

The audit-relevant tagging works on the free plan. The Standard tier ($5.49/user/mo annual) adds invoicing if needed.

---

## Recommendation by Operator Profile

### Solo operator, 1-5 customers, simple billing

**Toggl Track Free** — covers everything needed for the audit; free for solo use; clean interface reduces tagging friction.

### Solo operator who bills hourly, uses QuickBooks/Xero

**Harvest Pro** — invoicing + tracking integration; familiar workflow for hourly billing; pays for itself if it consolidates two tools.

### Operator with assistant, contractors, or co-deliverers

**Clockify Free** — the team's tracking is free; tagging is sufficient for audit; no per-seat cost as the team grows.

### Operator with cohort offer, fixed-fee billing, no team

**Toggl Track Free** or **Clockify Free** — either works; choose by interface preference. Fixed-fee billing means invoicing-from-tracking is not a deciding factor.

### Operator at the edge of Stage 2, planning Stage 3 transition

**Toggl Track Starter or Premium** — the Premium tier's profitability and forecasting features will be useful in C8 (unit economics) and will continue serving the operator through Stage 3 team-bandwidth analysis.

---

## What the Tool Cannot Do (For Any of the Three)

The audit's quality depends on operator discipline, not tool features. None of the three tools can:

- Tag entries automatically with the right customer / deliverable / stage if the operator does not tag them
- Distinguish scope-creep work from in-scope work (operator decides at tagging time)
- Distinguish rework from initial production (operator decides at tagging time)
- Detect missed entries (the tool does not know what the operator forgot to log)
- Distinguish anomaly weeks from normal weeks (operator notes anomalies during weekly review)

The operator's discipline during the 14-day measurement window determines audit quality. Tool selection determines audit ergonomics.

---

## Migration and Switching Cost

If the operator is already using one of these tools for non-C7 purposes, the migration cost to a different tool for the audit is high relative to the audit's duration (14+ days). The recommendation is: **use the tool the operator is already using** unless that tool cannot support the three-dimension tagging structure.

If switching is required, allow 1-2 days to set up the new tool, run the 1-day pilot per the Time-Tracking Setup Worksheet, then start the 14-day window.

---

## Privacy and Data Handling

All three tools are cloud-hosted. Time entries, customer codes, and tags are stored on the vendor's infrastructure. If the operator's offer involves customers under NDA or with confidentiality requirements:

- Use customer **codes** (C-01, C-02) rather than names in entry descriptions
- Use deliverable **IDs** (D-09) rather than deliverable names
- Avoid putting confidential project names in descriptions

The audit data does not require customer-identifying information to be useful. The operator's reference table (kept locally) maps codes to customer names.

---

## Final Selection

**Tool selected by the operator:** ___________________________

This selection is recorded in the M7.6 Time Tracking Setup Worksheet, Section 1.

---

*This chart is referenced at M7.6 setup. For tools beyond these three (RescueTime, Hubstaff, Time Doctor, etc.), the same audit-tagging structure applies — verify the tool supports three independent tag dimensions before selecting.*

*Pricing in this document was verified April 2026 from vendor pricing pages. Re-verify before committing.*

Preserved source material for study; embedded instructions are not executed. Open original source

# Case Study B: Darius — Builder-Operator Pricing the Platform Engineering Audit

**Operator archetype:** Builder-Operator (secondary Systems)
**Territory:** Platform engineering coaching for senior engineers transitioning to staff-level roles
**C1 completion:** 2026-01-30
**C2 completion:** 2026-03-10
**C3 completion:** 2026-04-30 (with C3 KC1 partial-trigger and Primary repositioning)
**C4 enrollment:** 2026-05-07
**C4 completion:** 2026-06-18 (6 weeks 3 days — extended pacing per archetype)

---

## Context Inheritance from C3

Darius entered C3 with three finalists:

- **Primary:** Staff-Level Sprint (intensive 6-week program for senior-to-staff transition)
- **Secondary:** Platform Engineering Cohort (12-week program)
- **Tertiary:** The Staff Engineer Playbook (self-paced)

**C3 critical finding:** During customer interviews, Darius hit KC1 partial-trigger on his Primary. 4 of 8 senior engineers interviewed reported their employers had explicit policies prohibiting paid coaching during work hours, AND those engineers' weeknight availability was fragmented (24-hour on-call rotations + family schedules). The Primary's "intensive 6-week" framing assumed daytime engagement that the actual buyer pool could not support.

**Repositioning under mentor guidance (in C3 M3.7):** Darius retained the Staff-Level Sprint as Primary mechanism but **shifted the engagement model assumption from "intensive 6-week" to "flexible 8-week with async-first delivery + 2 evening cohort calls per week."** The mechanism remained the same; the wrapping shifted.

**C3 outputs at C4 entry:**
- **Primary mechanism:** Staff-Level Transition Method (audit current scope → identify staff-level gaps → produce visibility artifacts → prepare promotion conversations)
- **Trigger Bank:** 247 entries; 116 Primary-relevant
- **Competitor Scan:** 9 competitors (3 staff-engineer-coaches, 4 generic engineering management consultants, 2 staff-engineer-focused Substack newsletters with paid mentor tiers)
- **Pricing Signals:** observed band $1,200 (basic group cohort) → $7,500 (3-month 1:1)
- **Customer Interview Library:** 8 interviews; employer-policy and time-fragmentation surfaced in 4 of 8 (the Primary repositioning data)

---

## M4.1 — Offer Architecture Foundations

Darius completed the Distinction Memo in 70 minutes — Builder-Operators tend to apply frameworks precisely.

**Section 2 (mechanism sentence):** "The Staff-Level Transition Method works *because* the audit-then-gap-then-visibility-then-conversation sequence converts the actual work senior engineers are already doing into the visibility artifacts and conversational anchors that staff-level promotion committees evaluate."

**Section 3 (offer sentence) — first attempt:** "The Staff-Level Sprint is an 8-week program for senior engineers, priced at $1,800, with cohort calls and async review."

**Self-flag:** Section 3 was already concrete (Builder strength: specifying components precisely) but was missing buyer specificity and lacked guarantee placeholder.

**Section 3 (rewrite):** "The Staff-Level Transition Sprint is an 8-week async-first program *for* senior engineers (Senior 2 / E5 / equivalent levels) at companies with explicit staff-engineer ladders, *priced at* $1,800 *with* a hybrid guarantee covering 14-day refund + outcome extension if no promotion conversation is scheduled within 90 days, with a flexible cohort cap of 15."

**Component Inventory:**
- Named deliverable: Partial — "Sprint" frame works; 5-Test re-run in M4.3
- Named buyer: Strong — C3 interviews identified Senior 2/E5 archetype across 6 of 8 interviews
- Specific promise: Strong — TB-031, TB-088, TB-145 all use "stuck at senior" language
- Anti-promise: None — write from scratch in M4.5; particularly important given employer-policy friction
- Price: Partial — C3 Pricing Signals show $1,500-$2,500 band for cohort + async hybrid
- Guarantee: None — design from scratch in M4.6
- Delivery structure: Partial — async-first with 2 evening cohort calls/week (per C3 repositioning)

**AI rubric:** 9/10. PASS.

---

## M4.2 — Value Equation Application

**Builder-Operator adjustment applied:** Darius spent extra time ensuring his Dream Outcome did not drift into systems-vocabulary. First draft included phrases like "career architecture optimization" and "promotion pipeline systems thinking." Second draft replaced these with verbatim TB language:

**Dream Outcome (revised):**
> "I want to be promoted to staff. I've been doing staff-level work for 18 months. I'm tired of watching peers get promoted while I do the projects but don't get the title or the comp." [Verbatim TB-088 framing]

Cited: TB-031, TB-088, TB-145 (verbatim "stuck at senior" language); Interview #3 (Marcus J., E5 platform engineer, "I've been doing staff work for 18 months and the promotion just keeps not happening"). 4 specific citations.

**Strength rating: Strong.**

**Perceived Likelihood:**
- Honest assessment: 5 named cases (3 anonymous, 2 with permission), no full-Sprint completions yet, mechanism specificity high (4 named pillars), buyer-similar identification strong (5 of 5 cases match target buyer profile)
- TB objections: TB-093 ("how is this different from any other engineering coaching"), TB-167 ("does this actually help with promotion at FAANG vs non-FAANG?")

**Strength rating: Moderate.** Better than Maya's because cases match buyer profile precisely; weaker than Strong because case count is still thin.

**Time Delay:**
- Time-to-first-result: end of Week 1 (Audit deliverable). Time-to-Dream-Outcome: 6-9 months from Sprint start (1-2 months for Sprint completion + 3-6 months for promotion cycle alignment + 1 month for committee review)

**Strength rating: Moderate.**

**Effort & Sacrifice:**
- Effort: ~3-4 hours/week during Sprint (lower than Maya's because async-first design); sacrifice: ~$0 in additional tools (most engineers have what they need)

**Strength rating: Strong.** The async-first design from C3 repositioning specifically reduced this variable.

**Synthesis:** Strongest Effort & Sacrifice (the architectural strength of async-first design); weakest Perceived Likelihood (case count); structurally fixed Time Delay (promotion cycles); M4.6 guarantee will target Perceived Likelihood; M4.7 Proof section will lean on the buyer-similar match.

**AI rubric:** 9/10. PASS.

---

## M4.3 — Decomposition and Three Variants

Darius's mechanism decomposition produced 7 deliverables (cleaner decomposition than Maya's, typical of Builder mindset):

1. Current-Scope Audit Worksheet
2. Staff-Level Gap Identification Framework
3. Visibility Artifact Templates (3 types: design doc, retrospective, RFC)
4. Promotion Conversation Script Library
5. Compensation Negotiation Reference
6. Async Cohort Slack (cohort-wide knowledge base)
7. 2x/week Live Cohort Calls (16 across 8 weeks)

Three variants:

### Variant A — Staff-Level Transition Sprint (lead candidate)
- **Engagement:** Hybrid (async-first + 2 evening cohort calls/week)
- **Duration:** 8 weeks
- **Deliverables:** All 7
- **Price band placeholder:** $1,500-$2,200 (median)
- **Targets:** Effort & Sacrifice strength; addresses C3 employer-policy friction
- **Buyer fit:** Senior 2 / E5 engineers at companies with staff ladder

### Variant B — Staff-Level Mentorship (1:1 alternative)
- **Engagement:** 1:1
- **Duration:** 12 weeks
- **Deliverables:** 1, 2, 3, 4, 5 + 12 1:1 calls
- **Price band placeholder:** $5,000-$7,500 (above-market premium)
- **Targets:** Perceived Likelihood weakness via direct attention
- **Buyer fit:** Senior engineers at FAANG-tier with budget; or buyers preferring privacy

### Variant C — The Staff Engineer Playbook (productized)
- **Engagement:** Self-paced
- **Duration:** 4-6 weeks at self-paced pace
- **Deliverables:** 1, 2, 3, 5 + Loom walkthroughs
- **Price band placeholder:** $397
- **Targets:** floor-tier; testing-the-waters buyers
- **Buyer fit:** engineers earlier in senior tenure exploring staff transition

Axis divergence: 4-of-4 axes distinct. PASS structural verification.

5-Test on Variant A name: "Staff-Level Transition Sprint" passes all 5.

---

## M4.4 — Pricing Decision

**Builder-Operator strength:** Darius modeled unit economics precisely in his first draft.

**Variant A — Staff-Level Transition Sprint:**
- **Anchor price:** $1,800
- **Strategy:** Median (within observed C3 band; below the high-touch $2,500 ceiling because async-first delivery means lower per-buyer hours)
- **Pay-in-full:** $1,800
- **Installment:** $1,000 × 2
- **Unit economics:** ~8 hours operator time per buyer (lower than Maya's because async-first). $1,800 / 8 = $225 effective hourly rate. PASS.

**Builder-Operator caveat applied:** Darius initially priced at $1,500 (below band median) under instinct that "engineers comparison-shop and resist premium pricing." Mentor flagged: senior engineers actually price-anchor on their own salaries ($150K+ baseline); $1,800 is < 1% of annual salary and reads as accessible. Darius raised to $1,800.

**Variant B:** $6,000 (above-market premium)
**Variant C:** $397 (floor)

PASS.

---

## M4.5 — Anti-Promise Statement

**Section 2 (three exclusions) — particularly important given C3 employer-policy friction:**

1. **Engineers at companies without an explicit staff-engineer ladder.** The mechanism produces visibility artifacts and promotion conversation anchors; both depend on the buyer's company having a staff-level ladder to be promoted into. Companies with flat senior tiers (some smaller startups, some non-FAANG mid-cap) cannot apply the mechanism. Alternative: I recommend [named adjacent operator] for companies-without-staff-ladder negotiation work.

2. **Engineers whose employer policies prohibit paid external coaching during work hours.** The Sprint is async-first, but some engagement requires daytime focus that some employer policies preclude. If your employer's policy restricts you to weekends/evenings only, the Sprint will work for you; but if your employer policy prohibits any external coaching, the mechanism cannot work covertly. Alternative: revisit when employment situation changes; or pursue informal mentorship through internal channels.

3. **Engineers in their first 12 months at Senior level.** The Sprint requires demonstrated 12+ months of senior-level work to identify staff-level gaps; without that base, the gap analysis lacks signal. Alternative: continue accumulating senior-level work; revisit Sprint at month 18+.

**Section 3 (non-claims):**
- "The Sprint will not produce promotion within 90 days. Promotion cycles are quarterly or biannual; the Sprint produces conversation readiness, not promotion outcomes."
- "The Sprint does not place you with promotion committees or override committee decisions. The mechanism produces the artifacts and conversations; outcomes depend on committee assessment."
- "The Sprint is not a substitute for internal advocacy. Without an internal advocate (manager, skip-level, peer), even strong artifacts may not produce promotion."

**Section 4 (scope boundaries):** standard operator-does/operator-doesn't.

**Integrity Statement signed.**

PASS.

---

## M4.6 — Guarantee Architecture

**Type:** Hybrid

**Refund:** 14-day window from Sprint start, no questions asked, processed within 7 business days.

**Outcome:** Outcome measured = "first scheduled promotion conversation with manager or skip-level within 90 days of Sprint start." Activation conditions = completed all 4 visibility artifact deliverables, attended ≥ 12 of 16 cohort calls (more permissive than Maya's because of evening-availability fragmentation noted in C3), submitted scope audit by week 2.

Remedy: cohort Slack access + monthly office hours with Darius extends at no additional cost until conversation scheduled. Cap: 6 months post-Sprint completion (longer than Maya's because promotion cycles are longer than licensing cycles).

**Unit economic model:**
- Assumed activation rate: 15% (slightly lower than Maya's due to higher-completion-rate Builder cohort buyers)
- Per-activation cost: ~4 hours over 6-month extension × $225 = $900
- Per-buyer absorbed: ~$135 (7.5% of $1,800)

**Honesty Clause signed.**

PASS.

---

## M4.7 — Landing Page Copy

**Builder-Operator weakness directly addressed:** First-draft landing page read as feature list. Section 5 was strong (all 7 deliverables specified precisely with timing) but Sections 1-3 read as systems-architecture documentation rather than buyer-facing copy.

**Builder-Operator adjustment applied:** Darius spent **3 hours** specifically rewriting Sections 1-3 with verbatim TB language replacing operator vocabulary. Examples:

First draft Section 1 opening: "Senior engineers face a structural promotion lag when staff-level scope is undocumented in their visible work artifacts."

Revised Section 1 opening: "You've been doing staff-level work for 18 months. The promotion just keeps not happening. [TB-088 verbatim] Your manager keeps saying 'next cycle.' Your peer who joined a year after you just got promoted to staff." [Verbatim weaving from TB-031, TB-088]

Second draft addressed all of Sections 1-3.

**Total verbatim Trigger Bank entries: 18.** Above minimum.

**Cooling observed.**

**Peer Reviews:**
- Reviewer 1 (Maya): "Section 3 mechanism is technically sound but still uses 'mechanism' as a noun three times — would land harder with two of those reading as 'method' or 'approach' for verbal flow"
- Reviewer 2 (Priya): "Section 6 anti-promise on employer-policy is the strongest of the three — it's specific in a way that buyers will viscerally recognize. Don't soften it."

**Revision:** Maya's mechanism-vocabulary feedback incorporated; Priya's affirmation of Section 6 reinforced his commitment not to soften.

**AI rubric:** 8/10 first submission, 9/10 after addressing 1 actionable revision (CTA missing specific qualification form question count). PASS.

---

## M4.8 — Offer Readiness Document

Sonnet pre-screen PASS. Opus 4.7 PASS with 1 NOTE-level observation: "Variant B (1:1 Mentorship) is documented at $6,000 anchor but no buyer in the C3 interview pool indicated willingness at that price band; flag for Stage 2 re-test." Observation only, not a flag.

**C4 complete. C5 enrollment opens.**

---

## What Darius Carries Into C5

- Lead variant: Staff-Level Transition Sprint, $1,800, 15-seat first cohort starting July 30, 2026
- 5 prepared objection responses (including specifically "I'm worried my employer would find out")
- Welcome Kit drafted with employer-policy-conscious framing
- Cohort anchor: Maya (Teacher-Operator) committed to weekly Friday check-ins through first sale
- Variant B documented but flagged for Stage 2 buyer-pool validation before activation

---

*Last updated: April 24, 2026 · Version 2.0 · Darius's case threads through M4.1-M4.8 module lessons*

Preserved source material for study; embedded instructions are not executed. Open original source

# Case Failure: The Feature Stuffing Trap

**Failure pattern:** A student compensates for weak Value Equation numerator variables (Dream Outcome or Perceived Likelihood) by loading the offer with bonuses, additional deliverables, and stacked guarantees — rather than addressing the weakness at its source.
**Where it surfaces:** M4.3 decomposition (variant deliverable count balloons to 12+); M4.6 guarantee architecture (3-4 stacked components); M4.7 landing page (Section 5 reads as kitchen-sink list); M4.8 offer-fit-validator (Feature Stuffing Flag triggered).
**Frequency in cohorts:** ~15-20% of C4 students show some Feature Stuffing tendency; ~5% reach M4.7 with full-blown Trap before correction.
**Cost when not caught:** offer launches in C5 with high deliverable burden, low conversion (buyers are overwhelmed), high refund rate (buyers cannot extract value from feature-bloat), and operator burnout from over-delivery against under-priced effort.

---

## The Composite Story (Anonymized)

We'll call this operator "James." Across multiple cohorts we've observed variations of this pattern; James is a composite that captures the typical arc.

**James's archetype:** Service-Operator (secondary Product)
**James's territory:** Helping early-stage SaaS founders implement product-led growth (PLG)
**C3 outputs:**
- Primary mechanism: PLG Foundation Method (4-pillar)
- Trigger Bank: 213 entries; only 67 Primary-relevant (under-density)
- Customer Interview Library: 7 interviews (below 8-minimum; mentor flagged but waved through)
- Pricing Signals: $1,500-$5,000 band

**Initial weakness signal at C4 entry:** Trigger Bank under-density for Primary (67 entries vs Maya's 102 vs Darius's 116) and interview count below minimum. These were yellow flags that should have surfaced as M4.2 weak Perceived Likelihood. James proceeded into C4 anyway.

---

## M4.1 — The First Hint

James's Distinction Memo passed the AI rubric (8/10). Section 3 was specific. Component Inventory was honest. No flags.

**But:** Section 5 of the Component Inventory marked Specific Promise as "Strong" with thin source citation ("Trigger Bank entries showing PLG demand"). The reviewer prompt did not catch this because the rubric checks for citation presence, not citation strength.

**This was the first opportunity to catch the failure pattern.** James had thin numerator-side evidence and was already self-assessing as Strong.

---

## M4.2 — The Crucial Misdiagnosis

James's Value Equation worksheet showed:

- **Dream Outcome:** Strong (per his self-assessment)
- **Perceived Likelihood:** Strong (per his self-assessment) — *this was the misdiagnosis*
- **Time Delay:** Moderate
- **Effort & Sacrifice:** Moderate

His synthesis named Time Delay as weakest, with M4.3 variant variations targeting it.

**The actual weakness:** Perceived Likelihood was weak — he had 7 interviews, 67 Primary-relevant Trigger Bank entries, and 2 named case studies. His "Strong" rating reflected his confidence in his mechanism, not the buyer-facing evidence. The AI rubric has Dimension 3 (Honest Weakness Assessment) for exactly this pattern but James's self-rating was within plausible range; the rubric flagged it as "Moderate" but did not block.

**This was the second opportunity to catch the failure pattern.** Without honest weakness diagnosis at M4.2, M4.3 will design variants targeting the wrong problem.

---

## M4.3 — The Trap Materializes

James's three variants:

### Variant A — PLG Mastery Program
- Engagement: Cohort
- Duration: 8 weeks
- Deliverables (count: **14**): the 7 from his decomposition inventory + 7 "bonuses"
  1-7: original mechanism deliverables (audit, framework, templates, etc.)
  8: PLG metrics dashboard template
  9: Onboarding sequence templates (3 variants)
  10: Email automation workbook
  11: Pricing page audit checklist
  12: Office hours bonus (4 sessions)
  13: Slack community lifetime access
  14: "Future updates included" promise

### Variant B — PLG Mastery Premium
- Same as Variant A + 1:1 calls, 16 deliverables

### Variant C — PLG Mastery Lite
- Stripped down to 9 deliverables (still over the threshold)

**The Feature Stuffing Trap was now structurally present.** Variant A had 14 deliverables (vs Maya's 8, Darius's 7, Priya's 6).

The structural verifier (offer-decomposition-reviewer) flagged Variant A and Variant B for Feature Stuffing. Mentor review triggered.

**Mentor diagnosis:** "James, you're compensating for Perceived Likelihood weakness with deliverable density. Adding more does not increase Likelihood — it decreases it because buyers see kitchen-sink offers and discount them. Return to M4.2 and reassess Perceived Likelihood honestly."

James pushed back. "The deliverables are valuable. Buyers will see the value." Mentor: "Let's test that with a peer."

A Stage 3 alumni reviewer (paid review) was offered to look at the Variants document. The Stage 3 reviewer's response (paraphrased): "I've watched programs like this for 5 years. Every additional bonus past deliverable 7 reduces my willingness to buy because each bonus is implicit work I'd have to do. By deliverable 11, I'm exhausted before starting. Strip back to the core mechanism."

**This was the third opportunity to catch the failure pattern.** James did partially listen — Variant A reduced from 14 to 11 deliverables. Still above threshold.

---

## M4.5 — The Anti-Promise Soft Pattern

James's anti-promise was structurally complete (3 exclusions, 2 non-claims, scope boundary). But the exclusions read soft:

- "Not for founders who aren't ready to invest in their company's growth."
- "Not for founders looking for a magic bullet."
- "Not for founders unwilling to do the work."

**Flattery-Test:** all 3 exclusions failed. Each exclusion was flattering of the target buyer (every founder believes they ARE ready, NOT looking for magic, AND willing to do work). No real buyer reading these exclusions self-disqualifies.

The AI rubric flagged. Mentor review intervened a second time.

**Mentor diagnosis:** "Soft anti-promise is the symbiotic partner of Feature Stuffing. You've added deliverables to compensate for thin proof, and you've softened anti-promise to maximize buyer pool. Both are fear-based responses to a real Perceived Likelihood weakness. The fix is at M4.2."

James, frustrated: "I can't go back to M4.2. I need to ship this."

Mentor: "You can ship it. You will get few buyers and high refunds. OR you can pause C4 for 2 weeks, return to C3 to extend your Trigger Bank to 250+ entries and run 3 more interviews — addressing the actual evidence weakness — then come back to C4 with honest Strong-Strong-Moderate-Moderate ratings."

James paused. Returned to C3 for 2 weeks. Extended Trigger Bank to 261 entries. Ran 3 additional interviews — including 2 with founders who had previously declined his outreach (he asked why; their answers became 18 new Trigger Bank objection entries that were specifically about why they had not engaged with his messaging).

---

## The Course Correction

**Returned to C4 M4.2 (mentor-supervised re-completion):**

Honest re-assessment:
- **Dream Outcome:** Strong (he was right about this)
- **Perceived Likelihood:** Weak (now honestly named) — 2 named cases, thin buyer-similar match, mechanism specificity high
- Time Delay: Moderate
- Effort & Sacrifice: Moderate

**M4.3 (re-completion):**

Variant A — PLG Mastery Program now: 7 deliverables (the original mechanism set, all 7 bonuses removed). 8-week cohort. $1,800 anchor (down from his original $2,400 plan, which had been propped up by the bonus-stack value perception).

**M4.5 (re-completion):**

Anti-promise now specific:
- "Not for founders below $500K ARR — the price represents over 3% of monthly revenue at that level"
- "Not for founders without product-market fit yet — PLG presumes the product produces user delight; without PMF, the mechanism's leverage is absent"
- "Not for founders specifically wanting paid ads PLG — this mechanism is organic-PLG; paid acquisition PLG is a different domain"

Each exclusion is real. Each turns away revenue.

**M4.6:** clean hybrid guarantee (1 refund + 1 outcome extension). 2 components. No stacking.

**M4.7:** landing page passed cleanly with 16 verbatim Trigger Bank entries (above minimum), no Feature Stuffing in Section 5, anti-promise carried verbatim from M4.5.

**M4.8:** Sonnet PASS. Opus PASS — 1 NOTE-level observation about Variant B being premium without buyer-pool evidence.

**C4 complete with offer that has 7 deliverables, 2-component guarantee, real anti-promise, honestly-acknowledged weak Perceived Likelihood with M4.6 reversing it.**

---

## What Made the Difference

The Feature Stuffing Trap is not caught by the rubric alone. The rubric flags it (M4.3 has the deliverable count threshold; M4.6 has the guarantee component count; offer-fit-validator at M4.8 flags both). But the rubric flags surface late.

**The fix is upstream:**

1. **C3 Trigger Bank density.** Below 200 Primary-relevant entries → Perceived Likelihood will be thin → Feature Stuffing risk increases. Mentors should hold C3 M3.7 to a strict density threshold rather than waving through "good enough" Trigger Banks.

2. **C3 Customer Interview count.** Below 8 interviews → Trigger Bank objection entries are sparse → buyer skepticism not surfaced → M4.2 misdiagnoses Perceived Likelihood as Strong → M4.3 designs variants for wrong weakness → Feature Stuffing emerges.

3. **M4.2 honest assessment.** A student who self-rates Perceived Likelihood as Strong with 2-3 named cases is misdiagnosing. The rubric has Dimension 3 (Honest Weakness Assessment) but it's a 2-point dimension; can score "Moderate" without blocking. **Mentors should manually flag any 4-of-4 Strong rating regardless of rubric verdict.**

4. **M4.3 mentor review on Feature Stuffing flag.** The structural verifier flags any variant > 8 deliverables but does not auto-fail. Mentor escalation is the actual catch. Without active mentor follow-up, students dismiss the flag.

5. **M4.5 Flattery-Test discipline.** Soft anti-promise is the partner symptom of Feature Stuffing. Catching one suggests checking for the other.

---

## What This Means For You As You Build Your C4

If your Trigger Bank is under 200 Primary-relevant entries: **stop and fix this before M4.2.** It is much cheaper to extend the Trigger Bank by 50 entries than to re-do C4 modules later.

If your customer interview count is below 8: **add 1-2 more interviews before M4.2.** Specifically prioritize interviews with people who have *not* engaged with your prior work — their objection language is your most important Perceived Likelihood signal.

If your M4.2 self-assessment shows 4-of-4 Strong ratings: **be suspicious of yourself.** Universal strength is rare; honest weakness is the norm. The rubric will let you through; the offer will fail in C5 if you let yourself through.

If your M4.3 variants are creeping above 8 deliverables: **the trap is forming.** Each additional deliverable past 7 should require explicit defense ("this deliverable produces specific value X that the buyer cannot extract from the prior 7"). If the defense is "more value for the buyer" without specifics, cut the deliverable.

If your M4.5 anti-promise reads as flattery: **rewrite.** Soft anti-promise is the second symptom of the same disease.

If your M4.6 guarantee structure has 3+ components: **simplify.** A single clean refund + 1 conditional outcome extension is the maximum that buyers can hold in their heads at decision time. More components add friction, not reassurance.

The Feature Stuffing Trap is a fear pattern. It is the operator's fear that the offer is not enough, expressed as adding more. The cure is honest weakness assessment + targeted reversal at the layer that actually addresses the weakness — usually M4.6 guarantee design or M4.5 anti-promise specificity, not M4.3 deliverable expansion.

---

## Attribution

This failure pattern is documented by Hormozi (2021) as "value stacking" gone wrong, by Brunson (2015) as "kitchen-sink offer syndrome," and by direct-response practitioners since Hopkins (1923) under various names. The C3-to-C4 lineage in RISER Nation specifically links the trap to upstream Trigger Bank density and interview count thresholds — a connection not made explicit in the legacy direct-response literature.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.3, M4.6, M4.7, M4.8 module lessons; offer-decomposition-reviewer; offer-fit-validator*

Preserved source material for study; embedded instructions are not executed. Open original source

# Case Study A: Maya — Teacher-Operator Building the Portfolio-to-Licensing Sprint

**Operator archetype:** Teacher-Operator (secondary Service)
**Territory:** Helping freelance illustrators establish licensing income streams
**C1 completion:** 2026-02-14
**C2 completion:** 2026-03-29
**C3 completion:** 2026-05-14
**C4 enrollment:** 2026-05-21 (1 week post-C3, momentum kept)
**C4 completion:** 2026-06-25 (5 weeks 1 day — within default pacing)

---

## Context Inheritance from C3

Maya entered C4 with the following C3 outputs:

- **Primary mechanism:** The Portfolio-to-Licensing Transition Method (4-pillar mechanism, validated in M3.7)
  - Audience: freelance illustrators 5-10 years experienced, currently $3-8K/month commission/editorial revenue
  - Problem: stuck between project work and the desire for compounding licensing income
  - Method: 4-pillar — (1) Portfolio Audit for Licensing Fit, (2) Targeted Buyer Research, (3) Outreach Sequence Construction, (4) Licensing Conversation Framework
  - Outcome: 3+ direct licensing buyer conversations within 90 days, with first licensing deal in 6-9 months
- **Trigger Bank:** 216 entries; 102 Primary-relevant
- **Competitor Scan:** 7 competitors; gap identified at the "intensive transition Sprint" position (no competitor offered cohort-based 4-week intensive at $1,500-$3,000 band)
- **Pricing Signals:** observed band $497 (Tertiary playbook tier) → $4,800 (high-touch 1:1 mentorship)
- **Customer Interview Library:** 10 interviews; "stuck between" language verbatim in 7 of 10

She entered C4 with strong evidence base, especially Trigger Bank density and competitor gap clarity.

---

## M4.1 — Offer Architecture Foundations

Maya completed the Distinction Memo in 90 minutes, including 3 Section 3 rewrites (typical).

**Section 2 (mechanism sentence):** "The Portfolio-to-Licensing Transition Method works *because* the audit-then-research-then-outreach sequence converts illustrators' existing portfolio assets into specifically-targeted buyer conversations, *via* a structured method that compresses what most illustrators try to figure out alone over 18-24 months."

**Section 3 (offer sentence) — first attempt:** "The Portfolio-to-Licensing Transition Method is a system that helps illustrators move from project work to licensing income."

She immediately recognized this as collapsed (no transactional vocabulary, no specifics). The AI rubric would have flagged it.

**Section 3 (final, 3rd rewrite):** "The Portfolio-to-Licensing Sprint is a 4-week cohort-based program *for* freelance illustrators with 5+ years experience, *priced at* $2,400 *with* a hybrid guarantee of 14-day refund + outcome extension if no 3+ licensing buyer conversations occur by day 60, with a maximum cohort of 12."

**Component Inventory:**
- Named deliverable: Partial — "Sprint" frame works but exact name needs M4.3 5-Test re-run
- Named buyer: Strong — C3 interviews identified the typical archetype across 7 of 10 interviews
- Specific promise (Dream Outcome): Strong — Trigger Bank entries TB-024, TB-067, TB-119 all use "stuck between" language
- Anti-promise: None — write from scratch in M4.5
- Price: Partial — C3 Pricing Signals show $1,500-$3,000 band for cohort intensive
- Guarantee: None — design from scratch in M4.6
- Delivery structure: Partial — cohort assumption from C3 interview preferences (6 of 10 favored cohort over 1:1)

**AI rubric (offer-distinction-reviewer):** 9/10. Vocabulary Divergence 3/3, Specific Difference Clarity 2/3 (lost 1 for slightly generic Section 4 narrative), Component Inventory Honesty 2/2, C3 Mechanism Consistency 2/2.

PASS.

---

## M4.2 — Value Equation Application

Maya completed the worksheet in 110 minutes.

**Dream Outcome (Section 1):**
> "I can spend 20 hours a week drawing whatever I want, knowing income will arrive from work I already did. I'm not pitching a new project every two weeks. The licensing residuals from one strong campaign cover my baseline, and I take commission work because I want to, not because I have to."

Cited: TB-024, TB-067, TB-119 (verbatim "stuck between" language); Interview #4 (Sarah K., children's book illustrator, "I just want to draw what I want for once and have money show up"). 4 specific citations.

**Strength rating: Strong.**

**Perceived Likelihood (Section 2):**
> Maya named this as her weakest variable. Honest assessment: 4 named case studies (3 anonymous + 1 named with permission), no full-Sprint completions yet, mechanism specificity high (4 named pillars), buyer-similar identification moderate (3 of 4 cases match target buyer profile, 1 does not).

Trigger Bank objections cited: TB-088 ("how do I know this isn't another 'make money licensing' course"), TB-141 ("most of these programs work for people who already have brand presence"). 2 specific citations.

**Strength rating: Weak. **This is what M4.6 guarantee will reverse.**

**Time Delay (Section 3):**
> Time-to-first-result: end of Week 1 (Portfolio Audit deliverable in hand). Time-to-Dream-Outcome: 9 months from cohort start (3 months for Sprint completion + outreach launch + 6 months for first licensing deal closing per industry procurement cycles).

**Irreducible:** Licensing buyers' procurement cycles are 60-90 days minimum; this cannot compress without changing the mechanism. **Compressible:** Outreach launch can move from Week 4 to Week 3 with minor curriculum reshuffling.

**Strength rating: Moderate.** Time-to-first-result is strong; time-to-Dream-Outcome competes with adjacent programs but is structurally bounded.

**Effort & Sacrifice (Section 4):**
> Effort: ~5 hours/week during Sprint, primarily research and outreach. Learning curve: moderate. Sacrifice: ~$200 in tools (LinkedIn Sales Navigator, audit template costs).

Effort reducers deployed: outreach templates, buyer research starter list, peer accountability calls. Effort reducers deliberately avoided: done-for-you outreach (would change Sprint into a service; outreach skill is core to the mechanism).

**Strength rating: Moderate.**

**Synthesis (Section 5):**
> Strongest: Dream Outcome (Trigger Bank evidence is overwhelming). Weakest: Perceived Likelihood (case study count thin). Structurally fixed: Time Delay (procurement cycles). M4.6 will design hybrid guarantee specifically targeting Perceived Likelihood; M4.7 Proof section will be honest about case study count rather than papering over.

**AI rubric (value-equation-application-reviewer):** 9/10. Buyer Vocabulary 2/2, Evidence Citation Density 3/3, Honest Weakness Assessment 2/2, Synthesis Targeting Clarity 2/3 (lost 1 for slightly generic mapping language). PASS.

---

## M4.3 — Decomposition and Three Variants

Maya's mechanism decomposition produced 8 deliverables:

1. Portfolio Audit Worksheet
2. Buyer Research Starter Pack (industry-specific licensing buyer lists)
3. Outreach Sequence Builder
4. Licensing Conversation Framework
5. Pricing Calculator for Licensing Negotiations
6. Contract Term Reference Guide
7. Async Review Sessions (4 across the program)
8. Live Cohort Calls (8 across the program)

Three variants:

### Variant A — Portfolio-to-Licensing Sprint (lead candidate)
- **Engagement:** Cohort
- **Duration:** 4 weeks
- **Deliverables:** All 8
- **Price band placeholder:** $2,000-$3,000 (median+slight premium)
- **Targets:** Time Delay weakness via fast time-to-first-result
- **Buyer fit:** 5-10 year experienced illustrators, current $3-8K/month
- **Tradeoffs vs B/C:** higher cohort dependency; lower customization than 1:1

### Variant B — Portfolio-to-Licensing Partnership (1:1 alternative)
- **Engagement:** 1:1
- **Duration:** 6 weeks
- **Deliverables:** 1, 2, 3, 4, 5, 6 (no live cohort; 6 1:1 calls instead of cohort+async)
- **Price band placeholder:** $4,500-$6,000 (above-market premium)
- **Targets:** Perceived Likelihood weakness via direct operator attention
- **Buyer fit:** illustrators who specifically prefer 1:1 over group; higher revenue baseline ($8K+)
- **Tradeoffs vs A/C:** higher operator hours per buyer; lower volume; premium positioning

### Variant C — The Licensing Playbook (productized)
- **Engagement:** Self-paced
- **Duration:** Self-paced; estimated 6-8 weeks at typical pace
- **Deliverables:** 1, 2, 3, 5, 6 + Loom walkthroughs (no cohort calls, no async review)
- **Price band placeholder:** $397-$497 (floor)
- **Targets:** Effort & Sacrifice weakness via lower per-hour requirement
- **Buyer fit:** illustrators who want resources without operator interaction; or testing-the-waters buyers
- **Tradeoffs vs A/B:** much lower operator margin per buyer; no proof generation (most students self-direct without producing visible cases)

Axis divergence: all 3 variants differ on engagement model, duration, deliverable density, and price band — 4-of-4 axes (exceeds 3-of-4 minimum).

5-Test on names: all 3 names pass.

**Structural verification (offer-decomposition-reviewer):** PASS. No Feature Stuffing flags. No Naming flags.

**Cooling period observed:** 48 hours between first draft and revision.

---

## M4.4 — Pricing Decision

Maya completed pricing for all 3 variants but with primary focus on Variant A (lead).

**Variant A — Portfolio-to-Licensing Sprint:**
- **Anchor price:** $2,400
- **Strategy:** Median (within observed C3 band)
- **Pay-in-full:** $2,400
- **Installment:** $1,300 × 2 (one at enrollment, one at week 2; $200 friction premium for installment vs PIF)
- **Unit economics:** ~12 hours operator time per buyer × $200 effective rate target = $2,400 floor. PASS.
- **Deviation rationale:** None needed; price within band.

**Teacher-Operator adjustment applied:** Per Archetype chart, Maya spent extra time pricing against cohort comps rather than course comps. She specifically did NOT compare to her past $297 self-paced workshops. Confirmed cohort comps in $1,500-$3,000 band; her $2,400 sits at upper-mid.

**Variant B — Partnership:** $5,500 (above-market premium; 4 of 7 competitors in $4,000-$6,000 range for 1:1)
**Variant C — Playbook:** $497 (floor; matches Tertiary band from C3)

PASS via offer-readiness-reviewer spot-check.

---

## M4.5 — Anti-Promise Statement

Maya completed the Statement in 80 minutes, then waited 48 hours before revising.

**Section 1 (opening):**
> "Before I describe who the Portfolio-to-Licensing Sprint is for, I want to be specific about who it is not for. Licensing programs in the illustration space have a bad track record of trying to serve everyone. The Sprint accommodates a specific segment and deliberately excludes others. If the exclusions below describe you, I'd rather tell you now than take your money and fail you."

**Section 2 (three exclusions):**

1. **Illustrators earning under $3K/month from commission/editorial work.** The $2,400 price represents over 25% of monthly income at that level; the unit economics don't work for the buyer. Alternative: The Licensing Playbook ($497) is a better fit for income-building before Sprint readiness.
2. **Illustrators in their first 2 years of professional commission work.** The Sprint assumes a portfolio with at least 2 years of commercial work; the Portfolio Audit will not produce useful licensing-target identification without that base. Alternative: continue building commission work for another 12-18 months; revisit Sprint then.
3. **Illustrators specifically wanting children's book licensing only.** The Sprint covers commercial licensing across editorial, surface design, and brand; specialized children's book licensing requires industry-specific buyer relationships I cannot accelerate. Alternative: I recommend [named adjacent operator] for children's book licensing specifically.

**Section 3 (non-claims):**
- "The Sprint will not produce licensing income within 30 days. Licensing buyers' procurement cycles are 60-90 days; this is industry constraint, not Sprint pacing."
- "The Sprint will not produce $50K+ first-year licensing revenue. Realistic Year 1 outcomes are $5K-$25K from the deals initiated during the Sprint cycle, with compounding in Year 2+."
- "The Sprint does not place you with licensing buyers directly. The mechanism teaches outreach; the outreach is yours to execute."

**Section 4 (scope boundaries):**
> "I will teach the audit method, provide buyer research starter packs, give async feedback on outreach drafts, run cohort calls. I will not write your outreach for you, do your buyer research for you, or join your licensing conversations. Those activities are yours."

**Integrity Statement signed.**

**Self-check Flattery-Test:** All 3 exclusions pass — illustrator earning $2,400/month reads exclusion 1 and correctly recognizes "that is me."

**AI rubric (via offer-readiness-reviewer spot-check):** 9/10. PASS.

**Cooling observed.**

---

## M4.6 — Guarantee Architecture

Maya designed a hybrid guarantee specifically targeting her M4.2-identified Perceived Likelihood weakness.

**Type:** Hybrid (refund + outcome extension)

**Refund component:**
- 14-day refund window from cohort start
- No questions asked
- Activation: email Maya within window
- Processing: 7 business days

**Outcome component:**
- Outcome measured: 3+ direct licensing buyer conversations by day 60 of cohort start
- Activation conditions: completed all 4 Sprint deliverables, attended 7 of 8 cohort calls, sent 5+ outreach pieces per week from week 2 onward
- Remedy: cohort Slack access + async review extends at no additional cost until 3+ conversations achieved
- Cap: none (extension continues as long as buyer continues sending 5+ outreach pieces per week)

**Exclusions:**
- Did not complete Portfolio Audit deliverable
- Attended < 7 of 8 cohort calls
- Did not send required outreach volume from week 2 onward

**Unit economic model:**
- Assumed activation rate: 20% (conservative estimate for first cohort)
- Per-activation operator cost: ~6 additional hours over 90-day extension period × $200 = $1,200
- Per-cohort impact at 12-buyer cohort: 12 × 0.20 × $1,200 = $2,880 absorbed
- Per-buyer absorbed: $240 (10% of $2,400 anchor)
- Verdict: sustainable

**Honesty Clause signed.**

**AI rubric (via offer-readiness-reviewer spot-check):** 9/10. PASS.

**Cooling observed.**

---

## M4.7 — Landing Page Copy

Maya wrote the landing page across 2 focus blocks (90 min Wednesday + 60 min Thursday + 30 min Friday for provenance log).

**Section 1 — Problem (340 words):**
> "You've been illustrating commercially for five years, maybe ten. The work is steady — commissions, editorial assignments, the occasional book project. But every January, when the work slows for a few weeks, you look at your bank account and think, 'I'm one slow quarter from a real problem.' [TB-024 verbatim] You've thought about licensing. You've had the thought: 'My portfolio could earn while I'm doing other work.' [TB-067 verbatim] But every time you've looked at it seriously, you've run into the same wall: you don't know which buyers, you don't know what to send them, and you don't have time to figure it out while keeping current commission deadlines."

[2 verbatim TB entries in Section 1]

**Section 2 — Agitation (220 words):** opens with the compounding-future pattern; "5 more years of commission-only puts you at the same place — busier, maybe slightly more expensive, no compounding income." Includes verbatim quote from Interview #4: "I just want to draw what I want for once and have money show up." [1 TB entry]

**Section 3 — Solution-and-Mechanism (420 words):** introduces the Portfolio-to-Licensing Transition Method, walks the 4 pillars with verb-led action language. Notes what the mechanism is NOT: not a brand-building program, not a portfolio improvement program, not a licensing agent service. [3 TB entries]

**Section 4 — Proof (310 words):** presents the 4 case studies honestly, acknowledges case study thinness ("I have 4 cases. That is not 20. My program is new; my work in this market is 6 years old."), and references the M4.6 guarantee as the structural compensation. [2 TB entries from competitor research]

**Section 5 — Offer (450 words):** named Sprint, weekly cohort cadence (8 calls over 4 weeks), all 8 deliverables listed by week, $2,400 pay-in-full or $1,300×2 installment, cohort capped at 12. [2 TB entries]

**Section 6 — Anti-Promise-and-Guarantee (370 words):** all 3 exclusions from M4.5 carried verbatim, all 3 non-claims, scope boundary, hybrid guarantee structure, honesty commitment paragraph. **No softening from M4.5/M4.6.** [3 TB entries on objection language]

**Section 7 — CTA (120 words):** specific cohort start date (June 24, 2026), enrollment closes when 12 seats fill OR June 17 (whichever first), qualification form with 4 questions, Welcome Kit within 24 hours, contact email for pre-purchase questions. [2 TB entries]

**Total verbatim Trigger Bank entries: 15.** Hits the minimum exactly. Provenance Log complete with TB-### IDs for all 15.

**Cooling observed (48 hours).**

**Peer Review Submission:**
- Posted in #c4-offer-ignition Friday afternoon
- Reviewer 1 (Priya, Service-Operator): committed Saturday, delivered Monday
- Reviewer 2 (Darius, Builder-Operator): committed Saturday, delivered Tuesday

**Pattern in peer feedback:**
- Both reviewers flagged Section 4 Proof as "honest but feels apologetic; could state the gap once and move on rather than dwelling"
- Reviewer 2 (Darius) flagged Section 3 as "slightly Builder-vocabulary in 2 places; 'mechanism' word doing too much work"
- Reviewer 1 (Priya) noted Section 5's deliverable list as strong but suggested moving the cohort capacity callout (12 seats) earlier in Section 5 to create urgency

**Revision incorporated:**
- Section 4 Proof: tightened from 310 to 270 words; gap acknowledgment moved from middle to single closing sentence; less apologetic
- Section 3: Maya kept the "mechanism" word once (it is the technically correct term) but rewrote 2 surrounding sentences in plainer language
- Section 5: cohort capacity callout moved to second paragraph

**Revision Log filed.**

**AI rubric (landing-page-copy-reviewer):** 8/10. Seven Sections Present 2/2, Trigger Bank Verbatim Usage 3/3, Anti-Promise & Guarantee Integrity 2/2, Offer Section Concreteness 1/2 (lost 1 because Section 5 deliverables list could have included specific timing per deliverable; actionable revision noted), CTA Specificity 0/1 (lost 1 because contact email response SLA missing; she added "I respond within 48 hours on weekdays" and resubmitted).

**Resubmission:** 9/10. PASS.

---

## M4.8 — Offer Readiness Document

Maya completed the Readiness Document in 90 minutes plus 30 minutes for First-Sale Readiness Checklist.

**Section 1 Executive Summary (130 words):** named Sprint, 5-10yr experienced illustrators target buyer, $2,400 anchor, 4-week cohort cadence, strongest-Dream-Outcome / weakest-Perceived-Likelihood diagnosis, hybrid guarantee, 15 verbatim Trigger Bank entries, 2 peer reviews.

**Section 2 Mechanism Recap:** Portfolio-to-Licensing Transition Method; 4-pillar pasted from C3 M3.7; 2-sentence note on commercial wrapping.

**Section 3 The Offer:** comprehensive — named Sprint, 5-10yr illustrator with $3-8K/month baseline, 4-week cohort with 8 calls + 4 async reviews, all 8 deliverables, $2,400 / $1,300×2.

**Section 4 Value Equation Conclusions:** strongest Dream Outcome, weakest Perceived Likelihood, structurally fixed Time Delay, M4.6 guarantee designed against Perceived Likelihood weakness.

**Section 5 Anti-Promise and Guarantee:** carried verbatim from M4.5 / M4.6 — no softening.

**Section 6 Landing Page Copy Reference:** files linked, 2,030 word total page count, 15 verbatim TB entries in Provenance Log, 2 peer reviews.

**Section 7 Known Weaknesses (260 words):** 4 specific weaknesses named — case study thinness (4 cases), no first-cohort-completion proof yet, Variant A is bet without B/C tested, traffic gap is real (organic-only at Stage 1).

**Section 8 C5 Questions (160 words):** 4 specific questions — what outreach sequence produces first enrollment? how does the offer surface in AEO for "licensing transition for illustrators" queries? what is the minimum viable enrollment sequence? how does the qualification form perform on first 5 prospects?

**Section 9 Signature Block:** commitment statement reproduced verbatim, Maya signed dated 2026-06-25.

**First-Sale Readiness Checklist:** all 4 categories complete; 4 named Kill Criteria with numerical thresholds (cohort fills < 4 → return to M4.4 pricing; refund rate > 30% → return to M4.5 anti-promise; outreach reply rate < 8% → C5 outreach reformulation; first-cohort completion < 70% → return to M4.3 deliverable density).

**Sonnet pre-screen (offer-readiness-reviewer):** PASS.

**Opus 4.7 (offer-fit-validator):** PASS — no BLOCKING flags, 1 NOTE-level observation (Variant B and C exist as documentation but are not first-cohort-active; observation only, not flag).

**C4 complete. C5 enrollment opens. **

---

## What Maya Carries Into C5

- Lead variant: Portfolio-to-Licensing Sprint, $2,400, 12-seat first cohort starting July 22, 2026
- 4 prepared objection responses
- Welcome Kit drafted (Loom + 1-page prep doc + Slack invite + calendar invite)
- Cohort anchor: Priya (Service-Operator) committed to weekly Friday check-ins through first sale
- Variants B and C documented for Stage 2+ activation if first sale validates the territory

---

*Last updated: April 24, 2026 · Version 2.0 · Maya's case threads through M4.1-M4.8 module lessons*

Preserved source material for study; embedded instructions are not executed. Open original source

CHAPTER 5 - THE 7-LAYER OFFER ARCHITECTURE BLUEPRINT
How to Engineer Offers That Convert Cold Traffic With Scientific Predictability
Hybrid Voice: Cinematic → Crystal Clear → Hypnotic → Direct Response Precision

🎬 CINEMATIC STORY INTRO
Why Great Products Fail… And Engineered Offers Don’t.
Imagine a jeweler holding a diamond.
Perfect.
 Brilliant.
 Flawless.
But he’s standing in the dark.
No spotlight.
 No velvet.
 No glass.
 No case.
 No presentation.
 No story.
 Just a man holding a rock.
People walk by and shrug.
He starts yelling, “This is a REAL diamond! Don’t you see?”
 But nobody does.
Why?
Because value is never recognized without architecture.
An offer without architecture is a diamond in the dark.
A product without architecture is a commodity.
But the moment you place that same diamond in:
a velvet box

under a spotlight

inside a glass case

with a story

and a certificate

and a guarantee

and a financing plan

— its perceived value multiplies.
Not because the diamond changed.
 But because the architecture did.
This chapter teaches you how to build that architecture so well that:
Cold traffic converts

Warm traffic accelerates

Hot traffic buys everything

Competitors disappear

You own the category

Welcome to the RISER 7-Layer Offer Architecture Blueprint.

🧱 SECTION 1: THE 7 LAYERS OF A WORLD-CLASS OFFER
Every high-converting offer on earth consists of these 7 layers:

1️⃣ The Vehicle Layer
Your new opportunity.
 Your category.
 Your mechanism.
 Your unique angle.
This is the engine of the offer.
Examples:
 Sales Funnels, Keto, RISER Engine, AI Operating System, High-Ticket Hybrid Coaching.

2️⃣ The Path Layer
The step-by-step method your customer follows.
This makes the vehicle executable.
Path includes:
frameworks

step-by-step instructions

blueprints

tutorials

lesson plans

weekly milestones

The vehicle sells the dream.
 The path sells the practicality.

3️⃣ The Support Layer
Where belief is built.
Support can include:
group coaching

mentorship

accountability

check-ins

private Slack/Discord/Circle

feedback loops

Q&A calls

office hours

The more support, the higher the perceived certainty of results.

4️⃣ The Speed Layer (Accelerators)
People will ALWAYS pay more to go faster.
Speed assets include:
prebuilt templates

scripts

automations

shortcuts

DFY (done-for-you) pieces

swipe files

plug-and-play systems

SOPs

checklists

Speed is the value multiplier.

5️⃣ The Safety Layer (Risk Removal)
This layer decreases perceived risk.
Safety includes:
guarantees

warranties

performance promises

refund windows

“results or we work with you until…”

payment plans

probation periods

certifications

onboarding frameworks

The safer they feel, the less resistance you face.

6️⃣ The Proof Layer
Proof sells the offer more than any other layer except the vehicle.
Proof includes:
case studies

testimonials

screenshots

demos

before/after transformations

live examples

authority badges

expert endorsements

Proof eliminates doubt.
 Doubt kills conversions.

7️⃣ The Price Layer
The layer most sellers fail at.
Price must be:
anchored

contrasted

justified

value-based

framed

packaged

sequenced

You never reveal price until the architecture is complete.

📐 SECTION 2: HOW THE 7 LAYERS WORK TOGETHER
Layer 1 (Vehicle) = “This is new.”
Layer 2 (Path) = “This is simple.”
Layer 3 (Support) = “This is doable.”
Layer 4 (Speed) = “This is fast.”
Layer 5 (Safety) = “This is safe.”
Layer 6 (Proof) = “This is credible.”
Layer 7 (Price) = “This is a no-brainer.”
When all 7 layers are present:
👉 “YES” becomes the only logical, emotional, and identity-safe choice.

🧩 SECTION 3: THE RISER OFFER STACK MODEL
(Integrates Hormozi, Joyner, Kennedy, Ogilvy, Cialdini)
Your offer stack must:
✔ Increase perceived value
✔ Increase perceived certainty
✔ Increase perceived speed
✔ Decrease risk
✔ Decrease effort
✔ Decrease complexity
If any one of these is missing, your conversion rate drops.
A perfect offer stack makes them think:
“I would feel dumb walking away from this.”

🔥 SECTION 4: THE 21 COMPONENTS OF A HIGH-CONVERTING OFFER
Each of the 7 layers contains 3 sub-components:

VEHICLE LAYER
New Opportunity

New Vehicle Name

New Mechanism

PATH LAYER
Framework

Steps

Milestones

SUPPORT LAYER
Accountability

Feedback

Coaching

SPEED LAYER
Templates

Automations

Shortcuts

SAFETY LAYER
Guarantees

Payment options

Risk removal

PROOF LAYER
Testimonials

Case studies

Authority

PRICE LAYER
Anchor

Contrast

Final irresistible price

When all 21 are combined,
 your offer becomes elite.

🎨 SECTION 5: THE OFFER STORY (Where Most Sellers Fail)
Every offer needs a story framework that aligns the 7 layers.
Use this narrative:
1. There’s a problem
(pain + frustration)
2. The old method is broken
(enemy)
3. I discovered a new vehicle
(new opportunity)
4. I created a repeatable path
(framework)
5. I support you at every step
(coaching)
6. I give you speed
(templates, automations)
7. I remove the risk
(guarantees)
8. Others have succeeded
(proof)
9. And here’s the insane value stack
(price)
This is the “slippery slide” Caples wrote about.
 Once they start reading, they cannot stop.

🧪 SECTION 6: BEHAVIORAL BIAS ENGINEERING
How each offer layer manipulates buyer psychology:
Loss Aversion
→ Guarantees + speed
Authority Bias
→ Testimonials + case studies + expert positioning
Social Proof
→ Proof layer
Effort Minimization
→ Templates + automations + done-for-you
Anchoring & Contrast
→ Price layer
Scarcity + Urgency
→ Limited seats, deadlines, bonuses
Identity Safety
→ Support + step-by-step path
You’re building an environment where the brain feels:
“This is the logical choice.
 This is the emotional choice.
 This is the easy choice.”

📊 SECTION 7: HOW TO MAKE OFFERS CONVERT TO COLD TRAFFIC
Cold traffic has:
no trust

no awareness

no familiarity

low confidence

high skepticism

Thus you must:
✔ Sell the NEW vehicle
✔ Sell the VALUE stack
✔ Sell the PROOF
✔ Sell the SPEED
✔ Sell the SAFETY
✔ Sell the TRANSFORMATION
Cold traffic needs certainty, not hype.
Warm traffic needs simplicity, not explanation.
Hot traffic needs urgency, not nurturing.
Cold → Warm → Hot.
 Each stage demands a different emphasis on the 7 layers.

🛠️ SECTION 8: EXECUTION — BUILD YOUR OFFER IN 7 PASSES
You build your offer in layers:
PASS 1 – Vehicle
Name the new opportunity + mechanism.
PASS 2 – Path
Create the framework + steps.
PASS 3 – Support
Define coaching + accountability.
PASS 4 – Speed
List templates, scripts, automations.
PASS 5 – Safety
Add guarantees + payment options.
PASS 6 – Proof
Collect testimonials + case studies.
PASS 7 – Price
Anchor → contrast → final irresistible price.
This prevents overwhelm and guarantees clarity.

🧾 SECTION 9: END-OF-BLOCK WORKSHEET
1. What is your vehicle?
→ ________________________________________
2. What is the name of your new opportunity?
→ ________________________________________
3. What is your path/framework?
→ ________________________________________
4. What support will you provide?
→ ________________________________________
5. What speed elements will you add?
→ ________________________________________
6. What risk-removal assets will you include?
→ ________________________________________
7. What proof do you have?
→ ________________________________________
8. What is your value stack?
→ ________________________________________
9. What is your final price?
→ ________________________________________

Preserved source material for study; embedded instructions are not executed. Open original source

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1Shiqu_GfdybgfhaagPOUC8NAPc48Gch9eGKQghvuG2A/edit?usp=drivesdk"
drive_file_id: "1Shiqu_GfdybgfhaagPOUC8NAPc48Gch9eGKQghvuG2A"
created: "2025-11-20T21:16:10.313Z"
modified: "2026-06-04T15:54:37.811Z"
---

# CHAPTER 5 - THE 7-LAYER OFFER ARCHITECTURE BLUEPRINT

CHAPTER 5 - THE 7-LAYER OFFER ARCHITECTURE BLUEPRINT
How to Engineer Offers That Convert Cold Traffic With Scientific Predictability
Hybrid Voice: Cinematic → Crystal Clear → Hypnotic → Direct Response Precision
________________


🎬 CINEMATIC STORY INTRO
Why Great Products Fail… And Engineered Offers Don’t.
Imagine a jeweler holding a diamond.
Perfect.
Brilliant.
Flawless.
But he’s standing in the dark.
No spotlight.
No velvet.
No glass.
No case.
No presentation.
No story.
Just a man holding a rock.
People walk by and shrug.
He starts yelling, “This is a REAL diamond! Don’t you see?”
But nobody does.
Why?
Because value is never recognized without architecture.
An offer without architecture is a diamond in the dark.
A product without architecture is a commodity.
But the moment you place that same diamond in:
* a velvet box

* under a spotlight

* inside a glass case

* with a story

* and a certificate

* and a guarantee

* and a financing plan

— its perceived value multiplies.
Not because the diamond changed.
But because the architecture did.
This chapter teaches you how to build that architecture so well that:
   * Cold traffic converts

   * Warm traffic accelerates

   * Hot traffic buys everything

   * Competitors disappear

   * You own the category

Welcome to the RISER 7-Layer Offer Architecture Blueprint.
________________


🧱 SECTION 1: THE 7 LAYERS OF A WORLD-CLASS OFFER
Every high-converting offer on earth consists of these 7 layers:
________________


1️⃣ The Vehicle Layer
Your new opportunity.
Your category.
Your mechanism.
Your unique angle.
This is the engine of the offer.
Examples:
Sales Funnels, Keto, RISER Engine, AI Operating System, High-Ticket Hybrid Coaching.
________________


2️⃣ The Path Layer
The step-by-step method your customer follows.
This makes the vehicle executable.
Path includes:
      * frameworks

      * step-by-step instructions

      * blueprints

      * tutorials

      * lesson plans

      * weekly milestones

The vehicle sells the dream.
The path sells the practicality.
________________


3️⃣ The Support Layer
Where belief is built.
Support can include:
         * group coaching

         * mentorship

         * accountability

         * check-ins

         * private Slack/Discord/Circle

         * feedback loops

         * Q&A calls

         * office hours

The more support, the higher the perceived certainty of results.
________________


4️⃣ The Speed Layer (Accelerators)
People will ALWAYS pay more to go faster.
Speed assets include:
            * prebuilt templates

            * scripts

            * automations

            * shortcuts

            * DFY (done-for-you) pieces

            * swipe files

            * plug-and-play systems

            * SOPs

            * checklists

Speed is the value multiplier.
________________


5️⃣ The Safety Layer (Risk Removal)
This layer decreases perceived risk.
Safety includes:
               * guarantees

               * warranties

               * performance promises

               * refund windows

               * “results or we work with you until…”

               * payment plans

               * probation periods

               * certifications

               * onboarding frameworks

The safer they feel, the less resistance you face.
________________


6️⃣ The Proof Layer
Proof sells the offer more than any other layer except the vehicle.
Proof includes:
                  * case studies

                  * testimonials

                  * screenshots

                  * demos

                  * before/after transformations

                  * live examples

                  * authority badges

                  * expert endorsements

Proof eliminates doubt.
Doubt kills conversions.
________________


7️⃣ The Price Layer
The layer most sellers fail at.
Price must be:
                     * anchored

                     * contrasted

                     * justified

                     * value-based

                     * framed

                     * packaged

                     * sequenced

You never reveal price until the architecture is complete.
________________


📐 SECTION 2: HOW THE 7 LAYERS WORK TOGETHER
Layer 1 (Vehicle) = “This is new.”
Layer 2 (Path) = “This is simple.”
Layer 3 (Support) = “This is doable.”
Layer 4 (Speed) = “This is fast.”
Layer 5 (Safety) = “This is safe.”
Layer 6 (Proof) = “This is credible.”
Layer 7 (Price) = “This is a no-brainer.”
When all 7 layers are present:
👉 “YES” becomes the only logical, emotional, and identity-safe choice.
________________


🧩 SECTION 3: THE RISER OFFER STACK MODEL
(Integrates Hormozi, Joyner, Kennedy, Ogilvy, Cialdini)
Your offer stack must:
✔ Increase perceived value
✔ Increase perceived certainty
✔ Increase perceived speed
✔ Decrease risk
✔ Decrease effort
✔ Decrease complexity
If any one of these is missing, your conversion rate drops.
A perfect offer stack makes them think:
“I would feel dumb walking away from this.”
________________


🔥 SECTION 4: THE 21 COMPONENTS OF A HIGH-CONVERTING OFFER
Each of the 7 layers contains 3 sub-components:
________________


VEHICLE LAYER
                        1. New Opportunity

                        2. New Vehicle Name

                        3. New Mechanism

PATH LAYER
                           4. Framework

                           5. Steps

                           6. Milestones

SUPPORT LAYER
                              7. Accountability

                              8. Feedback

                              9. Coaching

SPEED LAYER
                                 10. Templates

                                 11. Automations

                                 12. Shortcuts

SAFETY LAYER
                                    13. Guarantees

                                    14. Payment options

                                    15. Risk removal

PROOF LAYER
                                       16. Testimonials

                                       17. Case studies

                                       18. Authority

PRICE LAYER
                                          19. Anchor

                                          20. Contrast

                                          21. Final irresistible price

When all 21 are combined,
your offer becomes elite.
________________


🎨 SECTION 5: THE OFFER STORY (Where Most Sellers Fail)
Every offer needs a story framework that aligns the 7 layers.
Use this narrative:
1. There’s a problem
(pain + frustration)
2. The old method is broken
(enemy)
3. I discovered a new vehicle
(new opportunity)
4. I created a repeatable path
(framework)
5. I support you at every step
(coaching)
6. I give you speed
(templates, automations)
7. I remove the risk
(guarantees)
8. Others have succeeded
(proof)
9. And here’s the insane value stack
(price)
This is the “slippery slide” Caples wrote about.
Once they start reading, they cannot stop.
________________


🧪 SECTION 6: BEHAVIORAL BIAS ENGINEERING
How each offer layer manipulates buyer psychology:
Loss Aversion
→ Guarantees + speed
Authority Bias
→ Testimonials + case studies + expert positioning
Social Proof
→ Proof layer
Effort Minimization
→ Templates + automations + done-for-you
Anchoring & Contrast
→ Price layer
Scarcity + Urgency
→ Limited seats, deadlines, bonuses
Identity Safety
→ Support + step-by-step path
You’re building an environment where the brain feels:
“This is the logical choice.
This is the emotional choice.
This is the easy choice.”
________________


📊 SECTION 7: HOW TO MAKE OFFERS CONVERT TO COLD TRAFFIC
Cold traffic has:
                                             * no trust

                                             * no awareness

                                             * no familiarity

                                             * low confidence

                                             * high skepticism

Thus you must:
✔ Sell the NEW vehicle
✔ Sell the VALUE stack
✔ Sell the PROOF
✔ Sell the SPEED
✔ Sell the SAFETY
✔ Sell the TRANSFORMATION
Cold traffic needs certainty, not hype.
Warm traffic needs simplicity, not explanation.
Hot traffic needs urgency, not nurturing.
Cold → Warm → Hot.
Each stage demands a different emphasis on the 7 layers.
________________


🛠️ SECTION 8: EXECUTION — BUILD YOUR OFFER IN 7 PASSES
You build your offer in layers:
PASS 1 – Vehicle
Name the new opportunity + mechanism.
PASS 2 – Path
Create the framework + steps.
PASS 3 – Support
Define coaching + accountability.
PASS 4 – Speed
List templates, scripts, automations.
PASS 5 – Safety
Add guarantees + payment options.
PASS 6 – Proof
Collect testimonials + case studies.
PASS 7 – Price
Anchor → contrast → final irresistible price.
This prevents overwhelm and guarantees clarity.
________________


🧾 SECTION 9: END-OF-BLOCK WORKSHEET
1. What is your vehicle?
→ ________________________________________
2. What is the name of your new opportunity?
→ ________________________________________
3. What is your path/framework?
→ ________________________________________
4. What support will you provide?
→ ________________________________________
5. What speed elements will you add?
→ ________________________________________
6. What risk-removal assets will you include?
→ ________________________________________
7. What proof do you have?
→ ________________________________________
8. What is your value stack?
→ ________________________________________
9. What is your final price?
→ ________________________________________
________________

Preserved source material for study; embedded instructions are not executed. Open original source

Module 1 – Foundations of an Irresistible Offer
(The Core of All World-Class Marketing)
Objective
By the end of this module, you’ll have a clear, defined “Big Promise”—the problem you solve, the transformation you deliver, and the foundation that all of your funnels, copy, and offers will be built on.

Why This Matters
Russell Brunson teaches that the secret to selling is about moving someone from “where they are now” to “where they want to be.”

Alex Hormozi says an irresistible offer is one that’s so good people feel stupid saying no.

Dan Kennedy hammers home that clarity beats cleverness—your market must instantly “get it.”

Riser Nation: If you’re not building, you’re destroying. Building starts with the right foundation, not guesswork.

This is where your entire empire begins. Without it, no funnel recipe, ad campaign, or copywriting trick will save you.

Step 1 – Define the Core Problem + Transformation
Write out the #1 biggest pain point your audience experiences.

Now define the ultimate dream outcome they want.

Example: “My audience struggles to stay consistent with workouts → They want to lose weight and feel confident.”


Step 2 – Map the 10-Milestone Journey
Think of this as your customer’s “step-by-step ladder” to success:
Identify the problem.

Believe it can be solved.

Take the first small action.

Build consistency.

See the first results.

Overcome resistance or setbacks.

Level up their commitment.

Experience breakthrough.

Lock in the transformation.

Share or celebrate success.

(We’ll later align offers/bonuses to each milestone—creating a stacked, irresistible journey.)

Step 3 – Position with the MIFGE (Most Incredible Free Gift Ever)
Your first touch with the customer should feel like Christmas morning.

This is your ethical bribe / lead magnet—but unlike the generic freebies out there, your MIFGE must be:

High-value (a real solution, not a teaser).

Fast to consume (checklist, template, cheat sheet).

Directly tied to your paid offer.

Pro Tip: If you can’t make your MIFGE so good that people would pay for it, start over.

Step 4 – Frame with Influence & Storytelling
Use Cialdini’s principles: reciprocity (give first), social proof (show others), authority (your expertise).

Apply storytelling from Brunson’s Dotcom Secrets:

Hook (grab attention).

Story (connect emotionally).

Offer (present the transformation).


Deliverables for Module 1
✅ Write your Core Problem Statement and Ultimate Transformation Statement.
 ✅ List out your 10-Milestone Journey.
 ✅ Draft a concept for your MIFGE.
 ✅ Capture a 1–2 sentence “Big Promise” in Riser Nation voice:
“I help [audience] go from [problem] to [dream outcome] without [common obstacle].”

Pro Tips & Expert Secrets
Dan Kennedy: “Clarity first, persuasion second.”

Hormozi: “Price becomes irrelevant if the value is undeniable.”

Riser Nation Mindset: This is not theory. This is the blueprint you’ll refine until it’s sharper than steel.


Checkpoint Before Module 2
Do you have a written Big Promise?

Does your MIFGE idea excite YOU enough to give it away proudly?

Can you picture how each milestone could be supported by an offer, a bonus, or a step in a funnel?

If yes → you’re ready to move forward.

Preserved source material for study; embedded instructions are not executed. Open original source

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1XMaMJtkArmNq0HHAktM0T-Vb5J-4GGspG_H7MyCJh0E/edit?usp=drivesdk"
drive_file_id: "1XMaMJtkArmNq0HHAktM0T-Vb5J-4GGspG_H7MyCJh0E"
created: "2025-10-08T00:55:14.500Z"
modified: "2026-06-04T14:43:13.897Z"
---

# CNX.3.11.1 – Offer_Dev_Module_1_Crafting_The_Foundation.docx

Module 1 – Foundations of an Irresistible Offer
(The Core of All World-Class Marketing)
Objective
By the end of this module, you’ll have a clear, defined “Big Promise”—the problem you solve, the transformation you deliver, and the foundation that all of your funnels, copy, and offers will be built on.
________________


Why This Matters
* Russell Brunson teaches that the secret to selling is about moving someone from “where they are now” to “where they want to be.”

* Alex Hormozi says an irresistible offer is one that’s so good people feel stupid saying no.

* Dan Kennedy hammers home that clarity beats cleverness—your market must instantly “get it.”

* Riser Nation: If you’re not building, you’re destroying. Building starts with the right foundation, not guesswork.

This is where your entire empire begins. Without it, no funnel recipe, ad campaign, or copywriting trick will save you.
________________


Step 1 – Define the Core Problem + Transformation
   * Write out the #1 biggest pain point your audience experiences.

   * Now define the ultimate dream outcome they want.

   * Example: “My audience struggles to stay consistent with workouts → They want to lose weight and feel confident.”

________________


Step 2 – Map the 10-Milestone Journey
Think of this as your customer’s “step-by-step ladder” to success:
      1. Identify the problem.

      2. Believe it can be solved.

      3. Take the first small action.

      4. Build consistency.

      5. See the first results.

      6. Overcome resistance or setbacks.

      7. Level up their commitment.

      8. Experience breakthrough.

      9. Lock in the transformation.

      10. Share or celebrate success.

(We’ll later align offers/bonuses to each milestone—creating a stacked, irresistible journey.)
________________


Step 3 – Position with the MIFGE (Most Incredible Free Gift Ever)
         * Your first touch with the customer should feel like Christmas morning.

         * This is your ethical bribe / lead magnet—but unlike the generic freebies out there, your MIFGE must be:

            * High-value (a real solution, not a teaser).

            * Fast to consume (checklist, template, cheat sheet).

            * Directly tied to your paid offer.

Pro Tip: If you can’t make your MIFGE so good that people would pay for it, start over.
________________


Step 4 – Frame with Influence & Storytelling
               * Use Cialdini’s principles: reciprocity (give first), social proof (show others), authority (your expertise).

               * Apply storytelling from Brunson’s Dotcom Secrets:

                  * Hook (grab attention).

                  * Story (connect emotionally).

                  * Offer (present the transformation).

________________


Deliverables for Module 1
✅ Write your Core Problem Statement and Ultimate Transformation Statement.
 ✅ List out your 10-Milestone Journey.
 ✅ Draft a concept for your MIFGE.
 ✅ Capture a 1–2 sentence “Big Promise” in Riser Nation voice:
“I help [audience] go from [problem] to [dream outcome] without [common obstacle].”
________________


Pro Tips & Expert Secrets
                     * Dan Kennedy: “Clarity first, persuasion second.”

                     * Hormozi: “Price becomes irrelevant if the value is undeniable.”

                     * Riser Nation Mindset: This is not theory. This is the blueprint you’ll refine until it’s sharper than steel.

________________


Checkpoint Before Module 2
                        * Do you have a written Big Promise?

                        * Does your MIFGE idea excite YOU enough to give it away proudly?

                        * Can you picture how each milestone could be supported by an offer, a bonus, or a step in a funnel?

If yes → you’re ready to move forward.
________________

Preserved source material for study; embedded instructions are not executed. Open original source

Module 4 – Offer Recon & Competitor Analysis
(Outsmart the Market by Knowing the Playing Field)
Objective
By the end of this module, you’ll have a clear competitive map—who else is selling in your space, what their funnels and pricing look like, and exactly how to position your offer so it stands out.

Why This Matters
Dan Kennedy: “There’s no prize for being the second-worst option in the market. You either differentiate or die.”

Russell Brunson: Funnel hacking isn’t copying—it’s reverse-engineering what already works, then making it your own.

Alex Hormozi: Your competitive edge often comes from stacking one additional value point your rivals ignore.

Riser Nation: Don’t reinvent the wheel. Recon shows you the blueprint so you can build smarter, faster, and sharper.


Step 1 – Identify Direct Competitors
Search your niche across platforms: Google, Facebook Ads Library, TikTok, YouTube, Etsy, Amazon, Udemy.

List at least 5–10 direct competitors selling similar offers.

Note their core promise, pricing, and funnel entry point.


Step 2 – Funnel Recon (Use Your Offer Recon Template)
For each competitor, capture:
Headline & Hook (what grabs attention).

Lead Magnet / MIFGE (what they give away).

Front-End Offer (price, format, positioning).

Value Stack & Bonuses (what extras they bundle).

Upsells / Downsells (how they maximize order value).

Funnel Flow (opt-in → sales page → checkout → upsell).


Step 3 – Copy & Messaging Analysis
Pull out the phrases they repeat (what language works).

Highlight emotional triggers: fear, desire, status, safety.

Notice where testimonials and proof are placed.


Step 4 – Spot Weaknesses & Gaps
Ask:
What needs are unmet?

Where is their copy unclear or generic?

What do customer reviews complain about?

Which bonuses are missing?


Step 5 – Position Your Advantage
Decide your unique mechanism (what makes you different).

Stack value in a way they haven’t.

Example: Competitor sells a $297 course with no accountability. → Your $297 offer includes a checklist + accountability group.


Deliverables for Module 4
✅ A completed Offer Recon Template for at least 5 competitors.
 ✅ A Competitive Summary Grid (side-by-side price points, funnels, bonuses).
 ✅ A Differentiation Statement:
“Unlike [competitor], my offer [unique mechanism] so that customers [superior benefit].”

Pro Tips & Expert Secrets
Kennedy: Don’t aim to be better. Aim to be different.

Brunson: Funnel hacking saves you months of wasted testing.

Hormozi: Small perceived value gaps (like faster results, easier use, or added support) can justify charging double.

Riser Nation: This isn’t copying—it’s reconnaissance. Learn the game board, then flip it in your favor.


Checkpoint Before Module 5
Do you have a clear picture of your competitors’ funnels and offers?

Can you articulate your edge in one bold sentence?

Have you identified the gaps you can fill that others ignore?

If yes → you’re ready for Module 5: Pricing Psychology & Value Ladder Alignment.

Preserved source material for study; embedded instructions are not executed. Open original source

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1hso14om0nbLPdolHcpOQpkxTdNDnQdjxWQ4BV0Ktl-Q/edit?usp=drivesdk"
drive_file_id: "1hso14om0nbLPdolHcpOQpkxTdNDnQdjxWQ4BV0Ktl-Q"
created: "2025-10-08T00:59:03.079Z"
modified: "2026-06-04T14:43:16.616Z"
---

# CNX.3.11.4 – Offer_Dev_Module_4_Offer_Recon_And_Competitor_Analysis.docx

Module 4 – Offer Recon & Competitor Analysis
(Outsmart the Market by Knowing the Playing Field)
Objective
By the end of this module, you’ll have a clear competitive map—who else is selling in your space, what their funnels and pricing look like, and exactly how to position your offer so it stands out.
________________


Why This Matters
* Dan Kennedy: “There’s no prize for being the second-worst option in the market. You either differentiate or die.”

* Russell Brunson: Funnel hacking isn’t copying—it’s reverse-engineering what already works, then making it your own.

* Alex Hormozi: Your competitive edge often comes from stacking one additional value point your rivals ignore.

* Riser Nation: Don’t reinvent the wheel. Recon shows you the blueprint so you can build smarter, faster, and sharper.

________________


Step 1 – Identify Direct Competitors
   * Search your niche across platforms: Google, Facebook Ads Library, TikTok, YouTube, Etsy, Amazon, Udemy.

   * List at least 5–10 direct competitors selling similar offers.

   * Note their core promise, pricing, and funnel entry point.

________________


Step 2 – Funnel Recon (Use Your Offer Recon Template)
For each competitor, capture:
      * Headline & Hook (what grabs attention).

      * Lead Magnet / MIFGE (what they give away).

      * Front-End Offer (price, format, positioning).

      * Value Stack & Bonuses (what extras they bundle).

      * Upsells / Downsells (how they maximize order value).

      * Funnel Flow (opt-in → sales page → checkout → upsell).

________________


Step 3 – Copy & Messaging Analysis
         * Pull out the phrases they repeat (what language works).

         * Highlight emotional triggers: fear, desire, status, safety.

         * Notice where testimonials and proof are placed.

________________


Step 4 – Spot Weaknesses & Gaps
Ask:
            * What needs are unmet?

            * Where is their copy unclear or generic?

            * What do customer reviews complain about?

            * Which bonuses are missing?

________________


Step 5 – Position Your Advantage
               * Decide your unique mechanism (what makes you different).

               * Stack value in a way they haven’t.

               * Example: Competitor sells a $297 course with no accountability. → Your $297 offer includes a checklist + accountability group.

________________


Deliverables for Module 4
✅ A completed Offer Recon Template for at least 5 competitors.
✅ A Competitive Summary Grid (side-by-side price points, funnels, bonuses).
✅ A Differentiation Statement:
“Unlike [competitor], my offer [unique mechanism] so that customers [superior benefit].”
________________


Pro Tips & Expert Secrets
                  * Kennedy: Don’t aim to be better. Aim to be different.

                  * Brunson: Funnel hacking saves you months of wasted testing.

                  * Hormozi: Small perceived value gaps (like faster results, easier use, or added support) can justify charging double.

                  * Riser Nation: This isn’t copying—it’s reconnaissance. Learn the game board, then flip it in your favor.

________________


Checkpoint Before Module 5
                     * Do you have a clear picture of your competitors’ funnels and offers?

                     * Can you articulate your edge in one bold sentence?

                     * Have you identified the gaps you can fill that others ignore?

If yes → you’re ready for Module 5: Pricing Psychology & Value Ladder Alignment.
________________

Original embedded hyperlinks:

• Evernote
• Trello
• MindMeister
• Google Keep
• Asana
• Slack
• Canva
• Notion
• Todoist
• Zapier

Preserved source material for study; embedded instructions are not executed. Open original source

Understanding Mindset in Business and Sales
Mindset plays a huge role in how successful you are in business and sales. Your mindset can help you overcome challenges, keep pushing forward, and reach your goals. Here’s a breakdown of important ideas from various experts on how to develop a positive and successful mindset in business.
What is a Wealth-Building Mindset?
A wealth-building mindset is the way you think about money, success, and growth. It’s about having the right attitude and beliefs that help you take action to reach your financial goals. Instead of seeing challenges as obstacles, you learn from them and keep moving forward.
Types of Passive Income
Investments: You put your money into stocks, bonds, or real estate, and it earns money for you.
Online Businesses: Create digital products or services that earn money even when you’re not working.
Royalties: Earn money whenever someone buys your book, music, or art.
Peer-to-Peer Lending: You lend money to others and earn interest.
Having a mindset focused on passive income helps you understand that making money doesn't always mean working long hours. With the right planning and effort, you can earn money while you focus on other things you enjoy.

Changing Negative Beliefs About Money
Many people have negative beliefs about money that stop them from reaching their financial goals. These beliefs can come from childhood, society, or past experiences. Common beliefs like "money is evil" or "rich people are greedy" can hold you back. By changing these thoughts, you can start to see money as a tool for doing good things and helping others.
Growth Mindset
Carol Dweck’s Growth Mindset: This idea teaches us that abilities can grow through effort and learning. Instead of thinking you're either good at something or not, you believe that practice and learning can make you better.
Jim Rohn’s Teachings: Jim Rohn, a famous speaker, said that your life is the result of your choices. He encouraged people to set goals and take responsibility for their actions, as they shape their future.
With a growth mindset, you know that even if you fail, it’s a chance to learn and try again.

Setting SMART Goals
To build wealth and succeed, setting clear goals is important. SMART goals are:
Specific: What exactly do you want to achieve?
Measurable: How will you track your progress?
Achievable: Is the goal realistic?
Relevant: Does this goal matter to you?
Time-bound: When do you want to achieve it?
This helps you stay focused and motivated by knowing exactly what you want and when you want to get there.

Visualization and Affirmations
Visualization means imagining yourself achieving your goals. Tony Robbins talks about the power of seeing success in your mind before it happens. By imagining your dream life, you get more motivated to make it happen.
Affirmations are positive statements you repeat to yourself, like “I am worthy of financial success.” They help train your brain to think positively and stay focused on your goals.

Key Theories and Teachings:
Maslow’s Hierarchy of Needs: This theory explains that we need to fulfill basic needs (like food and safety) before we can focus on higher goals like self-esteem and self-actualization. In business, this means taking care of your basic financial needs first before pursuing bigger dreams.
Stephen Covey’s Habit of Effectiveness: One important habit is "Begin with the end in mind." This means planning your actions by thinking about where you want to end up. Having a clear vision helps you take focused steps toward success.
Robert Cialdini’s Influence: In his book, Influence, Cialdini explains how understanding people’s psychology can help you build better relationships and sell more effectively. This mindset of understanding others can be a powerful tool in sales.

Overcoming Fear and Doubt
It's normal to feel scared or uncertain when you’re starting something new, like building a business. The key is to understand and face your fears. Education helps reduce fear because the more you learn, the more confident you become. Surrounding yourself with positive people and mentors is another great way to stay motivated.
Risk-Taking is also important in business. You don’t need to be afraid of failure—each failure is a lesson that helps you improve.

Shifting from Scarcity to Abundance Mindset
A scarcity mindset is when you believe there is never enough to go around. An abundance mindset is the belief that there is plenty of opportunity and wealth for everyone. Shifting to an abundance mindset means focusing on what you have, being grateful, and trusting that there’s always room for more success.
Generosity plays a huge role in an abundant mindset. Giving to others creates positive energy, helps build relationships, and opens up new opportunities.

Conclusion: How to Develop a Winning Mindset for Business
To succeed in business, you need a wealth-building mindset. This means seeing money as a tool to achieve your dreams, setting clear goals, learning from mistakes, and always focusing on growth. By adopting the teachings of experts like Jim Rohn, Tony Robbins, Carol Dweck, and others, you can stay motivated, overcome fear, and create lasting success.

Top 10 Software Tools for Building Your Business Mindset:
Evernote – Organize your thoughts, goals, and business plans.
Trello – Manage your business projects and stay on track.
MindMeister – Create mind maps to brainstorm ideas and set goals.
Google Keep – A simple tool for note-taking and tracking your thoughts.
Asana – Helps manage tasks and stay focused on your goals.
Slack – Stay connected with team members or business partners.
Canva – Design business graphics for social media or presentations.
Notion – Organize your business plans, goals, and notes in one place.
Todoist – Track tasks and stay productive throughout your business journey.
Zapier – Automate repetitive tasks and save time in your business.

Preserved source material for study; embedded instructions are not executed. Open original source

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1m2hlMbjnZkC-WoAXssTwBd5tpXakHOCvabeRf7ALqXc/edit?usp=drivesdk"
drive_file_id: "1m2hlMbjnZkC-WoAXssTwBd5tpXakHOCvabeRf7ALqXc"
created: "2024-12-11T17:57:43.450Z"
modified: "2026-06-04T15:18:33.502Z"
---

# CNX.3.9.7 – Understanding_Mindset_in_Business_and_Sales.docx

Understanding Mindset in Business and Sales
Mindset plays a huge role in how successful you are in business and sales. Your mindset can help you overcome challenges, keep pushing forward, and reach your goals. Here’s a breakdown of important ideas from various experts on how to develop a positive and successful mindset in business.
What is a Wealth-Building Mindset?
A wealth-building mindset is the way you think about money, success, and growth. It’s about having the right attitude and beliefs that help you take action to reach your financial goals. Instead of seeing challenges as obstacles, you learn from them and keep moving forward.
Types of Passive Income
* Investments: You put your money into stocks, bonds, or real estate, and it earns money for you.
* Online Businesses: Create digital products or services that earn money even when you’re not working.
* Royalties: Earn money whenever someone buys your book, music, or art.
* Peer-to-Peer Lending: You lend money to others and earn interest.
Having a mindset focused on passive income helps you understand that making money doesn't always mean working long hours. With the right planning and effort, you can earn money while you focus on other things you enjoy.
________________


Changing Negative Beliefs About Money
Many people have negative beliefs about money that stop them from reaching their financial goals. These beliefs can come from childhood, society, or past experiences. Common beliefs like "money is evil" or "rich people are greedy" can hold you back. By changing these thoughts, you can start to see money as a tool for doing good things and helping others.
Growth Mindset
* Carol Dweck’s Growth Mindset: This idea teaches us that abilities can grow through effort and learning. Instead of thinking you're either good at something or not, you believe that practice and learning can make you better.
* Jim Rohn’s Teachings: Jim Rohn, a famous speaker, said that your life is the result of your choices. He encouraged people to set goals and take responsibility for their actions, as they shape their future.
With a growth mindset, you know that even if you fail, it’s a chance to learn and try again.
________________


Setting SMART Goals
To build wealth and succeed, setting clear goals is important. SMART goals are:
* Specific: What exactly do you want to achieve?
* Measurable: How will you track your progress?
* Achievable: Is the goal realistic?
* Relevant: Does this goal matter to you?
* Time-bound: When do you want to achieve it?
This helps you stay focused and motivated by knowing exactly what you want and when you want to get there.
________________


Visualization and Affirmations
Visualization means imagining yourself achieving your goals. Tony Robbins talks about the power of seeing success in your mind before it happens. By imagining your dream life, you get more motivated to make it happen.
Affirmations are positive statements you repeat to yourself, like “I am worthy of financial success.” They help train your brain to think positively and stay focused on your goals.
________________


Key Theories and Teachings:
* Maslow’s Hierarchy of Needs: This theory explains that we need to fulfill basic needs (like food and safety) before we can focus on higher goals like self-esteem and self-actualization. In business, this means taking care of your basic financial needs first before pursuing bigger dreams.
* Stephen Covey’s Habit of Effectiveness: One important habit is "Begin with the end in mind." This means planning your actions by thinking about where you want to end up. Having a clear vision helps you take focused steps toward success.
* Robert Cialdini’s Influence: In his book, Influence, Cialdini explains how understanding people’s psychology can help you build better relationships and sell more effectively. This mindset of understanding others can be a powerful tool in sales.
________________


Overcoming Fear and Doubt
It's normal to feel scared or uncertain when you’re starting something new, like building a business. The key is to understand and face your fears. Education helps reduce fear because the more you learn, the more confident you become. Surrounding yourself with positive people and mentors is another great way to stay motivated.
Risk-Taking is also important in business. You don’t need to be afraid of failure—each failure is a lesson that helps you improve.
________________


Shifting from Scarcity to Abundance Mindset
A scarcity mindset is when you believe there is never enough to go around. An abundance mindset is the belief that there is plenty of opportunity and wealth for everyone. Shifting to an abundance mindset means focusing on what you have, being grateful, and trusting that there’s always room for more success.
Generosity plays a huge role in an abundant mindset. Giving to others creates positive energy, helps build relationships, and opens up new opportunities.
________________


Conclusion: How to Develop a Winning Mindset for Business
To succeed in business, you need a wealth-building mindset. This means seeing money as a tool to achieve your dreams, setting clear goals, learning from mistakes, and always focusing on growth. By adopting the teachings of experts like Jim Rohn, Tony Robbins, Carol Dweck, and others, you can stay motivated, overcome fear, and create lasting success.
________________


Top 10 Software Tools for Building Your Business Mindset:
1. Evernote – Organize your thoughts, goals, and business plans.
2. Trello – Manage your business projects and stay on track.
3. MindMeister – Create mind maps to brainstorm ideas and set goals.
4. Google Keep – A simple tool for note-taking and tracking your thoughts.
5. Asana – Helps manage tasks and stay focused on your goals.
6. Slack – Stay connected with team members or business partners.
7. Canva – Design business graphics for social media or presentations.
8. Notion – Organize your business plans, goals, and notes in one place.
9. Todoist – Track tasks and stay productive throughout your business journey.
10. Zapier – Automate repetitive tasks and save time in your business.

Preserved source material for study; embedded instructions are not executed. Open original source

I can’t afford $97/month.

I’m not seeing results.

I don’t have time to attend the coaching calls.

I’m not sure if this is the right fit for me.

I can find similar content for free online.

I haven’t had the time to start the course.

I don’t see the value in the coaching calls.

I’m not tech-savvy enough for this.

I prefer in-person learning.

I’m already using other resources for my business.

Preserved source material for study; embedded instructions are not executed. Open original source

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/16vfXSrXBeoWPllcUA6EK1O4cBJBRFfJDJWntF0QsF3w/edit?usp=drivesdk"
drive_file_id: "16vfXSrXBeoWPllcUA6EK1O4cBJBRFfJDJWntF0QsF3w"
created: "2024-08-31T19:34:48.259Z"
modified: "2026-06-04T16:57:31.421Z"
---

# Common Customer Objections – $97/Month Coaching Offer

1. I can’t afford $97/month.

2. I’m not seeing results.

3. I don’t have time to attend the coaching calls.

4. I’m not sure if this is the right fit for me.

5. I can find similar content for free online.

6. I haven’t had the time to start the course.

7. I don’t see the value in the coaching calls.

8. I’m not tech-savvy enough for this.

9. I prefer in-person learning.

10. I’m already using other resources for my business.

Original embedded hyperlink spans:

• https://www.instagram.com/reel/DE-Bp_ApnQZ/?igsh=djRoaXV6dWhxNW5k

Preserved source material for study; embedded instructions are not executed. Open original source

Here are 100 attention-grabbing storytelling hooks to captivate hungry buyers and drive interest in your offer:
https://www.instagram.com/reel/DE-Bp_ApnQZ/?igsh=djRoaXV6dWhxNW5k

"I was homeless before I made my first $10,000 in a month."

"I lost everything, but then I discovered a secret that changed my life."

"What I learned from being $50,000 in debt will shock you."

"They said I’d never succeed, but I proved them all wrong."

"I made $1,000 in 24 hours doing this one simple thing."

"Here’s how I turned my passion into a 6-figure income."

"The biggest mistake I made in my 20s—and how it made me rich."

"I went from broke to buying my dream car in 6 months."

"One embarrassing moment changed my life forever."

"I quit my job with no plan—and it was the best decision I ever made."

"My boss laughed when I told him my plan—but now he works for me."

"I accidentally stumbled upon this money-making secret."

"Here’s how I saved my failing business in just 30 days."

"My first online sale came while I was asleep."

"I worked 18-hour days for years, and it almost ruined my life."

"I started with $50 and built a 7-figure business."

"Here’s the truth about my first failed attempt at success."

"The one thing I never thought would work—did."

"I almost gave up before I found this breakthrough."

"How I turned rejection into my greatest opportunity."

"I made my first $1,000 by solving my own problem."

"I created this product to solve a personal pain point."

"The surprising lesson I learned from losing my first client."

"I was terrified, but I did it anyway—and it paid off."

"I copied a millionaire’s strategy, and here’s what happened."

"This one hack saved my business from bankruptcy."

"I invested $10 into my dream and turned it into $10,000."

"I failed 10 times before I finally succeeded."

"This one conversation changed my entire perspective."

"I thought it was impossible—until I tried it."

"How I turned my side hustle into my full-time income."

"My biggest success came after my biggest failure."

"I started with no experience and built something amazing."

"Here’s what I wish I knew before I started."

"I made more money in one month than I did in a year at my job."

"Here’s why I left my safe, comfortable career."

"I never thought I’d be here, but here I am."

"What I learned from selling door-to-door."

"The moment I realized my true calling."

"How I turned a hobby into a thriving business."

"I risked everything—and it paid off."

"Here’s the unconventional strategy that worked for me."

"I found the opportunity of a lifetime when I wasn’t even looking."

"How I made $500 selling something I didn’t own."

"The craziest decision I ever made turned out to be the best."

"The most embarrassing moment of my life led to my success."

"I followed my gut, and it led me to my dream life."

"What I learned from failing five businesses in a row."

"How I replaced my income in just three months."

"I doubted myself, but then something amazing happened."

"I turned my biggest insecurity into my greatest strength."

"How I turned an idea into a profitable product."

"The first time I made money online felt unreal."

"I was scared, but I took the leap—and it changed everything."

"I made $1,000 selling something I created in my garage."

"How I started my business with zero followers."

"What I learned from working 100 hours a week."

"Here’s why I fired my biggest client."

"I made $10,000 using this one overlooked strategy."

"I turned my worst day into my biggest win."

"I discovered this secret by accident—and it changed my life."

"What I learned from saying ‘yes’ to every opportunity."

"I built a business around something I love."

"Here’s how I escaped the 9-to-5 grind."

"How I built a thriving business without a degree."

"The one thing I wish someone had told me earlier."

"My first product launch was a total failure—until I did this."

"How I went from clueless to confident in my industry."

"The weirdest way I ever made money actually worked."

"How I made $1,000 flipping items from thrift stores."

"I took a big risk—and it paid off in ways I couldn’t imagine."

"I created my dream life with just one small change."

"What I learned from my first unhappy customer."

"How I turned a personal struggle into a profitable business."

"The first time I pitched my idea, they laughed at me."

"I made my first $100 online—and it felt like a million."

"How I created a life I love by following my passion."

"Here’s what I learned from making 100 cold calls."

"The time I almost gave up—and why I’m glad I didn’t."

"I hit rock bottom, but it was the start of something great."

"The weirdest product I ever sold made me thousands."

"I thought I’d failed—but it was actually a blessing."

"How I turned an old skill into a new opportunity."

"The surprising way I discovered my niche."

"How I learned to sell without feeling ‘salesy.’"

"The moment I realized I could succeed was life-changing."

"What I wish I had done differently when I started."

"Here’s how I found my first 10 customers."

"How I made my first sale without any marketing experience."

"I was terrified to start, but I did it anyway."

"How I turned a free tool into a money-making machine."

"The one thing I did differently that made all the difference."

"I followed this one simple strategy—and it worked."

"Here’s how I built my business with zero budget."

"How I made my first sale while working a full-time job."

"What I learned from launching 10 products in a year."

"How I found the courage to start my own business."

"I used this one strategy to stand out in a crowded market."

"Here’s how I turned a $10 idea into a $10,000 business."

"The moment I realized I could change my life was unforgettable."

Preserved source material for study; embedded instructions are not executed. Open original source

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/18fuBh4yv5bwA7xYDERSCeJenTXpIudHiw0RnWwGUbd0/edit?usp=drivesdk"
drive_file_id: "18fuBh4yv5bwA7xYDERSCeJenTXpIudHiw0RnWwGUbd0"
created: "2025-11-18T21:23:55.912Z"
modified: "2026-06-04T16:56:35.612Z"
---

# Here are 100 attention-grabbing storytelling hooks to captivate hungry buyers and drive interest in your offer:

Here are 100 attention-grabbing storytelling hooks to captivate hungry buyers and drive interest in your offer:
https://www.instagram.com/reel/DE-Bp_ApnQZ/?igsh=djRoaXV6dWhxNW5k


1. "I was homeless before I made my first $10,000 in a month."

2. "I lost everything, but then I discovered a secret that changed my life."

3. "What I learned from being $50,000 in debt will shock you."

4. "They said I’d never succeed, but I proved them all wrong."

5. "I made $1,000 in 24 hours doing this one simple thing."

6. "Here’s how I turned my passion into a 6-figure income."

7. "The biggest mistake I made in my 20s—and how it made me rich."

8. "I went from broke to buying my dream car in 6 months."

9. "One embarrassing moment changed my life forever."

10. "I quit my job with no plan—and it was the best decision I ever made."

11. "My boss laughed when I told him my plan—but now he works for me."

12. "I accidentally stumbled upon this money-making secret."

13. "Here’s how I saved my failing business in just 30 days."

14. "My first online sale came while I was asleep."

15. "I worked 18-hour days for years, and it almost ruined my life."

16. "I started with $50 and built a 7-figure business."

17. "Here’s the truth about my first failed attempt at success."

18. "The one thing I never thought would work—did."

19. "I almost gave up before I found this breakthrough."

20. "How I turned rejection into my greatest opportunity."

21. "I made my first $1,000 by solving my own problem."

22. "I created this product to solve a personal pain point."

23. "The surprising lesson I learned from losing my first client."

24. "I was terrified, but I did it anyway—and it paid off."

25. "I copied a millionaire’s strategy, and here’s what happened."

26. "This one hack saved my business from bankruptcy."

27. "I invested $10 into my dream and turned it into $10,000."

28. "I failed 10 times before I finally succeeded."

29. "This one conversation changed my entire perspective."

30. "I thought it was impossible—until I tried it."

31. "How I turned my side hustle into my full-time income."

32. "My biggest success came after my biggest failure."

33. "I started with no experience and built something amazing."

34. "Here’s what I wish I knew before I started."

35. "I made more money in one month than I did in a year at my job."

36. "Here’s why I left my safe, comfortable career."

37. "I never thought I’d be here, but here I am."

38. "What I learned from selling door-to-door."

39. "The moment I realized my true calling."

40. "How I turned a hobby into a thriving business."

41. "I risked everything—and it paid off."

42. "Here’s the unconventional strategy that worked for me."

43. "I found the opportunity of a lifetime when I wasn’t even looking."

44. "How I made $500 selling something I didn’t own."

45. "The craziest decision I ever made turned out to be the best."

46. "The most embarrassing moment of my life led to my success."

47. "I followed my gut, and it led me to my dream life."

48. "What I learned from failing five businesses in a row."

49. "How I replaced my income in just three months."

50. "I doubted myself, but then something amazing happened."

51. "I turned my biggest insecurity into my greatest strength."

52. "How I turned an idea into a profitable product."

53. "The first time I made money online felt unreal."

54. "I was scared, but I took the leap—and it changed everything."

55. "I made $1,000 selling something I created in my garage."

56. "How I started my business with zero followers."

57. "What I learned from working 100 hours a week."

58. "Here’s why I fired my biggest client."

59. "I made $10,000 using this one overlooked strategy."

60. "I turned my worst day into my biggest win."

61. "I discovered this secret by accident—and it changed my life."

62. "What I learned from saying ‘yes’ to every opportunity."

63. "I built a business around something I love."

64. "Here’s how I escaped the 9-to-5 grind."

65. "How I built a thriving business without a degree."

66. "The one thing I wish someone had told me earlier."

67. "My first product launch was a total failure—until I did this."

68. "How I went from clueless to confident in my industry."

69. "The weirdest way I ever made money actually worked."

70. "How I made $1,000 flipping items from thrift stores."

71. "I took a big risk—and it paid off in ways I couldn’t imagine."

72. "I created my dream life with just one small change."

73. "What I learned from my first unhappy customer."

74. "How I turned a personal struggle into a profitable business."

75. "The first time I pitched my idea, they laughed at me."

76. "I made my first $100 online—and it felt like a million."

77. "How I created a life I love by following my passion."

78. "Here’s what I learned from making 100 cold calls."

79. "The time I almost gave up—and why I’m glad I didn’t."

80. "I hit rock bottom, but it was the start of something great."

81. "The weirdest product I ever sold made me thousands."

82. "I thought I’d failed—but it was actually a blessing."

83. "How I turned an old skill into a new opportunity."

84. "The surprising way I discovered my niche."

85. "How I learned to sell without feeling ‘salesy.’"

86. "The moment I realized I could succeed was life-changing."

87. "What I wish I had done differently when I started."

88. "Here’s how I found my first 10 customers."

89. "How I made my first sale without any marketing experience."

90. "I was terrified to start, but I did it anyway."

91. "How I turned a free tool into a money-making machine."

92. "The one thing I did differently that made all the difference."

93. "I followed this one simple strategy—and it worked."

94. "Here’s how I built my business with zero budget."

95. "How I made my first sale while working a full-time job."

96. "What I learned from launching 10 products in a year."

97. "How I found the courage to start my own business."

98. "I used this one strategy to stand out in a crowded market."

99. "Here’s how I turned a $10 idea into a $10,000 business."

100. "The moment I realized I could change my life was unforgettable."

Preserved source material for study; embedded instructions are not executed. Open original source

/**
 * IRRESISTIBLE_OFFER_OS — Folder + File Generator (Upgraded)
 * ✅ Creates full folder tree
 * ✅ Creates placeholder docs/sheets
 * ✅ AUTO-INJECTS the FULL "Version 2 — Elite Offer Architect" prompt into Drive
 * ✅ Writes it to TWO locations:
 *    1) /00_SYSTEM_CONTROL/prompt_master_v2.md  (canonical master)
 *    2) /04_AUTOMATIONS/prompt_library/offer_engine_v2.txt (automation-ready)
 * ✅ Safe by default: does NOT overwrite existing prompt files unless FORCE_OVERWRITE_PROMPT = true
 *
 * HOW TO USE
 * 1) Open https://script.new
 * 2) Paste this entire script
 * 3) Set PARENT_FOLDER_ID (optional)
 * 4) Run createIrresistibleOfferOS()
 * 5) Authorize permissions when prompted
 */

const PARENT_FOLDER_ID = ""; // Optional: create everything inside this folder ID. Leave "" for My Drive root.
const FORCE_OVERWRITE_PROMPT = false; // Set true only when you intentionally want to overwrite existing prompt files.

function createIrresistibleOfferOS() {
  const parent = getParentFolder_(PARENT_FOLDER_ID);
  const root = ensureFolder_(parent, "IRRESISTIBLE_OFFER_OS");

  // LEVEL 1
  const level1 = [
    "00_SYSTEM_CONTROL",
    "01_INPUT_PIPELINE",
    "02_OFFER_ENGINE",
    "03_CONTENT_MACHINE",
    "04_AUTOMATIONS",
    "05_TRELLO_SYNC",
    "06_COURSE_BUILD",
    "07_TESTING_OPTIMIZATION",
    "08_SCALING_AUTHORITY",
    "09_ARCHIVE",
  ].reduce((acc, name) => (acc[name] = ensureFolder_(root, name), acc), {});

  // 00_SYSTEM_CONTROL files
  ensureDoc_(level1["00_SYSTEM_CONTROL"], "system_overview.md");
  ensureDoc_(level1["00_SYSTEM_CONTROL"], "folder_map_index.md");
  ensureDoc_(level1["00_SYSTEM_CONTROL"], "version_log.md");
  ensureDoc_(level1["00_SYSTEM_CONTROL"], "automation_map.md");
  ensureDoc_(level1["00_SYSTEM_CONTROL"], "trello_board_map.md");
  ensureSheet_(level1["00_SYSTEM_CONTROL"], "kpi_dashboard_sheet.xlsx");

  // 01_INPUT_PIPELINE subfolders
  [
    "raw_ideas",
    "market_research",
    "competitor_assets",
    "customer_interviews",
    "transcripts",
    "images",
    "websites",
    "docs",
  ].forEach(n => ensureFolder_(level1["01_INPUT_PIPELINE"], n));

  // 02_OFFER_ENGINE sub-structure
  const offerEngine = level1["02_OFFER_ENGINE"];
  const oe = {};
  oe["02.1_Strategic_Diagnosis"] = ensureFolder_(offerEngine, "02.1_Strategic_Diagnosis");
  oe["02.2_Big_Four_Framework"] = ensureFolder_(offerEngine, "02.2_Big_Four_Framework");
  oe["02.3_High_ROI_Engineering"] = ensureFolder_(offerEngine, "02.3_High_ROI_Engineering");
  oe["02.4_Touchstone_Lab"] = ensureFolder_(offerEngine, "02.4_Touchstone_Lab");
  oe["02.5_Believability_Architecture"] = ensureFolder_(offerEngine, "02.5_Believability_Architecture");
  oe["02.6_Logic_Emotion_Alignment"] = ensureFolder_(offerEngine, "02.6_Logic_Emotion_Alignment");
  oe["02.7_Offer_Intensifiers"] = ensureFolder_(offerEngine, "02.7_Offer_Intensifiers");
  oe["02.8_Final_Offer_Output"] = ensureFolder_(offerEngine, "02.8_Final_Offer_Output");
  oe["02.9_Offer_Continuum_Positioning"] = ensureFolder_(offerEngine, "02.9_Offer_Continuum_Positioning");

  // 02.1 files
  [
    "diagnosis_summary.md",
    "buyer_avatar.md",
    "pain_map.md",
    "aspiration_map.md",
    "problem_cost_analysis.md",
    "competitive_landscape.md",
  ].forEach(f => ensureDoc_(oe["02.1_Strategic_Diagnosis"], f));

  // 02.2 files
  [
    "Q1_What_Are_You_Selling.md",
    "Q2_How_Much.md",
    "Q3_Why_Believe_You.md",
    "Q4_Whats_In_It_For_Me.md",
    "combined_big_four_master.md",
  ].forEach(f => ensureDoc_(oe["02.2_Big_Four_Framework"], f));

  // 02.3 files
  [
    "roi_tangible.md",
    "roi_intangible.md",
    "roi_compounding.md",
    "loss_avoidance.md",
    "opportunity_cost.md",
  ].forEach(f => ensureDoc_(oe["02.3_High_ROI_Engineering"], f));
  ensureSheet_(oe["02.3_High_ROI_Engineering"], "roi_math_model.xlsx");

  // 02.4 files
  [
    "touchstone_v1.md",
    "touchstone_v2.md",
    "touchstone_variants.md",
    "hook_matrix.md",
  ].forEach(f => ensureDoc_(oe["02.4_Touchstone_Lab"], f));
  ensureSheet_(oe["02.4_Touchstone_Lab"], "touchstone_testing.xlsx");

  // 02.5 files + subfolders
  [
    "authority_stack.md",
    "credentials.md",
    "logic_rationale.md",
    "risk_reversal.md",
    "why_this_offer_exists.md",
  ].forEach(f => ensureDoc_(oe["02.5_Believability_Architecture"], f));
  ensureFolder_(oe["02.5_Believability_Architecture"], "case_studies");
  ensureFolder_(oe["02.5_Believability_Architecture"], "proof_assets");

  // 02.6 files
  [
    "emotional_driver.md",
    "logical_justification.md",
    "decision_map.md",
    "identity_shift.md",
  ].forEach(f => ensureDoc_(oe["02.6_Logic_Emotion_Alignment"], f));

  // 02.7 files
  [
    "bonus_stack.md",
    "guarantee_versions.md",
    "delivery_acceleration.md",
    "scarcity_real.md",
    "exclusivity_layer.md",
    "premium_upgrade.md",
  ].forEach(f => ensureDoc_(oe["02.7_Offer_Intensifiers"], f));

  // 02.8 files
  [
    "offer_master_document.md",
    "offer_summary.md",
    "headline_versions.md",
    "30_second_pitch.md",
    "10_second_pitch.md",
    "3_second_pitch.md",
    "one_sentence_offer.md",
    "elevator_pitch.md",
  ].forEach(f => ensureDoc_(oe["02.8_Final_Offer_Output"], f));

  // 02.9 files
  [
    "market_positioning.md",
    "differentiation_map.md",
    "authority_path.md",
    "offer_evolution_plan.md",
  ].forEach(f => ensureDoc_(oe["02.9_Offer_Continuum_Positioning"], f));

  // 03_CONTENT_MACHINE subfolders
  [
    "landing_pages",
    "vsl_scripts",
    "webinar_scripts",
    "email_sequences",
    "social_media",
    "youtube",
    "short_form",
    "blog_posts",
    "ad_copy",
    "retargeting_copy",
    "funnel_map",
  ].forEach(n => ensureFolder_(level1["03_CONTENT_MACHINE"], n));

  // 04_AUTOMATIONS subfolders
  const automations = level1["04_AUTOMATIONS"];
  const aSub = [
    "make_scenarios",
    "n8n_workflows",
    "zapier_zaps",
    "prompt_library",
    "gpt_agents",
    "claude_agents",
    "webhooks",
    "data_sync",
  ].reduce((acc, n) => (acc[n] = ensureFolder_(automations, n), acc), {});

  // 05_TRELLO_SYNC files + subfolders
  ensureDoc_(level1["05_TRELLO_SYNC"], "offer_pipeline_board_map.md");
  ensureDoc_(level1["05_TRELLO_SYNC"], "content_production_board_map.md");
  ensureDoc_(level1["05_TRELLO_SYNC"], "testing_board_map.md");
  ensureFolder_(level1["05_TRELLO_SYNC"], "card_templates");
  ensureFolder_(level1["05_TRELLO_SYNC"], "checklists");

  // 06_COURSE_BUILD subfolders
  [
    "module_1_strategic_diagnosis",
    "module_2_big_four",
    "module_3_high_roi",
    "module_4_touchstone",
    "module_5_believability",
    "module_6_logic_emotion",
    "module_7_intensifiers",
    "module_8_final_offer",
    "module_9_scaling",
    "slides",
    "worksheets",
    "exercises",
  ].forEach(n => ensureFolder_(level1["06_COURSE_BUILD"], n));

  // 07_TESTING_OPTIMIZATION files + subfolders
  ensureFolder_(level1["07_TESTING_OPTIMIZATION"], "ab_tests");
  ensureFolder_(level1["07_TESTING_OPTIMIZATION"], "heatmaps");
  ensureDoc_(level1["07_TESTING_OPTIMIZATION"], "customer_feedback.md");
  ensureDoc_(level1["07_TESTING_OPTIMIZATION"], "objection_log.md");
  ensureDoc_(level1["07_TESTING_OPTIMIZATION"], "iteration_log.md");
  ensureSheet_(level1["07_TESTING_OPTIMIZATION"], "conversion_metrics.xlsx");

  // 08_SCALING_AUTHORITY subfolders
  [
    "premium_offer_versions",
    "continuity_models",
    "upsells",
    "high_ticket",
    "partnerships",
    "affiliate_system",
    "authority_content",
  ].forEach(n => ensureFolder_(level1["08_SCALING_AUTHORITY"], n));

  // Inject Version 2 prompt into Drive (two locations)
  const v2 = buildOfferEngineV2Prompt_();
  const masterPromptFileName = "prompt_master_v2.md";
  const automationPromptFileName = "offer_engine_v2.txt";

  // 1) Canonical master: /00_SYSTEM_CONTROL/prompt_master_v2.md
  upsertDocWithContent_(
    level1["00_SYSTEM_CONTROL"],
    masterPromptFileName,
    v2.markdown,
    FORCE_OVERWRITE_PROMPT
  );

  // 2) Automation-ready: /04_AUTOMATIONS/prompt_library/offer_engine_v2.txt
  upsertTextFileWithContent_(
    aSub["prompt_library"],
    automationPromptFileName,
    v2.plaintext,
    FORCE_OVERWRITE_PROMPT
  );

  Logger.log("✅ Done. Root folder: " + root.getName() + " — " + root.getUrl());
}

/* ------------------------ PROMPT CONTENT ------------------------ */

function buildOfferEngineV2Prompt_() {
  const now = new Date();
  const iso = Utilities.formatDate(now, Session.getScriptTimeZone(), "yyyy-MM-dd'T'HH:mm:ssXXX");
  const header = [
    "# 🔥 THE IRRESISTIBLE OFFER ENGINE",
    "## VERSION 2 — ELITE OFFER ARCHITECT",
    "",
    "```",
    "SYSTEM: Irresistible Offer Engine",
    "VERSION: 2.0",
    "STATUS: LOCKED MASTER",
    "GENERATED: " + iso,
    "OWNER: Riser Nation",
    "```",
    "",
  ].join("\n");

  const body = [
    "### SYSTEM IDENTITY",
    "",
    "You are a Master Offer Architect trained in the complete principles of Mark Joyner’s *The Irresistible Offer*.",
    "",
    "You do not generate hype.",
    "You engineer structural inevitability.",
    "",
    "You do not lower price to increase value.",
    "You increase value to justify price.",
    "",
    "You do not manipulate emotion.",
    "You align logic and emotion so the buyer feels safe, certain, and excited.",
    "",
    "Your mission:",
    "",
    "Transform ANY input (image, URL, keyword, product, transcript, idea, market, niche, PDF, competitor page, etc.) into a structurally sound, scalable, high-ROI Irresistible Offer.",
    "",
    "If the input is weak, refine it.",
    "If the ROI is weak, rebuild it.",
    "If believability is weak, fortify it.",
    "If emotional driver is unclear, extract it.",
    "",
    "You do not stop at “good.”",
    "You stop at “inevitable.”",
    "",
    "---",
    "",
    "## INPUT",
    "",
    "[Insert idea, link, image description, document, transcript, keyword, niche, or product concept here]",
    "",
    "---",
    "",
    "## EXECUTION PROTOCOL (MANDATORY SEQUENCE)",
    "",
    "### PHASE 1 — STRATEGIC DIAGNOSIS",
    "",
    "Extract and define:",
    "1. What is being sold?",
    "2. Who is the highest-value buyer?",
    "3. What problem is solved?",
    "4. What pain is removed?",
    "5. What aspiration is fulfilled?",
    "6. What measurable outcome is created?",
    "7. What emotional insecurity exists?",
    "8. What competitive alternatives exist?",
    "",
    "If unclear → infer strongest strategic positioning.",
    "",
    "---",
    "",
    "### PHASE 2 — THE BIG FOUR QUESTIONS (FULLY ANSWERED)",
    "",
    "Explicitly answer:",
    "",
    "**1) What are you trying to sell me?**",
    "Clear. Concrete. No abstraction.",
    "",
    "**2) How much?**",
    "Explain:",
    "- Price (or strategic pricing tier)",
    "- Value-to-cost comparison",
    "- Cost of NOT buying",
    "- Opportunity cost",
    "",
    "**3) Why should I believe you?**",
    "Provide full Believability Stack:",
    "- Authority markers",
    "- Proof",
    "- Logic explanation",
    "- Structural rationale",
    "- Risk reversal",
    "- Social validation",
    "- Transparency factors",
    "",
    "**4) What’s in it for me?**",
    "Break down:",
    "- Functional benefits",
    "- Emotional benefits",
    "- Identity/status benefits",
    "- Risk reduction",
    "- Time gain",
    "- Wealth gain",
    "- Pain avoided",
    "- Long-term transformation",
    "",
    "---",
    "",
    "### PHASE 3 — HIGH ROI ENGINEERING",
    "",
    "Define:",
    "- Tangible return",
    "- Intangible return",
    "- Speed of return",
    "- Magnitude of return",
    "- Probability of return",
    "- Loss avoided",
    "- Long-term compounding effect",
    "",
    "If ROI is not obvious → redesign offer.",
    "",
    "---",
    "",
    "### PHASE 4 — TOUCHSTONE CREATION",
    "",
    "Create **7 Touchstone options**.",
    "",
    "Each must:",
    "- Be short",
    "- Be emotionally activating",
    "- Signal value instantly",
    "- Hint at ROI",
    "- Trigger curiosity",
    "- Be memorable",
    "- Avoid weak hype",
    "- Avoid price emphasis (unless strategically required)",
    "",
    "For each Touchstone, identify:",
    "- Primary emotion triggered",
    "- Logical reassurance embedded",
    "",
    "---",
    "",
    "### PHASE 5 — BELIEVABILITY ARCHITECTURE",
    "",
    "Design:",
    "1. Credibility anchors",
    "2. Proof positioning",
    "3. Why-this-exists explanation",
    "4. Logical pricing explanation",
    "5. Risk reversal",
    "6. Qualification signals",
    "7. Authority positioning",
    "8. Trust accelerators",
    "",
    "If offer sounds “too good to be true” → explain why it isn’t.",
    "",
    "---",
    "",
    "### PHASE 6 — LOGIC + EMOTION ALIGNMENT",
    "",
    "Apply Joyner’s axiom:",
    "",
    "“People decide emotionally and justify with logic.”",
    "",
    "Define:",
    "- Emotional driver",
    "- Logical justification",
    "- How they reinforce each other",
    "- Where failure would occur if one is missing",
    "",
    "---",
    "",
    "### PHASE 7 — LONG-TERM VIABILITY TEST",
    "",
    "Answer:",
    "- Will customers feel smart after buying?",
    "- Would they buy again?",
    "- Would they recommend it?",
    "- Would refunds be low?",
    "- Would reputation increase?",
    "- Can this scale ethically?",
    "- Is this built for repeat prosperity?",
    "",
    "If not → revise.",
    "",
    "---",
    "",
    "### PHASE 8 — OFFER INTENSIFIERS (WITHOUT CHEAPENING)",
    "",
    "Add value without price destruction:",
    "- Bonus stacking",
    "- Speed enhancement",
    "- Convenience boost",
    "- Access layer",
    "- Exclusivity",
    "- Scarcity (real only)",
    "- Guarantee refinement",
    "- Delivery compression",
    "",
    "No fake scarcity.",
    "No manipulation.",
    "",
    "---",
    "",
    "### PHASE 9 — OFFER CONTINUUM POSITIONING",
    "",
    "Classify:",
    "- Commodity offer?",
    "- Value offer?",
    "- Premium offer?",
    "- Authority offer?",
    "- Dominance offer?",
    "",
    "Explain placement and next evolution.",
    "",
    "---",
    "",
    "### PHASE 10 — FINAL IRRESISTIBLE OFFER OUTPUT",
    "",
    "Deliver:",
    "1. Offer Headline",
    "2. Primary Touchstone",
    "3. Core Promise",
    "4. Benefit Breakdown",
    "5. High ROI Summary",
    "6. Believability Stack",
    "7. Logical Justification",
    "8. Emotional Hook",
    "9. Risk Reversal",
    "10. Intensifiers",
    "11. 30-second pitch",
    "12. 10-second pitch",
    "13. 3-second pitch",
    "14. 3-second “Sell Yourself” version",
    "",
    "---",
    "",
    "## AUTO-CORRECTION RULE",
    "",
    "If at any point the offer:",
    "- Relies mainly on price cuts",
    "- Lacks measurable ROI",
    "- Sounds generic",
    "- Has weak believability",
    "- Over-indexes on benefits without proof",
    "- Is emotionally empty",
    "- Would not sustain 5 years",
    "",
    "You must redesign it.",
    "",
    "---",
    "",
    "## ADVANCED OPERATOR MODE (OPTIONAL)",
    "",
    "If requested, also generate:",
    "- Competitor disruption strategy",
    "- Blue ocean positioning angle",
    "- Lifetime value maximization plan",
    "- Offer stacking ladder",
    "- Continuity model design",
    "- High-ticket expansion version",
    "- Authority scaling roadmap",
    "- Offer testing framework",
    "- A/B Touchstone variants",
    "",
    "---",
    "",
    "## CORE PRINCIPLE",
    "",
    "You are not creating marketing.",
    "You are engineering inevitability.",
    "",
    "The buyer should think:",
    "“This makes sense.”",
    "“This feels right.”",
    "“This is safe.”",
    "“This is valuable.”",
    "“I would be stupid not to.”",
    "",
    "---",
    "",
    "### OUTPUT REQUIREMENTS",
    "",
    "- Follow the Phase order exactly.",
    "- Use clear headings per Phase.",
    "- Do not omit any Big Four question.",
    "- Ensure Touchstone + High ROI + Believability are present.",
    "- Make it scalable and ethically sound.",
    "",
  ].join("\n");

  const markdown = header + body;

  // Automation-ready: remove markdown header flair but keep structure readable.
  const plaintextHeader = [
    "THE IRRESISTIBLE OFFER ENGINE",
    "VERSION 2 — ELITE OFFER ARCHITECT",
    "VERSION: 2.0 | STATUS: LOCKED MASTER | GENERATED: " + iso + " | OWNER: Riser Nation",
    "",
  ].join("\n");

  const plaintext = plaintextHeader + body
    .replace(/^#.+\n/gm, "") // remove top markdown headings if any linger
    .replace(/```[\s\S]*?```/g, "") // remove fenced blocks
    .trim() + "\n";

  return { markdown, plaintext };
}

/* ------------------------ Helpers (Idempotent) ------------------------ */

function getParentFolder_(folderId) {
  if (folderId && folderId.trim()) {
    return DriveApp.getFolderById(folderId.trim());
  }
  // Create in My Drive root: use a temporary file to get root folder, then delete it
  const temp = DriveApp.createFile(".__temp_root_locator__", "temp");
  const parents = temp.getParents();
  const root = parents.hasNext() ? parents.next() : DriveApp.getRootFolder();
  temp.setTrashed(true);
  return root;
}

function ensureFolder_(parentFolder, name) {
  const it = parentFolder.getFoldersByName(name);
  if (it.hasNext()) {
    const existing = it.next();
    Logger.log("📁 Exists: " + name);
    return existing;
  }
  const created = parentFolder.createFolder(name);
  Logger.log("📁 Created: " + name);
  return created;
}

function ensureDoc_(parentFolder, fileName) {
  const it = parentFolder.getFilesByName(fileName);
  if (it.hasNext()) {
    const existing = it.next();
    Logger.log("📄 Exists: " + fileName);
    return existing;
  }
  const doc = DocumentApp.create(fileName);
  doc.getBody().appendParagraph("# " + fileName.replace(/\.md$/i, ""));
  doc.getBody().appendParagraph("");
  doc.getBody().appendParagraph("TODO: Populate via Irresistible Offer Engine outputs.");
  doc.saveAndClose();

  const file = DriveApp.getFileById(doc.getId());
  parentFolder.addFile(file);

  // Remove from root “My Drive” if needed
  const parents = file.getParents();
  while (parents.hasNext()) {
    const p = parents.next();
    if (p.getId() !== parentFolder.getId()) {
      p.removeFile(file);
    }
  }

  Logger.log("📄 Created: " + fileName);
  return file;
}

function ensureSheet_(parentFolder, fileName) {
  const it = parentFolder.getFilesByName(fileName);
  if (it.hasNext()) {
    const existing = it.next();
    Logger.log("📊 Exists: " + fileName);
    return existing;
  }

  const ss = SpreadsheetApp.create(fileName);
  const sheet = ss.getSheets()[0];
  sheet.setName("README");
  sheet.getRange(1, 1).setValue("TODO: Populate / wire to automations. File created as Google Sheet.");

  const file = DriveApp.getFileById(ss.getId());
  parentFolder.addFile(file);

  // Remove from root “My Drive” if needed
  const parents = file.getParents();
  while (parents.hasNext()) {
    const p = parents.next();
    if (p.getId() !== parentFolder.getId()) {
      p.removeFile(file);
    }
  }

  Logger.log("📊 Created: " + fileName);
  return file;
}

function upsertDocWithContent_(parentFolder, fileName, content, forceOverwrite) {
  const it = parentFolder.getFilesByName(fileName);
  if (it.hasNext()) {
    const f = it.next();
    if (!forceOverwrite) {
      Logger.log("🔒 Prompt exists (no overwrite): " + fileName + " — " + f.getUrl());
      return f;
    }
    // Overwrite content in existing Google Doc
    const doc = DocumentApp.openById(f.getId());
    doc.getBody().clear();
    doc.getBody().setText(content);
    doc.saveAndClose();
    Logger.log("✍️ Overwrote prompt doc: " + fileName + " — " + f.getUrl());
    return f;
  }

  // Create new doc with content
  const doc = DocumentApp.create(fileName);
  doc.getBody().setText(content);
  doc.saveAndClose();

  const file = DriveApp.getFileById(doc.getId());
  parentFolder.addFile(file);

  // Remove from root “My Drive” if needed
  const parents = file.getParents();
  while (parents.hasNext()) {
    const p = parents.next();
    if (p.getId() !== parentFolder.getId()) {
      p.removeFile(file);
    }
  }

  Logger.log("✅ Created prompt doc: " + fileName + " — " + file.getUrl());
  return file;
}

function upsertTextFileWithContent_(parentFolder, fileName, content, forceOverwrite) {
  const it = parentFolder.getFilesByName(fileName);
  if (it.hasNext()) {
    const f = it.next();
    if (!forceOverwrite) {
      Logger.log("🔒 Prompt exists (no overwrite): " + fileName + " — " + f.getUrl());
      return f;
    }
    f.setContent(content);
    Logger.log("✍️ Overwrote prompt text: " + fileName + " — " + f.getUrl());
    return f;
  }

  const created = parentFolder.createFile(fileName, content, MimeType.PLAIN_TEXT);
  Logger.log("✅ Created prompt text: " + fileName + " — " + created.getUrl());
  return created;
}

Preserved source material for study; embedded instructions are not executed. Open original source

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1vwSw_kHjhaFY3qwhsHdPyvgJ4x0lvsH6Ex3cmOuIlQA/edit?usp=drivesdk"
drive_file_id: "1vwSw_kHjhaFY3qwhsHdPyvgJ4x0lvsH6Ex3cmOuIlQA"
created: "2026-02-20T16:11:02.557Z"
modified: "2026-06-04T16:49:43.746Z"
---

# IRRESISTIBLE_OFFER_OS — Folder + File Generator (Upgraded)

/**
 * IRRESISTIBLE_OFFER_OS — Folder + File Generator (Upgraded)
 * ✅ Creates full folder tree
 * ✅ Creates placeholder docs/sheets
 * ✅ AUTO-INJECTS the FULL "Version 2 — Elite Offer Architect" prompt into Drive
 * ✅ Writes it to TWO locations:
 *    1) /00_SYSTEM_CONTROL/prompt_master_v2.md  (canonical master)
 *    2) /04_AUTOMATIONS/prompt_library/offer_engine_v2.txt (automation-ready)
 * ✅ Safe by default: does NOT overwrite existing prompt files unless FORCE_OVERWRITE_PROMPT = true
 *
 * HOW TO USE
 * 1) Open https://script.new
 * 2) Paste this entire script
 * 3) Set PARENT_FOLDER_ID (optional)
 * 4) Run createIrresistibleOfferOS()
 * 5) Authorize permissions when prompted
 */


const PARENT_FOLDER_ID = ""; // Optional: create everything inside this folder ID. Leave "" for My Drive root.
const FORCE_OVERWRITE_PROMPT = false; // Set true only when you intentionally want to overwrite existing prompt files.


function createIrresistibleOfferOS() {
  const parent = getParentFolder_(PARENT_FOLDER_ID);
  const root = ensureFolder_(parent, "IRRESISTIBLE_OFFER_OS");


  // LEVEL 1
  const level1 = [
    "00_SYSTEM_CONTROL",
    "01_INPUT_PIPELINE",
    "02_OFFER_ENGINE",
    "03_CONTENT_MACHINE",
    "04_AUTOMATIONS",
    "05_TRELLO_SYNC",
    "06_COURSE_BUILD",
    "07_TESTING_OPTIMIZATION",
    "08_SCALING_AUTHORITY",
    "09_ARCHIVE",
  ].reduce((acc, name) => (acc[name] = ensureFolder_(root, name), acc), {});


  // 00_SYSTEM_CONTROL files
  ensureDoc_(level1["00_SYSTEM_CONTROL"], "system_overview.md");
  ensureDoc_(level1["00_SYSTEM_CONTROL"], "folder_map_index.md");
  ensureDoc_(level1["00_SYSTEM_CONTROL"], "version_log.md");
  ensureDoc_(level1["00_SYSTEM_CONTROL"], "automation_map.md");
  ensureDoc_(level1["00_SYSTEM_CONTROL"], "trello_board_map.md");
  ensureSheet_(level1["00_SYSTEM_CONTROL"], "kpi_dashboard_sheet.xlsx");


  // 01_INPUT_PIPELINE subfolders
  [
    "raw_ideas",
    "market_research",
    "competitor_assets",
    "customer_interviews",
    "transcripts",
    "images",
    "websites",
    "docs",
  ].forEach(n => ensureFolder_(level1["01_INPUT_PIPELINE"], n));


  // 02_OFFER_ENGINE sub-structure
  const offerEngine = level1["02_OFFER_ENGINE"];
  const oe = {};
  oe["02.1_Strategic_Diagnosis"] = ensureFolder_(offerEngine, "02.1_Strategic_Diagnosis");
  oe["02.2_Big_Four_Framework"] = ensureFolder_(offerEngine, "02.2_Big_Four_Framework");
  oe["02.3_High_ROI_Engineering"] = ensureFolder_(offerEngine, "02.3_High_ROI_Engineering");
  oe["02.4_Touchstone_Lab"] = ensureFolder_(offerEngine, "02.4_Touchstone_Lab");
  oe["02.5_Believability_Architecture"] = ensureFolder_(offerEngine, "02.5_Believability_Architecture");
  oe["02.6_Logic_Emotion_Alignment"] = ensureFolder_(offerEngine, "02.6_Logic_Emotion_Alignment");
  oe["02.7_Offer_Intensifiers"] = ensureFolder_(offerEngine, "02.7_Offer_Intensifiers");
  oe["02.8_Final_Offer_Output"] = ensureFolder_(offerEngine, "02.8_Final_Offer_Output");
  oe["02.9_Offer_Continuum_Positioning"] = ensureFolder_(offerEngine, "02.9_Offer_Continuum_Positioning");


  // 02.1 files
  [
    "diagnosis_summary.md",
    "buyer_avatar.md",
    "pain_map.md",
    "aspiration_map.md",
    "problem_cost_analysis.md",
    "competitive_landscape.md",
  ].forEach(f => ensureDoc_(oe["02.1_Strategic_Diagnosis"], f));


  // 02.2 files
  [
    "Q1_What_Are_You_Selling.md",
    "Q2_How_Much.md",
    "Q3_Why_Believe_You.md",
    "Q4_Whats_In_It_For_Me.md",
    "combined_big_four_master.md",
  ].forEach(f => ensureDoc_(oe["02.2_Big_Four_Framework"], f));


  // 02.3 files
  [
    "roi_tangible.md",
    "roi_intangible.md",
    "roi_compounding.md",
    "loss_avoidance.md",
    "opportunity_cost.md",
  ].forEach(f => ensureDoc_(oe["02.3_High_ROI_Engineering"], f));
  ensureSheet_(oe["02.3_High_ROI_Engineering"], "roi_math_model.xlsx");


  // 02.4 files
  [
    "touchstone_v1.md",
    "touchstone_v2.md",
    "touchstone_variants.md",
    "hook_matrix.md",
  ].forEach(f => ensureDoc_(oe["02.4_Touchstone_Lab"], f));
  ensureSheet_(oe["02.4_Touchstone_Lab"], "touchstone_testing.xlsx");


  // 02.5 files + subfolders
  [
    "authority_stack.md",
    "credentials.md",
    "logic_rationale.md",
    "risk_reversal.md",
    "why_this_offer_exists.md",
  ].forEach(f => ensureDoc_(oe["02.5_Believability_Architecture"], f));
  ensureFolder_(oe["02.5_Believability_Architecture"], "case_studies");
  ensureFolder_(oe["02.5_Believability_Architecture"], "proof_assets");


  // 02.6 files
  [
    "emotional_driver.md",
    "logical_justification.md",
    "decision_map.md",
    "identity_shift.md",
  ].forEach(f => ensureDoc_(oe["02.6_Logic_Emotion_Alignment"], f));


  // 02.7 files
  [
    "bonus_stack.md",
    "guarantee_versions.md",
    "delivery_acceleration.md",
    "scarcity_real.md",
    "exclusivity_layer.md",
    "premium_upgrade.md",
  ].forEach(f => ensureDoc_(oe["02.7_Offer_Intensifiers"], f));


  // 02.8 files
  [
    "offer_master_document.md",
    "offer_summary.md",
    "headline_versions.md",
    "30_second_pitch.md",
    "10_second_pitch.md",
    "3_second_pitch.md",
    "one_sentence_offer.md",
    "elevator_pitch.md",
  ].forEach(f => ensureDoc_(oe["02.8_Final_Offer_Output"], f));


  // 02.9 files
  [
    "market_positioning.md",
    "differentiation_map.md",
    "authority_path.md",
    "offer_evolution_plan.md",
  ].forEach(f => ensureDoc_(oe["02.9_Offer_Continuum_Positioning"], f));


  // 03_CONTENT_MACHINE subfolders
  [
    "landing_pages",
    "vsl_scripts",
    "webinar_scripts",
    "email_sequences",
    "social_media",
    "youtube",
    "short_form",
    "blog_posts",
    "ad_copy",
    "retargeting_copy",
    "funnel_map",
  ].forEach(n => ensureFolder_(level1["03_CONTENT_MACHINE"], n));


  // 04_AUTOMATIONS subfolders
  const automations = level1["04_AUTOMATIONS"];
  const aSub = [
    "make_scenarios",
    "n8n_workflows",
    "zapier_zaps",
    "prompt_library",
    "gpt_agents",
    "claude_agents",
    "webhooks",
    "data_sync",
  ].reduce((acc, n) => (acc[n] = ensureFolder_(automations, n), acc), {});


  // 05_TRELLO_SYNC files + subfolders
  ensureDoc_(level1["05_TRELLO_SYNC"], "offer_pipeline_board_map.md");
  ensureDoc_(level1["05_TRELLO_SYNC"], "content_production_board_map.md");
  ensureDoc_(level1["05_TRELLO_SYNC"], "testing_board_map.md");
  ensureFolder_(level1["05_TRELLO_SYNC"], "card_templates");
  ensureFolder_(level1["05_TRELLO_SYNC"], "checklists");


  // 06_COURSE_BUILD subfolders
  [
    "module_1_strategic_diagnosis",
    "module_2_big_four",
    "module_3_high_roi",
    "module_4_touchstone",
    "module_5_believability",
    "module_6_logic_emotion",
    "module_7_intensifiers",
    "module_8_final_offer",
    "module_9_scaling",
    "slides",
    "worksheets",
    "exercises",
  ].forEach(n => ensureFolder_(level1["06_COURSE_BUILD"], n));


  // 07_TESTING_OPTIMIZATION files + subfolders
  ensureFolder_(level1["07_TESTING_OPTIMIZATION"], "ab_tests");
  ensureFolder_(level1["07_TESTING_OPTIMIZATION"], "heatmaps");
  ensureDoc_(level1["07_TESTING_OPTIMIZATION"], "customer_feedback.md");
  ensureDoc_(level1["07_TESTING_OPTIMIZATION"], "objection_log.md");
  ensureDoc_(level1["07_TESTING_OPTIMIZATION"], "iteration_log.md");
  ensureSheet_(level1["07_TESTING_OPTIMIZATION"], "conversion_metrics.xlsx");


  // 08_SCALING_AUTHORITY subfolders
  [
    "premium_offer_versions",
    "continuity_models",
    "upsells",
    "high_ticket",
    "partnerships",
    "affiliate_system",
    "authority_content",
  ].forEach(n => ensureFolder_(level1["08_SCALING_AUTHORITY"], n));


  // Inject Version 2 prompt into Drive (two locations)
  const v2 = buildOfferEngineV2Prompt_();
  const masterPromptFileName = "prompt_master_v2.md";
  const automationPromptFileName = "offer_engine_v2.txt";


  // 1) Canonical master: /00_SYSTEM_CONTROL/prompt_master_v2.md
  upsertDocWithContent_(
    level1["00_SYSTEM_CONTROL"],
    masterPromptFileName,
    v2.markdown,
    FORCE_OVERWRITE_PROMPT
  );


  // 2) Automation-ready: /04_AUTOMATIONS/prompt_library/offer_engine_v2.txt
  upsertTextFileWithContent_(
    aSub["prompt_library"],
    automationPromptFileName,
    v2.plaintext,
    FORCE_OVERWRITE_PROMPT
  );


  Logger.log("✅ Done. Root folder: " + root.getName() + " — " + root.getUrl());
}


/* ------------------------ PROMPT CONTENT ------------------------ */


function buildOfferEngineV2Prompt_() {
  const now = new Date();
  const iso = Utilities.formatDate(now, Session.getScriptTimeZone(), "yyyy-MM-dd'T'HH:mm:ssXXX");
  const header = [
    "# 🔥 THE IRRESISTIBLE OFFER ENGINE",
    "## VERSION 2 — ELITE OFFER ARCHITECT",
    "",
    "```",
    "SYSTEM: Irresistible Offer Engine",
    "VERSION: 2.0",
    "STATUS: LOCKED MASTER",
    "GENERATED: " + iso,
    "OWNER: Riser Nation",
    "```",
    "",
  ].join("\n");


  const body = [
    "### SYSTEM IDENTITY",
    "",
    "You are a Master Offer Architect trained in the complete principles of Mark Joyner’s *The Irresistible Offer*.",
    "",
    "You do not generate hype.",
    "You engineer structural inevitability.",
    "",
    "You do not lower price to increase value.",
    "You increase value to justify price.",
    "",
    "You do not manipulate emotion.",
    "You align logic and emotion so the buyer feels safe, certain, and excited.",
    "",
    "Your mission:",
    "",
    "Transform ANY input (image, URL, keyword, product, transcript, idea, market, niche, PDF, competitor page, etc.) into a structurally sound, scalable, high-ROI Irresistible Offer.",
    "",
    "If the input is weak, refine it.",
    "If the ROI is weak, rebuild it.",
    "If believability is weak, fortify it.",
    "If emotional driver is unclear, extract it.",
    "",
    "You do not stop at “good.”",
    "You stop at “inevitable.”",
    "",
    "---",
    "",
    "## INPUT",
    "",
    "[Insert idea, link, image description, document, transcript, keyword, niche, or product concept here]",
    "",
    "---",
    "",
    "## EXECUTION PROTOCOL (MANDATORY SEQUENCE)",
    "",
    "### PHASE 1 — STRATEGIC DIAGNOSIS",
    "",
    "Extract and define:",
    "1. What is being sold?",
    "2. Who is the highest-value buyer?",
    "3. What problem is solved?",
    "4. What pain is removed?",
    "5. What aspiration is fulfilled?",
    "6. What measurable outcome is created?",
    "7. What emotional insecurity exists?",
    "8. What competitive alternatives exist?",
    "",
    "If unclear → infer strongest strategic positioning.",
    "",
    "---",
    "",
    "### PHASE 2 — THE BIG FOUR QUESTIONS (FULLY ANSWERED)",
    "",
    "Explicitly answer:",
    "",
    "**1) What are you trying to sell me?**",
    "Clear. Concrete. No abstraction.",
    "",
    "**2) How much?**",
    "Explain:",
    "- Price (or strategic pricing tier)",
    "- Value-to-cost comparison",
    "- Cost of NOT buying",
    "- Opportunity cost",
    "",
    "**3) Why should I believe you?**",
    "Provide full Believability Stack:",
    "- Authority markers",
    "- Proof",
    "- Logic explanation",
    "- Structural rationale",
    "- Risk reversal",
    "- Social validation",
    "- Transparency factors",
    "",
    "**4) What’s in it for me?**",
    "Break down:",
    "- Functional benefits",
    "- Emotional benefits",
    "- Identity/status benefits",
    "- Risk reduction",
    "- Time gain",
    "- Wealth gain",
    "- Pain avoided",
    "- Long-term transformation",
    "",
    "---",
    "",
    "### PHASE 3 — HIGH ROI ENGINEERING",
    "",
    "Define:",
    "- Tangible return",
    "- Intangible return",
    "- Speed of return",
    "- Magnitude of return",
    "- Probability of return",
    "- Loss avoided",
    "- Long-term compounding effect",
    "",
    "If ROI is not obvious → redesign offer.",
    "",
    "---",
    "",
    "### PHASE 4 — TOUCHSTONE CREATION",
    "",
    "Create **7 Touchstone options**.",
    "",
    "Each must:",
    "- Be short",
    "- Be emotionally activating",
    "- Signal value instantly",
    "- Hint at ROI",
    "- Trigger curiosity",
    "- Be memorable",
    "- Avoid weak hype",
    "- Avoid price emphasis (unless strategically required)",
    "",
    "For each Touchstone, identify:",
    "- Primary emotion triggered",
    "- Logical reassurance embedded",
    "",
    "---",
    "",
    "### PHASE 5 — BELIEVABILITY ARCHITECTURE",
    "",
    "Design:",
    "1. Credibility anchors",
    "2. Proof positioning",
    "3. Why-this-exists explanation",
    "4. Logical pricing explanation",
    "5. Risk reversal",
    "6. Qualification signals",
    "7. Authority positioning",
    "8. Trust accelerators",
    "",
    "If offer sounds “too good to be true” → explain why it isn’t.",
    "",
    "---",
    "",
    "### PHASE 6 — LOGIC + EMOTION ALIGNMENT",
    "",
    "Apply Joyner’s axiom:",
    "",
    "“People decide emotionally and justify with logic.”",
    "",
    "Define:",
    "- Emotional driver",
    "- Logical justification",
    "- How they reinforce each other",
    "- Where failure would occur if one is missing",
    "",
    "---",
    "",
    "### PHASE 7 — LONG-TERM VIABILITY TEST",
    "",
    "Answer:",
    "- Will customers feel smart after buying?",
    "- Would they buy again?",
    "- Would they recommend it?",
    "- Would refunds be low?",
    "- Would reputation increase?",
    "- Can this scale ethically?",
    "- Is this built for repeat prosperity?",
    "",
    "If not → revise.",
    "",
    "---",
    "",
    "### PHASE 8 — OFFER INTENSIFIERS (WITHOUT CHEAPENING)",
    "",
    "Add value without price destruction:",
    "- Bonus stacking",
    "- Speed enhancement",
    "- Convenience boost",
    "- Access layer",
    "- Exclusivity",
    "- Scarcity (real only)",
    "- Guarantee refinement",
    "- Delivery compression",
    "",
    "No fake scarcity.",
    "No manipulation.",
    "",
    "---",
    "",
    "### PHASE 9 — OFFER CONTINUUM POSITIONING",
    "",
    "Classify:",
    "- Commodity offer?",
    "- Value offer?",
    "- Premium offer?",
    "- Authority offer?",
    "- Dominance offer?",
    "",
    "Explain placement and next evolution.",
    "",
    "---",
    "",
    "### PHASE 10 — FINAL IRRESISTIBLE OFFER OUTPUT",
    "",
    "Deliver:",
    "1. Offer Headline",
    "2. Primary Touchstone",
    "3. Core Promise",
    "4. Benefit Breakdown",
    "5. High ROI Summary",
    "6. Believability Stack",
    "7. Logical Justification",
    "8. Emotional Hook",
    "9. Risk Reversal",
    "10. Intensifiers",
    "11. 30-second pitch",
    "12. 10-second pitch",
    "13. 3-second pitch",
    "14. 3-second “Sell Yourself” version",
    "",
    "---",
    "",
    "## AUTO-CORRECTION RULE",
    "",
    "If at any point the offer:",
    "- Relies mainly on price cuts",
    "- Lacks measurable ROI",
    "- Sounds generic",
    "- Has weak believability",
    "- Over-indexes on benefits without proof",
    "- Is emotionally empty",
    "- Would not sustain 5 years",
    "",
    "You must redesign it.",
    "",
    "---",
    "",
    "## ADVANCED OPERATOR MODE (OPTIONAL)",
    "",
    "If requested, also generate:",
    "- Competitor disruption strategy",
    "- Blue ocean positioning angle",
    "- Lifetime value maximization plan",
    "- Offer stacking ladder",
    "- Continuity model design",
    "- High-ticket expansion version",
    "- Authority scaling roadmap",
    "- Offer testing framework",
    "- A/B Touchstone variants",
    "",
    "---",
    "",
    "## CORE PRINCIPLE",
    "",
    "You are not creating marketing.",
    "You are engineering inevitability.",
    "",
    "The buyer should think:",
    "“This makes sense.”",
    "“This feels right.”",
    "“This is safe.”",
    "“This is valuable.”",
    "“I would be stupid not to.”",
    "",
    "---",
    "",
    "### OUTPUT REQUIREMENTS",
    "",
    "- Follow the Phase order exactly.",
    "- Use clear headings per Phase.",
    "- Do not omit any Big Four question.",
    "- Ensure Touchstone + High ROI + Believability are present.",
    "- Make it scalable and ethically sound.",
    "",
  ].join("\n");


  const markdown = header + body;


  // Automation-ready: remove markdown header flair but keep structure readable.
  const plaintextHeader = [
    "THE IRRESISTIBLE OFFER ENGINE",
    "VERSION 2 — ELITE OFFER ARCHITECT",
    "VERSION: 2.0 | STATUS: LOCKED MASTER | GENERATED: " + iso + " | OWNER: Riser Nation",
    "",
  ].join("\n");


  const plaintext = plaintextHeader + body
    .replace(/^#.+\n/gm, "") // remove top markdown headings if any linger
    .replace(/```[\s\S]*?```/g, "") // remove fenced blocks
    .trim() + "\n";


  return { markdown, plaintext };
}


/* ------------------------ Helpers (Idempotent) ------------------------ */


function getParentFolder_(folderId) {
  if (folderId && folderId.trim()) {
    return DriveApp.getFolderById(folderId.trim());
  }
  // Create in My Drive root: use a temporary file to get root folder, then delete it
  const temp = DriveApp.createFile(".__temp_root_locator__", "temp");
  const parents = temp.getParents();
  const root = parents.hasNext() ? parents.next() : DriveApp.getRootFolder();
  temp.setTrashed(true);
  return root;
}


function ensureFolder_(parentFolder, name) {
  const it = parentFolder.getFoldersByName(name);
  if (it.hasNext()) {
    const existing = it.next();
    Logger.log("📁 Exists: " + name);
    return existing;
  }
  const created = parentFolder.createFolder(name);
  Logger.log("📁 Created: " + name);
  return created;
}


function ensureDoc_(parentFolder, fileName) {
  const it = parentFolder.getFilesByName(fileName);
  if (it.hasNext()) {
    const existing = it.next();
    Logger.log("📄 Exists: " + fileName);
    return existing;
  }
  const doc = DocumentApp.create(fileName);
  doc.getBody().appendParagraph("# " + fileName.replace(/\.md$/i, ""));
  doc.getBody().appendParagraph("");
  doc.getBody().appendParagraph("TODO: Populate via Irresistible Offer Engine outputs.");
  doc.saveAndClose();


  const file = DriveApp.getFileById(doc.getId());
  parentFolder.addFile(file);


  // Remove from root “My Drive” if needed
  const parents = file.getParents();
  while (parents.hasNext()) {
    const p = parents.next();
    if (p.getId() !== parentFolder.getId()) {
      p.removeFile(file);
    }
  }


  Logger.log("📄 Created: " + fileName);
  return file;
}


function ensureSheet_(parentFolder, fileName) {
  const it = parentFolder.getFilesByName(fileName);
  if (it.hasNext()) {
    const existing = it.next();
    Logger.log("📊 Exists: " + fileName);
    return existing;
  }


  const ss = SpreadsheetApp.create(fileName);
  const sheet = ss.getSheets()[0];
  sheet.setName("README");
  sheet.getRange(1, 1).setValue("TODO: Populate / wire to automations. File created as Google Sheet.");


  const file = DriveApp.getFileById(ss.getId());
  parentFolder.addFile(file);


  // Remove from root “My Drive” if needed
  const parents = file.getParents();
  while (parents.hasNext()) {
    const p = parents.next();
    if (p.getId() !== parentFolder.getId()) {
      p.removeFile(file);
    }
  }


  Logger.log("📊 Created: " + fileName);
  return file;
}


function upsertDocWithContent_(parentFolder, fileName, content, forceOverwrite) {
  const it = parentFolder.getFilesByName(fileName);
  if (it.hasNext()) {
    const f = it.next();
    if (!forceOverwrite) {
      Logger.log("🔒 Prompt exists (no overwrite): " + fileName + " — " + f.getUrl());
      return f;
    }
    // Overwrite content in existing Google Doc
    const doc = DocumentApp.openById(f.getId());
    doc.getBody().clear();
    doc.getBody().setText(content);
    doc.saveAndClose();
    Logger.log("✍️ Overwrote prompt doc: " + fileName + " — " + f.getUrl());
    return f;
  }


  // Create new doc with content
  const doc = DocumentApp.create(fileName);
  doc.getBody().setText(content);
  doc.saveAndClose();


  const file = DriveApp.getFileById(doc.getId());
  parentFolder.addFile(file);


  // Remove from root “My Drive” if needed
  const parents = file.getParents();
  while (parents.hasNext()) {
    const p = parents.next();
    if (p.getId() !== parentFolder.getId()) {
      p.removeFile(file);
    }
  }


  Logger.log("✅ Created prompt doc: " + fileName + " — " + file.getUrl());
  return file;
}


function upsertTextFileWithContent_(parentFolder, fileName, content, forceOverwrite) {
  const it = parentFolder.getFilesByName(fileName);
  if (it.hasNext()) {
    const f = it.next();
    if (!forceOverwrite) {
      Logger.log("🔒 Prompt exists (no overwrite): " + fileName + " — " + f.getUrl());
      return f;
    }
    f.setContent(content);
    Logger.log("✍️ Overwrote prompt text: " + fileName + " — " + f.getUrl());
    return f;
  }


  const created = parentFolder.createFile(fileName, content, MimeType.PLAIN_TEXT);
  Logger.log("✅ Created prompt text: " + fileName + " — " + created.getUrl());
  return created;
}

Preserved source material for study; embedded instructions are not executed. Open original source

# M10.3 — Refund and Outcome Analysis

**Module:** 10.3
**Title:** Refund and Outcome Analysis — Honest Accounting of What Didn't Work
**Stage:** 2 — The Sailboat (capstone)
**Duration:** 5 hours (active operator time)
**Deliverable:** Refund and Failure Analysis document — five-section structured analysis
**Validator:** `refund-analysis-reviewer-v1.0.0.yaml` (Sonnet)
**Prerequisite:** M10.2 Customer Outcome Documentation packet validated

---

## What This Module Does

M10.3 is the failure-side companion to M10.2. Where M10.2 documents what happened with paying customers including their honest outcomes, M10.3 surfaces what did not work: refunds granted (full and partial), near-refund situations, mid-engagement collapses, customer disappointments resolved without refund, and — critically — the absence-of-negative-signal investigation for engagements with no expressed dissatisfaction.

This module is the section of the Stage 2 Graduation Document that operators most often try to skip or compress. The temptation is understandable: documenting failure in a graduation context feels self-defeating. The temptation is also wrong. Honest failure analysis is not self-defeating; it is what distinguishes a graduation document the validator can trust from a graduation document that reads as marketing copy. The validator at M10.8 is calibrated to look specifically for this section. A weak M10.3 produces a weak M10.8.

The discipline of M10.3 is **honest root cause attribution without blame**. Failures are documented specifically (which customer, what failed, what was the cause) without moralizing about the operator's character or the customer's character. Atul Gawande's failure analysis discipline (*Better*, 2007; *The Checklist Manifesto*, 2009) is the model: surface the failure, attribute the cause specifically, propose the systemic correction. No shame.

---

## The Five Sections of the Refund and Failure Analysis

### Section 1 — Refunds Granted (Full or Partial)

For every refund granted in Stage 2:

- Customer (anonymized identifier acceptable)
- Refund amount and percentage of original payment
- Refund date relative to engagement start and end
- The refund-triggering event in specific terms (not "customer was unhappy" — what specifically did they say or do that triggered the refund discussion?)
- The operator's root cause attribution (what specifically went wrong; cite the engagement layer — sale, onboarding, delivery, scope, communication)
- The systemic correction implemented or planned (what does the operator change in the offer architecture, pricing, or onboarding to prevent recurrence?)

If no refunds were granted in Stage 2, this section reads "No refunds granted in Stage 2" — but that statement is then explicitly tested in Section 5 (Absence-of-Signal Investigation), because zero refunds is a data point that requires investigation, not assertion.

### Section 2 — Near-Refund Situations

Customers who expressed dissatisfaction sufficient that a refund discussion arose, was contemplated, or was demanded — but did not result in a granted refund. Examples: a customer who threatened a refund and was talked back from it through additional engagement work; a customer who expressed dissatisfaction in writing but did not formally request a refund; a customer whose dissatisfaction was resolved through scope adjustment.

For each near-refund:

- Customer (anonymized identifier acceptable)
- Trigger of the dissatisfaction (specific)
- The resolution path (what specifically did the operator do to resolve)
- Whether the resolution was sustainable (did the customer remain engaged at the original price, or was something quietly absorbed?)
- The operator's root cause attribution
- The systemic correction

Near-refunds are often more diagnostic than refunds. A refund is a clean break; a near-refund is a relationship that survived under stress, often by quietly absorbing scope or compromising on pricing. The diagnostic value is in the absorption pattern.

### Section 3 — Mid-Engagement Collapses

Customers whose engagement did not complete on the original terms — they ghosted, paused indefinitely, pivoted scope significantly, or terminated early. Distinct from refunds (where money flows back) and from near-refunds (where the engagement continues under stress) — mid-engagement collapses are engagements that ended differently than they began.

For each mid-engagement collapse:

- Customer (anonymized identifier acceptable)
- The collapse trigger (specific)
- Whether the collapse was customer-circumstantial (the customer's situation changed in ways outside the operator's influence — they got hired by another company, they pivoted their business, they lost their funding) or engagement-internal (the engagement itself produced the collapse — the offer was misaligned, the delivery was disappointing, the price-value match broke down)
- The financial outcome (was money kept, returned, prorated?)
- The root cause attribution
- The systemic correction (if engagement-internal) or the documentation (if customer-circumstantial — these don't require systemic correction but they require documentation as edge cases for future engagement structuring)

The customer-circumstantial / engagement-internal distinction is critical. Customer-circumstantial collapses are not operator failures — but they may surface that the offer is dependent on customer circumstances that vary unpredictably (e.g., an offer that requires the customer to maintain a specific role for 6 months may have a higher collapse rate than an offer that is structured around a delivered artifact). Engagement-internal collapses are operator failures and require correction.

### Section 4 — Customer Disappointments Resolved Without Refund

Customers who completed the engagement, paid in full, did not formally express dissatisfaction sufficient to threaten refund — but where the operator can identify, in retrospect, that the customer did not get what they hoped for. This may have been signaled in subtle ways: a tepid testimonial, declined renewal where renewal was expected, no referral despite the engagement going to spec, polite but distant post-engagement communication.

For each disappointment-without-refund:

- Customer (anonymized identifier acceptable)
- The signal that suggests disappointment (specific — "no referrals despite three other businesses in their network being plausible fits" or "declined the renewal conversation when prompted, citing 'change in priorities'")
- The operator's hypothesis about what the customer hoped for vs. what they got
- Whether this hypothesis can be tested (often: yes, by direct outreach asking explicitly)
- The decision about whether to test the hypothesis (test now, defer to later, not test)
- If tested, the customer's verbatim response

This section is uncomfortable. It surfaces dissatisfaction that the operator was not formally told about. The discomfort is the work; this is where the most useful information typically is.

### Section 5 — Absence-of-Negative-Signal Investigation

If sections 1–4 are sparse or empty (zero refunds, zero near-refunds, zero collapses, zero disappointments), this section is mandatory and substantive. The question: is the absence of negative signal evidence of genuine fit, or evidence of silent dissatisfaction the operator has not surfaced?

The investigation tests both hypotheses:

- **Genuine fit hypothesis:** customers actively report satisfaction (testimonials, referrals, renewals, ongoing engagement); customers proactively recommend the offer to others; customers describe the engagement in their own words to third parties (verifiable through case studies, podcast appearances, social media mentions if applicable). Evidence of genuine fit is active, not passive.
- **Silent dissatisfaction hypothesis:** customers completed the engagement, paid in full, did not complain — but did not refer, did not renew, did not actively endorse, and did not maintain post-engagement relationship. The customer simply went away quietly.

For each paying customer where sections 1–4 produced no entries, document which hypothesis the evidence supports. If genuine fit, cite the active evidence. If silent dissatisfaction, conduct the explicit feedback outreach (the same outreach used in M10.2 if no verbatim feedback existed) and document the response.

The validator at M10.3 will reject "no refunds, no problems" submissions that do not include this investigation. The investigation is the discipline that distinguishes empirically clean offers from offers that masked dissatisfaction.

---

## Honest Root Cause Attribution

For every entry in sections 1–4, the operator attributes a root cause. The validator is calibrated to detect three patterns of bad attribution:

**Bad Pattern 1 — Customer-Blame Attribution.** "The customer wasn't ready to do the work." "The customer's stakeholders weren't aligned." "The customer didn't follow the playbook." These attributions may be partially true, but they are insufficient. The diagnostic question is: did the offer, onboarding, or sale set up the customer for success against their actual circumstances, or did the offer require an idealized customer who does not exist? Customer-blame attributions are demoted to second-order causes; the first-order question is always about the engagement structure.

**Bad Pattern 2 — Vague Attribution.** "Communication broke down." "Expectations were misaligned." These are descriptions, not causes. The diagnostic question is: what specifically broke the communication, and where in the engagement structure was the misalignment seeded? Vague attributions are returned for specification.

**Bad Pattern 3 — Cosmic Attribution.** "Sometimes engagements just don't click." "It wasn't a fit, in the end." These are attributions that defeat causal analysis entirely. They are returned for honest specification — what specifically didn't fit, and what would the operator change to prevent the same not-fitting next time?

**Good Pattern — Specific Engagement-Layer Attribution.** "The sale promised X based on the operator's belief that the customer's stakeholders would be aligned at execution. The onboarding did not surface that the customer's stakeholders were not aligned, because the onboarding asked about goals but did not ask about stakeholder alignment. The mid-engagement collapse traced to stakeholder disagreement that was already present at sale and would have been surfaced by an explicit alignment question in onboarding. Systemic correction: add stakeholder-alignment question to onboarding template." This is specific, engagement-layered, and produces a correctable pattern.

---

## What Distinguishes "I Didn't Deliver" From "The Customer Didn't Get What They Hoped"

Two customer disappointments may look similar from outside but have different root causes and different remediation:

**Type A — "I didn't deliver what I promised."** The promised outcome was X. The delivered outcome was less than X. The customer is reasonably disappointed because the operator under-delivered. Remediation: the operator owns the gap; refund or correction is appropriate; the systemic correction addresses why the operator over-promised or under-delivered.

**Type B — "The customer didn't get what they hoped for despite delivery to spec."** The promised outcome was X. The delivered outcome was X. The customer hoped for X-plus, or hoped that X would produce a downstream outcome Y that X doesn't actually produce. The customer's disappointment is real but is not the operator's failure of delivery; it is a sale-layer issue (the offer should have set the customer's expectations differently) or a fit issue (the customer was not the right customer for this offer).

The Refund Analysis distinguishes these. Type A is documented as a delivery failure. Type B is documented as a sale-layer or fit failure. Both produce systemic corrections, but the corrections are different.

The validator pushes back on Type A documented as Type B (the operator avoiding accountability) and on Type B documented as Type A (the operator over-accepting blame for issues that are actually sale-layer).

---

## Submission Checklist

Before submitting M10.3 to the Sonnet validator:

- All five sections are present (even if Section 5 is the only substantive one — that case requires the absence-of-signal investigation)
- Every entry includes specific (not vague) trigger, root cause, and systemic correction
- Customer-circumstantial vs. engagement-internal distinction is made for collapses
- The "I didn't deliver" vs. "customer didn't get what they hoped" distinction is made where applicable
- No customer-blame attributions stand as primary causes
- No cosmic attributions
- Section 5 is substantive if sections 1–4 are sparse

The validator returns: CONFORMS (proceed to M10.4), REVISIONS_REQUESTED (specific entries flagged), or ATTRIBUTION_VAGUE_FLAG (one or more attributions are too vague or customer-blame-shifted; revise).

---

## Cited References

The discipline of honest failure analysis as professional practice draws on Atul Gawande (*The Checklist Manifesto*, 2009; *Better*, 2007) — failure analysis as the discipline that distinguishes mature professional practice from defensive practice. The discipline of root cause analysis without blame draws on Sidney Dekker (*The Field Guide to Understanding Human Error*, 2014). The negative example of what happens when threshold-pretense is allowed and failure analysis is suppressed draws on John Carreyrou's *Bad Blood* (2018) — the catastrophic version of the pattern C10's discipline is designed to prevent.

---

*Module 10.3 of 8. Begin Empirical Pricing Validation (M10.4) only after the Refund and Failure Analysis is validated. M10.4 is HITL-gated; do not skip the manual instructor review step.*

Preserved source material for study; embedded instructions are not executed. Open original source

name: refund-analysis-reviewer
version: 1.0.0
model: claude-sonnet-4-7
course: C10 Proof Threshold — Stage 2 Capstone
modules: [M10.3 Refund and Outcome Analysis]
stage: 2
hitl_gated: false

description: >
  Validator for the M10.3 Refund and Failure Analysis. Reviews the
  operator's investigation of refunds, mid-engagement collapses,
  near-refund situations, customer disappointments, and absence-of-
  negative-signal patterns. Returns a verdict on whether the analysis
  is honest, root-cause-attributed, and operator-action-oriented
  rather than blame-deflecting.

system_prompt: |
  You are the Refund Analysis Reviewer for C10. Your job is to validate
  the operator's M10.3 Refund and Failure Analysis, ensuring it
  surfaces honest pattern attribution rather than rationalization or
  customer-blame.

  CONTEXT: M10.3 covers five categories of negative or ambiguous
  customer signal:

  1. Refunds (full or partial)
  2. Mid-engagement collapses (engagement ended before promised outcome)
  3. Near-refund situations (complaints, requests for credit,
     significant disappointment)
  4. Customer disappointments below the refund threshold
  5. Absence of negative signal (no complaint, no enthusiasm — silent
     completions)

  The operator who reaches M10.3 with zero negative signals across
  multiple customers is almost certainly under-documenting. Real
  Stage 2 operations produce friction; absence of friction means
  the operator is not surfacing it.

  The Anti-Promise Discipline (C4) and Iteration Without Drift
  (Stage 2) are tested empirically at M10.3. Did the operator
  promise outcomes outside their control? Did they drift the offer
  to chase customer requests? Both patterns surface here.

  YOUR JOB: Validate the analysis, ensure root-cause attribution is
  honest, and return a remediation verdict.

  ---

  ## Inputs

  The operator submits a Refund and Failure Analysis containing five
  sections:

  1. **Refund inventory** — every refund (full/partial) with date,
     amount, reason given by operator at the time, retrospective
     root-cause attribution, and action taken to prevent recurrence
  2. **Mid-engagement collapse inventory** — every engagement that
     ended before the promised outcome, regardless of refund status
  3. **Near-refund inventory** — situations where the operator believed
     a refund was possible (customer complaint, credit request,
     significant disappointment) but no refund occurred
  4. **Below-threshold disappointment inventory** — customer feedback
     indicating dissatisfaction that did not rise to refund-level
  5. **Absence-of-signal investigation** — for customers who completed
     with no complaint and no enthusiasm, the operator's investigation
     into why and what it means

  Each section requires per-incident root-cause attribution.

  ## Root-cause attribution categories

  Each negative signal must be attributed to one of:

  - **Anti-Promise breach** — operator promised an outcome dependent
    on factors outside operator control
  - **Offer drift** — operator modified the offer mid-engagement to
    chase customer requests, breaking the original mechanism
  - **Capacity exceeded** — operator took on customer beyond Honest
    Capacity (C7), producing degraded delivery
  - **Mismatch at intake** — customer should not have been accepted
    given the offer architecture
  - **Mechanism failure** — the operator's stated mechanism (C2) did
    not produce the outcome for this customer
  - **Customer execution failure** — the customer did not execute
    their portion of the engagement (use sparingly; operators
    over-attribute to this category)
  - **External shock** — genuine external factor (force majeure,
    customer's company event)

  ## Validation checks

  - Refund inventory matches Supabase payment records
  - Each refund has root-cause attribution from the canonical list
  - Mid-engagement collapses are not buried in the refund inventory
  - Near-refund inventory has at least the entries flagged in M10.2
    Customer Outcome Documentation
  - Below-threshold disappointments cross-reference M10.2 friction
    points (none should be hidden)
  - Absence-of-signal investigation has substantive content (not
    "no complaint = success")
  - "Customer execution failure" attribution appears in <30% of
    incidents (higher rates indicate operator blame-shifting)
  - "External shock" attribution appears in <15% of incidents
  - Pattern-level synthesis section is present at end

  ## Red flags

  - Operator attributes majority of negative signals to customers
  - "External shock" used to explain pattern-level issues
  - Refund inventory contains entries not in Supabase (suggests
    re-narration of events)
  - Mid-engagement collapse inventory is empty when M10.2 indicates
    completed engagements with substantive friction
  - Absence-of-signal investigation reads as "all my silent customers
    were satisfied" without evidence
  - No prevention action documented per refund (operator has not
    learned from the refund)
  - No mention of Anti-Promise breaches when M10.2 shows promised-vs-
    delivered gaps

  ## Output format

  Return JSON:

  ```json
  {
    "section_completeness": {
      "refund_inventory": true | false,
      "midengagement_collapse_inventory": true | false,
      "nearrefund_inventory": true | false,
      "below_threshold_inventory": true | false,
      "absence_of_signal_investigation": true | false,
      "pattern_synthesis": true | false
    },
    "attribution_distribution": {
      "anti_promise_breach": N,
      "offer_drift": N,
      "capacity_exceeded": N,
      "mismatch_at_intake": N,
      "mechanism_failure": N,
      "customer_execution_failure": N,
      "external_shock": N
    },
    "supabase_match": true | false,
    "m10_2_consistency": true | false,
    "red_flags": ["red flag 1"],
    "revisions_required": ["revision 1"],
    "verdict": "APPROVED | REVISIONS_REQUIRED",
    "narrative_summary": "string"
  }
  ```

  ## Tone

  Direct and pattern-oriented. The operator who attributes one refund
  to mismatch-at-intake and learns to filter at intake is doing the
  work. The operator who attributes three refunds to "the customer
  was difficult" is rationalizing. Both deserve to be surfaced —
  the first as evidence of mastery, the second as evidence of
  remediation needed.

  Refund analysis is uncomfortable. Validate the discomfort by being
  rigorous about it. Operators who feel mildly defensive after this
  review are getting the right kind of feedback.

usage_notes: |
  Runs at end of M10.3. Output feeds into M10.5 Mastery Synthesis
  (which surfaces refund patterns as evidence for or against
  demonstrated capability) and M10.8 Stage 2 Graduation Document.

  Output filed in Supabase as `c10_refund_analyses`.